From: mike bayer Date: Tue, 20 Sep 2016 15:56:05 +0000 (-0400) Subject: Merge "Allow SQL expressions to be set on PK columns" X-Git-Tag: rel_1_1_0~24 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=5af3c903368e9a437a6ceafce5dc993433420cc7;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git Merge "Allow SQL expressions to be set on PK columns" --- 5af3c903368e9a437a6ceafce5dc993433420cc7 diff --cc doc/build/changelog/changelog_11.rst index 0d6c6b1592,6aa5624dd5..efd2d33f9b --- a/doc/build/changelog/changelog_11.rst +++ b/doc/build/changelog/changelog_11.rst @@@ -21,27 -21,16 +21,37 @@@ .. changelog:: :version: 1.1.0 + .. change:: + :tags: bug, sql + :tickets: 3799 + + The "eq" and "ne" operators are no longer part of the list of + "associative" operators, while they remain considered to be + "commutative". This allows an expression like ``(x == y) == z`` + to be maintained at the SQL level with parenthesis. Pull request + courtesy John Passaro. + + .. change:: + :tags: bug, orm + :tickets: 3767 + + The primaryjoin of a :func:`.relationship` construct can now include + a :func:`.bindparam` object that includes a callable function to + generate values. Previously, the lazy loader strategy would + be incompatible with this use, and additionally would fail to correctly + detect if the "use_get" criteria should be used if the primary key + were involved with the bound parameter. + + .. change:: + :tags: bug, orm + :tickets: 3801 + + An UPDATE emitted from the ORM flush process can now accommodate a + SQL expression element for a column within the primary key of an + object, if the target database supports RETURNING in order to provide + the new value, or if the PK value is set "to itself" for the purposes + of bumping some other trigger / onupdate on the column. + .. change:: :tags: bug, orm :tickets: 3788