Oleg Nitz wrote:
> Dave Smith wrote:
>
>>Keep the result set open, retieve from the set as necessary, probably
>>using a cursor. That way if someone is doing a search that has 1 million
>>records and after I display the first 10 and the client chooses the 3rd
>>one, we have only created 10 objects.
>>
> No, no, no! We can't keep the result set open!
> 1) having open result set and open Connection for each client,
> we'll end up with too many open connections and too many open result
> sets (256 open cursors by default in Oracle).
Well then use limit and offset, but a cursor will be more efficient. I
think what you have done is fine as the default case, so I see this
fuctionality as an *option* not the default. Currently it is only doing
searches that I would want this functionallity not anywhere else.
> 2) How about transaction bounds? Can you keep cursor open after
> transaction ends? I don't think so.
>
As stated previously this case has to be read-only, and would have to
live within it's own transaction, or you are stuck with limit and offset.
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
