Re: CDR and timestamps

AS I understand it, CDR is now ER (Enterprise replication) and there are 3 primary ways to detect and resolve conflicts arising out of same row updates on two replicated servers. If timestamp is the primary resolution method, then the timestamps, converted to GMT are compared. All time computations are performed internally in GMT and have an accuracy of + - 1 sec. Note that, time synchronization between servers is not Informix responsibility, so for this to work, the two servers must have their clock synced by other means. Also, you can chose to apply conflict resolution on a row by row basis or on the entire transaction. I hope this helps. Sunil ___________________________________________ From: "Juan R. Guzman" <jguzman@transre.com> Message-Id: <331304DE.61AD@transre.com> Subject: Re: CDR and timestamps Date: Tue, 25 Feb 1997 15:27:26 GMT Reply-To: jguzman@transre.com Organization: Transatlantic Reinsurance Co. Sender: informix-list-owner@rmy.emory.edu To: informix-list@rmy.emory.edu _____________________________________________________________ Joel Vannorsdel wrote: > Usually the manner that this is controlled is by having a GMT offset on > each machine that is participating in replication. This way each > machine can provide the time corrected to GMT on an individual. Also > the time of an update usually does not affect other data. In the case > of an update to an existing row, how often would you have two different > users updating the same row at the same time. yes, rarely do users update the same row at the same time. But it is possible and if Informix hasn't resolved the issue then we're looking at two outcomes. 1) Informix Online didn't know what to do with the updates so it brought down CDR (best case scenario) or 2) It didn't know what to do with the updates but didn't bring down CDR so your data is now invalid and you don't know it (I've lived thru something similar in HDR with 7.11UC1). Either way I'm not happy. Any input from Informix people would be nice. thanks,