[GLASSFISH-4887] Support for SQL LIMIT / OFFSET with setMaxResults() / setFirstResult() Created: 24/Apr/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: entity-persistence
Affects Version/s: 9.0peur1
Fix Version/s: not determined

Type: Improvement Priority: Blocker
Reporter: batzee Assignee: tware
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 4,887

 Description   

Almost all web applications use pagination to split large tables into pages with
a relatively small number of rows each. In Toplink Essentials, setFirstResult()
and setMaxResults() can be used to achieve this.

At least for PostgreSQL and MySQL, and most likely for other RDBMs, a lot of I/O
effort can be saved by using the LIMIT and OFFSET sql clauses. Toplink
Essentials really should use it!!

(Hibernate has been doing this for a long time!!)



 Comments   
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk change to set fix version to "not determined" where the issue is open but the value is for a released version.

Generated at Thu Apr 02 03:56:20 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.