]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
- Fixed a major regression in the 1.0 series where the version_id_counter
authorMike Bayer <mike_mp@zzzcomputing.com>
Thu, 25 Jun 2015 01:53:15 +0000 (21:53 -0400)
committerMike Bayer <mike_mp@zzzcomputing.com>
Thu, 25 Jun 2015 01:53:15 +0000 (21:53 -0400)
commit1e2f1f5baabd4ec8866ec19b586bb493ea099852
tree73ecc79079315d2e86cbdc0ebffba0f8a48eeada
parent00656ae4930620bc8c0c4be6a82853f01c90f758
- Fixed a major regression in the 1.0 series where the version_id_counter
feature would cause an object's version counter to be incremented
when there was no net change to the object's row, but instead an object
related to it via relationship (e.g. typically many-to-one)
were associated or de-associated with it, resulting in an UPDATE
statement that updates the object's version counter and nothing else.
In the use case where the relatively recent "server side" and/or
"programmatic/conditional" version counter feature were used
(e.g. setting version_id_generator to False), the bug could cause an
UPDATE without a valid SET clause to be emitted.
fixes #3465
doc/build/changelog/changelog_10.rst
lib/sqlalchemy/orm/persistence.py
test/orm/test_versioning.py