diff options
author | Mike Bayer <mike_mp@zzzcomputing.com> | 2017-09-10 00:01:18 -0400 |
---|---|---|
committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2017-09-10 00:01:18 -0400 |
commit | db170dd4529c5176d38db649dd75427a932b47fe (patch) | |
tree | f7f25635bb520f34aa4d2b22d63d06592b58a00a /lib/sqlalchemy/testing/assertions.py | |
parent | ca2c42df6ba108289031ccecd030b7aa196a66d6 (diff) | |
download | sqlalchemy-db170dd4529c5176d38db649dd75427a932b47fe.tar.gz |
Warn instead of raise for unmapped column that matches on keyticket_4073
Modified the change made to the ORM update/delete evaluator in
:ticket:`3366` such that if an unmapped column expression is present
in the update or delete, if the evaluator can match its name to the
mapped columns of the target class, a warning is emitted, rather than
raising UnevaluatableError. This is essentially the pre-1.2 behavior,
and is to allow migration for applications that are currently relying
upon this pattern. However, if the given attribute name cannot be
matched to the columns of the mapper, the UnevaluatableError is
still raised, which is what was fixed in :ticket:`3366`.
Change-Id: I658ed0dbf485b7f8009774f9c12d9912447abd2a
Fixes: #4073
Diffstat (limited to 'lib/sqlalchemy/testing/assertions.py')
0 files changed, 0 insertions, 0 deletions