Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> How does a cursor get closed?
How does a cursor get closed?
According to other documents on metalink, the
close_cached_open_cursors parameter (which has been made an undocumented
parameter
in 8i) defaults to false, which means that
cursors are held open across commits and rollbacks. I guess my
question is, how do they get closed? I am interested in whether I should
look into setting session_cached_cursors for certain jdbc activity
that the developers are doing. From what I understand, this is helpful
in
forms, because as a user switches from one form to another, the old
cursors will get closed. By what mechanism do cursors actually close,
and also why does this happen with forms? If I'm not using forms, then
how does a cursor get closed? If it's just an LRU kind of thing, then
what am I gaining with session_Cached_cursors that I couldn't accomplish
with just bumping up open_cursors?
Thanks,
Dc.
Sent via Deja.com http://www.deja.com/
Before you buy.
Received on Tue Sep 05 2000 - 14:45:33 CDT