]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
- [feature] Calling rollback() within a
authorMike Bayer <mike_mp@zzzcomputing.com>
Tue, 24 Apr 2012 22:06:27 +0000 (18:06 -0400)
committerMike Bayer <mike_mp@zzzcomputing.com>
Tue, 24 Apr 2012 22:06:27 +0000 (18:06 -0400)
commit9cf10db8aa4692dc615f1a03db5ffe342c321586
treebc175ec68845968fd307317c062db44319d1688b
parentcfe56e3735d2ba34923c36e9f015253e535ed1bd
- [feature] Calling rollback() within a
session.begin_nested() will now only expire
those objects that had net changes within the
scope of that transaction, that is objects which
were dirty or were modified on a flush.  This
allows the typical use case for begin_nested(),
that of altering a small subset of objects, to
leave in place the data from the larger enclosing
set of objects that weren't modified in
that sub-transaction.  [ticket:2452]
- inline the "register_newly_XYZ" functions to operate
upon collections to reduce method calls
CHANGES
lib/sqlalchemy/orm/query.py
lib/sqlalchemy/orm/session.py
lib/sqlalchemy/orm/unitofwork.py
test/aaa_profiling/test_zoomark.py
test/orm/test_inspect.py
test/orm/test_transaction.py