[Zodb-checkins] SVN: ZODB/trunk/src/ZODB/tests/testfsoids.py
Changed the msg generated when an oid isn't found.
Tim Peters
tim.one at comcast.net
Tue Aug 31 19:53:45 EDT 2004
Log message for revision 27377:
Changed the msg generated when an oid isn't found.
Changed:
U ZODB/trunk/src/ZODB/tests/testfsoids.py
-=-
Modified: ZODB/trunk/src/ZODB/tests/testfsoids.py
===================================================================
--- ZODB/trunk/src/ZODB/tests/testfsoids.py 2004-08-31 23:51:07 UTC (rev 27376)
+++ ZODB/trunk/src/ZODB/tests/testfsoids.py 2004-08-31 23:53:45 UTC (rev 27377)
@@ -44,11 +44,11 @@
>>> t.run()
>>> t.report()
oid 0x00 <unknown> 0 revisions
- this oid was neither defined nor referenced
+ this oid was not defined (no data record for it found)
oid 0x01 <unknown> 0 revisions
- this oid was neither defined nor referenced
+ this oid was not defined (no data record for it found)
oid 0x123456 <unknown> 0 revisions
- this oid was neither defined nor referenced
+ this oid was not defined (no data record for it found)
That didn't tell us much, but does show that the specified oids are sorted
into increasing order.
@@ -65,7 +65,7 @@
tid description='initial database creation'
new revision persistent.mapping.PersistentMapping at 52
oid 0x01 <unknown> 0 revisions
- this oid was neither defined nor referenced
+ this oid was not defined (no data record for it found)
So we see oid 0 has been used in our one transaction, and that it was created
there, and is a PersistentMapping. 4 is the file offset to the start of the
@@ -151,7 +151,7 @@
new revision BTrees._OOBTree.OOBTree at 491
references 0x00 <unknown> at 491
oid 0x02 <unknown> 0 revisions
- this oid was neither defined nor referenced
+ this oid was not defined (no data record for it found)
Note that we didn't create any new object there (oid 2 is still unused), we
just made oid 1 refer to oid 0. Therefore there's a new "new revision" line
More information about the Zodb-checkins
mailing list