--On 30. Oktober 2005 22:17:44 -0500 Tim Peters <[EMAIL PROTECTED]> wrote:
Second, time-stamp skew doesn't lead to inconsistency.
Fleshing out a bit, ZODB uses time.gmtime() as a starting point, not
necessarily as its final timestamp. When generating a new tid, if
time.gmtime() is <= the l
[Andreas Jung]
>> Possibly a stupid question:
Nope, it's a good question!
>> Last night the European clocks switched back to winter-time. So the
>> ZODB might see multiple timestamps (and unordered transaction) from
>> transactions happened between 2am and 3am...just for curiosity: is
>> there a
Andreas Jung wrote:
Possibly a stupid question:
Last night the European clocks switched back to winter-time.
So the ZODB might see multiple timestamps (and unordered transaction)
from transactions happened between 2am and 3am...just for curiosity: is
there a risk getting an inconsistent ZODB?
Possibly a stupid question:
Last night the European clocks switched back to winter-time.
So the ZODB might see multiple timestamps (and unordered transaction) from
transactions happened between 2am and 3am...just for curiosity: is there a
risk getting an inconsistent ZODB?
Andreas
pgp2eIOfcTL
