]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
Filter attributes we don't map during a load_scalar_attributes
authorMike Bayer <mike_mp@zzzcomputing.com>
Sat, 28 Oct 2017 17:28:58 +0000 (13:28 -0400)
committerMike Bayer <mike_mp@zzzcomputing.com>
Sat, 28 Oct 2017 17:29:48 +0000 (13:29 -0400)
commitfd4289c5829d6498495ac59fe1dccb23b4975281
tree23881bd839a6ca99d62748ef910fc1c343c5284c
parentf7b957b589207cae98b6feec63be84ee6423c3ca
Filter attributes we don't map during a load_scalar_attributes

Fixed bug where a descriptor that is elsewhere a mapped column
or relationship within a hierarchy based on :class:`.AbstractConcreteBase`
would be referred towards during a refresh operation, causing an error
as the attribute is not mapped as a mapper property.
A similar issue can arise for other attributes like the "type" column
added by :class:`.AbstractConcreteBase` if the class fails to include
"concrete=True" in its mapper, however the check here should also
prevent that scenario from causing a problem.

Change-Id: I407b07a3a3e2c374da19fc86ed44b987d595dcfa
Fixes: #4124
doc/build/changelog/unreleased_11/4124.rst [new file with mode: 0644]
lib/sqlalchemy/orm/loading.py
lib/sqlalchemy/orm/mapper.py
test/ext/declarative/test_inheritance.py