summaryrefslogtreecommitdiff
path: root/lib/sqlalchemy/event/api.py
diff options
context:
space:
mode:
authorMike Bayer <mike_mp@zzzcomputing.com>2013-07-26 00:01:04 -0400
committerMike Bayer <mike_mp@zzzcomputing.com>2013-07-26 00:01:04 -0400
commit550141b14c8e165218cd32c27d91541eeee86d2a (patch)
tree1a87bc7934aab81f4b1b84c9100e73b56d45d09a /lib/sqlalchemy/event/api.py
parente60c16c7e6c2494b623553f41694c1ebde4d65d8 (diff)
downloadsqlalchemy-550141b14c8e165218cd32c27d91541eeee86d2a.tar.gz
- The mechanism by which attribute events pass along an
:class:`.AttributeImpl` as an "initiator" token has been changed; the object is now an event-specific object called :class:`.attributes.Event`. Additionally, the attribute system no longer halts events based on a matching "initiator" token; this logic has been moved to be specific to ORM backref event handlers, which are the typical source of the re-propagation of an attribute event onto subsequent append/set/remove operations. End user code which emulates the behavior of backrefs must now ensure that recursive event propagation schemes are halted, if the scheme does not use the backref handlers. Using this new system, backref handlers can now peform a "two-hop" operation when an object is appended to a collection, associated with a new many-to-one, de-associated with the previous many-to-one, and then removed from a previous collection. Before this change, the last step of removal from the previous collection would not occur. [ticket:2789]
Diffstat (limited to 'lib/sqlalchemy/event/api.py')
0 files changed, 0 insertions, 0 deletions