It looks like the FileStorage getTid implementation is broken. This was revealed by running the old getSerial tests against getTid. File storage's getTid incorrectly returns a serial for an object who's creation transaction has been undone. I think this is a bug that I can easily fix. Heck, there's already a test for it. :)
I'm just sharing here in case someone who worked on this before has any reason to think my analysis is incorrect. :)
Everyone else is free to ignore this. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org _______________________________________________ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org http://mail.zope.org/mailman/listinfo/zodb-dev
