sure. and WITH witango it works usually. Interesting thing is that
when it crashes, it does so only on the first hit of a record. You
can pound on the record to see if it will crash again, and it won't.
The records that are associated with crashes are not out of the
ordinary at all and have nothing in common. The crashed thread is
always the same - exactly the same.
On Nov 19, 2005, at 3:20 PM, William M Conlon wrote:
Can you execute the problematic query directly against your db,
without witango?
On Nov 19, 2005, at 2:41 PM, Roland Dumas wrote:
and it crashes witango still...... this is befuddling....
On Nov 19, 2005, at 11:35 AM, Roland Dumas wrote:
I've changed from witango generated sql to a direct dbms. Also
changed column from tinytext to varchar. I'll know if that
resolved the issue the next time a batch of orders is processed.
Thanks for all the ideas, folks.
On Nov 18, 2005, at 11:18 AM, Robert Shubert wrote:
I would definitely try a directdbms in that case, get away from
the SQL generator. The NULL could be an issue. Personally I’m in
the habit of making flags that contain a 0 or a 1 and block the
NULL case. It’s entirely possible that there’s some glitch in
dealing with the NULL column.
On other thing would be to trace the DB. You’d like to know if
the SQL statement is getting to the SQL server or not.
Robert
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
