diff options
| author | Mike Bayer <mike_mp@zzzcomputing.com> | 2014-07-24 14:04:23 -0400 |
|---|---|---|
| committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2014-07-24 14:04:23 -0400 |
| commit | 07c01b77f16a08cecdad2c80c1283bed46a7f815 (patch) | |
| tree | 89d3e7c9547acde21ef20f737f45543ce7c59ac0 | |
| parent | f2b267043e17b2b769dc2a5b8139f6be2a3d4e84 (diff) | |
| download | sqlalchemy-07c01b77f16a08cecdad2c80c1283bed46a7f815.tar.gz | |
merge 0.9.8 start
| -rw-r--r-- | doc/build/changelog/changelog_09.rst | 13 |
1 files changed, 7 insertions, 6 deletions
diff --git a/doc/build/changelog/changelog_09.rst b/doc/build/changelog/changelog_09.rst index b35d40b8e..3ec09076b 100644 --- a/doc/build/changelog/changelog_09.rst +++ b/doc/build/changelog/changelog_09.rst @@ -11,6 +11,9 @@ :start-line: 5 .. changelog:: + :version: 0.9.8 + +.. changelog:: :version: 0.9.7 :released: July 22, 2014 @@ -359,12 +362,10 @@ In this situation, a many-to-one relationship set to None, or in some cases a scalar attribute set to None, may not be detected as a net change in value, and therefore the UPDATE would not reset - what was on the previous row. - - The fix here takes on a different form in 1.0.0 vs. 0.9.5. - In 1.0.0, the issue is ultimately resolved by :ticket:`3061`, - which reverts the more patchwork version of the fix as it exists - in 0.9.5. + what was on the previous row. This is due to some as-yet + unresovled side effects of the way attribute history works in terms + of implicitly assuming None isn't really a "change" for a previously + un-set attribute. See also :ticket:`3061`. .. note:: |