[Tickets #12523] Re: AS: mix of unix timestamp and modseq breaks sync

[noreply at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/12523
------------------------------------------------------------------------------
  Ticket             | 12523
  Updated By         | Thomas Jarosch <thomas.jarosch at intra2net.com>
  Summary            | AS: mix of unix timestamp and modseq breaks sync
  Queue              | Synchronization
  Version            | Git master
  Type               | Bug
  State              | Assigned
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Thomas Jarosch <thomas.jarosch at intra2net.com> (2013-08-01 15:14) wrote:

> The question, then, is why does $change['mod'] contain a timestamp  
> in Horde_ActiveSync_State_Sql::updateState() and not the current  
> modseq value for that particular collection? It looks like the  
> problem is in Horde_Core_ActiveSync_Driver::changeMessage() we  
> unconditionally return the current time() as the mod value. We need  
> to poll the backend to find out if it supports modsequences and use  
> them, similar to what is done in the history related api calls.

yep, correct, I came to the same conclusion later on after dumping the  
activesync_map db table.

Next guess: It didn't cause a problem for you during development since
you migrated to modseq using the old timestamp values.