Re: Out of Memory on Large ResultSets/Needed: SetFetchSize Method

[Jakob Braeuchi]

hi andreas,
yes this does not affect the memory footprint of the jdbc part but it 
prevents unused 'business' objects from being instantiated.

jakob
Andreas Bohnert schrieb:
hi jakob,
Jakob Braeuchi wrote:
hi all,
ojb supports proprietary start- and endIndex for queries. this 
solutions does not use fetch size or limit hints.

but this does not affect the way jdbc selects the results and the memory 
consumption on jdbc side is still the same.
or do I miss something?

regards,
andreas

jakob
Martin Kal�n schrieb:
Martin Kal�n wrote:
It might be possible to use fetch size 1 explicitly only for iterators,
I will have a look at this too.

This is a bigger refactoring since it affects internal statement 
creation
and would need many internal methods' signature to be expanded with a 
flag
and/or explicit size for fetch size hints.

I will bring the discussion up on the dev-list pointing to this thread
and see what concensus is with respect to memory footpring vs network
traffic/JDBC overhead.
Regards,
 Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]