db-torque-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thoralf Rickert" <thoralf.rick...@cadooz.de>
Subject AW: CriteriaEnumeration
Date Mon, 12 Mar 2007 15:58:32 GMT
Hi Thomas,

Yes, you're right. It's similar to LargeSelect. But I think, it has two
advantages. With the correct combination of Criteria and
CriteriaPopulator I'm able to use doSelectJoinXXX and construct multiple
Torque objects at the same time (in my example this could be a store and
the corresponding address). The second advantage is, that it implements
the Enumeration interface and my opinion is, that this is more

On the other side, the read-ahead-cache seems to be very useful and
could speed up some operations. It's more aware of DB specific problems
with databases that doesn't understand the offset/limit feature.

> This is more or less what LargeSelect does. I used to use it 
> for such things - reading data one page at a time. It 
> provides the additional advantage of a "read-ahead-cache", 
> means it continues reading your data in the background while 
> you can process the first page of records.

> If you are interested, I created a small LargeSelectHelper 
> class which allows you to continuously read one page at a 
> time and let LargeSelect do the "chunking".

Sorry, I'm not sure, what you mean?  Do you think, it would be better
for the CriteriaEnumeration to work with the LargeSelect?


To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org

View raw message