2.0.17

Released: June 23, 2023

orm

• [orm] [bug] [regression] Fixed regression in the 2.0 series where a query that used undefer_group() with _orm.selectinload() or _orm.subqueryload() would raise an AttributeError. Pull request courtesy of Matthew Martin.

  References: #9870

• [orm] [bug] Fixed issue in ORM Annotated Declarative which prevented a _orm.declared_attr from being used on a mixin which did not return a Mapped datatype, and instead returned a supplemental ORM datatype such as AssociationProxy. The Declarative runtime would erroneously try to interpret this annotation as needing to be Mapped and raise an error.

  References: #9957

• [orm] [bug] [typing] Fixed typing issue where using the AssociationProxy return type from a _orm.declared_attr function was disallowed.

  References: #9957

• [orm] [bug] [regression] Fixed regression introduced in 2.0.16 by #9879 where passing a callable to the _orm.mapped_column.default parameter of _orm.mapped_column while also setting init=False would interpret this value as a Dataclass default value which would be assigned directly to new instances of the object directly, bypassing the default generator taking place as the _schema.Column.default value generator on the underlying _schema.Column. This condition is now detected so that the previous behavior is maintained, however a deprecation warning for this ambiguous use is emitted; to populate the default generator for a _schema.Column, the _orm.mapped_column.insert_default parameter should be used, which disambiguates from the _orm.mapped_column.default parameter whose name is fixed as per pep-681.

  References: #9936

• [orm] [bug] Additional hardening and documentation for the ORM _orm.Session "state change" system, which detects concurrent use of _orm.Session and _asyncio.AsyncSession objects; an additional check is added within the process to acquire connections from the underlying engine, which is a critical section with regards to internal connection management.

  References: #9973

• [orm] [bug] Fixed issue in ORM loader strategy logic which further allows for long chains of _orm.contains_eager() loader options across complex inheriting polymorphic / aliased / of_type() relationship chains to take proper effect in queries.

  References: #10006

• [orm] [bug] Fixed issue in support for the Enum datatype in the _orm.registry.type_annotation_map first added as part of #8859 where using a custom Enum with fixed configuration in the map would fail to transfer the Enum.name parameter, which among other issues would prevent PostgreSQL enums from working if the enum values were passed as individual values. Logic has been updated so that "name" is transferred over, but also that the default Enum which is against the plain Python enum.Enum class or other "empty" enum won't set a hardcoded name of "enum" either.

  References: #9963

orm declarative

• [orm] [declarative] [bug] A warning is emitted when an ORM _orm.relationship() and other MapperProperty objects are assigned to two different class attributes at once; only one of the attributes will be mapped. A warning for this condition was already in place for _schema.Column and _orm.mapped_column objects.

  References: #3532

typing

• [typing] [bug] Fixed typing issue which prevented _orm.WriteOnlyMapped and _orm.DynamicMapped attributes from being used fully within ORM queries.

  References: #9985

postgresql

• [postgresql] [usecase] The pg8000 dialect now supports RANGE and MULTIRANGE datatypes, using the existing RANGE API described at postgresql_ranges. Range and multirange types are supported in the pg8000 driver from version 1.29.8. Pull request courtesy Tony Locke.

  References: #9965

misc

• [bug] [ext] Fixed issue in mypy plugin for use with mypy 1.4.

  This change is also backported to: 1.4.49