[Zope-DB] DCOracle2 OracleDate and parameter sequence problem

[Christopher Jenkins]

"Matthew T. Kromer" wrote:
> 
> Christopher Jenkins wrote:
> 
> >Hi,
> >
> >I have recently started to use DCOracle2 beta5 (Oracle 9.0.1
> >on Sparc Solaris and Python 2.1.1) and have encountered
> >some strange problems when using OracleDate objects in
> >parameter sequences and either execute() or executemany()
> >
> 
> OK, I've fixed the problems you've reported in CVS.
> 
> Ken Mannheimer has directed all of my checkin messages to zope-db, of
> which I'm a bit dubious, but my suggestion of "dont send them anywhere"
> got shot down when someone complained about them showing up on the
> zope-checkins list.
> 
> Howls about the checkin messages to me in private, please...

Thank you very much for the prompt response.  This has fixed
the problem with OracleDate, but has uncovered a similar
problem with float types (despite the comment in my origional
message...).

If you have a table created by

create table t (n float);

Then from Python if you have a cursor object cur:-

>>> stmt="insert into t values (:1)"
>>> cur.execute(stmt, (None,))
4
>>> cur.execute(stmt, (1.0,))
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "DCOracle2.py", line 766, in execute
    result = self._cursor.execute()
dco2.DatabaseError: (1475, 'ORA-01475: must reparse cursor to change
bind variable datatype')

Note that in this case, the problem only manifests itself when the
inserts are performed in this order (None first) which is why I did
not pick it up earlier.

This problem does not seem to affect executemany().

I would very much appreciate your help with this issue.

Thanks again for all your help,

Chris