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

* Your Email Address
* Spam protection	Enter the letters below: .__..___.__..___..___ \| \|[__ [__] _/ [__ \|__\|[___\| \|./__.[___
Comment	> While tracking down failed History tests on Postgres, I noticed some > strange, at least undefined behavior of getMyModSeq(). Is it supposed > to return all history IDs of changed during the modseq sequence, or > only the most recent? It does neither, currently. And the docs are > confusing: "@return array An array of history object ids" > Returning all entries doesn't work because the returned hash is keyed > by object IDs, so it will only return at most one entry per object. > 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.
Attachment
Watch this ticket