Hi,
I looked at it. The error is referring to the fact that the operations
on the connection are not yet complete. Since it is taking place on a
close() you can simply NOT do the close and allow it to close on its
own when it goes out of scope. There was a change made to
cursor.close() which may affect this but it seems unlikely. It would
be helpful if you can provide a script that demonstrates the problem
so that I can figure out why this might be happening. Thanks. I
certainly have never run into this myself and I am using Django with
cx_Oracle quite heavily.
Anthony
2011/8/25 Sławek Ehlert <sl...@gm...>:
> Hi there!
>
> Can You look at
>
> https://groups.google.com/d/topic/django-users/P9brNKIFwgI/discussion
>
> Recently I saw a similar problem when using cx_Oracle 5.1 when switching
> Django 1.3 (Python 2.6) to another Oracle database (after syncing it) on
> 64bit platform.
>
> Downgrading to 5.0.4 "solved" the problem.
>
> Regards
>
> Sławek
>
>
> ------------------------------------------------------------------------------
> EMC VNX: the world's simplest storage, starting under $10K
> The only unified storage solution that offers unified management
> Up to 160% more powerful than alternatives and 25% more efficient.
> Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
> _______________________________________________
> cx-oracle-users mailing list
> cx-...@li...
> https://lists.sourceforge.net/lists/listinfo/cx-oracle-users
>
>
|