summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorMike Bayer <mike_mp@zzzcomputing.com>2015-06-24 21:53:15 -0400
committerMike Bayer <mike_mp@zzzcomputing.com>2015-06-24 21:53:15 -0400
commit1e2f1f5baabd4ec8866ec19b586bb493ea099852 (patch)
tree73ecc79079315d2e86cbdc0ebffba0f8a48eeada /doc
parent00656ae4930620bc8c0c4be6a82853f01c90f758 (diff)
downloadsqlalchemy-1e2f1f5baabd4ec8866ec19b586bb493ea099852.tar.gz
- 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
Diffstat (limited to 'doc')
-rw-r--r--doc/build/changelog/changelog_10.rst15
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/build/changelog/changelog_10.rst b/doc/build/changelog/changelog_10.rst
index ccc92e937..c588ed753 100644
--- a/doc/build/changelog/changelog_10.rst
+++ b/doc/build/changelog/changelog_10.rst
@@ -19,6 +19,21 @@
:version: 1.0.6
.. change::
+ :tags: bug, orm
+ :tickets: 3465
+
+ 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.
+
+ .. change::
:tags: bug, mssql
:tickets: 3464