[Zodb-checkins] CVS: ZODB3 - NEWS.txt:1.33.6.43
Tim Peters
tim.one at comcast.net
Fri Aug 27 15:15:29 EDT 2004
Update of /cvs-repository/ZODB3
In directory cvs.zope.org:/tmp/cvs-serv20511
Modified Files:
Tag: Zope-2_7-branch
NEWS.txt
Log Message:
Spelling.
=== ZODB3/NEWS.txt 1.33.6.42 => 1.33.6.43 ===
--- ZODB3/NEWS.txt:1.33.6.42 Fri Aug 27 15:04:28 2004
+++ ZODB3/NEWS.txt Fri Aug 27 15:15:29 2004
@@ -10,8 +10,8 @@
a transaction that hasn't been abort()'ed or commit()'ed). Otherwise,
because Connection objects are reused from a pool, and retain their caches
across closing and (re)opening, opening a Connection could pick up data
-from a previous, "abandonned" transaction. In the worst case of this, if a
-subtransaction was abandonned, close+reopen could leave the subtransaction
+from a previous, "abandoned" transaction. In the worst case of this, if a
+subtransaction was abandoned, close+reopen could leave the subtransaction
changes in cache, but not reflected anywhere in a storage, and POSKeyErrors
could result. See Collector issue 789 for one nasty instance of this.
@@ -28,7 +28,7 @@
Connection) "join" transactions).
Avoiding the new exception should be easy: if you start a transaction,
-finish it (do a commit() or an abort() before closing any connections it
+finish it (do a commit() or an abort()) before closing any connections it
involves. If you see the new exception in "working" code, that code
was working by accident before.
More information about the Zodb-checkins
mailing list