Tickets :: Comment on [#12600] Horde_History::getByModSeq() broken by design?

* Your Email Address
* Spam protection	Enter the letters below: .__.. ..___.. ,. . \| \|\|_/ \| \./ \|__\| \|__\|\| \ \| \| \| \|
Comment	>> Returning the most recent entry doesn't work because the query >> doesn't specify any order, so selectAssoc() will return whatever >> happens to be the last returned row. > > The function searches for unique object uids that changed during a > given modseq range. > So it's not important which row it returns. > > If we want to return the most recent row, we could add an "ORDER BY > modseq DESC" statement, though it's not currently not needed. The > user can use the getLatestEntry($object_uid) if really needed. > > Thanks for checking it in detail though! >
Attachment
Watch this ticket