From: Mike Bayer Date: Thu, 6 Feb 2025 18:59:22 +0000 (-0500) Subject: changelog edits X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=f976e7b775eda7013338800889e125937910ad35;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git changelog edits Change-Id: I61164f4af388d8f4f157ad6afe96ccbb668587a7 --- diff --git a/doc/build/changelog/unreleased_20/12077.rst b/doc/build/changelog/unreleased_20/12077.rst index ac1c5a95e5..94511b172d 100644 --- a/doc/build/changelog/unreleased_20/12077.rst +++ b/doc/build/changelog/unreleased_20/12077.rst @@ -2,6 +2,7 @@ :tags: postgresql, usecase, asyncio :tickets: 12077 - Added an additional ``shield()`` call within the connection terminate - process of the asyncpg driver, to mitigate an issue where terminate would - be prevented from completing under the anyio concurrency library. + Added an additional ``asyncio.shield()`` call within the connection + terminate process of the asyncpg driver, to mitigate an issue where + terminate would be prevented from completing under the anyio concurrency + library. diff --git a/doc/build/changelog/unreleased_20/12117.rst b/doc/build/changelog/unreleased_20/12117.rst index b4da4db1ef..a82ddc36f8 100644 --- a/doc/build/changelog/unreleased_20/12117.rst +++ b/doc/build/changelog/unreleased_20/12117.rst @@ -2,7 +2,8 @@ :tags: bug, dml, mariadb, mysql :tickets: 12117 - Fixed a bug where the :class:`MySQLCompiler` would not properly compile statements - where :meth:`_mysql.Insert.on_duplicate_key_update` was passed values that included - :class:`InstrumentedAttribute` as keys. - Pull request courtesy of mingyu. + Fixed a bug where the MySQL statement compiler would not properly compile + statements where :meth:`_mysql.Insert.on_duplicate_key_update` was passed + values that included ORM-mapped attributes (e.g. + :class:`InstrumentedAttribute` objects) as keys. Pull request courtesy of + mingyu. diff --git a/doc/build/changelog/unreleased_20/12159.rst b/doc/build/changelog/unreleased_20/12159.rst index 3babbf9db7..50496759fa 100644 --- a/doc/build/changelog/unreleased_20/12159.rst +++ b/doc/build/changelog/unreleased_20/12159.rst @@ -2,9 +2,9 @@ :tags: bug, postgresql :tickets: 12159 - Adjusted the asyncpg connection wrapper so that the asyncpg - ``.transaction()`` call sends ``None`` for isolation_level if not otherwise - set in the SQLAlchemy dialect/wrapper, thereby allowing asyncpg to make use - of the server level setting for isolation_level in the absense of a - client-level setting. Previously, this behavior of asyncpg was blocked by a - hardcoded ``read_committed``. + Adjusted the asyncpg connection wrapper so that the + ``connection.transaction()`` call sent to asyncpg sends ``None`` for + ``isolation_level`` if not otherwise set in the SQLAlchemy dialect/wrapper, + thereby allowing asyncpg to make use of the server level setting for + ``isolation_level`` in the absense of a client-level setting. Previously, + this behavior of asyncpg was blocked by a hardcoded ``read_committed``. diff --git a/doc/build/changelog/unreleased_20/12285.rst b/doc/build/changelog/unreleased_20/12285.rst index 2c1451b360..5d815f84ca 100644 --- a/doc/build/changelog/unreleased_20/12285.rst +++ b/doc/build/changelog/unreleased_20/12285.rst @@ -1,6 +1,10 @@ .. change:: - :tags: change, sqlite, aiosqlite, asyncio, pool + :tags: bug, sqlite, aiosqlite, asyncio, pool :tickets: 12285 - Changed default connection pool of aiosqlite from NullPool to AsyncAdaptedQueuePool for consistency with pysqlite. + Changed default connection pool used by the ``aiosqlite`` dialect + from :class:`.NullPool` to :class:`.AsyncAdaptedQueuePool`; this change + should have been made when 2.0 was first released as the ``pysqlite`` + dialect was similarly changed to use :class:`.QueuePool` as detailed + in :ref:`change_7490`. diff --git a/doc/build/changelog/unreleased_20/12289.rst b/doc/build/changelog/unreleased_20/12289.rst index 7ac111c0f5..33bc0f50a0 100644 --- a/doc/build/changelog/unreleased_20/12289.rst +++ b/doc/build/changelog/unreleased_20/12289.rst @@ -2,7 +2,7 @@ :tags: bug, engine :tickets: 12289 - Fixed issue where creating an :class:`.Engine` using multiple calls to - :meth:`.Engine.execution_options` where a subsequent call involved certain - options such as ``isolation_level`` would lead to an internal error + Fixed event-related issue where invoking :meth:`.Engine.execution_options` + on a :class:`.Engine` multiple times while making use of event-registering + parameters such as ``isolation_level`` would lead to internal errors involving event registration. diff --git a/doc/build/changelog/unreleased_20/12302.rst b/doc/build/changelog/unreleased_20/12302.rst index 38d4544898..43c1f7fafc 100644 --- a/doc/build/changelog/unreleased_20/12302.rst +++ b/doc/build/changelog/unreleased_20/12302.rst @@ -2,7 +2,7 @@ :tags: bug, sql :tickets: 12302 - Reorganized the internals by which the `.c` collection on a + Reorganized the internals by which the ``.c`` collection on a :class:`.FromClause` gets generated so that it is resilient against the collection being accessed in concurrent fashion. An example is creating a :class:`.Alias` or :class:`.Subquery` and accessing it as a module level diff --git a/doc/build/changelog/unreleased_20/12314.rst b/doc/build/changelog/unreleased_20/12314.rst index 6d5e83adeb..626c316bf9 100644 --- a/doc/build/changelog/unreleased_20/12314.rst +++ b/doc/build/changelog/unreleased_20/12314.rst @@ -2,8 +2,8 @@ :tags: bug, sql :tickets: 12314 - Fixed SQL rendering bug which impacted caching where using a ``None`` value - inside of an ``in_()`` expression would bypass the usual "expanded bind - parameter" logic used by the IN construct, which allows proper caching to - take place. + Fixed SQL composition bug which impacted caching where using a ``None`` + value inside of an ``in_()`` expression would bypass the usual "expanded + bind parameter" logic used by the IN construct, which allows proper caching + to take place. diff --git a/doc/build/changelog/whatsnew_20.rst b/doc/build/changelog/whatsnew_20.rst index 26241d58db..5b81b4aa49 100644 --- a/doc/build/changelog/whatsnew_20.rst +++ b/doc/build/changelog/whatsnew_20.rst @@ -2185,6 +2185,11 @@ hold onto database connections after they are released, did in fact have a measurable negative performance impact. As always, the pool class is customizable via the :paramref:`_sa.create_engine.poolclass` parameter. +.. versionchanged:: 2.0.37 - an equivalent change is also made for the + ``aiosqlite`` dialect, using :class:`._pool.AsyncAdaptedQueuePool` instead + of :class:`._pool.NullPool`. The ``aiosqlite`` dialect was not included + in the initial change in error. + .. seealso:: :ref:`pysqlite_threading_pooling`