Re: massive performance problem with q.setStartAtIndex() and q.setEndAtIndex()
Armin Waibel <[email protected]>
| Newsgroups | gmane.comp.jakarta.ojb.user |
|---|---|
| Message-ID | <[email protected]> |
Hi Björn, (sorry for the late replay, googlemail marked you as spam) in upcoming OJB 1.0.5 native limit/offset will be supported for most popular databases and can be easily implemented for all databases. See also: http://marc.info/?l=ojb-user&m=117320896526677&w=2 regards, Armin Björn Agel wrote: > hi there, > > i figured out a performance problem with large tables using > q.setStartAtIndex() and q.setEndAtIndex() > there are more than 100.000 entries in the table and a simple search > which should return about 90.000 items still takes more than 10(!) seconds. > i am using the index methods to retrieve only 10 datasets per query out > of these 90.000 total items using an iterator. > > when i implement the same query directly as a sql command like: > "SELECT * FROM user WHERE name LIKE '%name%' LIMIT 50000,10" > the query takes less than 1 second ... > > am i doing something wrong or is it a bug ? > > with best regards, > Björn > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >