[Zodb-checkins] CVS: ZODB3 - NEWS.txt:1.33.6.80

[Tim Peters]

Update of /cvs-repository/ZODB3
In directory cvs.zope.org:/tmp/cvs-serv13892

Modified Files:
      Tag: Zope-2_7-branch
	NEWS.txt 
Log Message:
referencesf():  Use %r instead of %s format in the error message, else
the pickle shown is full of unprintable characters.


=== ZODB3/NEWS.txt 1.33.6.79 => 1.33.6.80 ===
--- ZODB3/NEWS.txt:1.33.6.79	Mon May  2 16:30:26 2005
+++ ZODB3/NEWS.txt	Thu Jun  2 17:24:43 2005
@@ -6,20 +6,27 @@
 ---------------
 
 Doing a subtransaction commit erroneously processed invalidations, which could
-lead to an inconsistent view of the database.  For example, let T be the 
-transaction of which the subtransaction commit was a part.  If T read a 
-persistent object O's state before the subtransaction commit, did not commit 
-new state of its own for O during its subtransaction commit, and O was 
+lead to an inconsistent view of the database.  For example, let T be the
+transaction of which the subtransaction commit was a part.  If T read a
+persistent object O's state before the subtransaction commit, did not commit
+new state of its own for O during its subtransaction commit, and O was
 modified before the subtransaction commit by a different transaction, then the
-subtransaction commit processed an invalidation for O, and the state T read 
-for O originally was discarded in T.  If T went on to access O again, it saw 
+subtransaction commit processed an invalidation for O, and the state T read
+for O originally was discarded in T.  If T went on to access O again, it saw
 the newly committed (by a different transaction) state for O::
 
     o_attr = O.some_attribute
     get_transaction().commit(True)
     assert o_attr == O.some_attribute
 
-could fail, and despite that T never modifed O.
+could fail, and despite that T never modified O.
+
+Error reporting
+---------------
+
+- In the unlikely event that ``referencesf()`` reports an unpickling error
+  (for example, a corrupt database can cause this), the message it
+  produces no longer contains unprintable characters.
 
 
 What's new in ZODB3 3.2.8?