From: Mike Bayer Date: Sun, 29 Oct 2023 20:32:30 +0000 (-0400) Subject: cherry-pick changelog from 1.4.50 X-Git-Tag: rel_2_0_23~5 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=67bc920af817dbe8697943e08eba0ae8963b8498;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git cherry-pick changelog from 1.4.50 --- diff --git a/doc/build/changelog/changelog_14.rst b/doc/build/changelog/changelog_14.rst index 709e0e9780..5853c78be4 100644 --- a/doc/build/changelog/changelog_14.rst +++ b/doc/build/changelog/changelog_14.rst @@ -15,7 +15,81 @@ This document details individual issue-level changes made throughout .. changelog:: :version: 1.4.50 - :include_notes_from: unreleased_14 + :released: October 29, 2023 + + .. change:: + :tags: bug, sql + :tickets: 10142 + :versions: 2.0.23 + + Fixed issue where using the same bound parameter more than once with + ``literal_execute=True`` in some combinations with other literal rendering + parameters would cause the wrong values to render due to an iteration + issue. + + .. change:: + :tags: mysql, usecase + :versions: 2.0.20 + + Updated aiomysql dialect since the dialect appears to be maintained again. + Re-added to the ci testing using version 0.2.0. + + .. change:: + :tags: bug, orm + :tickets: 10223 + :versions: 2.0.20 + + Fixed fundamental issue which prevented some forms of ORM "annotations" + from taking place for subqueries which made use of :meth:`_sql.Select.join` + against a relationship target. These annotations are used whenever a + subquery is used in special situations such as within + :meth:`_orm.PropComparator.and_` and other ORM-specific scenarios. + + .. change:: + :tags: bug, sql + :tickets: 10213 + :versions: 2.0.20 + + Fixed issue where unpickling of a :class:`_schema.Column` or other + :class:`_sql.ColumnElement` would fail to restore the correct "comparator" + object, which is used to generate SQL expressions specific to the type + object. + + .. change:: + :tags: bug, mysql + :tickets: 10492 + :versions: 2.0.23 + + Repaired a new incompatibility in the MySQL "pre-ping" routine where the + ``False`` argument passed to ``connection.ping()``, which is intended to + disable an unwanted "automatic reconnect" feature, is being deprecated in + MySQL drivers and backends, and is producing warnings for some versions of + MySQL's native client drivers. It's removed for mysqlclient, whereas for + PyMySQL and drivers based on PyMySQL, the parameter will be deprecated and + removed at some point, so API introspection is used to future proof against + these various stages of removal. + + .. change:: + :tags: schema, bug + :tickets: 10207 + :versions: 2.0.21 + + Modified the rendering of the Oracle only :paramref:`.Identity.order` + parameter that's part of both :class:`.Sequence` and :class:`.Identity` to + only take place for the Oracle backend, and not other backends such as that + of PostgreSQL. A future release will rename the + :paramref:`.Identity.order`, :paramref:`.Sequence.order` and + :paramref:`.Identity.on_null` parameters to Oracle-specific names, + deprecating the old names, these parameters only apply to Oracle. + + .. change:: + :tags: bug, mssql, reflection + :tickets: 10504 + :versions: 2.0.23 + + Fixed issue where identity column reflection would fail + for a bigint column with a large identity start value + (more than 18 digits). .. changelog:: :version: 1.4.49 diff --git a/doc/build/changelog/unreleased_14/10142.rst b/doc/build/changelog/unreleased_14/10142.rst deleted file mode 100644 index 91643c69ec..0000000000 --- a/doc/build/changelog/unreleased_14/10142.rst +++ /dev/null @@ -1,9 +0,0 @@ -.. change:: - :tags: bug, sql - :tickets: 10142 - :versions: 2.0.23 - - Fixed issue where using the same bound parameter more than once with - ``literal_execute=True`` in some combinations with other literal rendering - parameters would cause the wrong values to render due to an iteration - issue. diff --git a/doc/build/changelog/unreleased_14/10207.rst b/doc/build/changelog/unreleased_14/10207.rst deleted file mode 100644 index aef31e6a42..0000000000 --- a/doc/build/changelog/unreleased_14/10207.rst +++ /dev/null @@ -1,12 +0,0 @@ -.. change:: - :tags: schema, bug - :tickets: 10207 - :versions: 2.0.21 - - Modified the rendering of the Oracle only :paramref:`.Identity.order` - parameter that's part of both :class:`.Sequence` and :class:`.Identity` to - only take place for the Oracle backend, and not other backends such as that - of PostgreSQL. A future release will rename the - :paramref:`.Identity.order`, :paramref:`.Sequence.order` and - :paramref:`.Identity.on_null` parameters to Oracle-specific names, - deprecating the old names, these parameters only apply to Oracle. diff --git a/doc/build/changelog/unreleased_14/10213.rst b/doc/build/changelog/unreleased_14/10213.rst deleted file mode 100644 index 96c17b1946..0000000000 --- a/doc/build/changelog/unreleased_14/10213.rst +++ /dev/null @@ -1,9 +0,0 @@ -.. change:: - :tags: bug, sql - :tickets: 10213 - :versions: 2.0.20 - - Fixed issue where unpickling of a :class:`_schema.Column` or other - :class:`_sql.ColumnElement` would fail to restore the correct "comparator" - object, which is used to generate SQL expressions specific to the type - object. diff --git a/doc/build/changelog/unreleased_14/10223.rst b/doc/build/changelog/unreleased_14/10223.rst deleted file mode 100644 index 7c74424060..0000000000 --- a/doc/build/changelog/unreleased_14/10223.rst +++ /dev/null @@ -1,10 +0,0 @@ -.. change:: - :tags: bug, orm - :tickets: 10223 - :versions: 2.0.20 - - Fixed fundamental issue which prevented some forms of ORM "annotations" - from taking place for subqueries which made use of :meth:`_sql.Select.join` - against a relationship target. These annotations are used whenever a - subquery is used in special situations such as within - :meth:`_orm.PropComparator.and_` and other ORM-specific scenarios. diff --git a/doc/build/changelog/unreleased_14/10492.rst b/doc/build/changelog/unreleased_14/10492.rst deleted file mode 100644 index 8ddf5738b6..0000000000 --- a/doc/build/changelog/unreleased_14/10492.rst +++ /dev/null @@ -1,13 +0,0 @@ -.. change:: - :tags: bug, mysql - :tickets: 10492 - :versions: 2.0.23 - - Repaired a new incompatibility in the MySQL "pre-ping" routine where the - ``False`` argument passed to ``connection.ping()``, which is intended to - disable an unwanted "automatic reconnect" feature, is being deprecated in - MySQL drivers and backends, and is producing warnings for some versions of - MySQL's native client drivers. It's removed for mysqlclient, whereas for - PyMySQL and drivers based on PyMySQL, the parameter will be deprecated and - removed at some point, so API introspection is used to future proof against - these various stages of removal. diff --git a/doc/build/changelog/unreleased_14/10504.rst b/doc/build/changelog/unreleased_14/10504.rst deleted file mode 100644 index 7afc00f667..0000000000 --- a/doc/build/changelog/unreleased_14/10504.rst +++ /dev/null @@ -1,8 +0,0 @@ -.. change:: - :tags: bug, mssql, reflection - :tickets: 10504 - :versions: 2.0.23 - - Fixed issue where identity column reflection would fail - for a bigint column with a large identity start value - (more than 18 digits). diff --git a/doc/build/changelog/unreleased_14/aiomysql.rst b/doc/build/changelog/unreleased_14/aiomysql.rst deleted file mode 100644 index ef6fc4c94f..0000000000 --- a/doc/build/changelog/unreleased_14/aiomysql.rst +++ /dev/null @@ -1,6 +0,0 @@ -.. change:: - :tags: mysql, usecase - :versions: 2.0.20 - - Updated aiomysql dialect since the dialect appears to be maintained again. - Re-added to the ci testing using version 0.2.0.