On Tue, Jun 16, 2009 at 1:58 PM, Joe Baldwin wrote:
> That sounds logical. So if I limit my sort ordering to the initial query
> then the objects in pages 2-n will remain hollow?
>
> (I have a few instances in which there is sort ordering by the client (which
> is post query - resultset ordering).
2009/6/16 Joe Baldwin
> That sounds logical. So if I limit my sort ordering to the initial query
> then the objects in pages 2-n will remain hollow?
>
Yes. Adding an ordering leads to ORDER BY statements in generated SQL, so
all the processing remains the same.
That sounds logical. So if I limit my sort ordering to the initial
query then the objects in pages 2-n will remain hollow?
(I have a few instances in which there is sort ordering by the client
(which is post query - resultset ordering). I will have to take a
look at this design to impleme
The trick of paginated query is that all objects returned are HOLLOW, thus
having only identifier. Ordering.orderList will surely resolve *all*
records, how else would it know parameters of each object. To order a long
list properly you need to set ordering to a query:
query.setPageSize(RowsPerPag
This is a question concerning making performance enhancements with
Cayenne directives.
Lets say you use the following SelectQuery method
query.setPageSize(RowsPerPage);
But then you decide to sort order the result list using
Ordering order = new Ordering(._PROPERTY, true);
