]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
this approach seems to allow many-to-one post updates to occur as a single action...
authorMike Bayer <mike_mp@zzzcomputing.com>
Fri, 18 Jun 2010 15:36:35 +0000 (11:36 -0400)
committerMike Bayer <mike_mp@zzzcomputing.com>
Fri, 18 Jun 2010 15:36:35 +0000 (11:36 -0400)
commit46e0138405778379848e6c6f2ab424388724e555
tree85ca8c4f1e12e0fcc7185a99a3726e370ad652ff
parent0276ec0cd874aafb06606c443e8cdeb692c232f9
this approach seems to allow many-to-one post updates to occur as a single action.   for one-to-many, we
have it working the old way still. as usual the huge job is the tests.   also I am not yet certain
that post updates can always be a "full mapper" operation, i.e. are never involved in per-state dependencies,
or even if the old approach supports that.
lib/sqlalchemy/orm/dependency.py
lib/sqlalchemy/orm/unitofwork.py