diff options
| author | Mike Bayer <mike_mp@zzzcomputing.com> | 2012-10-06 12:46:02 -0400 |
|---|---|---|
| committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2012-10-06 12:46:02 -0400 |
| commit | ab59e3e1135e1c5b59d19a54114163119d5ab1a4 (patch) | |
| tree | 65c9c88fc5bfb4b6841e70730b231d5904266917 /lib/sqlalchemy/sql/compiler.py | |
| parent | b7b242dbb5709aab76d1a035db3d5a72d079740c (diff) | |
| download | sqlalchemy-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 'lib/sqlalchemy/sql/compiler.py')
0 files changed, 0 insertions, 0 deletions