[PR #227] [CLOSED] Scheduled weekly dependency update for week 30 #245

New issue

Closed

opened 2026-02-26 01:33:44 +03:00 by kerem · 0 comments

kerem commented 2026-02-26 01:33:44 +03:00

Owner

Copy link

📋 Pull Request Information

Original PR: https://github.com/jeffknupp/sandman2/pull/227
Author: @pyup-bot
Created: 7/26/2021
Status: ❌ Closed

Base: master ← Head: pyup-scheduled-update-2021-07-26

---

📝 Commits (10+)

• b0a5aed Update flask from 1.1.2 to 2.0.1
• 3b2cb55 Update flask-admin from 1.5.7 to 1.5.8
• 6b25ef4 Update flask-sqlalchemy from 2.4.4 to 2.5.1
• a3aab21 Update sqlalchemy from 1.3.20 to 1.4.22
• 2273e42 Update coverage from 5.3 to 5.5
• 535af15 Update pytest from 6.2.0 to 6.2.4
• fa5076f Update flask-cors from 3.0.9 to 3.0.10
• fbf3c09 Update pytest-cov from 2.10.1 to 2.12.1
• 300889e Update pytest-flask from 1.1.0 to 1.2.0
• 378a2f5 Update six from 1.15.0 to 1.16.0

📊 Changes

1 file changed (+12 additions, -12 deletions)

View changed files

📝 requirements.txt (+12 -12)

📄 Description

Update Flask from 1.1.2 to 2.0.1.

Changelog

2.0.1

-------------

Released 2021-05-21

-   Re-add the ``filename`` parameter in ``send_from_directory``. The
 ``filename`` parameter has been renamed to ``path``, the old name
 is deprecated. :pr:`4019`
-   Mark top-level names as exported so type checking understands
 imports in user projects. :issue:`4024`
-   Fix type annotation for ``g`` and inform mypy that it is a namespace
 object that has arbitrary attributes. :issue:`4020`
-   Fix some types that weren't available in Python 3.6.0. :issue:`4040`
-   Improve typing for ``send_file``, ``send_from_directory``, and
 ``get_send_file_max_age``. :issue:`4044`, :pr:`4026`
-   Show an error when a blueprint name contains a dot. The ``.`` has
 special meaning, it is used to separate (nested) blueprint names and
 the endpoint name. :issue:`4041`
-   Combine URL prefixes when nesting blueprints that were created with
 a ``url_prefix`` value. :issue:`4037`
-   Roll back a change to the order that URL matching was done. The
 URL is again matched after the session is loaded, so the session is
 available in custom URL converters. :issue:`4053`
-   Re-add deprecated ``Config.from_json``, which was accidentally
 removed early. :issue:`4078`
-   Improve typing for some functions using ``Callable`` in their type
 signatures, focusing on decorator factories. :issue:`4060`
-   Nested blueprints are registered with their dotted name. This allows
 different blueprints with the same name to be nested at different
 locations. :issue:`4069`
-   ``register_blueprint`` takes a ``name`` option to change the
 (pre-dotted) name the blueprint is registered with. This allows the
 same blueprint to be registered multiple times with unique names for
 ``url_for``. Registering the same blueprint with the same name
 multiple times is deprecated. :issue:`1091`
-   Improve typing for ``stream_with_context``. :issue:`4052`

2.0.0

-------------

Released 2021-05-11

-   Drop support for Python 2 and 3.5.
-   Bump minimum versions of other Pallets projects: Werkzeug >= 2,
 Jinja2 >= 3, MarkupSafe >= 2, ItsDangerous >= 2, Click >= 8. Be sure
 to check the change logs for each project. For better compatibility
 with other applications (e.g. Celery) that still require Click 7,
 there is no hard dependency on Click 8 yet, but using Click 7 will
 trigger a DeprecationWarning and Flask 2.1 will depend on Click 8.
-   JSON support no longer uses simplejson. To use another JSON module,
 override ``app.json_encoder`` and ``json_decoder``. :issue:`3555`
-   The ``encoding`` option to JSON functions is deprecated. :pr:`3562`
-   Passing ``script_info`` to app factory functions is deprecated. This
 was not portable outside the ``flask`` command. Use
 ``click.get_current_context().obj`` if it's needed. :issue:`3552`
-   The CLI shows better error messages when the app failed to load
 when looking up commands. :issue:`2741`
-   Add :meth:`sessions.SessionInterface.get_cookie_name` to allow
 setting the session cookie name dynamically. :pr:`3369`
-   Add :meth:`Config.from_file` to load config using arbitrary file
 loaders, such as ``toml.load`` or ``json.load``.
 :meth:`Config.from_json` is deprecated in favor of this. :pr:`3398`
-   The ``flask run`` command will only defer errors on reload. Errors
 present during the initial call will cause the server to exit with
 the traceback immediately. :issue:`3431`
-   :func:`send_file` raises a :exc:`ValueError` when passed an
 :mod:`io` object in text mode. Previously, it would respond with
 200 OK and an empty file. :issue:`3358`
-   When using ad-hoc certificates, check for the cryptography library
 instead of PyOpenSSL. :pr:`3492`
-   When specifying a factory function with ``FLASK_APP``, keyword
 argument can be passed. :issue:`3553`
-   When loading a ``.env`` or ``.flaskenv`` file, the current working
 directory is no longer changed to the location of the file.
 :pr:`3560`
-   When returning a ``(response, headers)`` tuple from a view, the
 headers replace rather than extend existing headers on the response.
 For example, this allows setting the ``Content-Type`` for
 ``jsonify()``. Use ``response.headers.extend()`` if extending is
 desired. :issue:`3628`
-   The ``Scaffold`` class provides a common API for the ``Flask`` and
 ``Blueprint`` classes. ``Blueprint`` information is stored in
 attributes just like ``Flask``, rather than opaque lambda functions.
 This is intended to improve consistency and maintainability.
 :issue:`3215`
-   Include ``samesite`` and ``secure`` options when removing the
 session cookie. :pr:`3726`
-   Support passing a ``pathlib.Path`` to ``static_folder``. :pr:`3579`
-   ``send_file`` and ``send_from_directory`` are wrappers around the
 implementations in ``werkzeug.utils``. :pr:`3828`
-   Some ``send_file`` parameters have been renamed, the old names are
 deprecated. ``attachment_filename`` is renamed to ``download_name``.
 ``cache_timeout`` is renamed to ``max_age``. ``add_etags`` is
 renamed to ``etag``. :pr:`3828, 3883`
-   ``send_file`` passes ``download_name`` even if
 ``as_attachment=False`` by using ``Content-Disposition: inline``.
 :pr:`3828`
-   ``send_file`` sets ``conditional=True`` and ``max_age=None`` by
 default. ``Cache-Control`` is set to ``no-cache`` if ``max_age`` is
 not set, otherwise ``public``. This tells browsers to validate
 conditional requests instead of using a timed cache. :pr:`3828`
-   ``helpers.safe_join`` is deprecated. Use
 ``werkzeug.utils.safe_join`` instead. :pr:`3828`
-   The request context does route matching before opening the session.
 This could allow a session interface to change behavior based on
 ``request.endpoint``. :issue:`3776`
-   Use Jinja's implementation of the ``|tojson`` filter. :issue:`3881`
-   Add route decorators for common HTTP methods. For example,
 ``app.post("/login")`` is a shortcut for
 ``app.route("/login", methods=["POST"])``. :pr:`3907`
-   Support async views, error handlers, before and after request, and
 teardown functions. :pr:`3412`
-   Support nesting blueprints. :issue:`593, 1548`, :pr:`3923`
-   Set the default encoding to "UTF-8" when loading ``.env`` and
 ``.flaskenv`` files to allow to use non-ASCII characters. :issue:`3931`
-   ``flask shell`` sets up tab and history completion like the default
 ``python`` shell if ``readline`` is installed. :issue:`3941`
-   ``helpers.total_seconds()`` is deprecated. Use
 ``timedelta.total_seconds()`` instead. :pr:`3962`
-   Add type hinting. :pr:`3973`.

1.1.4

-------------

Released 2021-05-13

-   Update ``static_folder`` to use ``_compat.fspath`` instead of
 ``os.fspath`` to continue supporting Python < 3.6 :issue:`4050`

1.1.3

-------------

Released 2021-05-13

-   Set maximum versions of Werkzeug, Jinja, Click, and ItsDangerous.
 :issue:`4043`
-   Re-add support for passing a ``pathlib.Path`` for ``static_folder``.
 :pr:`3579`

Links

• PyPI: https://pypi.org/project/flask
• Changelog: https://pyup.io/changelogs/flask/
• Homepage: https://palletsprojects.com/p/flask

Update Flask-Admin from 1.5.7 to 1.5.8.

Changelog

1.5.8

-----

* SQLAlchemy 1.4.5+ compatibility fixes
* Redis CLI fixes

Links

• PyPI: https://pypi.org/project/flask-admin
• Changelog: https://pyup.io/changelogs/flask-admin/
• Repo: https://github.com/flask-admin/flask-admin/
• Docs: https://pythonhosted.org/Flask-Admin/

Update Flask-SQLAlchemy from 2.4.4 to 2.5.1.

Changelog

2.5.1

-------------

Released 2021-03-18

-   Fix compatibility with Python 2.7.

2.5.0

-------------

Released 2021-03-18

-   Update to support SQLAlchemy 1.4.
-   SQLAlchemy ``URL`` objects are immutable. Some internal methods have
 changed to return a new URL instead of ``None``. :issue:`885`

Links

• PyPI: https://pypi.org/project/flask-sqlalchemy
• Changelog: https://pyup.io/changelogs/flask-sqlalchemy/
• Repo: https://github.com/pallets/flask-sqlalchemy
• Docs: https://pythonhosted.org/Flask-SQLAlchemy/

Update SQLAlchemy from 1.3.20 to 1.4.22.

Changelog

1.4.22

:released: July 21, 2021

 .. change::
     :tags: bug, sql
     :tickets: 6786

     Fixed issue where use of the :paramref:`_sql.case.whens` parameter passing
     a dictionary positionally and not as a keyword argument would emit a 2.0
     deprecation warning, referring to the deprecation of passing a list
     positionally. The dictionary format of "whens", passed positionally, is
     still supported and was accidentally marked as deprecated.


 .. change::
     :tags: bug, orm
     :tickets: 6775

     Fixed issue in new :meth:`_schema.Table.table_valued` method where the
     resulting :class:`_sql.TableValuedColumn` construct would not respond
     correctly to alias adaptation as is used throughout the ORM, such as for
     eager loading, polymorphic loading, etc.


 .. change::
     :tags: bug, orm
     :tickets: 6769

     Fixed issue where usage of the :meth:`_result.Result.unique` method with an
     ORM result that included column expressions with unhashable types, such as
     ``JSON`` or ``ARRAY`` using non-tuples would silently fall back to using
     the ``id()`` function, rather than raising an error. This now raises an
     error when the :meth:`_result.Result.unique` method is used in a 2.0 style
     ORM query. Additionally, hashability is assumed to be True for result
     values of unknown type, such as often happens when using SQL functions of
     unknown return type; if values are truly not hashable then the ``hash()``
     itself will raise.

     For legacy ORM queries, since the legacy :class:`_orm.Query` object
     uniquifies in all cases, the old rules remain in place, which is to use
     ``id()`` for result values of unknown type as this legacy uniquing is
     mostly for the purpose of uniquing ORM entities and not column values.

 .. change::
     :tags: orm, bug
     :tickets: 6771

     Fixed an issue where clearing of mappers during things like test suite
     teardowns could cause a "dictionary changed size" warning during garbage
     collection, due to iteration of a weak-referencing dictionary. A ``list()``
     has been applied to prevent concurrent GC from affecting this operation.

 .. change::
     :tags: bug, sql
     :tickets: 6770

     Fixed issue where type-specific bound parameter handlers would not be
     called upon in the case of using the :meth:`_sql.Insert.values` method with
     the Python ``None`` value; in particular, this would be noticed when using
     the :class:`_types.JSON` datatype as well as related PostgreSQL specific
     types such as :class:`_postgresql.JSONB` which would fail to encode the
     Python ``None`` value into JSON null, however the issue was generalized to
     any bound parameter handler in conjunction with this specific method of
     :class:`_sql.Insert`.


 .. change::
     :tags: bug, engine
     :tickets: 6740

     Added some guards against ``KeyError`` in the event system to accommodate
     the case that the interpreter is shutting down at the same time
     :meth:`_engine.Engine.dispose` is being called, which would cause stack
     trace warnings.


 .. change::
     :tags: bug, orm, regression
     :tickets: 6793

     Fixed critical caching issue where the ORM's persistence feature using
     INSERT..RETURNING would cache an incorrect query when mixing the "bulk
     save" and standard "flush" forms of INSERT.

.. changelog::

1.4.21

:released: July 14, 2021

 .. change::
     :tags: usecase, orm
     :tickets: 6708

     Modified the approach used for history tracking of scalar object
     relationships that are not many-to-one, i.e. one-to-one relationships that
     would otherwise be one-to-many. When replacing a one-to-one value, the
     "old" value that would be replaced is no longer loaded immediately, and is
     instead handled during the flush process. This eliminates an historically
     troublesome lazy load that otherwise often occurs when assigning to a
     one-to-one attribute, and is particularly troublesome when using
     "lazy='raise'" as well as asyncio use cases.

     This change does cause a behavioral change within the
     :meth:`_orm.AttributeEvents.set` event, which is nonetheless currently
     documented, which is that the event applied to such a one-to-one attribute
     will no longer receive the "old" parameter if it is unloaded and the
     :paramref:`_orm.relationship.active_history` flag is not set. As is
     documented in :meth:`_orm.AttributeEvents.set`, if the event handler needs
     to receive the "old" value when the event fires off, the active_history
     flag must be established either with the event listener or with the
     relationship. This is already the behavior with other kinds of attributes
     such as many-to-one and column value references.

     The change additionally will defer updating a backref on the "old" value
     in the less common case that the "old" value is locally present in the
     session, but isn't loaded on the relationship in question, until the
     next flush occurs.  If this causes an issue, again the normal
     :paramref:`_orm.relationship.active_history` flag can be set to ``True``
     on the relationship.

 .. change::
     :tags: usecase, sql
     :tickets: 6752

     Added new method :meth:`_sql.HasCTE.add_cte` to each of the
     :func:`_sql.select`, :func:`_sql.insert`, :func:`_sql.update` and
     :func:`_sql.delete` constructs. This method will add the given
     :class:`_sql.CTE` as an "independent" CTE of the statement, meaning it
     renders in the WITH clause above the statement unconditionally even if it
     is not otherwise referenced in the primary statement. This is a popular use
     case on the PostgreSQL database where a CTE is used for a DML statement
     that runs against database rows independently of the primary statement.

 .. change::
     :tags: bug, postgresql
     :tickets: 6755

     Fixed issue in :meth:`_postgresql.Insert.on_conflict_do_nothing` and
     :meth:`_postgresql.Insert.on_conflict_do_update` where the name of a unique
     constraint passed as the ``constraint`` parameter would not be properly
     truncated for length if it were based on a naming convention that generated
     a too-long name for the PostgreSQL max identifier length of 63 characters,
     in the same way which occurs within a CREATE TABLE statement.

 .. change::
     :tags: bug, sql
     :tickets: 6710

     Fixed issue in CTE constructs where a recursive CTE that referred to a
     SELECT that has duplicate column names, which are typically deduplicated
     using labeling logic in 1.4, would fail to refer to the deduplicated label
     name correctly within the WITH clause.

 .. change::
     :tags: bug, regression, mssql
     :tickets: 6697

     Fixed regression where the special dotted-schema name handling for the SQL
     Server dialect would not function correctly if the dotted schema name were
     used within the ``schema_translate_map`` feature.

 .. change::
     :tags: orm, regression
     :tickets: 6718

     Fixed ORM regression where ad-hoc label names generated for hybrid
     properties and potentially other similar types of ORM-enabled expressions
     would usually be propagated outwards through subqueries, allowing the name
     to be retained in the final keys of the result set even when selecting from
     subqueries. Additional state is now tracked in this case that isn't lost
     when a hybrid is selected out of a Core select / subquery.


 .. change::
     :tags: bug, postgresql
     :tickets: 6739

     Fixed issue where the PostgreSQL ``ENUM`` datatype as embedded in the
     ``ARRAY`` datatype would fail to emit correctly in create/drop when the
     ``schema_translate_map`` feature were also in use. Additionally repairs a
     related issue where the same ``schema_translate_map`` feature would not
     work for the ``ENUM`` datatype in combination with a ``CAST``, that's also
     intrinsic to how the ``ARRAY(ENUM)`` combination works on the PostgreSQL
     dialect.


 .. change::
     :tags: bug, sql, regression
     :tickets: 6735

     Fixed regression where the :func:`_sql.tablesample` construct would fail to
     be executable when constructed given a floating-point sampling value not
     embedded within a SQL function.

 .. change::
     :tags: bug, postgresql
     :tickets: 6696

     Fixed issue in :meth:`_postgresql.Insert.on_conflict_do_nothing` and
     :meth:`_postgresql.Insert.on_conflict_do_update` where the name of a unique
     constraint passed as the ``constraint`` parameter would not be properly
     quoted if it contained characters which required quoting.


 .. change::
     :tags: bug, regression, orm
     :tickets: 6698

     Fixed regression caused in 1.4.19 due to :ticket:`6503` and related
     involving :meth:`_orm.Query.with_entities` where the new structure used
     would be inappropriately transferred to an enclosing :class:`_orm.Query`
     when making use of set operations such as :meth:`_orm.Query.union`, causing
     the JOIN instructions within to be applied to the outside query as well.

 .. change::
     :tags: bug, orm, regression
     :tickets: 6762

     Fixed regression which appeared in version 1.4.3 due to :ticket:`6060`
     where rules that limit ORM adaptation of derived selectables interfered
     with other ORM-adaptation based cases, in this case when applying
     adaptations for a :func:`_orm.with_polymorphic` against a mapping which
     uses a :func:`_orm.column_property` which in turn makes use of a scalar
     select that includes a :func:`_orm.aliased` object of the mapped table.

.. changelog::

1.4.20

:released: June 28, 2021

 .. change::
     :tags: bug, regression, orm
     :tickets: 6680

     Fixed regression in ORM regarding an internal reconstitution step for the
     :func:`_orm.with_polymorphic` construct, when the user-facing object is
     garbage collected as the query is processed. The reconstitution was not
     ensuring the sub-entities for the "polymorphic" case were handled, leading
     to an ``AttributeError``.

 .. change::
     :tags: usecase, sql
     :tickets: 6646

     Add a impl parameter to :class:`_types.PickleType` constructor, allowing
     any arbitary type to be used in place of the default implementation of
     :class:`_types.LargeBinary`. Pull request courtesy jason3gb.

 .. change::
     :tags: bug, engine
     :tickets: 5348

     Fixed an issue in the C extension for the :class:`_result.Row` class which
     could lead to a memory leak in the unlikely case of a :class:`_result.Row`
     object which referred to an ORM object that then was mutated to refer back
     to the ``Row`` itself, creating a cycle. The Python C APIs for tracking GC
     cycles has been added to the native :class:`_result.Row` implementation to
     accommodate for this case.


 .. change::
     :tags: bug, engine
     :tickets: 6665

     Fixed old issue where a :func:`_sql.select()` made against the token "*",
     which then yielded exactly one column, would fail to correctly organize the
     ``cursor.description`` column name into the keys of the result object.



 .. change::
     :tags: usecase, mysql
     :tickets: 6659

     Made a small adjustment in the table reflection feature of the MySQL
     dialect to accommodate for alternate MySQL-oriented databases such as TiDB
     which include their own "comment" directives at the end of a constraint
     directive within "CREATE TABLE" where the format doesn't have the
     additional space character after the comment, in this case the TiDB
     "clustered index" feature. Pull request courtesy Daniël van Eeden.

 .. change::
     :tags: bug, schema
     :tickets: 6685

     Fixed issue where passing ``None`` for the value of
     :paramref:`_schema.Table.prefixes` would not store an empty list, but
     rather the constant ``None``, which may be unexpected by third party
     dialects. The issue is revealed by a usage in recent versions of Alembic
     that are passing ``None`` for this value. Pull request courtesy Kai
     Mueller.

 .. change::
     :tags: bug, regression, ext
     :tickets: 6679

     Fixed regression in :mod:`sqlalchemy.ext.automap` extension such that the
     use case of creating an explicit mapped class to a table that is also the
     :paramref:`_orm.relationship.secondary` element of a
     :func:`_orm.relationship` that automap will be generating would emit the
     "overlaps" warnings introduced in 1.4 and discussed at :ref:`error_qzyx`.
     While generating this case from automap is still subject to the same
     caveats that the "overlaps" warning refers towards, as automap is intended
     for more ad-hoc use cases, the condition which produces the warning is
     disabled when a many-to-many relationship with this particular pattern is
     generated.



 .. change::
     :tags: bug, regression, orm
     :tickets: 6678

     Adjusted :meth:`_orm.Query.union` and similar set operations to be
     correctly compatible with the new capabilities just added in
     :ticket:`6661`, with SQLAlchemy 1.4.19, such that the SELECT statements
     rendered as elements of the UNION or other set operation will include
     directly mapped columns that are mapped as deferred; this both fixes a
     regression involving unions with multiple levels of nesting that would
     produce a column mismatch, and also allows the :func:`_orm.undefer` option
     to be used at the top level of such a :class:`_orm.Query` without having to
     apply the option to each of the elements within the UNION.

 .. change::
     :tags: bug, sql, orm
     :tickets: 6668

     Fixed the class hierarchy for the :class:`_schema.Sequence` and the more
     general :class:`_schema.DefaultGenerator` base, as these are "executable"
     as statements they need to include :class:`_sql.Executable` in their
     hierarchy, not just :class:`_roles.StatementRole` as was applied
     arbitrarily to :class:`_schema.Sequence` previously. The fix allows
     :class:`_schema.Sequence` to work in all ``.execute()`` methods including
     with :meth:`_orm.Session.execute` which was not working in the case that a
     :meth:`_orm.SessionEvents.do_orm_execute` handler was also established.


 .. change::
     :tags: bug, orm
     :tickets: 6538

     Adjusted the check in the mapper for a callable object that is used as a
     ``validates`` validator function or a ``reconstructor`` reconstruction
     function, to check for "callable" more liberally such as to accommodate
     objects based on fundamental attributes like ``__func__`` and
     ``__call___``, rather than testing for ``MethodType`` / ``FunctionType``,
     allowing things like cython functions to work properly. Pull request
     courtesy Miłosz Stypiński.

.. changelog::

1.4.19

:released: June 22, 2021

 .. change::
     :tags: bug, mssql
     :tickets: 6658

     Fixed bug where the "schema_translate_map" feature would fail to function
     correctly in conjunction with an INSERT into a table that has an IDENTITY
     column, where the value of the IDENTITY column were specified in the values
     of the INSERT thus triggering SQLAlchemy's feature of setting IDENTITY
     INSERT to "on"; it's in this directive where the schema translate map would
     fail to be honored.


 .. change::
     :tags: bug, sql
     :tickets: 6663

     Fixed issue in CTE constructs mostly relevant to ORM use cases where a
     recursive CTE against "anonymous" labels such as those seen in ORM
     ``column_property()`` mappings would render in the
     ``WITH RECURSIVE xyz(...)`` section as their raw internal label and not a
     cleanly anonymized name.

 .. change::
     :tags: mssql, change
     :tickets: 6503, 6253

     Made improvements to the server version regexp used by the pymssql dialect
     to prevent a regexp overflow in case of an invalid version string.

 .. change::
     :tags: bug, orm, regression
     :tickets: 6503, 6253

     Fixed further regressions in the same area as that of :ticket:`6052` where
     loader options as well as invocations of methods like
     :meth:`_orm.Query.join` would fail if the left side of the statement for
     which the option/join depends upon were replaced by using the
     :meth:`_orm.Query.with_entities` method, or when using 2.0 style queries
     when using the :meth:`_sql.Select.with_only_columns` method. A new set of
     state has been added to the objects which tracks the "left" entities that
     the options / join were made against which is memoized when the lead
     entities are changed.

 .. change::
     :tags: bug, asyncio, postgresql
     :tickets: 6652

     Fixed bug in asyncio implementation where the greenlet adaptation system
     failed to propagate ``BaseException`` subclasses, most notably including
     ``asyncio.CancelledError``, to the exception handling logic used by the
     engine to invalidate and clean up the connection, thus preventing
     connections from being correctly disposed when a task was cancelled.



 .. change::
     :tags: usecase, asyncio
     :tickets: 6583

     Implemented :class:`_asyncio.async_scoped_session` to address some
     asyncio-related incompatibilities between :class:`_orm.scoped_session` and
     :class:`_asyncio.AsyncSession`, in which some methods (notably the
     :meth:`_asyncio.async_scoped_session.remove` method) should be used with
     the ``await`` keyword.

     .. seealso::

         :ref:`asyncio_scoped_session`

 .. change::
     :tags: usecase, mysql
     :tickets: 6132

     Added new construct :class:`_mysql.match`, which provides for the full
     range of MySQL's MATCH operator including multiple column support and
     modifiers. Pull request courtesy Anton Kovalevich.

     .. seealso::

         :class:`_mysql.match`

 .. change::
     :tags: bug, postgresql, oracle
     :tickets: 6649

     Fixed issue where the ``INTERVAL`` datatype on PostgreSQL and Oracle would
     produce an ``AttributeError`` when used in the context of a comparison
     operation against a ``timedelta()`` object. Pull request courtesy
     MajorDallas.

 .. change::
     :tags: bug, mypy
     :tickets: 6476

     Fixed issue in mypy plugin where class info for a custom declarative base
     would not be handled correctly on a cached mypy pass, leading to an
     AssertionError being raised.

 .. change::
     :tags: bug, orm
     :tickets: 6661

     Refined the behavior of ORM subquery rendering with regards to deferred
     columns and column properties to be more compatible with that of 1.3 while
     also providing for 1.4's newer features. As a subquery in 1.4 does not make
     use of loader options, including :func:`_orm.undefer`, a subquery that is
     against an ORM entity with deferred attributes will now render those
     deferred attributes that refer directly to mapped table columns, as these
     are needed in the outer SELECT if that outer SELECT makes use of these
     columns; however a deferred attribute that refers to a composed SQL
     expression as we normally do with :func:`_orm.column_property` will not be
     part of the subquery, as these can be selected explicitly if needed in the
     subquery. If the entity is being SELECTed from this subquery, the column
     expression can still render on "the outside" in terms of the derived
     subquery columns. This produces essentially the same behavior as when
     working with 1.3. However in this case the fix has to also make sure that
     the ``.selected_columns`` collection of an ORM-enabled :func:`_sql.select`
     also follows these rules, which in particular allows recursive CTEs to
     render correctly in this scenario, which were previously failing to render
     correctly due to this issue.

 .. change::
     :tags: bug, postgresql
     :tickets: 6621

     Fixed issue where the pool "pre ping" feature would implicitly start a
     transaction, which would then interfere with custom transactional flags
     such as PostgreSQL's "read only" mode when used with the psycopg2 driver.


.. changelog::

1.4.18

:released: June 10, 2021

 .. change::
     :tags: bug, orm
     :tickets: 6072, 6487

     Clarified the current purpose of the
     :paramref:`_orm.relationship.bake_queries` flag, which in 1.4 is to enable
     or disable "lambda caching" of statements within the "lazyload" and
     "selectinload" loader strategies; this is separate from the more
     foundational SQL query cache that is used for most statements.
     Additionally, the lazy loader no longer uses its own cache for many-to-one
     SQL queries, which was an implementation quirk that doesn't exist for any
     other loader scenario. Finally, the "lru cache" warning that the lazyloader
     and selectinloader strategies could emit when handling a wide array of
     class/relationship combinations has been removed; based on analysis of some
     end-user cases, this warning doesn't suggest any significant issue. While
     setting ``bake_queries=False`` for such a relationship will remove this
     cache from being used, there's no particular performance gain in this case
     as using no caching vs. using a cache that needs to refresh often likely
     still wins out on the caching being used side.


 .. change::
     :tags: bug, asyncio
     :tickets: 6575

     Fixed an issue that presented itself when using the :class:`_pool.NullPool`
     or the :class:`_pool.StaticPool` with an async engine. This mostly affected
     the aiosqlite dialect.

 .. change::
     :tags: bug, sqlite, regression
     :tickets: 6586

     The fix for pysqlcipher released in version 1.4.3 :ticket:`5848` was
     unfortunately non-working, in that the new ``on_connect_url`` hook was
     erroneously not receiving a ``URL`` object under normal usage of
     :func:`_sa.create_engine` and instead received a string that was unhandled;
     the test suite failed to fully set up the actual conditions under which
     this hook is called. This has been fixed.

 .. change::
     :tags: bug, postgresql, regression
     :tickets: 6581

     Fixed regression where using the PostgreSQL "INSERT..ON CONFLICT" structure
     would fail to work with the psycopg2 driver if it were used in an
     "executemany" context along with bound parameters in the "SET" clause, due
     to the implicit use of the psycopg2 fast execution helpers which are not
     appropriate for this style of INSERT statement; as these helpers are the
     default in 1.4 this is effectively a regression.  Additional checks to
     exclude this kind of statement from that particular extension have been
     added.

 .. change::
     :tags: bug, orm, regression
     :tickets: 6285

     Adjusted the means by which classes such as :class:`_orm.scoped_session`
     and :class:`_asyncio.AsyncSession` are generated from the base
     :class:`_orm.Session` class, such that custom :class:`_orm.Session`
     subclasses such as that used by Flask-SQLAlchemy don't need to implement
     positional arguments when they call into the superclass method, and can
     continue using the same argument styles as in previous releases.

 .. change::
     :tags: bug, orm, regression
     :tickets: 6595

     Fixed issue where query production for joinedload against a complex left
     hand side involving joined-table inheritance could fail to produce a
     correct query, due to a clause adaption issue.

 .. change::
     :tags: bug, orm, regression, performance
     :tickets: 6596

     Fixed regression involving how the ORM would resolve a given mapped column
     to a result row, where under cases such as joined eager loading, a slightly
     more expensive "fallback" could take place to set up this resolution due to
     some logic that was removed since 1.3. The issue could also cause
     deprecation warnings involving column resolution to be emitted when using a
     1.4 style query with joined eager loading.

 .. change::
     :tags: bug, orm
     :tickets: 6591

     Fixed issue in experimental "select ORM objects from INSERT/UPDATE" use
     case where an error was raised if the statement were against a
     single-table-inheritance subclass.

 .. change::
     :tags: bug, asyncio
     :tickets: 6592

     Added ``asyncio.exceptions.TimeoutError``,
     ``asyncio.exceptions.CancelledError`` as so-called "exit exceptions", a
     class of exceptions that include things like ``GreenletExit`` and
     ``KeyboardInterrupt``, which are considered to be events that warrant
     considering a DBAPI connection to be in an unusable state where it should
     be recycled.

 .. change::
     :tags: bug, orm
     :tickets: 6400

     The warning that's emitted for :func:`_orm.relationship` when multiple
     relationships would overlap with each other as far as foreign key
     attributes written towards, now includes the specific "overlaps" argument
     to use for each warning in order to silence the warning without changing
     the mapping.

 .. change::
     :tags: usecase, asyncio
     :tickets: 6319

     Implemented a new registry architecture that allows the ``Async`` version
     of an object, like ``AsyncSession``, ``AsyncConnection``, etc., to be
     locatable given the proxied "sync" object, i.e. ``Session``,
     ``Connection``. Previously, to the degree such lookup functions were used,
     an ``Async`` object would be re-created each time, which was less than
     ideal as the identity and state of the "async" object would not be
     preserved across calls.

     From there, new helper functions :func:`_asyncio.async_object_session`,
     :func:`_asyncio.async_session` as well as a new :class:`_orm.InstanceState`
     attribute :attr:`_orm.InstanceState.async_session` have been added, which
     are used to retrieve the original :class:`_asyncio.AsyncSession` associated
     with an ORM mapped object, a :class:`_orm.Session` associated with an
     :class:`_asyncio.AsyncSession`, and an :class:`_asyncio.AsyncSession`
     associated with an :class:`_orm.InstanceState`, respectively.

     This patch also implements new methods
     :meth:`_asyncio.AsyncSession.in_nested_transaction`,
     :meth:`_asyncio.AsyncSession.get_transaction`,
     :meth:`_asyncio.AsyncSession.get_nested_transaction`.

.. changelog::

1.4.17

:released: May 29, 2021

 .. change::
     :tags: bug, orm, regression
     :tickets: 6558

     Fixed regression caused by just-released performance fix mentioned in 6550
     where a query.join() to a relationship could produce an AttributeError if
     the query were made against non-ORM structures only, a fairly unusual
     calling pattern.

.. changelog::

1.4.16

:released: May 28, 2021

 .. change::
     :tags: bug, engine
     :tickets: 6482

     Fixed issue where an ` sign in the database portion of a URL would not
     be interpreted correctly if the URL also had a username:password section.


 .. change::
     :tags: bug, ext
     :tickets: 6529

     Fixed a deprecation warning that was emitted when using
     :func:`_automap.automap_base` without passing an existing
     ``Base``.


 .. change::
     :tags: bug, pep484
     :tickets: 6461

     Remove pep484 types from the code.
     Current effort is around the stub package, and having typing in
     two places makes thing worse, since the types in the SQLAlchemy
     source were usually outdated compared to the version in the stubs.

 .. change::
     :tags: usecase, mssql
     :tickets: 6464

     Implemented support for a :class:`_sql.CTE` construct to be used directly
     as the target of a :func:`_sql.delete` construct, i.e. "WITH ... AS cte
     DELETE FROM cte". This appears to be a useful feature of SQL Server.

 .. change::
     :tags: bug, general
     :tickets: 6540, 6543

     Resolved various deprecation warnings which were appearing as of Python
     version 3.10.0b1.

 .. change::
     :tags: bug, orm
     :tickets: 6471

     Fixed issue when using :paramref:`_orm.relationship.cascade_backrefs`
     parameter set to ``False``, which per :ref:`change_5150` is set to become
     the standard behavior in SQLAlchemy 2.0, where adding the item to a
     collection that uniquifies, such as ``set`` or ``dict`` would fail to fire
     a cascade event if the object were already associated in that collection
     via the backref. This fix represents a fundamental change in the collection
     mechanics by introducing a new event state which can fire off for a
     collection mutation even if there is no net change on the collection; the
     action is now suited using a new event hook
     :meth:`_orm.AttributeEvents.append_wo_mutation`.



 .. change::
     :tags: bug, orm, regression
     :tickets: 6550

     Fixed regression involving clause adaption of labeled ORM compound
     elements, such as single-table inheritance discriminator expressions with
     conditionals or CASE expressions, which could cause aliased expressions
     such as those used in ORM join / joinedload operations to not be adapted
     correctly, such as referring to the wrong table in the ON clause in a join.

     This change also improves a performance bump that was located within the
     process of invoking :meth:`_sql.Select.join` given an ORM attribute
     as a target.

 .. change::
     :tags: bug, orm, regression
     :tickets: 6495

     Fixed regression where the full combination of joined inheritance, global
     with_polymorphic, self-referential relationship and joined loading would
     fail to be able to produce a query with the scope of lazy loads and object
     refresh operations that also attempted to render the joined loader.

 .. change::
     :tags: bug, engine
     :tickets: 6329

     Fixed a long-standing issue with :class:`.URL` where query parameters
     following the question mark would not be parsed correctly if the URL did
     not contain a database portion with a backslash.

 .. change::
     :tags: bug, sql, regression
     :tickets: 6549

     Fixed regression in dynamic loader strategy and :func:`_orm.relationship`
     overall where the :paramref:`_orm.relationship.order_by` parameter were
     stored as a mutable list, which could then be mutated when combined with
     additional "order_by" methods used against the dynamic query object,
     causing the ORDER BY criteria to continue to grow repetitively.

 .. change::
     :tags: bug, orm
     :tickets: 6484

     Enhanced the bind resolution rules for :meth:`_orm.Session.execute` so that
     when a non-ORM statement such as an :func:`_sql.insert` construct
     nonetheless is built against ORM objects, to the greatest degree possible
     the ORM entity will be used to resolve the bind, such as for a
     :class:`_orm.Session` that has a bind map set up on a common superclass
     without specific mappers or tables named in the map.

 .. change::
     :tags: bug, regression, ext
     :tickets: 6390

     Fixed regression in the ``sqlalchemy.ext.instrumentation`` extension that
     prevented instrumentation disposal from working completely. This fix
     includes both a 1.4 regression fix as well as a fix for a related issue
     that existed in 1.3 also.   As part of this change, the
     :class:`sqlalchemy.ext.instrumentation.InstrumentationManager` class now
     has a new method ``unregister()``, which replaces the previous method
     ``dispose()``, which was not called as of version 1.4.


.. changelog::

1.4.15

:released: May 11, 2021

 .. change::
     :tags: bug, documentation, mysql
     :tickets: 5397

     Added support for the ``ssl_check_hostname=`` parameter in mysql connection
     URIs and updated the mysql dialect documentation regarding secure
     connections. Original pull request courtesy of Jerry Zhao.

 .. change::
     :tags: bug, orm, regression
     :tickets: 6449

     Fixed additional regression caused by "eager loaders run on unexpire"
     feature :ticket:`1763` where the feature would run for a
     ``contains_eager()`` eagerload option in the case that the
     ``contains_eager()`` were chained to an additional eager loader option,
     which would then produce an incorrect query as the original query-bound
     join criteria were no longer present.

 .. change::
     :tags: feature, general
     :tickets: 6241

     A new approach has been applied to the warnings system in SQLAlchemy to
     accurately predict the appropriate stack level for each warning
     dynamically. This allows evaluating the source of SQLAlchemy-generated
     warnings and deprecation warnings to be more straightforward as the warning
     will indicate the source line within end-user code, rather than from an
     arbitrary level within SQLAlchemy's own source code.

 .. change::
     :tags: bug, orm
     :tickets: 6459

     Fixed issue in subquery loader strategy which prevented caching from
     working correctly. This would have been seen in the logs as a "generated"
     message instead of "cached" for all subqueryload SQL emitted, which by
     saturating the cache with new keys would degrade overall performance; it
     also would produce "LRU size alert" warnings.


 .. change::
     :tags: bug, sql
     :tickets: 6460

     Adjusted the logic added as part of :ticket:`6397` in 1.4.12 so that
     internal mutation of the :class:`.BindParameter` object occurs within the
     clause construction phase as it did before, rather than in the compilation
     phase. In the latter case, the mutation still produced side effects against
     the incoming construct and additionally could potentially interfere with
     other internal mutation routines.

.. changelog::

1.4.14

:released: May 6, 2021

 .. change::
     :tags: bug, regression, orm
     :tickets: 6426

     Fixed regression involving ``lazy='dynamic'`` loader in conjunction with a
     detached object. The previous behavior was that the dynamic loader upon
     calling methods like ``.all()`` returns empty lists for detached objects
     without error, this has been restored; however a warning is now emitted as
     this is not the correct result. Other dynamic loader scenarios correctly
     raise ``DetachedInstanceError``.

 .. change::
     :tags: bug, regression, sql
     :tickets: 6428

     Fixed regression caused by the "empty in" change just made in
     :ticket:`6397` 1.4.12 where the expression needs to be parenthesized for
     the "not in" use case, otherwise the condition will interfere with the
     other filtering criteria.


 .. change::
     :tags: bug, sql, regression
     :tickets: 6436

     The :class:`.TypeDecorator` class will now emit a warning when used in SQL
     compilation with caching unless the ``.cache_ok`` flag is set to ``True``
     or ``False``. A new class-level attribute :attr:`.TypeDecorator.cache_ok`
     may be set which will be used as an indication that all the parameters
     passed to the object are safe to be used as a cache key if set to ``True``,
     ``False`` means they are not.

 .. change::
     :tags: engine, bug, regression
     :tickets: 6427

     Established a deprecation path for calling upon the
     :meth:`_cursor.CursorResult.keys` method for a statement that returns no
     rows to provide support for legacy patterns used by the "records" package
     as well as any other non-migrated applications. Previously, this would
     raise :class:`.ResourceClosedException` unconditionally in the same way as
     it does when attempting to fetch rows. While this is the correct behavior
     going forward, the :class:`_cursor.LegacyCursorResult` object will now in
     this case return an empty list for ``.keys()`` as it did in 1.3, while also
     emitting a 2.0 deprecation warning. The :class:`_cursor.CursorResult`, used
     when using a 2.0-style "future" engine, will continue to raise as it does
     now.

 .. change::
     :tags: usecase, engine, orm
     :tickets: 6288

     Applied consistent behavior to the use case of
     calling ``.commit()`` or ``.rollback()`` inside of an existing
     ``.begin()`` context manager, with the addition of potentially
     emitting SQL within the block subsequent to the commit or rollback.
     This change continues upon the change first added in
     :ticket:`6155` where the use case of calling "rollback" inside of
     a ``.begin()`` contextmanager block was proposed:

     * calling ``.commit()`` or ``.rollback()`` will now be allowed
       without error or warning within all scopes, including
       that of legacy and future :class:`_engine.Engine`, ORM
       :class:`_orm.Session`, asyncio :class:`.AsyncEngine`.  Previously,
       the :class:`_orm.Session` disallowed this.

     * The remaining scope of the context manager is then closed;
       when the block ends, a check is emitted to see if the transaction
       was already ended, and if so the block returns without action.

     * It will now raise **an error** if subsequent SQL of any kind
       is emitted within the block, **after** ``.commit()`` or
       ``.rollback()`` is called.   The block should be closed as
       the state of the executable object would otherwise be undefined
       in this state.

.. changelog::

1.4.13

:released: May 3, 2021

 .. change::
     :tags: bug, regression, orm
     :tickets: 6410

     Fixed regression in ``selectinload`` loader strategy that would cause it to
     cache its internal state incorrectly when handling relationships that join
     across more than one column, such as when using a composite foreign key.
     The invalid caching would then cause other unrelated loader operations to
     fail.


 .. change::
     :tags: bug, orm, regression
     :tickets: 6414

     Fixed regression where :meth:`_orm.Query.filter_by` would not work if the
     lead entity were a SQL function or other expression derived from the
     primary entity in question, rather than a simple entity or column of that
     entity. Additionally, improved the behavior of
     :meth:`_sql.Select.filter_by` overall to work with column expressions even
     in a non-ORM context.

 .. change::
     :tags: bug, engine, regression
     :tickets: 6408

     Restored a legacy transactional behavior that was inadvertently removed
     from the :class:`_engine.Connection` as it was never tested as a known use
     case in previous versions, where calling upon the
     :meth:`_engine.Connection.begin_nested` method, when no transaction is
     present, does not create a SAVEPOINT at all and instead starts an outer
     transaction, returning a :class:`.RootTransaction` object instead of a
     :class:`.NestedTransaction` object.  This :class:`.RootTransaction` then
     will emit a real COMMIT on the database connection when committed.
     Previously, the 2.0 style behavior was present in all cases that would
     autobegin a transaction but not commit it, which is a behavioral change.

     When using a :term:`2.0 style` connection object, the behavior is unchanged
     from previous 1.4 versions; calling :meth:`_future.Connection.begin_nested`
     will "autobegin" the outer transaction if not already present, and then as
     instructed emit a SAVEPOINT, returning the :class:`.NestedTransaction`
     object. The outer transaction is committed by calling upon
     :meth:`_future.Connection.commit`, as is "commit-as-you-go" style usage.

     In non-"future" mode, while the old behavior is restored, it also
     emits a 2.0 deprecation warning as this is a legacy behavior.


 .. change::
     :tags: bug, asyncio, regression
     :tickets: 6409

     Fixed a regression introduced by :ticket:`6337` that would create an
     ``asyncio.Lock`` which could be attached to the wrong loop when
     instantiating the async engine before any asyncio loop was started, leading
     to an asyncio error message when attempting to use the engine under certain
     circumstances.

 .. change::
     :tags: bug, orm, regression
     :tickets: 6419

     Fixed regression where using :func:`_orm.selectinload` and
     :func:`_orm.subqueryload` to load a two-level-deep path would lead to an
     attribute error.

 .. change::
     :tags: bug, orm, regression
     :tickets: 6420

     Fixed regression where using the :func:`_orm.noload` loader strategy in
     conjunction with a "dynamic" relationship would lead to an attribute error
     as the noload strategy would attempt to apply itself to the dynamic loader.

 .. change::
     :tags: usecase, postgresql
     :tickets: 6198

     Add support for server side cursors in the pg8000 dialect for PostgreSQL.
     This allows use of the
     :paramref:`.Connection.execution_options.stream_results` option.

.. changelog::

1.4.12

:released: April 29, 2021

 .. change::
     :tags: bug, orm, regression, caching
     :tickets: 6391

     Fixed critical regression where bound parameter tracking as used in the SQL
     caching system could fail to track all parameters for the case where the
     same SQL expression containing a parameter were used in an ORM-related
     query using a feature such as class inheritance, which was then embedded in
     an enclosing expression which would make use of that same expression
     multiple times, such as a UNION. The ORM would individually copy the
     individual SELECT statements as part of compilation with class inheritance,
     which then embedded in the enclosing statement would fail to accommodate
     for all parameters. The logic that tracks this condition has been adjusted
     to work for multiple copies of a parameter.

 .. change::
     :tags: bug, sql
     :tickets: 6258, 6397

     Revised the "EMPTY IN" expression to no longer rely upon using a subquery,
     as this was causing some compatibility and performance problems. The new
     approach for selected databases takes advantage of using a NULL-returning
     IN expression combined with the usual "1 != 1" or "1 = 1" expression
     appended by AND or OR. The expression is now the default for all backends
     other than SQLite, which still had some compatibility issues regarding
     tuple "IN" for older SQLite versions.

     Third party dialects can still override how the "empty set" expression
     renders by implementing a new compiler method
     ``def visit_empty_set_op_expr(self, type_, expand_op)``, which takes
     precedence over the existing
     ``def visit_empty_set_expr(self, element_types)`` which remains in place.


 .. change::
     :tags: bug, orm
     :tickets: 6350

     Fixed two distinct issues mostly affecting
     :class:`_hybrid.hybrid_property`, which would come into play under common
     mis-configuration scenarios that were silently ignored in 1.3, and now
     failed in 1.4, where the "expression" implementation would return a non
     :class:`_sql.ClauseElement` such as a boolean value. For both issues, 1.3's
     behavior was to silently ignore the mis-configuration and ultimately
     attempt to interpret the value as a SQL expression, which would lead to an
     incorrect query.

     * Fixed issue regarding interaction of the attribute system with
       hybrid_property, where if the ``__clause_element__()`` method of the
       attribute returned a non-:class:`_sql.ClauseElement` object, an internal
       ``AttributeError`` would lead the attribute to return the ``expression``
       function on the hybrid_property itself, as the attribute error was
       against the name ``.expression`` which would invoke the ``__getattr__()``
       method as a fallback. This now raises explicitly. In 1.3 the
       non-:class:`_sql.ClauseElement` was returned directly.

     * Fixed issue in SQL argument coercions system where passing the wrong
       kind of object to methods that expect column expressions would fail if
       the object were altogether not a SQLAlchemy object, such as a Python
       function, in cases where the object were not just coerced into a bound
       value. Again 1.3 did not have a comprehensive argument coercion system
       so this case would also pass silently.


 .. change::
     :tags: bug, orm
     :tickets: 6378

     Fixed issue where using a :class:`_sql.Select` as a subquery in an ORM
     context would modify the :class:`_sql.Select` in place to disable
     eagerloads on that object, which would then cause that same
     :class:`_sql.Select` to not eagerload if it were then re-used in a
     top-level execution context.


 .. change::
     :tags: bug, regression, sql
     :tickets: 6343

     Fixed regression where usage of the :func:`_sql.text` construct inside the
     columns clause of a :class:`_sql.Select` construct, which is better handled
     by using a :func:`_sql.literal_column` construct, would nonetheless prevent
     constructs like :func:`_sql.union` from working correctly. Other use cases,
     such as constructing subuqeries, continue to work the same as in prior
     versions where the :func:`_sql.text` construct is silently omitted from the
     collection of exported columns.   Also repairs similar use within the
     ORM.


 .. change::
     :tags: bug, regression, sql
     :tickets: 6261

     Fixed regression involving legacy methods such as
     :meth:`_sql.Select.append_column` where internal assertions would fail.

 .. change::
     :tags: usecase, sqlite
     :tickets: 6379

     Default to using ``SingletonThreadPool`` for in-memory SQLite databases
     created using URI filenames. Previously the default pool used was the
     ``NullPool`` that precented sharing the same database between multiple
     engines.

 .. change::
     :tags: bug, regression, sql
     :tickets: 6300

     Fixed regression caused by :ticket:`5395` where tuning back the check for
     sequences in :func:`_sql.select` now caused failures when doing 2.0-style
     querying with a mapped class that also happens to have an ``__iter__()``
     method. Tuned the check some more to accommodate this as well as some other
     interesting ``__iter__()`` scenarios.


 .. change::
     :tags: bug, mssql, schema
     :tickets: 6345

     Add :meth:`_types.TypeEngine.as_generic` support for
     :class:`sqlalchemy.dialects.mysql.BIT` columns, mapping
     them to :class:`_sql.sqltypes.Boolean`.

 .. change::
     :tags: bug, orm, regression
     :tickets: 6360, 6359

     Fixed issue where the new :ref:`autobegin <session_autobegin>` behavior
     failed to "autobegin" in the case where an existing persistent object has
     an attribute change, which would then impact the behavior of
     :meth:`_orm.Session.rollback` in that no snapshot was created to be rolled
     back. The "attribute modify" mechanics have been updated to ensure
     "autobegin", which does not perform any database work, does occur when
     persistent attributes change in the same manner as when
     :meth:`_orm.Session.add` is called. This is a regression as in 1.3, the
     rollback() method always had a transaction to roll back and would expire
     every time.

 .. change::
     :tags: bug, mssql, regression
     :tickets: 6366

     Fixed regression caused by :ticket:`6306` which added support for
     ``DateTime(timezone=True)``, where the previous behavior of the pyodbc
     driver of implicitly dropping the tzinfo from a timezone-aware date when
     INSERTing into a timezone-naive DATETIME column were lost, leading to a SQL
     Server error when inserting timezone-aware datetime objects into
     timezone-native database columns.

 .. change::
     :tags: orm, bug, regression
     :tickets: 6386

     Fixed regression in ORM where using hybrid property to indicate an
     expression from a different entity would confuse the column-labeling logic
     in the ORM and attempt to derive the name of the hybrid from that other
     class, leading to an attribute error. The owning class of the hybrid
     attribute is now tracked along with the name.

 .. change::
     :tags: orm, bug, regression
     :tickets: 6401

     Fixed regression in hybrid_property where a hybrid against a SQL function
     would generate an ``AttributeError`` when attempting to generate an entry
     for the ``.c`` collection of a subquery in some cases; among other things
     this would impact its use in cases like that of ``Query.count()``.


 .. change::
     :tags: bug, postgresql
     :tickets: 6373

     Fixed very old issue where the :class:`_types.Enum` datatype would not
     inherit the :paramref:`_schema.MetaData.schema` parameter of a
     :class:`_schema.MetaData` object when that object were passed to the
     :class:`_types.Enum` using :paramref:`_types.Enum.metadata`.

 .. change::
     :tags: bug, orm, dataclasses
     :tickets: 6346

     Adjusted the declarative scan for dataclasses so that the inheritance
     behavior of :func:`_orm.declared_attr` established on a mixin, when using
     the new form of having it inside of a ``dataclasses.field()`` construct and
     not actually a descriptor attribute on the class, correctly accommodates
     the case when the target class to be mapped is a subclass of an existing
     mapped class which has already mapped that :func:`_orm.declared_attr`, and
     therefore should not be re-applied to this class.


 .. change::
     :tags: bug, schema, mysql, mariadb, oracle, postgresql
     :tickets: 6338

     Ensure that the MySQL and MariaDB dialect ignore the
     :class:`_sql.Identity` construct while rendering the ``AUTO_INCREMENT``
     keyword in a create table.

     The Oracle and PostgreSQL compiler was updated to not render
     :class:`_sql.Identity` if the database version does not support it
     (Oracle < 12 and PostgreSQL < 10). Previously it was rendered regardless
     of the database version.

 .. change::
     :tags: bug, orm
     :tickets: 6353

     Fixed an issue with the (deprecated in 1.4)
     :meth:`_schema.ForeignKeyConstraint.copy` method that caused an error when
     invoked with the ``schema`` argument.

 .. change::
     :tags: bug, engine
     :tickets: 6361

     Fixed issue where usage of an explicit :class:`.Sequence` would produce
     inconsistent "inline" behavior for an :class:`.Insert` construct that
     includes multiple values phrases; the first seq would be inline but
     subsequent ones would be "pre-execute", leading to inconsistent sequence
     ordering. The sequence expressions are now fully inline.

.. changelog::

1.4.11

:released: April 21, 2021

 .. change::
     :tags: bug, engine, regression
     :tickets: 6337

     Fixed critical regression caused by the change in :ticket:`5497` where the
     connection pool "init" phase no longer occurred within mutexed isolation,
     allowing other threads to proceed with the dialect uninitialized, which
     could then impact the compilation of SQL statements.


 .. change::
     :tags: bug, orm, regression, declarative
     :tickets: 6331

     Fixed regression where recent changes to support Python dataclasses had the
     inadvertent effect that an ORM mapped class could not successfully override
     the ``__new__()`` method.

.. changelog::

1.4.10

:released: April 20, 2021

 .. change::
     :tags: bug, declarative, regression
     :tickets: 6291

     Fixed :func:`_declarative.instrument_declarative` that called
     a non existing registry method.

 .. change::
     :tags: bug, orm
     :tickets: 6320

     Fixed bug in new :func:`_orm.with_loader_criteria` feature where using a
     mixin class with :func:`_orm.declared_attr` on an attribute that were
     accessed inside the custom lambda would emit a warning regarding using an
     unmapped declared attr, when the lambda callable were first initialized.
     This warning is now prevented using special instrumentation for this
     lambda initialization step.


 .. change::
     :tags: usecase, mssql
     :tickets: 6306

     The :paramref:`_types.DateTime.timezone` parameter when set to ``True``
     will now make use of the ``DATETIMEOFFSET`` column type with SQL Server
     when used to emit DDL, rather than ``DATETIME`` where the flag was silently
     ignored.

 .. change::
     :tags: orm, bug, regression
     :tickets: 6326

     Fixed additional regression caused by the "eagerloaders on refresh" feature
     added in :ticket:`1763` where the refresh operation historical

---

<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

## 📋 Pull Request Information **Original PR:** https://github.com/jeffknupp/sandman2/pull/227 **Author:** [@pyup-bot](https://github.com/pyup-bot) **Created:** 7/26/2021 **Status:** ❌ Closed **Base:** `master` ← **Head:** `pyup-scheduled-update-2021-07-26` --- ### 📝 Commits (10+) - [`b0a5aed`](https://github.com/jeffknupp/sandman2/commit/b0a5aeda767d74391e9731c3b254ca86013a3093) Update flask from 1.1.2 to 2.0.1 - [`3b2cb55`](https://github.com/jeffknupp/sandman2/commit/3b2cb557b5fd9f9a94d6d727e867ea186eda61a7) Update flask-admin from 1.5.7 to 1.5.8 - [`6b25ef4`](https://github.com/jeffknupp/sandman2/commit/6b25ef48857f51db37425c8d8227870337871ea1) Update flask-sqlalchemy from 2.4.4 to 2.5.1 - [`a3aab21`](https://github.com/jeffknupp/sandman2/commit/a3aab2131d07bbbaff4b9a5637985dbe382301b5) Update sqlalchemy from 1.3.20 to 1.4.22 - [`2273e42`](https://github.com/jeffknupp/sandman2/commit/2273e422cd92ec9bae7f4456e29a9994304f43bd) Update coverage from 5.3 to 5.5 - [`535af15`](https://github.com/jeffknupp/sandman2/commit/535af1513ebddbce8b285c37cf4f6763015af5e9) Update pytest from 6.2.0 to 6.2.4 - [`fa5076f`](https://github.com/jeffknupp/sandman2/commit/fa5076ffbb353d7ff32dc0567dae47761ed9c90f) Update flask-cors from 3.0.9 to 3.0.10 - [`fbf3c09`](https://github.com/jeffknupp/sandman2/commit/fbf3c091a73a669f13aa4d947e3c9fb191503d76) Update pytest-cov from 2.10.1 to 2.12.1 - [`300889e`](https://github.com/jeffknupp/sandman2/commit/300889ee18055a8c5324be08ebb327c2d5d00049) Update pytest-flask from 1.1.0 to 1.2.0 - [`378a2f5`](https://github.com/jeffknupp/sandman2/commit/378a2f5049c865d9d16a32ad6ecc30ea72d23d17) Update six from 1.15.0 to 1.16.0 ### 📊 Changes **1 file changed** (+12 additions, -12 deletions) <details> <summary>View changed files</summary> 📝 `requirements.txt` (+12 -12) </details> ### 📄 Description ### Update [Flask](https://pypi.org/project/Flask) from **1.1.2** to **2.0.1**. <details> <summary>Changelog</summary> ### 2.0.1 ``` ------------- Released 2021-05-21 - Re-add the ``filename`` parameter in ``send_from_directory``. The ``filename`` parameter has been renamed to ``path``, the old name is deprecated. :pr:`4019` - Mark top-level names as exported so type checking understands imports in user projects. :issue:`4024` - Fix type annotation for ``g`` and inform mypy that it is a namespace object that has arbitrary attributes. :issue:`4020` - Fix some types that weren&#39;t available in Python 3.6.0. :issue:`4040` - Improve typing for ``send_file``, ``send_from_directory``, and ``get_send_file_max_age``. :issue:`4044`, :pr:`4026` - Show an error when a blueprint name contains a dot. The ``.`` has special meaning, it is used to separate (nested) blueprint names and the endpoint name. :issue:`4041` - Combine URL prefixes when nesting blueprints that were created with a ``url_prefix`` value. :issue:`4037` - Roll back a change to the order that URL matching was done. The URL is again matched after the session is loaded, so the session is available in custom URL converters. :issue:`4053` - Re-add deprecated ``Config.from_json``, which was accidentally removed early. :issue:`4078` - Improve typing for some functions using ``Callable`` in their type signatures, focusing on decorator factories. :issue:`4060` - Nested blueprints are registered with their dotted name. This allows different blueprints with the same name to be nested at different locations. :issue:`4069` - ``register_blueprint`` takes a ``name`` option to change the (pre-dotted) name the blueprint is registered with. This allows the same blueprint to be registered multiple times with unique names for ``url_for``. Registering the same blueprint with the same name multiple times is deprecated. :issue:`1091` - Improve typing for ``stream_with_context``. :issue:`4052` ``` ### 2.0.0 ``` ------------- Released 2021-05-11 - Drop support for Python 2 and 3.5. - Bump minimum versions of other Pallets projects: Werkzeug &gt;= 2, Jinja2 &gt;= 3, MarkupSafe &gt;= 2, ItsDangerous &gt;= 2, Click &gt;= 8. Be sure to check the change logs for each project. For better compatibility with other applications (e.g. Celery) that still require Click 7, there is no hard dependency on Click 8 yet, but using Click 7 will trigger a DeprecationWarning and Flask 2.1 will depend on Click 8. - JSON support no longer uses simplejson. To use another JSON module, override ``app.json_encoder`` and ``json_decoder``. :issue:`3555` - The ``encoding`` option to JSON functions is deprecated. :pr:`3562` - Passing ``script_info`` to app factory functions is deprecated. This was not portable outside the ``flask`` command. Use ``click.get_current_context().obj`` if it&#39;s needed. :issue:`3552` - The CLI shows better error messages when the app failed to load when looking up commands. :issue:`2741` - Add :meth:`sessions.SessionInterface.get_cookie_name` to allow setting the session cookie name dynamically. :pr:`3369` - Add :meth:`Config.from_file` to load config using arbitrary file loaders, such as ``toml.load`` or ``json.load``. :meth:`Config.from_json` is deprecated in favor of this. :pr:`3398` - The ``flask run`` command will only defer errors on reload. Errors present during the initial call will cause the server to exit with the traceback immediately. :issue:`3431` - :func:`send_file` raises a :exc:`ValueError` when passed an :mod:`io` object in text mode. Previously, it would respond with 200 OK and an empty file. :issue:`3358` - When using ad-hoc certificates, check for the cryptography library instead of PyOpenSSL. :pr:`3492` - When specifying a factory function with ``FLASK_APP``, keyword argument can be passed. :issue:`3553` - When loading a ``.env`` or ``.flaskenv`` file, the current working directory is no longer changed to the location of the file. :pr:`3560` - When returning a ``(response, headers)`` tuple from a view, the headers replace rather than extend existing headers on the response. For example, this allows setting the ``Content-Type`` for ``jsonify()``. Use ``response.headers.extend()`` if extending is desired. :issue:`3628` - The ``Scaffold`` class provides a common API for the ``Flask`` and ``Blueprint`` classes. ``Blueprint`` information is stored in attributes just like ``Flask``, rather than opaque lambda functions. This is intended to improve consistency and maintainability. :issue:`3215` - Include ``samesite`` and ``secure`` options when removing the session cookie. :pr:`3726` - Support passing a ``pathlib.Path`` to ``static_folder``. :pr:`3579` - ``send_file`` and ``send_from_directory`` are wrappers around the implementations in ``werkzeug.utils``. :pr:`3828` - Some ``send_file`` parameters have been renamed, the old names are deprecated. ``attachment_filename`` is renamed to ``download_name``. ``cache_timeout`` is renamed to ``max_age``. ``add_etags`` is renamed to ``etag``. :pr:`3828, 3883` - ``send_file`` passes ``download_name`` even if ``as_attachment=False`` by using ``Content-Disposition: inline``. :pr:`3828` - ``send_file`` sets ``conditional=True`` and ``max_age=None`` by default. ``Cache-Control`` is set to ``no-cache`` if ``max_age`` is not set, otherwise ``public``. This tells browsers to validate conditional requests instead of using a timed cache. :pr:`3828` - ``helpers.safe_join`` is deprecated. Use ``werkzeug.utils.safe_join`` instead. :pr:`3828` - The request context does route matching before opening the session. This could allow a session interface to change behavior based on ``request.endpoint``. :issue:`3776` - Use Jinja&#39;s implementation of the ``|tojson`` filter. :issue:`3881` - Add route decorators for common HTTP methods. For example, ``app.post(&quot;/login&quot;)`` is a shortcut for ``app.route(&quot;/login&quot;, methods=[&quot;POST&quot;])``. :pr:`3907` - Support async views, error handlers, before and after request, and teardown functions. :pr:`3412` - Support nesting blueprints. :issue:`593, 1548`, :pr:`3923` - Set the default encoding to &quot;UTF-8&quot; when loading ``.env`` and ``.flaskenv`` files to allow to use non-ASCII characters. :issue:`3931` - ``flask shell`` sets up tab and history completion like the default ``python`` shell if ``readline`` is installed. :issue:`3941` - ``helpers.total_seconds()`` is deprecated. Use ``timedelta.total_seconds()`` instead. :pr:`3962` - Add type hinting. :pr:`3973`. ``` ### 1.1.4 ``` ------------- Released 2021-05-13 - Update ``static_folder`` to use ``_compat.fspath`` instead of ``os.fspath`` to continue supporting Python &lt; 3.6 :issue:`4050` ``` ### 1.1.3 ``` ------------- Released 2021-05-13 - Set maximum versions of Werkzeug, Jinja, Click, and ItsDangerous. :issue:`4043` - Re-add support for passing a ``pathlib.Path`` for ``static_folder``. :pr:`3579` ``` </details> <details> <summary>Links</summary> - PyPI: https://pypi.org/project/flask - Changelog: https://pyup.io/changelogs/flask/ - Homepage: https://palletsprojects.com/p/flask </details> ### Update [Flask-Admin](https://pypi.org/project/Flask-Admin) from **1.5.7** to **1.5.8**. <details> <summary>Changelog</summary> ### 1.5.8 ``` ----- * SQLAlchemy 1.4.5+ compatibility fixes * Redis CLI fixes ``` </details> <details> <summary>Links</summary> - PyPI: https://pypi.org/project/flask-admin - Changelog: https://pyup.io/changelogs/flask-admin/ - Repo: https://github.com/flask-admin/flask-admin/ - Docs: https://pythonhosted.org/Flask-Admin/ </details> ### Update [Flask-SQLAlchemy](https://pypi.org/project/Flask-SQLAlchemy) from **2.4.4** to **2.5.1**. <details> <summary>Changelog</summary> ### 2.5.1 ``` ------------- Released 2021-03-18 - Fix compatibility with Python 2.7. ``` ### 2.5.0 ``` ------------- Released 2021-03-18 - Update to support SQLAlchemy 1.4. - SQLAlchemy ``URL`` objects are immutable. Some internal methods have changed to return a new URL instead of ``None``. :issue:`885` ``` </details> <details> <summary>Links</summary> - PyPI: https://pypi.org/project/flask-sqlalchemy - Changelog: https://pyup.io/changelogs/flask-sqlalchemy/ - Repo: https://github.com/pallets/flask-sqlalchemy - Docs: https://pythonhosted.org/Flask-SQLAlchemy/ </details> ### Update [SQLAlchemy](https://pypi.org/project/SQLAlchemy) from **1.3.20** to **1.4.22**. <details> <summary>Changelog</summary> ### 1.4.22 ``` :released: July 21, 2021 .. change:: :tags: bug, sql :tickets: 6786 Fixed issue where use of the :paramref:`_sql.case.whens` parameter passing a dictionary positionally and not as a keyword argument would emit a 2.0 deprecation warning, referring to the deprecation of passing a list positionally. The dictionary format of &quot;whens&quot;, passed positionally, is still supported and was accidentally marked as deprecated. .. change:: :tags: bug, orm :tickets: 6775 Fixed issue in new :meth:`_schema.Table.table_valued` method where the resulting :class:`_sql.TableValuedColumn` construct would not respond correctly to alias adaptation as is used throughout the ORM, such as for eager loading, polymorphic loading, etc. .. change:: :tags: bug, orm :tickets: 6769 Fixed issue where usage of the :meth:`_result.Result.unique` method with an ORM result that included column expressions with unhashable types, such as ``JSON`` or ``ARRAY`` using non-tuples would silently fall back to using the ``id()`` function, rather than raising an error. This now raises an error when the :meth:`_result.Result.unique` method is used in a 2.0 style ORM query. Additionally, hashability is assumed to be True for result values of unknown type, such as often happens when using SQL functions of unknown return type; if values are truly not hashable then the ``hash()`` itself will raise. For legacy ORM queries, since the legacy :class:`_orm.Query` object uniquifies in all cases, the old rules remain in place, which is to use ``id()`` for result values of unknown type as this legacy uniquing is mostly for the purpose of uniquing ORM entities and not column values. .. change:: :tags: orm, bug :tickets: 6771 Fixed an issue where clearing of mappers during things like test suite teardowns could cause a &quot;dictionary changed size&quot; warning during garbage collection, due to iteration of a weak-referencing dictionary. A ``list()`` has been applied to prevent concurrent GC from affecting this operation. .. change:: :tags: bug, sql :tickets: 6770 Fixed issue where type-specific bound parameter handlers would not be called upon in the case of using the :meth:`_sql.Insert.values` method with the Python ``None`` value; in particular, this would be noticed when using the :class:`_types.JSON` datatype as well as related PostgreSQL specific types such as :class:`_postgresql.JSONB` which would fail to encode the Python ``None`` value into JSON null, however the issue was generalized to any bound parameter handler in conjunction with this specific method of :class:`_sql.Insert`. .. change:: :tags: bug, engine :tickets: 6740 Added some guards against ``KeyError`` in the event system to accommodate the case that the interpreter is shutting down at the same time :meth:`_engine.Engine.dispose` is being called, which would cause stack trace warnings. .. change:: :tags: bug, orm, regression :tickets: 6793 Fixed critical caching issue where the ORM&#39;s persistence feature using INSERT..RETURNING would cache an incorrect query when mixing the &quot;bulk save&quot; and standard &quot;flush&quot; forms of INSERT. .. changelog:: ``` ### 1.4.21 ``` :released: July 14, 2021 .. change:: :tags: usecase, orm :tickets: 6708 Modified the approach used for history tracking of scalar object relationships that are not many-to-one, i.e. one-to-one relationships that would otherwise be one-to-many. When replacing a one-to-one value, the &quot;old&quot; value that would be replaced is no longer loaded immediately, and is instead handled during the flush process. This eliminates an historically troublesome lazy load that otherwise often occurs when assigning to a one-to-one attribute, and is particularly troublesome when using &quot;lazy=&#39;raise&#39;&quot; as well as asyncio use cases. This change does cause a behavioral change within the :meth:`_orm.AttributeEvents.set` event, which is nonetheless currently documented, which is that the event applied to such a one-to-one attribute will no longer receive the &quot;old&quot; parameter if it is unloaded and the :paramref:`_orm.relationship.active_history` flag is not set. As is documented in :meth:`_orm.AttributeEvents.set`, if the event handler needs to receive the &quot;old&quot; value when the event fires off, the active_history flag must be established either with the event listener or with the relationship. This is already the behavior with other kinds of attributes such as many-to-one and column value references. The change additionally will defer updating a backref on the &quot;old&quot; value in the less common case that the &quot;old&quot; value is locally present in the session, but isn&#39;t loaded on the relationship in question, until the next flush occurs. If this causes an issue, again the normal :paramref:`_orm.relationship.active_history` flag can be set to ``True`` on the relationship. .. change:: :tags: usecase, sql :tickets: 6752 Added new method :meth:`_sql.HasCTE.add_cte` to each of the :func:`_sql.select`, :func:`_sql.insert`, :func:`_sql.update` and :func:`_sql.delete` constructs. This method will add the given :class:`_sql.CTE` as an &quot;independent&quot; CTE of the statement, meaning it renders in the WITH clause above the statement unconditionally even if it is not otherwise referenced in the primary statement. This is a popular use case on the PostgreSQL database where a CTE is used for a DML statement that runs against database rows independently of the primary statement. .. change:: :tags: bug, postgresql :tickets: 6755 Fixed issue in :meth:`_postgresql.Insert.on_conflict_do_nothing` and :meth:`_postgresql.Insert.on_conflict_do_update` where the name of a unique constraint passed as the ``constraint`` parameter would not be properly truncated for length if it were based on a naming convention that generated a too-long name for the PostgreSQL max identifier length of 63 characters, in the same way which occurs within a CREATE TABLE statement. .. change:: :tags: bug, sql :tickets: 6710 Fixed issue in CTE constructs where a recursive CTE that referred to a SELECT that has duplicate column names, which are typically deduplicated using labeling logic in 1.4, would fail to refer to the deduplicated label name correctly within the WITH clause. .. change:: :tags: bug, regression, mssql :tickets: 6697 Fixed regression where the special dotted-schema name handling for the SQL Server dialect would not function correctly if the dotted schema name were used within the ``schema_translate_map`` feature. .. change:: :tags: orm, regression :tickets: 6718 Fixed ORM regression where ad-hoc label names generated for hybrid properties and potentially other similar types of ORM-enabled expressions would usually be propagated outwards through subqueries, allowing the name to be retained in the final keys of the result set even when selecting from subqueries. Additional state is now tracked in this case that isn&#39;t lost when a hybrid is selected out of a Core select / subquery. .. change:: :tags: bug, postgresql :tickets: 6739 Fixed issue where the PostgreSQL ``ENUM`` datatype as embedded in the ``ARRAY`` datatype would fail to emit correctly in create/drop when the ``schema_translate_map`` feature were also in use. Additionally repairs a related issue where the same ``schema_translate_map`` feature would not work for the ``ENUM`` datatype in combination with a ``CAST``, that&#39;s also intrinsic to how the ``ARRAY(ENUM)`` combination works on the PostgreSQL dialect. .. change:: :tags: bug, sql, regression :tickets: 6735 Fixed regression where the :func:`_sql.tablesample` construct would fail to be executable when constructed given a floating-point sampling value not embedded within a SQL function. .. change:: :tags: bug, postgresql :tickets: 6696 Fixed issue in :meth:`_postgresql.Insert.on_conflict_do_nothing` and :meth:`_postgresql.Insert.on_conflict_do_update` where the name of a unique constraint passed as the ``constraint`` parameter would not be properly quoted if it contained characters which required quoting. .. change:: :tags: bug, regression, orm :tickets: 6698 Fixed regression caused in 1.4.19 due to :ticket:`6503` and related involving :meth:`_orm.Query.with_entities` where the new structure used would be inappropriately transferred to an enclosing :class:`_orm.Query` when making use of set operations such as :meth:`_orm.Query.union`, causing the JOIN instructions within to be applied to the outside query as well. .. change:: :tags: bug, orm, regression :tickets: 6762 Fixed regression which appeared in version 1.4.3 due to :ticket:`6060` where rules that limit ORM adaptation of derived selectables interfered with other ORM-adaptation based cases, in this case when applying adaptations for a :func:`_orm.with_polymorphic` against a mapping which uses a :func:`_orm.column_property` which in turn makes use of a scalar select that includes a :func:`_orm.aliased` object of the mapped table. .. changelog:: ``` ### 1.4.20 ``` :released: June 28, 2021 .. change:: :tags: bug, regression, orm :tickets: 6680 Fixed regression in ORM regarding an internal reconstitution step for the :func:`_orm.with_polymorphic` construct, when the user-facing object is garbage collected as the query is processed. The reconstitution was not ensuring the sub-entities for the &quot;polymorphic&quot; case were handled, leading to an ``AttributeError``. .. change:: :tags: usecase, sql :tickets: 6646 Add a impl parameter to :class:`_types.PickleType` constructor, allowing any arbitary type to be used in place of the default implementation of :class:`_types.LargeBinary`. Pull request courtesy jason3gb. .. change:: :tags: bug, engine :tickets: 5348 Fixed an issue in the C extension for the :class:`_result.Row` class which could lead to a memory leak in the unlikely case of a :class:`_result.Row` object which referred to an ORM object that then was mutated to refer back to the ``Row`` itself, creating a cycle. The Python C APIs for tracking GC cycles has been added to the native :class:`_result.Row` implementation to accommodate for this case. .. change:: :tags: bug, engine :tickets: 6665 Fixed old issue where a :func:`_sql.select()` made against the token &quot;*&quot;, which then yielded exactly one column, would fail to correctly organize the ``cursor.description`` column name into the keys of the result object. .. change:: :tags: usecase, mysql :tickets: 6659 Made a small adjustment in the table reflection feature of the MySQL dialect to accommodate for alternate MySQL-oriented databases such as TiDB which include their own &quot;comment&quot; directives at the end of a constraint directive within &quot;CREATE TABLE&quot; where the format doesn&#39;t have the additional space character after the comment, in this case the TiDB &quot;clustered index&quot; feature. Pull request courtesy Daniël van Eeden. .. change:: :tags: bug, schema :tickets: 6685 Fixed issue where passing ``None`` for the value of :paramref:`_schema.Table.prefixes` would not store an empty list, but rather the constant ``None``, which may be unexpected by third party dialects. The issue is revealed by a usage in recent versions of Alembic that are passing ``None`` for this value. Pull request courtesy Kai Mueller. .. change:: :tags: bug, regression, ext :tickets: 6679 Fixed regression in :mod:`sqlalchemy.ext.automap` extension such that the use case of creating an explicit mapped class to a table that is also the :paramref:`_orm.relationship.secondary` element of a :func:`_orm.relationship` that automap will be generating would emit the &quot;overlaps&quot; warnings introduced in 1.4 and discussed at :ref:`error_qzyx`. While generating this case from automap is still subject to the same caveats that the &quot;overlaps&quot; warning refers towards, as automap is intended for more ad-hoc use cases, the condition which produces the warning is disabled when a many-to-many relationship with this particular pattern is generated. .. change:: :tags: bug, regression, orm :tickets: 6678 Adjusted :meth:`_orm.Query.union` and similar set operations to be correctly compatible with the new capabilities just added in :ticket:`6661`, with SQLAlchemy 1.4.19, such that the SELECT statements rendered as elements of the UNION or other set operation will include directly mapped columns that are mapped as deferred; this both fixes a regression involving unions with multiple levels of nesting that would produce a column mismatch, and also allows the :func:`_orm.undefer` option to be used at the top level of such a :class:`_orm.Query` without having to apply the option to each of the elements within the UNION. .. change:: :tags: bug, sql, orm :tickets: 6668 Fixed the class hierarchy for the :class:`_schema.Sequence` and the more general :class:`_schema.DefaultGenerator` base, as these are &quot;executable&quot; as statements they need to include :class:`_sql.Executable` in their hierarchy, not just :class:`_roles.StatementRole` as was applied arbitrarily to :class:`_schema.Sequence` previously. The fix allows :class:`_schema.Sequence` to work in all ``.execute()`` methods including with :meth:`_orm.Session.execute` which was not working in the case that a :meth:`_orm.SessionEvents.do_orm_execute` handler was also established. .. change:: :tags: bug, orm :tickets: 6538 Adjusted the check in the mapper for a callable object that is used as a ``validates`` validator function or a ``reconstructor`` reconstruction function, to check for &quot;callable&quot; more liberally such as to accommodate objects based on fundamental attributes like ``__func__`` and ``__call___``, rather than testing for ``MethodType`` / ``FunctionType``, allowing things like cython functions to work properly. Pull request courtesy Miłosz Stypiński. .. changelog:: ``` ### 1.4.19 ``` :released: June 22, 2021 .. change:: :tags: bug, mssql :tickets: 6658 Fixed bug where the &quot;schema_translate_map&quot; feature would fail to function correctly in conjunction with an INSERT into a table that has an IDENTITY column, where the value of the IDENTITY column were specified in the values of the INSERT thus triggering SQLAlchemy&#39;s feature of setting IDENTITY INSERT to &quot;on&quot;; it&#39;s in this directive where the schema translate map would fail to be honored. .. change:: :tags: bug, sql :tickets: 6663 Fixed issue in CTE constructs mostly relevant to ORM use cases where a recursive CTE against &quot;anonymous&quot; labels such as those seen in ORM ``column_property()`` mappings would render in the ``WITH RECURSIVE xyz(...)`` section as their raw internal label and not a cleanly anonymized name. .. change:: :tags: mssql, change :tickets: 6503, 6253 Made improvements to the server version regexp used by the pymssql dialect to prevent a regexp overflow in case of an invalid version string. .. change:: :tags: bug, orm, regression :tickets: 6503, 6253 Fixed further regressions in the same area as that of :ticket:`6052` where loader options as well as invocations of methods like :meth:`_orm.Query.join` would fail if the left side of the statement for which the option/join depends upon were replaced by using the :meth:`_orm.Query.with_entities` method, or when using 2.0 style queries when using the :meth:`_sql.Select.with_only_columns` method. A new set of state has been added to the objects which tracks the &quot;left&quot; entities that the options / join were made against which is memoized when the lead entities are changed. .. change:: :tags: bug, asyncio, postgresql :tickets: 6652 Fixed bug in asyncio implementation where the greenlet adaptation system failed to propagate ``BaseException`` subclasses, most notably including ``asyncio.CancelledError``, to the exception handling logic used by the engine to invalidate and clean up the connection, thus preventing connections from being correctly disposed when a task was cancelled. .. change:: :tags: usecase, asyncio :tickets: 6583 Implemented :class:`_asyncio.async_scoped_session` to address some asyncio-related incompatibilities between :class:`_orm.scoped_session` and :class:`_asyncio.AsyncSession`, in which some methods (notably the :meth:`_asyncio.async_scoped_session.remove` method) should be used with the ``await`` keyword. .. seealso:: :ref:`asyncio_scoped_session` .. change:: :tags: usecase, mysql :tickets: 6132 Added new construct :class:`_mysql.match`, which provides for the full range of MySQL&#39;s MATCH operator including multiple column support and modifiers. Pull request courtesy Anton Kovalevich. .. seealso:: :class:`_mysql.match` .. change:: :tags: bug, postgresql, oracle :tickets: 6649 Fixed issue where the ``INTERVAL`` datatype on PostgreSQL and Oracle would produce an ``AttributeError`` when used in the context of a comparison operation against a ``timedelta()`` object. Pull request courtesy MajorDallas. .. change:: :tags: bug, mypy :tickets: 6476 Fixed issue in mypy plugin where class info for a custom declarative base would not be handled correctly on a cached mypy pass, leading to an AssertionError being raised. .. change:: :tags: bug, orm :tickets: 6661 Refined the behavior of ORM subquery rendering with regards to deferred columns and column properties to be more compatible with that of 1.3 while also providing for 1.4&#39;s newer features. As a subquery in 1.4 does not make use of loader options, including :func:`_orm.undefer`, a subquery that is against an ORM entity with deferred attributes will now render those deferred attributes that refer directly to mapped table columns, as these are needed in the outer SELECT if that outer SELECT makes use of these columns; however a deferred attribute that refers to a composed SQL expression as we normally do with :func:`_orm.column_property` will not be part of the subquery, as these can be selected explicitly if needed in the subquery. If the entity is being SELECTed from this subquery, the column expression can still render on &quot;the outside&quot; in terms of the derived subquery columns. This produces essentially the same behavior as when working with 1.3. However in this case the fix has to also make sure that the ``.selected_columns`` collection of an ORM-enabled :func:`_sql.select` also follows these rules, which in particular allows recursive CTEs to render correctly in this scenario, which were previously failing to render correctly due to this issue. .. change:: :tags: bug, postgresql :tickets: 6621 Fixed issue where the pool &quot;pre ping&quot; feature would implicitly start a transaction, which would then interfere with custom transactional flags such as PostgreSQL&#39;s &quot;read only&quot; mode when used with the psycopg2 driver. .. changelog:: ``` ### 1.4.18 ``` :released: June 10, 2021 .. change:: :tags: bug, orm :tickets: 6072, 6487 Clarified the current purpose of the :paramref:`_orm.relationship.bake_queries` flag, which in 1.4 is to enable or disable &quot;lambda caching&quot; of statements within the &quot;lazyload&quot; and &quot;selectinload&quot; loader strategies; this is separate from the more foundational SQL query cache that is used for most statements. Additionally, the lazy loader no longer uses its own cache for many-to-one SQL queries, which was an implementation quirk that doesn&#39;t exist for any other loader scenario. Finally, the &quot;lru cache&quot; warning that the lazyloader and selectinloader strategies could emit when handling a wide array of class/relationship combinations has been removed; based on analysis of some end-user cases, this warning doesn&#39;t suggest any significant issue. While setting ``bake_queries=False`` for such a relationship will remove this cache from being used, there&#39;s no particular performance gain in this case as using no caching vs. using a cache that needs to refresh often likely still wins out on the caching being used side. .. change:: :tags: bug, asyncio :tickets: 6575 Fixed an issue that presented itself when using the :class:`_pool.NullPool` or the :class:`_pool.StaticPool` with an async engine. This mostly affected the aiosqlite dialect. .. change:: :tags: bug, sqlite, regression :tickets: 6586 The fix for pysqlcipher released in version 1.4.3 :ticket:`5848` was unfortunately non-working, in that the new ``on_connect_url`` hook was erroneously not receiving a ``URL`` object under normal usage of :func:`_sa.create_engine` and instead received a string that was unhandled; the test suite failed to fully set up the actual conditions under which this hook is called. This has been fixed. .. change:: :tags: bug, postgresql, regression :tickets: 6581 Fixed regression where using the PostgreSQL &quot;INSERT..ON CONFLICT&quot; structure would fail to work with the psycopg2 driver if it were used in an &quot;executemany&quot; context along with bound parameters in the &quot;SET&quot; clause, due to the implicit use of the psycopg2 fast execution helpers which are not appropriate for this style of INSERT statement; as these helpers are the default in 1.4 this is effectively a regression. Additional checks to exclude this kind of statement from that particular extension have been added. .. change:: :tags: bug, orm, regression :tickets: 6285 Adjusted the means by which classes such as :class:`_orm.scoped_session` and :class:`_asyncio.AsyncSession` are generated from the base :class:`_orm.Session` class, such that custom :class:`_orm.Session` subclasses such as that used by Flask-SQLAlchemy don&#39;t need to implement positional arguments when they call into the superclass method, and can continue using the same argument styles as in previous releases. .. change:: :tags: bug, orm, regression :tickets: 6595 Fixed issue where query production for joinedload against a complex left hand side involving joined-table inheritance could fail to produce a correct query, due to a clause adaption issue. .. change:: :tags: bug, orm, regression, performance :tickets: 6596 Fixed regression involving how the ORM would resolve a given mapped column to a result row, where under cases such as joined eager loading, a slightly more expensive &quot;fallback&quot; could take place to set up this resolution due to some logic that was removed since 1.3. The issue could also cause deprecation warnings involving column resolution to be emitted when using a 1.4 style query with joined eager loading. .. change:: :tags: bug, orm :tickets: 6591 Fixed issue in experimental &quot;select ORM objects from INSERT/UPDATE&quot; use case where an error was raised if the statement were against a single-table-inheritance subclass. .. change:: :tags: bug, asyncio :tickets: 6592 Added ``asyncio.exceptions.TimeoutError``, ``asyncio.exceptions.CancelledError`` as so-called &quot;exit exceptions&quot;, a class of exceptions that include things like ``GreenletExit`` and ``KeyboardInterrupt``, which are considered to be events that warrant considering a DBAPI connection to be in an unusable state where it should be recycled. .. change:: :tags: bug, orm :tickets: 6400 The warning that&#39;s emitted for :func:`_orm.relationship` when multiple relationships would overlap with each other as far as foreign key attributes written towards, now includes the specific &quot;overlaps&quot; argument to use for each warning in order to silence the warning without changing the mapping. .. change:: :tags: usecase, asyncio :tickets: 6319 Implemented a new registry architecture that allows the ``Async`` version of an object, like ``AsyncSession``, ``AsyncConnection``, etc., to be locatable given the proxied &quot;sync&quot; object, i.e. ``Session``, ``Connection``. Previously, to the degree such lookup functions were used, an ``Async`` object would be re-created each time, which was less than ideal as the identity and state of the &quot;async&quot; object would not be preserved across calls. From there, new helper functions :func:`_asyncio.async_object_session`, :func:`_asyncio.async_session` as well as a new :class:`_orm.InstanceState` attribute :attr:`_orm.InstanceState.async_session` have been added, which are used to retrieve the original :class:`_asyncio.AsyncSession` associated with an ORM mapped object, a :class:`_orm.Session` associated with an :class:`_asyncio.AsyncSession`, and an :class:`_asyncio.AsyncSession` associated with an :class:`_orm.InstanceState`, respectively. This patch also implements new methods :meth:`_asyncio.AsyncSession.in_nested_transaction`, :meth:`_asyncio.AsyncSession.get_transaction`, :meth:`_asyncio.AsyncSession.get_nested_transaction`. .. changelog:: ``` ### 1.4.17 ``` :released: May 29, 2021 .. change:: :tags: bug, orm, regression :tickets: 6558 Fixed regression caused by just-released performance fix mentioned in 6550 where a query.join() to a relationship could produce an AttributeError if the query were made against non-ORM structures only, a fairly unusual calling pattern. .. changelog:: ``` ### 1.4.16 ``` :released: May 28, 2021 .. change:: :tags: bug, engine :tickets: 6482 Fixed issue where an ` sign in the database portion of a URL would not be interpreted correctly if the URL also had a username:password section. .. change:: :tags: bug, ext :tickets: 6529 Fixed a deprecation warning that was emitted when using :func:`_automap.automap_base` without passing an existing ``Base``. .. change:: :tags: bug, pep484 :tickets: 6461 Remove pep484 types from the code. Current effort is around the stub package, and having typing in two places makes thing worse, since the types in the SQLAlchemy source were usually outdated compared to the version in the stubs. .. change:: :tags: usecase, mssql :tickets: 6464 Implemented support for a :class:`_sql.CTE` construct to be used directly as the target of a :func:`_sql.delete` construct, i.e. &quot;WITH ... AS cte DELETE FROM cte&quot;. This appears to be a useful feature of SQL Server. .. change:: :tags: bug, general :tickets: 6540, 6543 Resolved various deprecation warnings which were appearing as of Python version 3.10.0b1. .. change:: :tags: bug, orm :tickets: 6471 Fixed issue when using :paramref:`_orm.relationship.cascade_backrefs` parameter set to ``False``, which per :ref:`change_5150` is set to become the standard behavior in SQLAlchemy 2.0, where adding the item to a collection that uniquifies, such as ``set`` or ``dict`` would fail to fire a cascade event if the object were already associated in that collection via the backref. This fix represents a fundamental change in the collection mechanics by introducing a new event state which can fire off for a collection mutation even if there is no net change on the collection; the action is now suited using a new event hook :meth:`_orm.AttributeEvents.append_wo_mutation`. .. change:: :tags: bug, orm, regression :tickets: 6550 Fixed regression involving clause adaption of labeled ORM compound elements, such as single-table inheritance discriminator expressions with conditionals or CASE expressions, which could cause aliased expressions such as those used in ORM join / joinedload operations to not be adapted correctly, such as referring to the wrong table in the ON clause in a join. This change also improves a performance bump that was located within the process of invoking :meth:`_sql.Select.join` given an ORM attribute as a target. .. change:: :tags: bug, orm, regression :tickets: 6495 Fixed regression where the full combination of joined inheritance, global with_polymorphic, self-referential relationship and joined loading would fail to be able to produce a query with the scope of lazy loads and object refresh operations that also attempted to render the joined loader. .. change:: :tags: bug, engine :tickets: 6329 Fixed a long-standing issue with :class:`.URL` where query parameters following the question mark would not be parsed correctly if the URL did not contain a database portion with a backslash. .. change:: :tags: bug, sql, regression :tickets: 6549 Fixed regression in dynamic loader strategy and :func:`_orm.relationship` overall where the :paramref:`_orm.relationship.order_by` parameter were stored as a mutable list, which could then be mutated when combined with additional &quot;order_by&quot; methods used against the dynamic query object, causing the ORDER BY criteria to continue to grow repetitively. .. change:: :tags: bug, orm :tickets: 6484 Enhanced the bind resolution rules for :meth:`_orm.Session.execute` so that when a non-ORM statement such as an :func:`_sql.insert` construct nonetheless is built against ORM objects, to the greatest degree possible the ORM entity will be used to resolve the bind, such as for a :class:`_orm.Session` that has a bind map set up on a common superclass without specific mappers or tables named in the map. .. change:: :tags: bug, regression, ext :tickets: 6390 Fixed regression in the ``sqlalchemy.ext.instrumentation`` extension that prevented instrumentation disposal from working completely. This fix includes both a 1.4 regression fix as well as a fix for a related issue that existed in 1.3 also. As part of this change, the :class:`sqlalchemy.ext.instrumentation.InstrumentationManager` class now has a new method ``unregister()``, which replaces the previous method ``dispose()``, which was not called as of version 1.4. .. changelog:: ``` ### 1.4.15 ``` :released: May 11, 2021 .. change:: :tags: bug, documentation, mysql :tickets: 5397 Added support for the ``ssl_check_hostname=`` parameter in mysql connection URIs and updated the mysql dialect documentation regarding secure connections. Original pull request courtesy of Jerry Zhao. .. change:: :tags: bug, orm, regression :tickets: 6449 Fixed additional regression caused by &quot;eager loaders run on unexpire&quot; feature :ticket:`1763` where the feature would run for a ``contains_eager()`` eagerload option in the case that the ``contains_eager()`` were chained to an additional eager loader option, which would then produce an incorrect query as the original query-bound join criteria were no longer present. .. change:: :tags: feature, general :tickets: 6241 A new approach has been applied to the warnings system in SQLAlchemy to accurately predict the appropriate stack level for each warning dynamically. This allows evaluating the source of SQLAlchemy-generated warnings and deprecation warnings to be more straightforward as the warning will indicate the source line within end-user code, rather than from an arbitrary level within SQLAlchemy&#39;s own source code. .. change:: :tags: bug, orm :tickets: 6459 Fixed issue in subquery loader strategy which prevented caching from working correctly. This would have been seen in the logs as a &quot;generated&quot; message instead of &quot;cached&quot; for all subqueryload SQL emitted, which by saturating the cache with new keys would degrade overall performance; it also would produce &quot;LRU size alert&quot; warnings. .. change:: :tags: bug, sql :tickets: 6460 Adjusted the logic added as part of :ticket:`6397` in 1.4.12 so that internal mutation of the :class:`.BindParameter` object occurs within the clause construction phase as it did before, rather than in the compilation phase. In the latter case, the mutation still produced side effects against the incoming construct and additionally could potentially interfere with other internal mutation routines. .. changelog:: ``` ### 1.4.14 ``` :released: May 6, 2021 .. change:: :tags: bug, regression, orm :tickets: 6426 Fixed regression involving ``lazy=&#39;dynamic&#39;`` loader in conjunction with a detached object. The previous behavior was that the dynamic loader upon calling methods like ``.all()`` returns empty lists for detached objects without error, this has been restored; however a warning is now emitted as this is not the correct result. Other dynamic loader scenarios correctly raise ``DetachedInstanceError``. .. change:: :tags: bug, regression, sql :tickets: 6428 Fixed regression caused by the &quot;empty in&quot; change just made in :ticket:`6397` 1.4.12 where the expression needs to be parenthesized for the &quot;not in&quot; use case, otherwise the condition will interfere with the other filtering criteria. .. change:: :tags: bug, sql, regression :tickets: 6436 The :class:`.TypeDecorator` class will now emit a warning when used in SQL compilation with caching unless the ``.cache_ok`` flag is set to ``True`` or ``False``. A new class-level attribute :attr:`.TypeDecorator.cache_ok` may be set which will be used as an indication that all the parameters passed to the object are safe to be used as a cache key if set to ``True``, ``False`` means they are not. .. change:: :tags: engine, bug, regression :tickets: 6427 Established a deprecation path for calling upon the :meth:`_cursor.CursorResult.keys` method for a statement that returns no rows to provide support for legacy patterns used by the &quot;records&quot; package as well as any other non-migrated applications. Previously, this would raise :class:`.ResourceClosedException` unconditionally in the same way as it does when attempting to fetch rows. While this is the correct behavior going forward, the :class:`_cursor.LegacyCursorResult` object will now in this case return an empty list for ``.keys()`` as it did in 1.3, while also emitting a 2.0 deprecation warning. The :class:`_cursor.CursorResult`, used when using a 2.0-style &quot;future&quot; engine, will continue to raise as it does now. .. change:: :tags: usecase, engine, orm :tickets: 6288 Applied consistent behavior to the use case of calling ``.commit()`` or ``.rollback()`` inside of an existing ``.begin()`` context manager, with the addition of potentially emitting SQL within the block subsequent to the commit or rollback. This change continues upon the change first added in :ticket:`6155` where the use case of calling &quot;rollback&quot; inside of a ``.begin()`` contextmanager block was proposed: * calling ``.commit()`` or ``.rollback()`` will now be allowed without error or warning within all scopes, including that of legacy and future :class:`_engine.Engine`, ORM :class:`_orm.Session`, asyncio :class:`.AsyncEngine`. Previously, the :class:`_orm.Session` disallowed this. * The remaining scope of the context manager is then closed; when the block ends, a check is emitted to see if the transaction was already ended, and if so the block returns without action. * It will now raise **an error** if subsequent SQL of any kind is emitted within the block, **after** ``.commit()`` or ``.rollback()`` is called. The block should be closed as the state of the executable object would otherwise be undefined in this state. .. changelog:: ``` ### 1.4.13 ``` :released: May 3, 2021 .. change:: :tags: bug, regression, orm :tickets: 6410 Fixed regression in ``selectinload`` loader strategy that would cause it to cache its internal state incorrectly when handling relationships that join across more than one column, such as when using a composite foreign key. The invalid caching would then cause other unrelated loader operations to fail. .. change:: :tags: bug, orm, regression :tickets: 6414 Fixed regression where :meth:`_orm.Query.filter_by` would not work if the lead entity were a SQL function or other expression derived from the primary entity in question, rather than a simple entity or column of that entity. Additionally, improved the behavior of :meth:`_sql.Select.filter_by` overall to work with column expressions even in a non-ORM context. .. change:: :tags: bug, engine, regression :tickets: 6408 Restored a legacy transactional behavior that was inadvertently removed from the :class:`_engine.Connection` as it was never tested as a known use case in previous versions, where calling upon the :meth:`_engine.Connection.begin_nested` method, when no transaction is present, does not create a SAVEPOINT at all and instead starts an outer transaction, returning a :class:`.RootTransaction` object instead of a :class:`.NestedTransaction` object. This :class:`.RootTransaction` then will emit a real COMMIT on the database connection when committed. Previously, the 2.0 style behavior was present in all cases that would autobegin a transaction but not commit it, which is a behavioral change. When using a :term:`2.0 style` connection object, the behavior is unchanged from previous 1.4 versions; calling :meth:`_future.Connection.begin_nested` will &quot;autobegin&quot; the outer transaction if not already present, and then as instructed emit a SAVEPOINT, returning the :class:`.NestedTransaction` object. The outer transaction is committed by calling upon :meth:`_future.Connection.commit`, as is &quot;commit-as-you-go&quot; style usage. In non-&quot;future&quot; mode, while the old behavior is restored, it also emits a 2.0 deprecation warning as this is a legacy behavior. .. change:: :tags: bug, asyncio, regression :tickets: 6409 Fixed a regression introduced by :ticket:`6337` that would create an ``asyncio.Lock`` which could be attached to the wrong loop when instantiating the async engine before any asyncio loop was started, leading to an asyncio error message when attempting to use the engine under certain circumstances. .. change:: :tags: bug, orm, regression :tickets: 6419 Fixed regression where using :func:`_orm.selectinload` and :func:`_orm.subqueryload` to load a two-level-deep path would lead to an attribute error. .. change:: :tags: bug, orm, regression :tickets: 6420 Fixed regression where using the :func:`_orm.noload` loader strategy in conjunction with a &quot;dynamic&quot; relationship would lead to an attribute error as the noload strategy would attempt to apply itself to the dynamic loader. .. change:: :tags: usecase, postgresql :tickets: 6198 Add support for server side cursors in the pg8000 dialect for PostgreSQL. This allows use of the :paramref:`.Connection.execution_options.stream_results` option. .. changelog:: ``` ### 1.4.12 ``` :released: April 29, 2021 .. change:: :tags: bug, orm, regression, caching :tickets: 6391 Fixed critical regression where bound parameter tracking as used in the SQL caching system could fail to track all parameters for the case where the same SQL expression containing a parameter were used in an ORM-related query using a feature such as class inheritance, which was then embedded in an enclosing expression which would make use of that same expression multiple times, such as a UNION. The ORM would individually copy the individual SELECT statements as part of compilation with class inheritance, which then embedded in the enclosing statement would fail to accommodate for all parameters. The logic that tracks this condition has been adjusted to work for multiple copies of a parameter. .. change:: :tags: bug, sql :tickets: 6258, 6397 Revised the &quot;EMPTY IN&quot; expression to no longer rely upon using a subquery, as this was causing some compatibility and performance problems. The new approach for selected databases takes advantage of using a NULL-returning IN expression combined with the usual &quot;1 != 1&quot; or &quot;1 = 1&quot; expression appended by AND or OR. The expression is now the default for all backends other than SQLite, which still had some compatibility issues regarding tuple &quot;IN&quot; for older SQLite versions. Third party dialects can still override how the &quot;empty set&quot; expression renders by implementing a new compiler method ``def visit_empty_set_op_expr(self, type_, expand_op)``, which takes precedence over the existing ``def visit_empty_set_expr(self, element_types)`` which remains in place. .. change:: :tags: bug, orm :tickets: 6350 Fixed two distinct issues mostly affecting :class:`_hybrid.hybrid_property`, which would come into play under common mis-configuration scenarios that were silently ignored in 1.3, and now failed in 1.4, where the &quot;expression&quot; implementation would return a non :class:`_sql.ClauseElement` such as a boolean value. For both issues, 1.3&#39;s behavior was to silently ignore the mis-configuration and ultimately attempt to interpret the value as a SQL expression, which would lead to an incorrect query. * Fixed issue regarding interaction of the attribute system with hybrid_property, where if the ``__clause_element__()`` method of the attribute returned a non-:class:`_sql.ClauseElement` object, an internal ``AttributeError`` would lead the attribute to return the ``expression`` function on the hybrid_property itself, as the attribute error was against the name ``.expression`` which would invoke the ``__getattr__()`` method as a fallback. This now raises explicitly. In 1.3 the non-:class:`_sql.ClauseElement` was returned directly. * Fixed issue in SQL argument coercions system where passing the wrong kind of object to methods that expect column expressions would fail if the object were altogether not a SQLAlchemy object, such as a Python function, in cases where the object were not just coerced into a bound value. Again 1.3 did not have a comprehensive argument coercion system so this case would also pass silently. .. change:: :tags: bug, orm :tickets: 6378 Fixed issue where using a :class:`_sql.Select` as a subquery in an ORM context would modify the :class:`_sql.Select` in place to disable eagerloads on that object, which would then cause that same :class:`_sql.Select` to not eagerload if it were then re-used in a top-level execution context. .. change:: :tags: bug, regression, sql :tickets: 6343 Fixed regression where usage of the :func:`_sql.text` construct inside the columns clause of a :class:`_sql.Select` construct, which is better handled by using a :func:`_sql.literal_column` construct, would nonetheless prevent constructs like :func:`_sql.union` from working correctly. Other use cases, such as constructing subuqeries, continue to work the same as in prior versions where the :func:`_sql.text` construct is silently omitted from the collection of exported columns. Also repairs similar use within the ORM. .. change:: :tags: bug, regression, sql :tickets: 6261 Fixed regression involving legacy methods such as :meth:`_sql.Select.append_column` where internal assertions would fail. .. change:: :tags: usecase, sqlite :tickets: 6379 Default to using ``SingletonThreadPool`` for in-memory SQLite databases created using URI filenames. Previously the default pool used was the ``NullPool`` that precented sharing the same database between multiple engines. .. change:: :tags: bug, regression, sql :tickets: 6300 Fixed regression caused by :ticket:`5395` where tuning back the check for sequences in :func:`_sql.select` now caused failures when doing 2.0-style querying with a mapped class that also happens to have an ``__iter__()`` method. Tuned the check some more to accommodate this as well as some other interesting ``__iter__()`` scenarios. .. change:: :tags: bug, mssql, schema :tickets: 6345 Add :meth:`_types.TypeEngine.as_generic` support for :class:`sqlalchemy.dialects.mysql.BIT` columns, mapping them to :class:`_sql.sqltypes.Boolean`. .. change:: :tags: bug, orm, regression :tickets: 6360, 6359 Fixed issue where the new :ref:`autobegin &lt;session_autobegin&gt;` behavior failed to &quot;autobegin&quot; in the case where an existing persistent object has an attribute change, which would then impact the behavior of :meth:`_orm.Session.rollback` in that no snapshot was created to be rolled back. The &quot;attribute modify&quot; mechanics have been updated to ensure &quot;autobegin&quot;, which does not perform any database work, does occur when persistent attributes change in the same manner as when :meth:`_orm.Session.add` is called. This is a regression as in 1.3, the rollback() method always had a transaction to roll back and would expire every time. .. change:: :tags: bug, mssql, regression :tickets: 6366 Fixed regression caused by :ticket:`6306` which added support for ``DateTime(timezone=True)``, where the previous behavior of the pyodbc driver of implicitly dropping the tzinfo from a timezone-aware date when INSERTing into a timezone-naive DATETIME column were lost, leading to a SQL Server error when inserting timezone-aware datetime objects into timezone-native database columns. .. change:: :tags: orm, bug, regression :tickets: 6386 Fixed regression in ORM where using hybrid property to indicate an expression from a different entity would confuse the column-labeling logic in the ORM and attempt to derive the name of the hybrid from that other class, leading to an attribute error. The owning class of the hybrid attribute is now tracked along with the name. .. change:: :tags: orm, bug, regression :tickets: 6401 Fixed regression in hybrid_property where a hybrid against a SQL function would generate an ``AttributeError`` when attempting to generate an entry for the ``.c`` collection of a subquery in some cases; among other things this would impact its use in cases like that of ``Query.count()``. .. change:: :tags: bug, postgresql :tickets: 6373 Fixed very old issue where the :class:`_types.Enum` datatype would not inherit the :paramref:`_schema.MetaData.schema` parameter of a :class:`_schema.MetaData` object when that object were passed to the :class:`_types.Enum` using :paramref:`_types.Enum.metadata`. .. change:: :tags: bug, orm, dataclasses :tickets: 6346 Adjusted the declarative scan for dataclasses so that the inheritance behavior of :func:`_orm.declared_attr` established on a mixin, when using the new form of having it inside of a ``dataclasses.field()`` construct and not actually a descriptor attribute on the class, correctly accommodates the case when the target class to be mapped is a subclass of an existing mapped class which has already mapped that :func:`_orm.declared_attr`, and therefore should not be re-applied to this class. .. change:: :tags: bug, schema, mysql, mariadb, oracle, postgresql :tickets: 6338 Ensure that the MySQL and MariaDB dialect ignore the :class:`_sql.Identity` construct while rendering the ``AUTO_INCREMENT`` keyword in a create table. The Oracle and PostgreSQL compiler was updated to not render :class:`_sql.Identity` if the database version does not support it (Oracle &lt; 12 and PostgreSQL &lt; 10). Previously it was rendered regardless of the database version. .. change:: :tags: bug, orm :tickets: 6353 Fixed an issue with the (deprecated in 1.4) :meth:`_schema.ForeignKeyConstraint.copy` method that caused an error when invoked with the ``schema`` argument. .. change:: :tags: bug, engine :tickets: 6361 Fixed issue where usage of an explicit :class:`.Sequence` would produce inconsistent &quot;inline&quot; behavior for an :class:`.Insert` construct that includes multiple values phrases; the first seq would be inline but subsequent ones would be &quot;pre-execute&quot;, leading to inconsistent sequence ordering. The sequence expressions are now fully inline. .. changelog:: ``` ### 1.4.11 ``` :released: April 21, 2021 .. change:: :tags: bug, engine, regression :tickets: 6337 Fixed critical regression caused by the change in :ticket:`5497` where the connection pool &quot;init&quot; phase no longer occurred within mutexed isolation, allowing other threads to proceed with the dialect uninitialized, which could then impact the compilation of SQL statements. .. change:: :tags: bug, orm, regression, declarative :tickets: 6331 Fixed regression where recent changes to support Python dataclasses had the inadvertent effect that an ORM mapped class could not successfully override the ``__new__()`` method. .. changelog:: ``` ### 1.4.10 ``` :released: April 20, 2021 .. change:: :tags: bug, declarative, regression :tickets: 6291 Fixed :func:`_declarative.instrument_declarative` that called a non existing registry method. .. change:: :tags: bug, orm :tickets: 6320 Fixed bug in new :func:`_orm.with_loader_criteria` feature where using a mixin class with :func:`_orm.declared_attr` on an attribute that were accessed inside the custom lambda would emit a warning regarding using an unmapped declared attr, when the lambda callable were first initialized. This warning is now prevented using special instrumentation for this lambda initialization step. .. change:: :tags: usecase, mssql :tickets: 6306 The :paramref:`_types.DateTime.timezone` parameter when set to ``True`` will now make use of the ``DATETIMEOFFSET`` column type with SQL Server when used to emit DDL, rather than ``DATETIME`` where the flag was silently ignored. .. change:: :tags: orm, bug, regression :tickets: 6326 Fixed additional regression caused by the &quot;eagerloaders on refresh&quot; feature added in :ticket:`1763` where the refresh operation historical --- _{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

kerem 2026-02-26 01:33:44 +03:00

• closed this issue
• added the
  pull-request
  label

kerem referenced this issue 2026-02-26 01:33:47 +03:00

[PR #245] [CLOSED] Scheduled weekly dependency update for week 45 #258

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

master

pyup-scheduled-update-2026-04-20

pyup-scheduled-update-2024-09-16

pyup-scheduled-update-2023-07-24

pyup-scheduled-update-2023-06-19

pyup-scheduled-update-2023-05-22

pyup-scheduled-update-2023-05-15

pyup-scheduled-update-2023-05-08

dependabot/pip/flask-2.3.2

pyup-scheduled-update-2023-05-01

pyup-scheduled-update-2023-04-03

dependabot/pip/werkzeug-2.2.3

pyup-scheduled-update-2022-11-14

pyup-scheduled-update-2022-10-03

pyup-scheduled-update-2022-08-01

pyup-scheduled-update-2022-06-13

pyup-scheduled-update-2022-05-30

pyup-scheduled-update-2022-03-07

pyup-scheduled-update-2022-01-10

pyup-scheduled-update-2021-11-01

pyup-scheduled-update-2020-10-05

pyup-scheduled-update-2019-09-30

pyup-scheduled-update-2019-07-29

pyup-scheduled-update-2019-07-22

pyup-scheduled-update-2019-05-27

pyup-scheduled-update-2019-03-11

marshmallow

pyup-scheduled-update-2019-02-25

pyup-scheduled-update-2019-02-18

pyup-scheduled-update-2019-01-28

pyup-scheduled-update-2019-01-14

docker

name-map-stupid

swagger

fix-pagination

doc-expansion

specify-schema

No results found.

Labels

Clear labels   

bug

  

duplicate

  

enhancement

  

help wanted

  

invalid

  

pull-request

Mirrored from GitHub Pull Request

  

question

  

refactoring

  

research

  

wontfix

No labels

bug

duplicate

enhancement

help wanted

invalid

pull-request

question

refactoring

research

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/sandman2-jeffknupp#245

No description provided.