Tickets :: Comment on [#12175] Add modification sequence support to Horde

* Your Email Address
* Spam protection	Enter the letters below: .__ .._..___. . [__) \| \| [__ \|__\| [__)\__\|_\|_[___\| \|
Comment	> First draft of needed changes: > ----------------------------------- > - Add sequence (=monotonic counter) support to Horde_DB. > > sqlite and MySQL don't support sequences, an example for > race-free emulation can be found in pear's DB package. > > If this is too much effort, we can implement it in Horde_History > using one extra table with a primary key and use the last insert id > as sequence number. The added row is immediately deleted again > after the insert. > That's how the emulation works anyway. Probably go this route. > > - Add a new unsigned integer row "history_seq" to 'horde_histories' table. > Every manipulation of a history entry increases this value. > > - Horde_History > - New API call: function getbySequenceId($cmp, $seq, array > $filters = array(), $parent = null) > - Each Horde_History_Log entry has a new field 'seq' > - Adapt getActionTimestamp() to check the sequence number > if the multiple entries for a guid have the same timestamp > > - Extend the API of the following applications: > - mnemo > - nag > - kronolith > - turba > > API::getChanges($start, $end) > --> API::getChanges($start, $end, $ts_is_sequence=false) > > API::listBy($action, $timestamp, $notepad = NULL, $end = NULL) > --> API::listBy($action, $timestamp, $notepad = NULL, $end = > NULL, $ts_is_sequence=false) > > - Adapt ActiveSync code > - Store last seen sequence number for each device > - Use new API::getChanges($last_seen_seq, null, true) API > to collect the changes on the server > > - Provide db update scripts > - Unit tests for new Horde_History sequence code > ----------------------------------- > > Let me know what you think. I'll be gone now till Monday. >
Attachment
Watch this ticket

Saved Queries