From: Mike Bayer <mike_mp@zzzcomputing.com>
Date: Thu, 12 Jun 2008 20:29:13 +0000 (+0000)
Subject: updated verbiage for 0.5beta1 release
X-Git-Tag: rel_0_5beta1
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=d3fb8ff9044b6dcaec7a983ecb99498a5669e9de;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git

updated verbiage for 0.5beta1 release
---

diff --git a/CHANGES b/CHANGES
index 1b7255e9d3..5441a14707 100644
--- a/CHANGES
+++ b/CHANGES
@@ -4,8 +4,14 @@
 CHANGES
 =======
 
-user_defined_state
+0.5beta1
 ==================
+    - An ongoing document describing the changes from 0.4 to 0.5
+      is at:  http://www.sqlalchemy.org/trac/wiki/05Migration
+
+      For this section, the list below primarily lists changes 
+      within the attribute instrumentation API and is only a
+      small fraction of the full changes between 0.4/0.5.
 
     - The "__init__" trigger/decorator added by mapper now attempts
       to exactly mirror the argument signature of the original
@@ -30,15 +36,6 @@ user_defined_state
       descriptors attached to the class.  A deprecation warning will
       be issued when accessed.
 
-    - attribute savepoint/rollback capability has been added.  For
-      starters, this takes effect within the flush() call, so that
-      attribute changes which occur within flush() are rolled back
-      when the flush fails.  Since it's primarily new primary key
-      values that get assigned within flush(), expiring those
-      attributes is not an option.  The next place we might use
-      savepoints is within SAVEPOINT transactions, since rolling
-      back to a savepoint is a transaction-contained operation.
-
     - The _prepare_instrumentation alias for prepare_instrumentation
       has been removed.