summaryrefslogtreecommitdiff
path: root/CHANGES
diff options
context:
space:
mode:
authorMike Bayer <mike_mp@zzzcomputing.com>2012-10-06 12:46:02 -0400
committerMike Bayer <mike_mp@zzzcomputing.com>2012-10-06 12:46:02 -0400
commitab59e3e1135e1c5b59d19a54114163119d5ab1a4 (patch)
tree65c9c88fc5bfb4b6841e70730b231d5904266917 /CHANGES
parentb7b242dbb5709aab76d1a035db3d5a72d079740c (diff)
downloadsqlalchemy-ab59e3e1135e1c5b59d19a54114163119d5ab1a4.tar.gz
- [bug] Continuing [ticket:2566] regarding extra
state post-flush due to event listeners; any states that are marked as "dirty" from an attribute perspective, usually via column-attribute set events within after_insert(), after_update(), etc., will get the "history" flag reset in all cases, instead of only those instances that were part of the flush. This has the effect that this "dirty" state doesn't carry over after the flush and won't result in UPDATE statements. A warning is emitted to this effect; the set_committed_state() method can be used to assign attributes on objects without producing history events. [ticket:2582]
Diffstat (limited to 'CHANGES')
-rw-r--r--CHANGES15
1 files changed, 15 insertions, 0 deletions
diff --git a/CHANGES b/CHANGES
index 67bcb40bd..33bf4107c 100644
--- a/CHANGES
+++ b/CHANGES
@@ -246,6 +246,21 @@ underneath "0.7.xx".
inside of the flush, but for now, results
can't be guaranteed.
+ - [bug] Continuing [ticket:2566] regarding extra
+ state post-flush due to event listeners;
+ any states that are marked as "dirty" from an
+ attribute perspective, usually via column-attribute
+ set events within after_insert(), after_update(),
+ etc., will get the "history" flag reset
+ in all cases, instead of only those instances
+ that were part of the flush. This has the effect
+ that this "dirty" state doesn't carry over
+ after the flush and won't result in UPDATE
+ statements. A warning is emitted to this
+ effect; the set_committed_state()
+ method can be used to assign attributes on objects
+ without producing history events. [ticket:2582]
+
- [feature] ORM entities can be passed
to select() as well as the select_from(),
correlate(), and correlate_except()