From: Mike Bayer Date: Mon, 16 Jan 2023 21:30:10 +0000 (-0500) Subject: fix doc warnings X-Git-Tag: rel_2_0_0rc3~9 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=3bd40c1b9a265c3bed52bfe3394f21d75bf52025;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git fix doc warnings Change-Id: I38e465ef1902584c3242bb06ed5ed18a8c018285 --- diff --git a/doc/build/changelog/migration_14.rst b/doc/build/changelog/migration_14.rst index 1c588f018e..ac6cb6a535 100644 --- a/doc/build/changelog/migration_14.rst +++ b/doc/build/changelog/migration_14.rst @@ -2359,7 +2359,7 @@ to be more noticeable. :ticket:`1763` -.. _change_8879 +.. _change_8879: Column loaders such as ``deferred()``, ``with_expression()`` only take effect when indicated on the outermost, full entity query -------------------------------------------------------------------------------------------------------------------------------- diff --git a/doc/build/changelog/unreleased_14/9075.rst b/doc/build/changelog/unreleased_14/9075.rst index 0d96be7708..3263fa30be 100644 --- a/doc/build/changelog/unreleased_14/9075.rst +++ b/doc/build/changelog/unreleased_14/9075.rst @@ -5,14 +5,14 @@ Fixed bug / regression where using :func:`.bindparam()` with the same name as a column in the :meth:`.Update.values` method of :class:`.Update`, as - well as the :meth:`.Insert.values` method of :class:`.Insert` in 2.0 only, - would in some cases silently fail to honor the SQL expression in which the - parameter were presented, replacing the expression with a new parameter of - the same name and discarding any other elements of the SQL expression, such - as SQL functions, etc. The specific case would be statements that were - constructed against ORM entities rather than plain :class:`.Table` - instances, but would occur if the statement were invoked with a - :class:`.Session` or a :class:`.Connection`. + well as the :meth:`_sql.Insert.values` method of :class:`_sql.Insert` in + 2.0 only, would in some cases silently fail to honor the SQL expression in + which the parameter were presented, replacing the expression with a new + parameter of the same name and discarding any other elements of the SQL + expression, such as SQL functions, etc. The specific case would be + statements that were constructed against ORM entities rather than plain + :class:`.Table` instances, but would occur if the statement were invoked + with a :class:`.Session` or a :class:`.Connection`. :class:`.Update` part of the issue was present in both 2.0 and 1.4 and is backported to 1.4.