Re: FetchSpecificationBatchIterator

Hi,

>The batch iterator works great except for one draw back. Currently if
>the batch size is set over around 300 then the JDBC query actually runs
>out of memory (something like more than 64 KB has been exceeded). I
>remember this wasn't the case in the 4.5 world, Oracle actually chokes
>for IN queries greater than 1,000 if I recall correctly. For my
>purposes batching groups of 250 eos is fine, but for other applications
>a larger batch size would be nice. Any suggestions?

250 records "should be enough for everyone"...

How about a qualifier making use of BETWEEN AND clause? I'd like to know
why EOF isn't using it for batch faulting. Maybe it is Plugins fault.

For integers it should be perfectly safe. At first I thought that this
would not be suitable for text keys, but no - if you fetch keys ordered by
the database - it will be equally safe also for text keys.

One thing more - your code doesn't check if the query didn't return less
rows than you were expecing. With any kind of range predicate in use the
situation where more rows than expected will get in is also possibe.

Regards,
Wojtek




-------------------------------------------------------
This SF.net email is sponsored by: ApacheCon, November 18-21 in
Las Vegas (supported by COMDEX), the only Apache event to be
fully supported by the ASF. http://www.apachecon.com