Hi,

I know this is a recurrent topic but I cannot get it clear into my mind.
The different ways for managing very large result sets seems to be the
following: 

1) Using getStartAtIndex() and getEndAtIndex(): this sounds like an
efficient way but if I look into the DB log there's no LIMIT option in
the SQL query! This is really surprising isn't it? I guess that only the
records whose ID respect the specified range are materialized, but what
about the DB load?

2) Using getIteratorByQuery() which could avoid to materialize all the
resulting objects. This is good, but getStartAtIndex() and
getEndAtIndex() seems to NOT work with it (only with
getCollectionByQuery). Could someone confirm this?

3) Using proxies: the lazy loading looks interesting but I cannot figure
out the difference with iterators. Maybe is it the same mechanism as
iterators but adapted for auto-retrieval?

Thanks..

Vincent




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

Reply via email to