From: Mike Bayer Date: Fri, 11 Feb 2022 17:48:23 +0000 (-0500) Subject: remove dupe 'always" use X-Git-Tag: rel_2_0_0b1~489 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=46b2d7ae6d630260acf4de32906a0cabced78d1c;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git remove dupe 'always" use Change-Id: Ib46d6f622fdf11f9813154c6f7a55bbe229b0184 --- diff --git a/doc/build/changelog/migration_20.rst b/doc/build/changelog/migration_20.rst index ad0dce3f10..406f782e5d 100644 --- a/doc/build/changelog/migration_20.rst +++ b/doc/build/changelog/migration_20.rst @@ -327,7 +327,7 @@ based database is used. This is set along with setting the ``check_same_thread`` parameter to ``False``. It has been observed that the previous approach of defaulting to :class:`_pool.NullPool`, which does not hold onto database connections after they are released, did in fact have a -measurable negative performance impact. As always, the pool class is always +measurable negative performance impact. As always, the pool class is customizable via the :paramref:`_sa.create_engine.poolclass` parameter. .. seealso:: diff --git a/doc/build/changelog/unreleased_20/7490.rst b/doc/build/changelog/unreleased_20/7490.rst index 0e1487cce3..81862ba8c4 100644 --- a/doc/build/changelog/unreleased_20/7490.rst +++ b/doc/build/changelog/unreleased_20/7490.rst @@ -7,7 +7,7 @@ ``check_same_thread`` parameter to ``False``. It has been observed that the previous approach of defaulting to :class:`_pool.NullPool`, which does not hold onto database connections after they are released, did in fact have a - measurable negative performance impact. As always, the pool class is always + measurable negative performance impact. As always, the pool class is customizable via the :paramref:`_sa.create_engine.poolclass` parameter. .. seealso::