Reid....
I'm assuming your question is how to get around the where clause size errors?
Option One:
Since I'm loading the items for the where clause in a scalar array (e.g. @Items), I
compare the number of entries in the array to 50. (e.g. if (50 < $#Items)) If less
than, run as normal, if more I take the first fifty entries build the where clause,
store the results in an array. Then compare the total number of items minus 50 to 50
(e.g. if (50 < ($#Items - 50)) and build new where clause, append to result array. I
continue until $#Items is less than 50.
Its very inefficent but works for most of what I need.
Option Two: (If my where clauses are just too damn big.)
I have a table called session. Before I begin work I create a unique session ID based
upon PID of the perl process, time in seconds and a random alpha/number. I then take
all the items that would be in the where clause and dump them into the session table
along with the session id. (e.g. Session Id, Item - repeat) Then I create a join
between the two tables comparing the Item in the Session table to the Item in the
Target Table. The inefficencies here are in Inserting all the Items to the session
table prior to creating a Select/Join Query and then deleting the Data from the
session table.
--
Anthony Baratta
President
KeyBoard Jockeys
South Park Speaks Version 3 is here!!!
http://www.baratta.com/southpark
Powered by Tsunami
-------------------------------------------------------------------------
To unsubscribe, go to http://www.Hughes.com.au/extras/email/
This archive was generated by hypermail 2b30 : Mon Mar 04 2002 - 09:03:52 EST