Woah. I was under the impression that internally it's doing what's optimal
by considering what database is being used. I noticed the "i believe" in
your post. Can you please confirm this? If so, do future releases of IBatis
plan on considering the database when using PaginatedList. It doesn't seem
like it should be too difficult.
Zarar
----- Original Message -----
From: "Niels Beekman" <[EMAIL PROTECTED]>
To: <user-java@ibatis.apache.org>
Sent: Thursday, November 03, 2005 10:07 AM
Subject: RE: paginated list
It doesn't, it just skips results in the ResultSet I believe. If you
want to get optimal performance, roll your own implementation of paging
and use the LIMIT/OFFSET statements, however, it won't be
database-independent.
Niels
-----Original Message-----
From: Eugeny N Dzhurinsky [mailto:[EMAIL PROTECTED]
Sent: donderdag 3 november 2005 16:04
To: user-java@ibatis.apache.org
Subject: paginated list
Can somebody please explain how this work? I need to show results from
some
table, i'm using limit/offset statements in SQL query, but I saw iBATIS
can
handle pages in result set somehow, so I might not be forced to add
limit/offset statements in the SQL clauses. But I'm wandering how does
iBATIS
handles various databases (in postgresql statement must ends with limit
N
offset M whicle in MySQL syntax is limit N,M).
--
Eugene N Dzhurinsky
