CVS commit: pkgsrc/databases/py-sqlalchemy

["Adam Ciarcinski" <adam%netbsd.org@localhost>]

Module Name:    pkgsrc
Committed By:   adam
Date:           Tue Feb 24 19:40:24 UTC 2026

Modified Files:
        pkgsrc/databases/py-sqlalchemy: Makefile distinfo

Log Message:
py-sqlalchemy: updated to 2.0.47

2.0.47

orm

[orm] [bug]

Fixed issue when using ORM mappings with Python 3.14’s PEP 649 feature that no longer requires “future annotations”, where the ORM’s introspection of the __init__ method of mapped classes would fail 
if non-present identifiers in annotations were present. The vendored getfullargspec() method has been amended to use Format.FORWARDREF under Python 3.14 to prevent resolution of names that aren’t 
present.

engine

[engine] [usecase]

The connection object returned by Engine.raw_connection() now supports the context manager protocol, automatically returning the connection to the pool when exiting the context.

postgresql

[postgresql] [bug]

Fixed an issue in the PostgreSQL dialect where foreign key constraint reflection would incorrectly swap or fail to capture onupdate and ondelete values when these clauses appeared in a different 
order than expected in the constraint definition. This issue primarily affected PostgreSQL-compatible databases such as CockroachDB, which may return ON DELETE before ON UPDATE in the constraint 
definition string. The reflection logic now correctly parses both clauses regardless of their ordering.

[postgresql] [bug]

Fixed issue in the “Insert Many Values” Behavior for INSERT statements feature where using PostgreSQL’s ON CONFLICT clause with Insert.returning.sort_by_parameter_order enabled would generate invalid 
SQL when the insert used an implicit sentinel (server-side autoincrement primary key). The generated SQL would incorrectly declare a sentinel counter column in the imp_sen table alias without 
providing corresponding values in the VALUES clause, leading to a ProgrammingError indicating column count mismatch. The fix allows batch execution mode when embed_values_counter is active, as the 
embedded counter provides the ordering capability needed even with upsert behaviors, rather than unnecessarily downgrading to row-at-a-time execution.

[postgresql] [bug]

Fixed issue where Insert.on_conflict_do_update() parameters were not respecting compilation options such as literal_binds=True. Pull request courtesy Loïc Simon.

[postgresql] [bug]

Fixed issue where Insert.on_conflict_do_update() using parametrized bound parameters in the set_ clause would fail when used with executemany batching. For dialects that use the 
use_insertmanyvalues_wo_returning optimization (psycopg2), insertmanyvalues is now disabled when there is an ON CONFLICT clause. For cases with RETURNING, row-at-a-time mode is used when the SET 
clause contains parametrized bindparams (bindparams that receive values from the parameters dict), ensuring each row’s parameters are correctly applied. ON CONFLICT statements using expressions like 
excluded.<column> continue to batch normally.

mysql

[mysql] [bug]

Fixed issue where DDL compilation options were registered to the hard-coded dialect name mysql. This made it awkward for MySQL-derived dialects like MariaDB, StarRocks, etc. to work with such options 
when different sets of options exist for different platforms. Options are now registered under the actual dialect name, and a fallback was added to help avoid errors when an option does not exist for 
that dialect.

To maintain backwards compatibility, when using the MariaDB dialect with the options mysql_with_parser or mysql_using without also specifying the corresponding mariadb_ prefixed options, a 
deprecation warning will be emitted. The mysql_ prefixed options will continue to work during the deprecation period. Users should update their code to additionally specify mariadb_with_parser and 
mariadb_using when using the mariadb:// dialect, or specify both options to support both dialects.

Pull request courtesy Tiansu Yu.

sqlite

[sqlite] [bug]

Fixed issue where Insert.on_conflict_do_update() parameters were not respecting compilation options such as literal_binds=True. Pull request courtesy Loïc Simon.

[sqlite] [bug]

Fixed issue where Insert.on_conflict_do_update() using parametrized bound parameters in the set_ clause would fail when used with executemany batching. Row-at-a-time mode is now used for ON CONFLICT 
statements with RETURNING that contain parametrized bindparams, ensuring each row’s parameters are correctly applied. ON CONFLICT statements using expressions like excluded.<column> continue to batch 
normally.


To generate a diff of this commit:
cvs rdiff -u -r1.95 -r1.96 pkgsrc/databases/py-sqlalchemy/Makefile
cvs rdiff -u -r1.82 -r1.83 pkgsrc/databases/py-sqlalchemy/distinfo

Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.

Modified files:

Index: pkgsrc/databases/py-sqlalchemy/Makefile
diff -u pkgsrc/databases/py-sqlalchemy/Makefile:1.95 pkgsrc/databases/py-sqlalchemy/Makefile:1.96
--- pkgsrc/databases/py-sqlalchemy/Makefile:1.95        Sun Jan 25 13:16:09 2026
+++ pkgsrc/databases/py-sqlalchemy/Makefile     Tue Feb 24 19:40:24 2026
@@ -1,6 +1,6 @@
-# $NetBSD: Makefile,v 1.95 2026/01/25 13:16:09 adam Exp $
+# $NetBSD: Makefile,v 1.96 2026/02/24 19:40:24 adam Exp $
 
-DISTNAME=      sqlalchemy-2.0.46
+DISTNAME=      sqlalchemy-2.0.47
 PKGNAME=       ${PYPKGPREFIX}-${DISTNAME}
 CATEGORIES=    databases python
 MASTER_SITES=  ${MASTER_SITE_PYPI:=S/SQLAlchemy/}

Index: pkgsrc/databases/py-sqlalchemy/distinfo
diff -u pkgsrc/databases/py-sqlalchemy/distinfo:1.82 pkgsrc/databases/py-sqlalchemy/distinfo:1.83
--- pkgsrc/databases/py-sqlalchemy/distinfo:1.82        Sun Jan 25 13:16:10 2026
+++ pkgsrc/databases/py-sqlalchemy/distinfo     Tue Feb 24 19:40:24 2026
@@ -1,5 +1,5 @@
-$NetBSD: distinfo,v 1.82 2026/01/25 13:16:10 adam Exp $
+$NetBSD: distinfo,v 1.83 2026/02/24 19:40:24 adam Exp $
 
-BLAKE2s (sqlalchemy-2.0.46.tar.gz) = 01034508817155fe5d9d218f5ffd59f6e1c9f92c232ebfc64b93c8c9ca7fef0a
-SHA512 (sqlalchemy-2.0.46.tar.gz) = bc1fb1983207384e109c27c09eddbbfd96c80324349d93f084c922f5d1fc82c8f3ec63d9e9f10bdccc3a8ee902aa517adc1cc2db0d05302a52b0425ebbbc3aa7
-Size (sqlalchemy-2.0.46.tar.gz) = 9865393 bytes
+BLAKE2s (sqlalchemy-2.0.47.tar.gz) = ee31e7cf52569406fe4eeeb44754211727d6ceec06f7525fe57d95916e5326f9
+SHA512 (sqlalchemy-2.0.47.tar.gz) = aa2030e769e2010a475cb1572df5b38cddf17f4cc1a8b268254682d1844089154b7cc3c548ff2d609aa4473c384c1f69409318bb5b81c13a55d1c08a2e592e96
+Size (sqlalchemy-2.0.47.tar.gz) = 9886323 bytes