Merge "Allow SQL expressions to be set on PK columns"

diff --cc doc/build/changelog/changelog_11.rst
index 0d6c6b15925cd83e589a8b6ae155fae18cf00497,6aa5624dd5f8a8cf26a878974b2722f417fb1f78..efd2d33f9b43a5c8a0beecf3c40c8f99318d7126
--- 1/doc/build/changelog/changelog_11.rst
--- 2/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