From: Mike Bayer Date: Tue, 30 Mar 2021 22:58:27 +0000 (-0400) Subject: - 1.3.24 X-Git-Tag: rel_1_3_24 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=ee17cbad9ed4adbc1a6a1b6273ad1ded66e25d99;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git - 1.3.24 --- diff --git a/doc/build/changelog/changelog_13.rst b/doc/build/changelog/changelog_13.rst index c6516c66af..a50d012fb3 100644 --- a/doc/build/changelog/changelog_13.rst +++ b/doc/build/changelog/changelog_13.rst @@ -12,7 +12,148 @@ .. changelog:: :version: 1.3.24 - :include_notes_from: unreleased_13 + :released: March 30, 2021 + + .. change:: + :tags: bug, schema + :tickets: 6152 + + Fixed bug first introduced in as some combination of :ticket:`2892`, + :ticket:`2919` nnd :ticket:`3832` where the attachment events for a + :class:`_types.TypeDecorator` would be doubled up against the "impl" class, + if the "impl" were also a :class:`_types.SchemaType`. The real-world case + is any :class:`_types.TypeDecorator` against :class:`_types.Enum` or + :class:`_types.Boolean` would get a doubled + :class:`_schema.CheckConstraint` when the ``create_constraint=True`` flag + is set. + + + .. change:: + :tags: bug, schema, sqlite + :tickets: 6007 + :versions: 1.4.0 + + Fixed issue where the CHECK constraint generated by :class:`_types.Boolean` + or :class:`_types.Enum` would fail to render the naming convention + correctly after the first compilation, due to an unintended change of state + within the name given to the constraint. This issue was first introduced in + 0.9 in the fix for issue #3067, and the fix revises the approach taken at + that time which appears to have been more involved than what was needed. + + .. change:: + :tags: bug, orm + :tickets: 5983 + :versions: 1.4.0 + + Removed very old warning that states that passive_deletes is not intended + for many-to-one relationships. While it is likely that in many cases + placing this parameter on a many-to-one relationship is not what was + intended, there are use cases where delete cascade may want to be + disallowed following from such a relationship. + + + + .. change:: + :tags: bug, postgresql + :tickets: 5989 + :versions: 1.4.0 + + Fixed issue where using :class:`_postgresql.aggregate_order_by` would + return ARRAY(NullType) under certain conditions, interfering with + the ability of the result object to return data correctly. + + .. change:: + :tags: bug, schema + :tickets: 5919 + :versions: 1.4.0 + + Repaired / implemented support for primary key constraint naming + conventions that use column names/keys/etc as part of the convention. In + particular, this includes that the :class:`.PrimaryKeyConstraint` object + that's automatically associated with a :class:`.schema.Table` will update + its name as new primary key :class:`_schema.Column` objects are added to + the table and then to the constraint. Internal failure modes related to + this constraint construction process including no columns present, no name + present or blank name present are now accommodated. + + .. change:: + :tags: bug, schema + :tickets: 6071 + :versions: 1.4.3 + + Adjusted the logic that emits DROP statements for :class:`_schema.Sequence` + objects among the dropping of multiple tables, such that all + :class:`_schema.Sequence` objects are dropped after all tables, even if the + given :class:`_schema.Sequence` is related only to a :class:`_schema.Table` + object and not directly to the overall :class:`_schema.MetaData` object. + The use case supports the same :class:`_schema.Sequence` being associated + with more than one :class:`_schema.Table` at a time. + + .. change:: + :tags: bug, orm + :tickets: 5952 + :versions: 1.4.0 + + Fixed issue where the process of joining two tables could fail if one of + the tables had an unrelated, unresolvable foreign key constraint which + would raise :class:`_exc.NoReferenceError` within the join process, which + nonetheless could be bypassed to allow the join to complete. The logic + which tested the exception for significance within the process would make + assumptions about the construct which would fail. + + + .. change:: + :tags: bug, postgresql, reflection + :tickets: 6161 + :versions: 1.4.4 + + Fixed issue in PostgreSQL reflection where a column expressing "NOT NULL" + will supersede the nullability of a corresponding domain. + + .. change:: + :tags: bug, engine + :tickets: 5929 + :versions: 1.4.0 + + Fixed bug where the "schema_translate_map" feature failed to be taken into + account for the use case of direct execution of + :class:`_schema.DefaultGenerator` objects such as sequences, which included + the case where they were "pre-executed" in order to generate primary key + values when implicit_returning was disabled. + + .. change:: + :tags: bug, orm + :tickets: 6001 + :versions: 1.4.0 + + Fixed issue where the :class:`_mutable.MutableComposite` construct could be + placed into an invalid state when the parent object was already loaded, and + then covered by a subsequent query, due to the composite properties' + refresh handler replacing the object with a new one not handled by the + mutable extension. + + + .. change:: + :tags: bug, types, postgresql + :tickets: 6023 + :versions: 1.4.3 + + Adjusted the psycopg2 dialect to emit an explicit PostgreSQL-style cast for + bound parameters that contain ARRAY elements. This allows the full range of + datatypes to function correctly within arrays. The asyncpg dialect already + generated these internal casts in the final statement. This also includes + support for array slice updates as well as the PostgreSQL-specific + :meth:`_postgresql.ARRAY.contains` method. + + .. change:: + :tags: bug, mssql, reflection + :tickets: 5921 + + Fixed issue regarding SQL Server reflection for older SQL Server 2005 + version, a call to sp_columns would not proceed correctly without being + prefixed with the EXEC keyword. This method is not used in current 1.4 + series. + .. changelog:: :version: 1.3.23 diff --git a/doc/build/changelog/unreleased_13/5919.rst b/doc/build/changelog/unreleased_13/5919.rst deleted file mode 100644 index f56da617d2..0000000000 --- a/doc/build/changelog/unreleased_13/5919.rst +++ /dev/null @@ -1,13 +0,0 @@ -.. change:: - :tags: bug, schema - :tickets: 5919 - :versions: 1.4.0 - - Repaired / implemented support for primary key constraint naming - conventions that use column names/keys/etc as part of the convention. In - particular, this includes that the :class:`.PrimaryKeyConstraint` object - that's automatically associated with a :class:`.schema.Table` will update - its name as new primary key :class:`_schema.Column` objects are added to - the table and then to the constraint. Internal failure modes related to - this constraint construction process including no columns present, no name - present or blank name present are now accommodated. diff --git a/doc/build/changelog/unreleased_13/5921.rst b/doc/build/changelog/unreleased_13/5921.rst deleted file mode 100644 index 90600a4bd8..0000000000 --- a/doc/build/changelog/unreleased_13/5921.rst +++ /dev/null @@ -1,9 +0,0 @@ -.. change:: - :tags: bug, mssql, reflection - :tickets: 5921 - - Fixed issue regarding SQL Server reflection for older SQL Server 2005 - version, a call to sp_columns would not proceed correctly without being - prefixed with the EXEC keyword. This method is not used in current 1.4 - series. - diff --git a/doc/build/changelog/unreleased_13/5929.rst b/doc/build/changelog/unreleased_13/5929.rst deleted file mode 100644 index 38bca63a22..0000000000 --- a/doc/build/changelog/unreleased_13/5929.rst +++ /dev/null @@ -1,10 +0,0 @@ -.. change:: - :tags: bug, engine - :tickets: 5929 - :versions: 1.4.0 - - Fixed bug where the "schema_translate_map" feature failed to be taken into - account for the use case of direct execution of - :class:`_schema.DefaultGenerator` objects such as sequences, which included - the case where they were "pre-executed" in order to generate primary key - values when implicit_returning was disabled. diff --git a/doc/build/changelog/unreleased_13/5952.rst b/doc/build/changelog/unreleased_13/5952.rst deleted file mode 100644 index 8f70df710a..0000000000 --- a/doc/build/changelog/unreleased_13/5952.rst +++ /dev/null @@ -1,12 +0,0 @@ -.. change:: - :tags: bug, orm - :tickets: 5952 - :versions: 1.4.0 - - Fixed issue where the process of joining two tables could fail if one of - the tables had an unrelated, unresolvable foreign key constraint which - would raise :class:`_exc.NoReferenceError` within the join process, which - nonetheless could be bypassed to allow the join to complete. The logic - which tested the exception for significance within the process would make - assumptions about the construct which would fail. - diff --git a/doc/build/changelog/unreleased_13/5983.rst b/doc/build/changelog/unreleased_13/5983.rst deleted file mode 100644 index 42b3f1adb6..0000000000 --- a/doc/build/changelog/unreleased_13/5983.rst +++ /dev/null @@ -1,12 +0,0 @@ -.. change:: - :tags: bug, orm - :tickets: 5983 - :versions: 1.4.0 - - Removed very old warning that states that passive_deletes is not intended - for many-to-one relationships. While it is likely that in many cases - placing this parameter on a many-to-one relationship is not what was - intended, there are use cases where delete cascade may want to be - disallowed following from such a relationship. - - diff --git a/doc/build/changelog/unreleased_13/5989.rst b/doc/build/changelog/unreleased_13/5989.rst deleted file mode 100644 index 018d56afe7..0000000000 --- a/doc/build/changelog/unreleased_13/5989.rst +++ /dev/null @@ -1,8 +0,0 @@ -.. change:: - :tags: bug, postgresql - :tickets: 5989 - :versions: 1.4.0 - - Fixed issue where using :class:`_postgresql.aggregate_order_by` would - return ARRAY(NullType) under certain conditions, interfering with - the ability of the result object to return data correctly. diff --git a/doc/build/changelog/unreleased_13/6001.rst b/doc/build/changelog/unreleased_13/6001.rst deleted file mode 100644 index 728ce20a43..0000000000 --- a/doc/build/changelog/unreleased_13/6001.rst +++ /dev/null @@ -1,11 +0,0 @@ -.. change:: - :tags: bug, orm - :tickets: 6001 - :versions: 1.4.0 - - Fixed issue where the :class:`_mutable.MutableComposite` construct could be - placed into an invalid state when the parent object was already loaded, and - then covered by a subsequent query, due to the composite properties' - refresh handler replacing the object with a new one not handled by the - mutable extension. - diff --git a/doc/build/changelog/unreleased_13/6007.rst b/doc/build/changelog/unreleased_13/6007.rst deleted file mode 100644 index 62c5af1d4c..0000000000 --- a/doc/build/changelog/unreleased_13/6007.rst +++ /dev/null @@ -1,11 +0,0 @@ -.. change:: - :tags: bug, schema, sqlite - :tickets: 6007 - :versions: 1.4.0 - - Fixed issue where the CHECK constraint generated by :class:`_types.Boolean` - or :class:`_types.Enum` would fail to render the naming convention - correctly after the first compilation, due to an unintended change of state - within the name given to the constraint. This issue was first introduced in - 0.9 in the fix for issue #3067, and the fix revises the approach taken at - that time which appears to have been more involved than what was needed. \ No newline at end of file diff --git a/doc/build/changelog/unreleased_13/6023.rst b/doc/build/changelog/unreleased_13/6023.rst deleted file mode 100644 index 1c4b6ac8ce..0000000000 --- a/doc/build/changelog/unreleased_13/6023.rst +++ /dev/null @@ -1,11 +0,0 @@ -.. change:: - :tags: bug, types, postgresql - :tickets: 6023 - :versions: 1.4.3 - - Adjusted the psycopg2 dialect to emit an explicit PostgreSQL-style cast for - bound parameters that contain ARRAY elements. This allows the full range of - datatypes to function correctly within arrays. The asyncpg dialect already - generated these internal casts in the final statement. This also includes - support for array slice updates as well as the PostgreSQL-specific - :meth:`_postgresql.ARRAY.contains` method. \ No newline at end of file diff --git a/doc/build/changelog/unreleased_13/6071.rst b/doc/build/changelog/unreleased_13/6071.rst deleted file mode 100644 index 44e8abfaba..0000000000 --- a/doc/build/changelog/unreleased_13/6071.rst +++ /dev/null @@ -1,12 +0,0 @@ -.. change:: - :tags: bug, schema - :tickets: 6071 - :versions: 1.4.3 - - Adjusted the logic that emits DROP statements for :class:`_schema.Sequence` - objects among the dropping of multiple tables, such that all - :class:`_schema.Sequence` objects are dropped after all tables, even if the - given :class:`_schema.Sequence` is related only to a :class:`_schema.Table` - object and not directly to the overall :class:`_schema.MetaData` object. - The use case supports the same :class:`_schema.Sequence` being associated - with more than one :class:`_schema.Table` at a time. diff --git a/doc/build/changelog/unreleased_13/6152.rst b/doc/build/changelog/unreleased_13/6152.rst deleted file mode 100644 index b6dae22a49..0000000000 --- a/doc/build/changelog/unreleased_13/6152.rst +++ /dev/null @@ -1,13 +0,0 @@ -.. change:: - :tags: bug, schema - :tickets: 6152 - - Fixed bug first introduced in as some combination of :ticket:`2892`, - :ticket:`2919` nnd :ticket:`3832` where the attachment events for a - :class:`_types.TypeDecorator` would be doubled up against the "impl" class, - if the "impl" were also a :class:`_types.SchemaType`. The real-world case - is any :class:`_types.TypeDecorator` against :class:`_types.Enum` or - :class:`_types.Boolean` would get a doubled - :class:`_schema.CheckConstraint` when the ``create_constraint=True`` flag - is set. - diff --git a/doc/build/changelog/unreleased_13/6161.rst b/doc/build/changelog/unreleased_13/6161.rst deleted file mode 100644 index df41b857a4..0000000000 --- a/doc/build/changelog/unreleased_13/6161.rst +++ /dev/null @@ -1,7 +0,0 @@ -.. change:: - :tags: bug, postgresql, reflection - :tickets: 6161 - :versions: 1.4.4 - - Fixed issue in PostgreSQL reflection where a column expressing "NOT NULL" - will supersede the nullability of a corresponding domain. diff --git a/doc/build/conf.py b/doc/build/conf.py index 94a2652acd..7686b4bb4c 100644 --- a/doc/build/conf.py +++ b/doc/build/conf.py @@ -171,9 +171,9 @@ copyright = u"2007-2021, the SQLAlchemy authors and contributors" # noqa # The short X.Y version. version = "1.3" # The full version, including alpha/beta/rc tags. -release = "1.3.23" +release = "1.3.24" -release_date = "February 1, 2021" +release_date = "March 30, 2021" site_base = os.environ.get("RTD_SITE_BASE", "http://www.sqlalchemy.org") site_adapter_template = "docs_adapter.mako"