People did report this bug elsewhere on the list. Apparently we're waiting until monday when Jim Fulton can take a look at this. They're pretty sure it's just a display problem and not something wrong with the object database, but they want to make sure and check with Jim.
Hi. How's Jim getting on with this? Apologies if I missed something on the list.
He has checked in the fix - if you are tracking CVS you need to update lib/python/ZODB/TimeStamp.c and rebuild it. For those not using CVS, I've attached a copy of the updated file to this email (but you'll still have to rebuild the extension for the change to take effect). Brian Lloyd brian@digicool.com Software Engineer 540.371.6909 Digital Creations http://www.digicool.com