Tickets :: Comment on [#14368] Improve EAS performance with large History tables

* Your Email Address
* Spam protection	Enter the letters below: . .. .. ,. . , \|__\|\| \| \./ \| \./ \| \|\|__\| \| \|___ \|
Comment	> Ok, this should do it. If there is a large difference in the last > and current syncStamp, we now update the state with the new value > (only implemented in the Sql state driver, not the Mongo driver). > > It should be noted that this is only an issue when the client and/or > user is multiplexing all collections and not using separate > collections for each calendar/addressbook etc... In that case, the > modseq is tracked for the individual collection, so there would never > be that large of a difference in syncstamps unless the client was > turned off for years....
Attachment
Watch this ticket