Subsequent easter-egg troubleshooting has led us to set the prefetch size to
None for the problematic query. That fixed the problem FOR THAT QUERY. I
don't understand why, and I don't want to turn prefetching off for every
query, so I'm still troubled...
Another source said that including all selected columns in an order by
clause would work, but that didn't turn out to be true.
I won't bug the Webware list with this any more--and sorry again for an
off-topic post--I just want to close the loop from my first off-topic post.
Now I'm back to work on the spinning-thread issue.
Cheers!
--
David Hancock | dhancock@... | 410-266-4384
-----Original Message-----
From: Hancock, David (DHANCOCK) [mailto:DHANCOCK@...]
Sent: Tuesday, March 11, 2003 6:57 PM
To: webware-discuss@...
Subject: [Webware-discuss] Oracle/DCOracle/Python problem while using
Webware
First, sorry for the off-topic posting, but I'm trying several venues with
this question because it's becoming a larger problem. This is not a Webware
problem, nor probably a Python or even DCOracle2 problem, but it's biting us
in the backside in some of our applications.
We use Oracle and DCOracle2 as our DB API-2.0-compliant connector.
Unfortunately, we're occasionally getting erroneous NULLs returned for
columns when the result set is a bit larger than a few (we see the problem
when 140 rows are returned, but not when 5 are returned). For example, a
column might have character data: 'FreeText' in it, but when we get it back
from DCOracle2 its None (meaning NULL). Turning on an Oracle trace shows
that Oracle itself is returning the NULL, which seems like a Bad Thing To
Do.
Has anybody else encountered this? It shows up on a Zope mailing list, but
without any workaround suggested.
Again, sorry for the o/t posting--I'm a little desperate.
Cheers!
--
David Hancock | dhancock@... | 410-266-4384
|