]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
projects / thirdparty / sqlalchemy / sqlalchemy.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 946e71e) | patch
allow column named twice warning to take effect
authorMike Bayer <mike_mp@zzzcomputing.com>
Tue, 9 May 2023 15:33:30 +0000 (11:33 -0400)
committerMike Bayer <mike_mp@zzzcomputing.com>
Tue, 9 May 2023 15:34:17 +0000 (11:34 -0400)
commit4e3806861b19a00203f95b6ecbe411a4e252d152
tree7270372745caeed7f7b55d7ae358b42f53a29c6btree | snapshot
parent946e71efdfc93777027f4fd7360a524051be393dcommit | diff
allow column named twice warning to take effect

Fixed issue in :func:`_orm.mapped_column` construct where the correct
warning for "column X named directly multiple times" would not be emitted
when ORM mapped attributes referred to the same :class:`_schema.Column`, if
the :func:`_orm.mapped_column` construct were involved, raising an internal
assertion instead.

Fixes: #9630
Change-Id: I5d9dfaaa225aefb487c9cd981ba3ad78507bb577
doc/build/changelog/unreleased_20/9630.rst [new file with mode: 0644] blob
lib/sqlalchemy/orm/decl_base.py diff | blob | blame | history
test/orm/declarative/test_basic.py diff | blob | blame | history
Mirror of https://github.com/sqlalchemy/sqlalchemy.git