CVS commit: pkgsrc/databases/py-sqlalchemy

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

Module Name:    pkgsrc
Committed By:   adam
Date:           Sat Aug  9 05:42:57 UTC 2025

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

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


To generate a diff of this commit:
cvs rdiff -u -r1.89 -r1.90 pkgsrc/databases/py-sqlalchemy/Makefile
cvs rdiff -u -r1.77 -r1.78 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.89 pkgsrc/databases/py-sqlalchemy/Makefile:1.90
--- pkgsrc/databases/py-sqlalchemy/Makefile:1.89        Fri Jul  4 09:08:33 2025
+++ pkgsrc/databases/py-sqlalchemy/Makefile     Sat Aug  9 05:42:57 2025
@@ -1,6 +1,6 @@
-# $NetBSD: Makefile,v 1.89 2025/07/04 09:08:33 wiz Exp $
+# $NetBSD: Makefile,v 1.90 2025/08/09 05:42:57 adam Exp $
 
-DISTNAME=      sqlalchemy-2.0.41
+DISTNAME=      sqlalchemy-2.0.42
 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.77 pkgsrc/databases/py-sqlalchemy/distinfo:1.78
--- pkgsrc/databases/py-sqlalchemy/distinfo:1.77        Fri May 16 12:54:01 2025
+++ pkgsrc/databases/py-sqlalchemy/distinfo     Sat Aug  9 05:42:57 2025
@@ -1,5 +1,5 @@
-$NetBSD: distinfo,v 1.77 2025/05/16 12:54:01 adam Exp $
+$NetBSD: distinfo,v 1.78 2025/08/09 05:42:57 adam Exp $
 
-BLAKE2s (sqlalchemy-2.0.41.tar.gz) = abe635cf9129f0182b18d57c69f5de4c4ff7026b85dc6bd53d0d74f6d18b309e
-SHA512 (sqlalchemy-2.0.41.tar.gz) = bb8df574a0e2a0faf8a44e8d217f9eb14b0138aaae7dd947c94b3c4efa6c73b2cf9199303ffed679778002804bc5aa5583b16ddd986f7b4b9235c9d951e284e4
-Size (sqlalchemy-2.0.41.tar.gz) = 9689424 bytes
+BLAKE2s (sqlalchemy-2.0.42.tar.gz) = 358dad8685a3fb70cc8f570a193a7567c471856a606edd0e45f359f0d6693344
+SHA512 (sqlalchemy-2.0.42.tar.gz) = 4784c37c3b359ce6de8f23dbbff137e90a60c635c404c125be71f37de4c59661d181114b508ad0171d4c0cab1368a40229f1d4c6725d7a3a066c1fd0e5da4ee7
+Size (sqlalchemy-2.0.42.tar.gz) = 9749972 bytes