Hello,
Anthony Tuininga wrote:
> This is a known issue with cx_Oracle 4.0.1 which is resolved in 4.1
> but probably not the way you expect. :-) A programming exception is
> raised when this situation is detected rather than simply providing
> incorrect information. This is necessary because of the way that
> Oracle works.
By the way, a run under Purify noticed that the variable
var->internalFetchNum (used to check that the LOB variable is in sync
with the cursor) is not initialized.
This cannot produce any bug - this number is only incremented and
compared with previous values, so the initial value does not matter.
But I suggest that someone add the following line to the function
Variable_New in Variable.c
var->internalFetchNum=0;
--
Amaury Forgeot d'Arc
|
