[Zope-DB] Re: Weird DCOracle2 Error

Matthew T. Kromer matt at bane.mi.org
Thu Nov 4 21:46:55 EST 2004

Yes, I actually thought it was fixed in the source...  There are times 
when the OCINumber field is not initialized properly I think when the 
indicator of a row was turned on, when doing a subsequent fetch.  What 
I recall is that a fetch of a NULL number followed by a fetch of a real 
number would glitch on the second fetch, because the setup would skip 
that field thinking it was already initialized (but it wasn't).

Its been a while since I've poked at that code, as I recall it was 
simple to fix, but it may have been I only sent a patch to someone 
because I didnt have CVS commit privileges.

On Nov 4, 2004, at 8:02 AM, Chris Withers wrote:

> Hi Matt,
> Have you ever seen anything like this:
> Module Shared.DC.ZRDB.DA, line 454, in __call__
> - <SQL instance at b69132f0>
> Module Products.ZOracleDA.db, line 183, in query
> Module Products.ZOracleDA.DCOracle2.DCOracle2, line 1223, in fetchmany 
> Module Products.ZOracleDA.DCOracle2.DCOracle2, line 1190, in 
> fetchoneDatabaseError: (22060, 'OCI-22060: argument [2] is an invalid 
> or uninitialized number')
> Even if you haven't (;-)) what would be the correct way to go about 
> fixing the problem?
> (it is, of course, an intermittent problem, which I can't reliably 
> reproduce ;-) )
> cheers,
> Chris
> -- 
> Simplistix - Content Management, Zope & Python Consulting
>            - http://www.simplistix.co.uk

More information about the Zope-DB mailing list