]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
Use ARRAY type for any_(), all_() coercion
authorMike Bayer <mike_mp@zzzcomputing.com>
Sat, 20 Sep 2025 18:08:55 +0000 (14:08 -0400)
committerMike Bayer <mike_mp@zzzcomputing.com>
Sat, 20 Sep 2025 18:25:22 +0000 (14:25 -0400)
commit41718f8753baa8751831103a21f3b682079852ee
treec928e4700953e6e16d44cbb2f54440c39f2886a4
parent774b8d89f944c3018af486f4d39c6d09acdb4dcf
Use ARRAY type for any_(), all_() coercion

Fixed issue where the :func:`_sql.any_` and :func:`_sql.all_` aggregation
operators would not correctly coerce the datatype of the compared value, in
those cases where the compared value were not a simple int/str etc., such
as a Python ``Enum`` or other custom value.   This would lead to execution
time errors for these values.  This issue is essentially the same as
:ticket:`6515` which was for the now-legacy :meth:`.ARRAY.any` and
:meth:`.ARRAY.all` methods.

Fixes: #12874
Change-Id: I980894c23b9974bc84d584a1a4c5fae72dded6d3
(cherry picked from commit aaa85f707e312bbf21b21926b0901aa14e3f3856)
doc/build/changelog/unreleased_20/12874.rst [new file with mode: 0644]
lib/sqlalchemy/sql/elements.py
test/dialect/postgresql/test_types.py
test/sql/test_operators.py