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

* Your Email Address
* Spam protection	Enter the letters below: .__..___..___. ..__. \| \| \| [__ \| \|[__] \|__\| \| \| \|/\\|\| \|
Comment	>> 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. >
Attachment
Watch this ticket