]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
ensure result_map objects collection is non-empty
authorMike Bayer <mike_mp@zzzcomputing.com>
Tue, 30 Apr 2024 19:41:04 +0000 (15:41 -0400)
committerMike Bayer <mike_mp@zzzcomputing.com>
Tue, 30 Apr 2024 19:50:09 +0000 (15:50 -0400)
commitf505795a931f3aba1709cb0b731d6fbd74007b38
tree6c785ce28dfe8b76d9ebe5185d0e8e588554e5c0
parent1c1c8518fc04e1f6f9477f02a73ec490afd6daaa
ensure result_map objects collection is non-empty

Fixed issue in cursor handling which affected handling of duplicate
:class:`_sql.Column` or similar objcts in the columns clause of
:func:`_sql.select`, both in combination with arbitary :func:`_sql.text()`
clauses in the SELECT list, as well as when attempting to retrieve
:meth:`_engine.Result.mappings` for the object, which would lead to an
internal error.

Fixes: #11306
Change-Id: I418073b2fdba86b2121b6d00eaa40b1805b69bb8
(cherry picked from commit fbb7172c69402d5f0776edc96d1c23a7cfabd3d0)
doc/build/changelog/unreleased_20/11306.rst [new file with mode: 0644]
lib/sqlalchemy/engine/cursor.py
lib/sqlalchemy/sql/compiler.py
test/sql/test_resultset.py