cayenne-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrus Adamchik (JIRA)" <>
Subject [jira] [Commented] (CAY-2092) Exception for query that uses pagination and sorting on to-many
Date Wed, 20 Mar 2019 05:39:00 GMT


Andrus Adamchik commented on CAY-2092:

> Why does it not make sense to order before pagination? 
It does make sense in a general case of course. Here I was talking about very specific case
- ordering on a to-many relationship. E.g. you are fetching Artists, but ordering on Artist's
"" property. This seems valid, but not very useful, no?

> Exception for query that uses pagination and sorting on to-many
> ---------------------------------------------------------------
>                 Key: CAY-2092
>                 URL:
>             Project: Cayenne
>          Issue Type: Bug
>    Affects Versions: 4.0.M3
>            Reporter: Andrus Adamchik
>            Priority: Minor
> Somehow we haven't seen this reported before, perhaps because the combination makes no
practical sense. I was able to find it during regression testing of a LinkRest app that translates
REST calls to Cayenne SelectQueries. Anyways, a query that uses pagination and also ordering
on a property of a to-many relationship (the ordering part doesn't make sense) ends up generating
the following exception, even though all the data is there:
> org.apache.cayenne.CayenneRuntimeException: [v.4.0.M3 Feb 08 2016 16:38:05] Some ObjectIds
are missing from the database. Expected 62, fetched 31
> 	at org.apache.cayenne.access.IncrementalFaultList.checkPageResultConsistency(
> 	at org.apache.cayenne.access.IncrementalFaultList.resolveInterval(
> 	at org.apache.cayenne.access.IncrementalFaultList.get(
> 	at

This message was sent by Atlassian JIRA

View raw message