[OGo-Developer] Re: additional field for synchronizatin
Wolfgang Sourdeau
developer@opengroupware.org
Thu, 23 Aug 2007 15:41:38 -0400
> I do not really like that the change states are stored in the table
> instead of a proper transaction table, but its probably the pragmatic
> thing to do.
> (querying c_lastmodified (a date) is highly unreliable given that you
> can have hundreds of updates in a second - which is extremely common
> especially during synchronizations - which is why there are SyncML
> anchors ...)
Yes, you can have hundreds of updates in a second, but you'd have to
be a cyborg to be able to do it on the same single event that belongs to you...
the c_lastmodified and the c_deleted fields are per-event. Not per update.
W.