[Zope-Checkins] CVS: Zope/doc - CHANGES.txt:1.625.2.167

[Chris McDonough]

Update of /cvs-repository/Zope/doc
In directory cvs.zope.org:/tmp/cvs-serv15549

Modified Files:
      Tag: Zope-2_7-branch
	CHANGES.txt 
Log Message:



=== Zope/doc/CHANGES.txt 1.625.2.166 => 1.625.2.167 ===
--- Zope/doc/CHANGES.txt:1.625.2.166	Sun May 23 00:52:09 2004
+++ Zope/doc/CHANGES.txt	Sun May 23 02:08:08 2004
@@ -123,6 +123,19 @@
        
     Bugs Fixed
 
+     - Collector #789: Zope's transaction behavior flawed.  Historically,
+       if an error bubbled up to Zope's publishing machinery, execution
+       of the error handler code would be performed in a context
+       that was essentially "between" two transactions.  This caused
+       problems for applications (like sessioning) which want to be able
+       to write to the database during an error message.  That need may sound
+       insane, but since the transaction is aborted after the error handler
+       has executed, it has the same effect as the "old" behavior inasmuch
+       as no inconsistent state will ever be committed to the database
+       as a result of this behavior unless someone really wants to shoot
+       themselves by calling "get_transaction().commit()" during error
+       handling code.
+
      - TransientObjects (session data objects) may have lost state at
        ZODB commit time after they were mutated via their __setitem__,
        __delitem__, update, or clear methods because they did not