<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>support sort option for RDO objects</title> 
  <pubDate>Sat, 04 Apr 2026 06:36:03 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/14782</link> 
  <atom:link rel="self" type="application/rss+xml" title="support sort option for RDO objects" href="https://bugs.horde.org/ticket/14782/rss" /> 
  <description>support sort option for RDO objects</description> 
 
   
   
  <item> 
   <title>Horde RDO permits to define relationships over different db </title> 
   <description>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-&gt;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-&gt;B could return the collection of elements B sorted by x in descending order:

A-&gt;B[0]-&gt;x &gt; A-&gt;B[1]-&gt;x &gt; A-&gt;B[2]-&gt;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.</description> 
   <pubDate>Mon, 19 Feb 2018 07:40:50 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/14782#t92740</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
