[Zope-DB] Problem with DCOracle2 null's

[Matthew T. Kromer]

If you're doing this on NT, you *may* be running into problems with the 
NATIVENUMERIC define. It should be -DNATIVENUMERIC=1, but you might have 
to set that in the project. If thats turned on, it will use newer Oracle 
calls to deal with numbers rather than coercing everything as strings.


Gilberto Pereira wrote:

> Hello DCOracle2 users...
>
> Since I upgraded the dco2.c library from the CVS version (because of 
> the memory leak problem), I’m having problems when trying to get 
> values from columns of the type number when all the values are null.
> Every select returns either junk or the following error:
> OCI-22060: argument [2] is an invalid or unitialized number
>
> I’ve returned to my old version (dco2.c, v1.129), and it’s working 
> fine with this kind of selects. But recently I've noticed the same 
> problem reported by Jerry (DCOracle2 query return null value column), 
> and the solution suggested by Matthew means using the last CVS version.
>
> Is anybody else getting this error, or have I done something wrong 
> compiling the library?
>
> I'm using Zope 2.6.1 or 2.5.1 on WinXP, Python 2.1.3, with Oracle 8.1.7
> I’ve compiled the dco2.c v1.136 with the DCO2NT build for MS VC++ 6.0 
> with some warnings, but without problems
>
> Regards,
>
> Gil
>
>
> _______________________________________________
> Zope-DB mailing list
> Zope-DB at zope.org
> http://mail.zope.org/mailman/listinfo/zope-d
> b



-- 
Matt Kromer
Zope Corporation  http://www.zope.com/