Re: Whatcha' wanta have?????

Serge Rielau wrote: >> > I think for this requirement scrollable cursors are the right answer. > What happens there is that the resultset gets materialized on the > server and the client can then browse through it by position. > This allows the server to only materialzie to the current high > watermark, without having to redo the work for the next request, as it > would have to do with a pure SQL solution which would resubmit similar > statements over and over again. > (Scrollable cursor scan do other nifty things like optimistic locked > etc..) But when it's based on discrete statements, when does the engine know it's ok to discard the result set? Or will it be dependent on the same prepared cursor being used each time?