[Tickets #14782] support sort option for RDO objects

[email protected]
Newsgroups gmane.comp.horde.bugs
Message-ID <[email protected]>
BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: https://bugs.horde.org/ticket/14782
------------------------------------------------------------------------------
  Ticket           | 14782
  Erstellt Von     | [email protected]
  Zusammenfassung  | support sort option for RDO objects
  Warteschlange    | Horde Framework Packages
  Typ              | Enhancement
  Status           | New
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


[email protected] (2018-02-19 07:40) hat geschrieben:

Horde RDO permits to define relationships over different db tables and  
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.



-- 
bugs mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.