Re: [cx-oracle-users] Crash of OCIStmtRelease during cursor.close()

[Anthony T. <ant...@gm...>]

On Thu, Nov 4, 2010 at 11:53 AM,  <Gui...@su...> wrote:
> Ok, that seems kind of consistent with what I meant to try out.
> After you told me not to call close() explicitly, I commented the line out, but just to make sure the destructor was in fact being called I used the C/Python function Py_CLEAR(cursor), which decrements the number of handles on the cursor AND sets it to NULL afterwards.
>
> But tell me this: when the cursor actually goes out of scope and its automatically closed, won't it be cursor_close() which will be called when cursor is destroyed? If not, what will?

There is an internal method Cursor_FreeHandle() which is called.
Cursor_Free() does not directly call Cursor_Close() so they are not
the same thing.

> I meant to test this today but couldn't so I will tomorrow. You'll be first to know the outcome.

Thanks.

> Thank you very much,

You're welcome.

Anthony