How does Enterprise Replication do timestamp conflict resolution?
On 26th September 2001 mpruet@home.com (Madison Pruet) wrote:- There seems to be a bit of confusion with what ER uses for timestamp conflict resolution. It uses the output of time() which is defined as “time in seconds since 00:00:00 UDT, January 1, 1907”. It is not timezone sensitive or daylight time sensitive. In order to get the local time (which is timezone/daylight sensitive) you must call localtime(). There is no problem replicating across multiple time zones, or between time zones where one is in daylight savings and the other is not. There are many folks doing that now. There was a problem with NT a few years ago because VC++ 4.0 was not calculating time values correctly. The main reason for this is because Micorsoft maintains the time using the local time as the base instead of GMT time. This adds a bit of complexity to date calculation that they were mis-handling in the libc routines. The net result was that time() returned a value about 6 hours off for those time zones that
