-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Unknown
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Usually, limit/skip feature goes hand in hand with sorting. Notice that we have two kinds of skip/limit info sources:
- HQL/Criteria
List<Call> calls1 = entityManager.createQuery( "select c " + "from Call c " + "join c.phone p " + "order by p.number " + "limit 50", Call.class) .getResultList(); // same thing List<Call> calls2 = entityManager.createQuery( "select c " + "from Call c " + "join c.phone p " + "order by p.number " + "fetch first 50 rows only", Call.class) .getResultList();
- QueryOptions's `setFirstResult()` and `setMaxResults()` methods
List<Person> persons = entityManager.createQuery("select p " + "from Person p " + "order by p.age ", Person.class). .setFirstResult(20) .setMaxResults(50) .getResultList();
We need to cover both cases.
It is possible that we'll need to use the jdbcParameterBindings parameter of the SelectMqlTranslator.translate method when working on this ticket.
Addressing the source code notes tagged with TODO-HIBERNATE-70 is in scope of this ticket.
- depends on
-
HIBERNATE-68 sorting MQL translation
-
- In Progress
-
- is related to
-
HIBERNATE-68 sorting MQL translation
-
- In Progress
-
- related to
-
HIBERNATE-68 sorting MQL translation
-
- In Progress
-