Summary | support sort option for RDO objects |
Queue | Horde Framework Packages |
Type | Enhancement |
State | Accepted |
Priority | 1. Low |
Owners | |
Requester | birnbacs (at) gmail (dot) com |
Created | 2018-02-19 (1114 days ago) |
Due | 02/28/2018 (1105 days ago) |
Updated | 2018-03-02 (1103 days ago) |
Assigned | |
Resolved | |
Milestone | |
Patch | No |
Type ⇒ Enhancement
State ⇒ New
Priority ⇒ 1. Low
Summary ⇒ support sort option for RDO objects
Due ⇒ 2018-02-28
Queue ⇒ Horde Framework Packages
Milestone ⇒
Patch ⇒ No
makes access easy. With a ONE:MANY relationship between data types A
and B, accessing a B from a given A is as easy as A->B[i].
In some cases it is desirable to have the returned multitude of B
objects in a predetermined order. For instance, elements B might each
have an element x and A->B could return the collection of elements B
sorted by x in descending order:
A->B[0]->x > A->B[1]->x > A->B[2]->x ...
Ralf Lang suggested in the dev mailinglist that this could be
implemented through the mapper or in the Rdo_Query object. He details
that eager relations are implemented as joins while lazy relations are
essentially an automated way to implement the above. So the requested
feature would require two implementations.
It seems to me that in both variants the sorting should be done on the
DB side to avoid unnecessary overhead.