[Tickets #13868] Re: Changes made in kronolith are not send to AS devices.

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: https://bugs.horde.org/ticket/13868
------------------------------------------------------------------------------
  Ticket             | 13868
  Updated By         | horde at vdorst.com
  Summary            | Changes made in kronolith are not send to AS devices.
  Queue              | Synchronization
  Version            | FRAMEWORK_5_2
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
+New Attachment     | horde_histories.png
------------------------------------------------------------------------------


horde at vdorst.com (2015-02-26 11:43) wrote:

I was looking in the database table "horde_histories".
So every change in contacts, calender and tasks are logged in  
"horde_histories" right?

- I was wondering if "history_modseq" should allways increased or can  
it reset? And when will it reset? See upper picture of the table where  
history_id gets async with history_modseq.

- high "history_modseq" is related to the lasted modification? See  
lower picture of the table where history_ts is sorted min to max.  
Where I can see that the highest history_ts is not allways the lasted  
history_id. Is this correct?


Can I empty horde_histories to start over without any consequence?





horde at vdorst.com (2015-02-26 11:43) uploaded: horde_histories.png

https://bugs.horde.org/h/services/download/?app=whups&actionID=download_file&file=horde_histories.png&ticket=13868&fn=%2Fhorde_histories.png