Log message:
py-sqlalchemy: updated to 2.0.45
2.0.45
orm
[orm] [bug]
Fixed issue where calling Mapper.add_property() within mapper event hooks such \ 
as MapperEvents.instrument_class(), MapperEvents.after_mapper_constructed(), or \ 
MapperEvents.before_mapper_configured() would raise an AttributeError because \ 
the mapper’s internal property collections were not yet initialized. The \ 
Mapper.add_property() method now handles early-stage property additions \ 
correctly, allowing properties including column properties, deferred columns, \ 
and relationships to be added during mapper initialization events. Pull request \ 
courtesy G Allajmi.
[orm] [bug]
Fixed issue in Python 3.14 where dataclass transformation would fail when a \ 
mapped class using MappedAsDataclass included a relationship() referencing a \ 
class that was not available at runtime (e.g., within a TYPE_CHECKING block). \ 
This occurred when using Python 3.14’s PEP 649 deferred annotations feature, \ 
which is the default behavior without a from __future__ import annotations \ 
directive.
examples
[examples] [bug]
Fixed the “short_selects” performance example where the cache was being used \ 
in all the examples, making it impossible to compare performance with and \ 
without the cache. Less important comparisons like “lambdas” and “baked \ 
queries” have been removed.
sql
[sql] [bug]
Some improvements to the ClauseElement.params() method to replace bound \ 
parameters in a query were made, however the ultimate issue in 12915 involving \ 
ORM aliased() cannot be fixed fully until 2.1, where the method is being \ 
rewritten to work without relying on Core cloned traversal.
[sql] [bug]
Fixed issue where using the ColumnOperators.in_() operator with a nested \ 
CompoundSelect statement (e.g. an INTERSECT of UNION queries) would raise a \ 
NotImplementedError when the nested compound select was the first argument to \ 
the outer compound select. The _scalar_type() internal method now properly \ 
handles nested compound selects.
typing
[typing] [bug]
Fixed typing issue where Select.with_for_update() would not support lists of ORM \ 
entities or other FROM clauses in the Select.with_for_update.of parameter. Pull \ 
request courtesy Shamil.
[typing] [bug]
Fixed typing issue where coalesce would not return the correct return type when \ 
a nullable form of that argument were passed, even though this function is meant \ 
to select the non-null entry among possibly null arguments. Pull request \ 
courtesy Yannick PÉROUX.
postgresql
[postgresql] [usecase]
Added support for reflection of collation in types for PostgreSQL. The collation \ 
will be set only if different from the default one for the type. Pull request \ 
courtesy Denis Laxalde.
[postgresql] [bug]
Fixed issue where PostgreSQL dialect options such as postgresql_include on \ 
PrimaryKeyConstraint and UniqueConstraint were rendered in the wrong position \ 
when combined with constraint deferrability options like deferrable=True. Pull \ 
request courtesy G Allajmi.
[postgresql] [bug]
Fixed the structure of the SQL string used for the “Insert Many Values” \ 
Behavior for INSERT statements feature when an explicit sequence with nextval() \ 
is used. The SQL function invocation for the sequence has been moved from being \ 
rendered inline within each tuple inside of VALUES to being rendered once in the \ 
SELECT that reads from VALUES. This change ensures the function is invoked in \ 
the correct order as rows are processed, rather than assuming PostgreSQL will \ 
execute inline function calls within VALUES in a particular order. While current \ 
PostgreSQL versions appear to handle the previous approach correctly, the \ 
database does not guarantee this behavior for future versions.
mysql
[mysql] [usecase]
Added support for MySQL 8.0.1 + FOR SHARE to be emitted for the \ 
Select.with_for_update() method, which offers compatibility with NOWAIT and SKIP \ 
LOCKED. The new syntax is used only for MySQL when version 8.0.1 or higher is \ 
detected. Pull request courtesy JetDrag.
sqlite
[sqlite] [bug] [reflection]
A series of improvements have been made for reflection of CHECK constraints on \ 
SQLite. The reflection logic now correctly handles table names containing the \ 
strings “CHECK” or “CONSTRAINT”, properly supports all four SQLite \ 
identifier quoting styles (double quotes, single quotes, brackets, and \ 
backticks) for constraint names, and accurately parses CHECK constraint \ 
expressions containing parentheses within string literals using balanced \ 
parenthesis matching with string context tracking. Big thanks to GruzdevAV for \ 
new test cases and implementation ideas.
[sqlite] [bug]
Fixed issue where SQLite dialect would fail to reflect constraint names that \ 
contained uppercase letters or other characters requiring quoting. The regular \ 
expressions used to parse primary key, foreign key, and unique constraint names \ 
from the CREATE TABLE statement have been updated to properly handle both quoted \ 
and unquoted constraint names.
tests
[tests] [change]
A noxfile.py has been added to allow testing with nox. This is a direct port of \ 
2.1’s move to nox, however leaves the tox.ini file in place and retains all \ 
test documentation in terms of tox. Version 2.1 will move to nox fully, \ 
including deprecation warnings for tox and new testing documentation.

Log message:
py-sqlalchemy: updated to 2.0.44
2.0.44
platform
[platform] [bug]
Unblocked automatic greenlet installation for Python 3.14 now that there are \ 
greenlet wheels on pypi for python 3.14.
orm
[orm] [usecase]
The way ORM Annotated Declarative interprets Python PEP 695 type aliases in \ 
Mapped[] annotations has been refined to expand the lookup scheme. A PEP 695 \ 
type can now be resolved based on either its direct presence in \ 
registry.type_annotation_map or its immediate resolved value, as long as a \ 
recursive lookup across multiple PEP 695 types is not required for it to \ 
resolve. This change reverses part of the restrictions introduced in 2.0.37 as \ 
part of 11955, which deprecated (and disallowed in 2.1) the ability to resolve \ 
any PEP 695 type that was not explicitly present in \ 
registry.type_annotation_map. Recursive lookups of PEP 695 types remains \ 
deprecated in 2.0 and disallowed in version 2.1, as do implicit lookups of \ 
NewType types without an entry in registry.type_annotation_map.
engine
[engine] [bug]
Implemented initial support for free-threaded Python by adding new tests and \ 
reworking the test harness to include Python 3.13t and Python 3.14t in test \ 
runs. Two concurrency issues have been identified and fixed: the first involves \ 
initialization of the .c collection on a FromClause, a continuation of 12302, \ 
where an optional mutex under free-threading is added; the second involves \ 
synchronization of the pool “first_connect” event, which first received \ 
thread synchronization in 2964, however under free-threading the creation of the \ 
mutex itself runs under the same free-threading mutex. Support for free-threaded \ 
wheels on Pypi is implemented as well within the 2.1 series only. Initial pull \ 
request and test suite courtesy Lysandros Nikolaou.
sql
[sql] [bug]
Improved the implementation of UpdateBase.returning() to use more robust logic \ 
in setting up the .c collection of a derived statement such as a CTE. This fixes \ 
issues related to RETURNING clauses that feature expressions based on returned \ 
columns with or without qualifying labels.
schema
[schema] [bug]
Fixed issue where MetaData.reflect() did not forward dialect-specific keyword \ 
arguments to the Inspector methods, causing options like oracle_resolve_synonyms \ 
to be ignored during reflection. The method now ensures that all extra kwargs \ 
passed to MetaData.reflect() are forwarded to Inspector.get_table_names() and \ 
related reflection methods. Pull request courtesy Lukáš Kožušník.
typing
[typing] [bug]
Fixed typing bug where the Session.execute() method advertised that it would \ 
return a CursorResult if given an insert/update/delete statement. This is not \ 
the general case as several flavors of ORM insert/update do not actually yield a \ 
CursorResult which cannot be differentiated at the typing overload level, so the \ 
method now yields Result in all cases. For those cases where CursorResult is \ 
known to be returned and the .rowcount attribute is required, please use \ 
typing.cast().
[typing] [bug]
Added new decorator mapped_as_dataclass(), which is a function based form of \ 
registry.mapped_as_dataclass(); the method form registry.mapped_as_dataclass() \ 
does not seem to be correctly recognized within the scope of PEP 681 in recent \ 
mypy versions.
postgresql
[postgresql] [bug]
Fixed issue where selecting an enum array column containing NULL values would \ 
fail to parse properly in the PostgreSQL dialect. The _split_enum_values() \ 
function now correctly handles NULL entries by converting them to Python None \ 
values.
sqlite
[sqlite] [bug]
Fixed issue where SQLite table reflection would fail for tables using WITHOUT \ 
ROWID and/or STRICT table options when the table contained generated columns. \ 
The regular expression used to parse CREATE TABLE statements for generated \ 
column detection has been updated to properly handle these SQLite table options \ 
that appear after the column definitions. Pull request courtesy Tip ten Brink.
mssql
[mssql] [bug]
Improved the base implementation of the asyncio cursor such that it includes the \ 
option for the underlying driver’s cursor to be actively closed in those cases \ 
where it requires await in order to complete the close sequence, rather than \ 
relying on garbage collection to “close” it, when a plain Result is returned \ 
that does not use await for any of its methods. The previous approach of relying \ 
on gc was fine for MySQL and SQLite dialects but has caused problems with the \ 
aioodbc implementation on top of SQL Server. The new option is enabled for those \ 
dialects which have an “awaitable” cursor.close(), which includes the \ 
aioodbc, aiomysql, and asyncmy dialects (aiosqlite is also modified for 2.1 \ 
only).
[mssql] [bug]
Fixed issue where the index reflection for SQL Server would not correctly return \ 
the order of the column inside an index when the order of the columns in the \ 
index did not match the order of the columns in the table. Pull request courtesy \ 
of Allen Chen.
[mssql] [bug] [reflection]
Fixed issue in the MSSQL dialect’s foreign key reflection query where \ 
duplicate rows could be returned when a foreign key column and its referenced \ 
primary key column have the same name, and both the referencing and referenced \ 
tables have indexes with the same name. This resulted in an \ 
“ForeignKeyConstraint with duplicate source column references are not \ 
supported” error when attempting to reflect such tables. The query has been \ 
corrected to exclude indexes on the child table when looking for unique indexes \ 
referenced by foreign keys.
misc
[bug] [ext]
Fixed issue caused by an unwanted functional change while typing the MutableList \ 
class. This change also reverts all other functional changes done in the same \ 
change.

Log message:
*: remove reference to (removed) Python 3.9

Log message:
py-sqlalchemy: updated to 2.0.43
2.0.43
orm
[orm] [bug]
Fixed issue where using the post_update feature would apply incorrect \ 
“pre-fetched” values to the ORM objects after a multi-row UPDATE process \ 
completed. These “pre-fetched” values would come from any column that had an \ 
Column.onupdate callable or a version id generator used by \ 
Mapper.version_id_generator; for a version id generator that delivered random \ 
identifiers like timestamps or UUIDs, this incorrect data would lead to a DELETE \ 
statement against those same rows to fail in the next step.
[orm] [bug]
Fixed issue where mapped_column.use_existing_column parameter in mapped_column() \ 
would not work when the mapped_column() is used inside of an Annotated type \ 
alias in polymorphic inheritance scenarios. The parameter is now properly \ 
recognized and processed during declarative mapping configuration.
[orm] [bug]
Improved the implementation of the selectin_polymorphic() inheritance loader \ 
strategy to properly render the IN expressions using chunks of 500 records each, \ 
in the same manner as that of the selectinload() relationship loader strategy. \ 
Previously, the IN expression would be arbitrarily large, leading to failures on \ 
databases that have limits on the size of IN expressions including Oracle \ 
Database.
engine
[engine] [usecase]
Added new parameter create_engine.skip_autocommit_rollback which provides for a \ 
per-dialect feature of preventing the DBAPI .rollback() from being called under \ 
any circumstances, if the connection is detected as being in “autocommit” \ 
mode. This improves upon a critical performance issue identified in MySQL \ 
dialects where the network overhead of the .rollback() call remains prohibitive \ 
even if autocommit mode is set.
See also
Fully preventing ROLLBACK calls under autocommit
postgresql
[postgresql] [bug]
Fixed regression in PostgreSQL dialect where JSONB subscription syntax would \ 
generate incorrect SQL for JSONB-returning functions, causing syntax errors. The \ 
dialect now properly wraps function calls and expressions in parentheses when \ 
using the [] subscription syntax, generating (function_call)[index] instead of \ 
function_call[index] to comply with PostgreSQL syntax requirements.
oracle
[oracle] [usecase]
Extended VECTOR to support sparse vectors. This update introduces \ 
VectorStorageType to specify sparse or dense storage and added SparseVector. \ 
Pull request courtesy Suraj Shaw.

Log message:
py-sqlalchemy: updated to 2.0.42
2.0.42
orm
[orm] [usecase]
Added dataclass_metadata argument to all ORM attribute constructors that accept \ 
dataclasses parameters, e.g. mapped_column.dataclass_metadata, \ 
relationship.dataclass_metadata, etc. It’s passed to the underlying dataclass \ 
metadata attribute of the dataclass field. Pull request courtesy Sigmund Lahn.
[orm] [bug]
Implemented the defer(), undefer() and load_only() loader options to work for \ 
composite attributes, a use case that had never been supported previously.
[orm] [bug]
Fixed bug where the ORM would pull in the wrong column into an UPDATE when a key \ 
name inside of the ValuesBase.values() method could be located from an ORM \ 
entity mentioned in the statement, but where that ORM entity was not the actual \ 
table that the statement was inserting or updating. An extra check for this edge \ 
case is added to avoid this problem.
engine
[engine]
Improved validation of execution parameters passed to the Connection.execute() \ 
and similar methods to provided a better error when tuples are passed in. \ 
Previously the execution would fail with a difficult to understand error \ 
message.
sql
[sql] [usecase]
The values() construct gains a new method Values.cte(), which allows creation of \ 
a named, explicit-columns CTE against an unnamed VALUES expression, producing a \ 
syntax that allows column-oriented selection from a VALUES construct on modern \ 
versions of PostgreSQL, SQLite, and MariaDB.
[sql] [bug]
Fixed issue where select() of a free-standing scalar expression that has a unary \ 
operator applied, such as negation, would not apply result processors to the \ 
selected column even though the correct type remains in place for the unary \ 
expression.
[sql] [bug]
Hardening of the compiler’s actions for UPDATE statements that access multiple \ 
tables to report more specifically when tables or aliases are referenced in the \ 
SET clause; on cases where the backend does not support secondary tables in the \ 
SET clause, an explicit error is raised, and on the MySQL or similar backends \ 
that support such a SET clause, more specific checking for not-properly-included \ 
tables is performed. Overall the change is preventing these erroneous forms of \ 
UPDATE statements from being compiled, whereas previously it was relied on the \ 
database to raise an error, which was not always guaranteed to happen, or to be \ 
non-ambiguous, due to cases where the parent table included the same column name \ 
as the secondary table column being updated.
postgresql
[postgresql] [usecase]
Added support for PostgreSQL 14+ JSONB subscripting syntax. When connected to \ 
PostgreSQL 14 or later, JSONB columns now automatically use the native subscript \ 
notation jsonb_col['key'] instead of the arrow operator jsonb_col -> 'key' \ 
for both read and write operations. This provides better compatibility with \ 
PostgreSQL’s native JSONB subscripting feature while maintaining backward \ 
compatibility with older PostgreSQL versions. JSON columns continue to use the \ 
traditional arrow syntax regardless of PostgreSQL version.
[postgresql] [usecase]
Added postgresql_ops key to the dialect_options entry in reflected dictionary. \ 
This maps names of columns used in the index to respective operator class, if \ 
distinct from the default one for column’s data type. Pull request courtesy \ 
Denis Laxalde.
See also
Operator Classes
[postgresql] [bug] [reflection]
Fixed regression caused by 10665 where the newly modified constraint reflection \ 
query would fail on older versions of PostgreSQL such as version 9.6. Pull \ 
request courtesy Denis Laxalde.
[postgresql] [bug]
Re-raise catched CancelledError in the terminate method of the asyncpg dialect \ 
to avoid possible hangs of the code execution.
[postgresql] [bug] [reflection]
Fixes bug that would mistakenly interpret a domain or enum type with name \ 
starting in interval as an INTERVAL type while reflecting a table.
mysql
[mysql] [bug]
Fixed yet another regression caused by by the DEFAULT rendering changes in \ 
2.0.40 12425, similar to 12488, this time where using a CURRENT_TIMESTAMP \ 
function with a fractional seconds portion inside a textual default value would \ 
also fail to be recognized as a non-parenthesized server default.
mssql
[mssql] [bug]
Reworked SQL Server column reflection to be based on the sys.columns table \ 
rather than information_schema.columns view. By correctly using the SQL Server \ 
object_id() function as a lead and joining to related tables on object_id rather \ 
than names, this repairs a variety of issues in SQL Server reflection, \ 
including:
Issue where reflected column comments would not correctly line up with the \ 
columns themselves in the case that the table had been ALTERed
Correctly targets tables with awkward names such as names with brackets, when \ 
reflecting not just the basic table / columns but also extended information \ 
including IDENTITY, computed columns, comments which did not work previously
Correctly targets IDENTITY, computed status from temporary tables which did not \ 
work previously

Log message:
*: mark more py-cython dependencies as needing Python>=3.11

Log message:
py-sqlalchemy: updated to 2.0.41
2.0.41
platform
[platform] [bug]
Adjusted the test suite as well as the ORM’s method of scanning classes for \ 
annotations to work under current beta releases of Python 3.14 (currently \ 
3.14.0b1) as part of an ongoing effort to support the production release of this \ 
Python release. Further changes to Python’s means of working with annotations \ 
is expected in subsequent beta releases for which SQLAlchemy’s test suite will \ 
need further adjustments.
engine
[engine] [bug]
The error message that is emitted when a URL cannot be parsed no longer includes \ 
the URL itself within the error message.
typing
[typing] [bug]
Removed __getattr__() rule from sqlalchemy/__init__.py that appeared to be \ 
trying to correct for a previous typographical error in the imports. This rule \ 
interferes with type checking and is removed.
postgresql
[postgresql] [usecase]
Added support for postgresql_include keyword argument to UniqueConstraint and \ 
PrimaryKeyConstraint. Pull request courtesy Denis Laxalde.
See also
PostgreSQL Constraint Options
mysql
[mysql] [bug]
Fixed regression caused by the DEFAULT rendering changes in version 2.0.40 via \ 
12425 where using lowercase on update in a MySQL server default would \ 
incorrectly apply parenthesis, leading to errors when MySQL interpreted the \ 
rendered DDL. Pull request courtesy Alexander Ruehe.
sqlite
[sqlite] [bug]
Fixed and added test support for some SQLite SQL functions hardcoded into the \ 
compiler, most notably the localtimestamp function which rendered with incorrect \ 
internal quoting.
oracle
[oracle] [usecase]
Added new datatype VECTOR and accompanying DDL and DQL support to fully support \ 
this type for Oracle Database. This change includes the base VECTOR type that \ 
adds new type-specific methods l2_distance, cosine_distance, inner_product as \ 
well as new parameters oracle_vector for the Index construct, allowing vector \ 
indexes to be configured, and oracle_fetch_approximate for the Select.fetch() \ 
clause. Pull request courtesy Suraj Shaw.
See also
VECTOR Datatype
misc
[bug] [installation]
Removed the “license classifier” from setup.cfg for SQLAlchemy 2.0, which \ 
eliminates loud deprecation warnings when building the package. SQLAlchemy 2.1 \ 
will use a full PEP 639 configuration in pyproject.toml while SQLAlchemy 2.0 \ 
remains using setup.cfg for setup.

Log message:
py-sqlalchemy: updated to 2.0.40
2.0.40
Released: March 27, 2025
orm
[orm] [bug]
Fixed regression which occurred as of 2.0.37 where the checked ArgumentError \ 
that’s raised when an inappropriate type or object is used inside of a Mapped \ 
annotation would raise TypeError with “boolean value of this clause is not \ 
defined” if the object resolved into a SQL expression in a boolean context, \ 
for programs where future annotations mode was not enabled. This case is now \ 
handled explicitly and a new error message has also been tailored for this case. \ 
In addition, as there are at least half a dozen distinct error scenarios for \ 
intepretation of the Mapped construct, these scenarios have all been unified \ 
under a new subclass of ArgumentError called MappedAnnotationError, to provide \ 
some continuity between these different scenarios, even though specific \ 
messaging remains distinct.
[orm] [bug]
Fixed regression in ORM Annotated Declarative class interpretation caused by \ 
typing_extension==4.13.0 that introduced a different implementation for \ 
TypeAliasType while SQLAlchemy assumed that it would be equivalent to the typing \ 
version, leading to pep-695 type annotations not resolving to SQL types as \ 
expected.
sql
[sql] [usecase]
Implemented support for the GROUPS frame specification in window functions by \ 
adding over.groups option to over() and FunctionElement.over(). Pull request \ 
courtesy Kaan Dikmen.
[sql] [bug]
Fixed issue in CTE constructs involving multiple DDL Insert statements with \ 
multiple VALUES parameter sets where the bound parameter names generated for \ 
these parameter sets would conflict, generating a compile time error.
[sql] [bug]
Fixed regression caused by 7471 leading to a SQL compilation issue where name \ 
disambiguation for two same-named FROM clauses with table aliasing in use at the \ 
same time would produce invalid SQL in the FROM clause with two “AS” clauses \ 
for the aliased table, due to double aliasing.
asyncio
[asyncio] [bug]
Fixed issue where AsyncSession.get_transaction() and \ 
AsyncSession.get_nested_transaction() would fail with NotImplementedError if the \ 
“proxy transaction” used by AsyncSession were garbage collected and needed \ 
regeneration.
postgresql
[postgresql] [usecase]
Added support for specifying a list of columns for SET NULL and SET DEFAULT \ 
actions of ON DELETE clause of foreign key definition on PostgreSQL. Pull \ 
request courtesy Denis Laxalde.
See also
PostgreSQL Constraint Options
[postgresql] [usecase]
When building a PostgreSQL ARRAY literal using array with an empty clauses \ 
argument, the array.type_ parameter is now significant in that it will be used \ 
to render the resulting ARRAY[] SQL expression with a cast, such as \ 
ARRAY[]::INTEGER. Pull request courtesy Denis Laxalde.
mysql
[mysql] [bug]
Support has been re-added for the MySQL-Connector/Python DBAPI using the \ 
mysql+mysqlconnector:// URL scheme. The DBAPI now works against modern MySQL \ 
versions as well as MariaDB versions (in the latter case it’s required to pass \ 
charset/collation explicitly). Note however that server side cursor support is \ 
disabled due to unresolved issues with this driver.
[mysql] [bug]
Fixed issue in MySQL server default reflection where a default that has spaces \ 
would not be correctly reflected. Additionally, expanded the rules for when to \ 
apply parenthesis to a server default in DDL to suit the general case of a \ 
default string that contains non-word characters such as spaces or operators and \ 
is not a string literal.
sqlite
[sqlite] [bug]
Expanded the rules for when to apply parenthesis to a server default in DDL to \ 
suit the general case of a default string that contains non-word characters such \ 
as spaces or operators and is not a string literal.