]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
Honor additional row coming in with value of None
authorMike Bayer <mike_mp@zzzcomputing.com>
Mon, 3 Oct 2016 20:55:54 +0000 (16:55 -0400)
committerMike Bayer <mike_mp@zzzcomputing.com>
Tue, 4 Oct 2016 16:07:08 +0000 (12:07 -0400)
commitc3abfe50645abdb27e41639701a68d2e6eaeff2c
tree2dc506ea94a33229ff424710f8facf1049f29f5e
parent728ce8cc480d0ada690e5a97067cff821b9a65f3
Honor additional row coming in with value of None

The change in #3431 still checks that the instance() is
non-None, deferring to other loading schemes if it is.
These columns are dedicated towards the entity however, so if the value
is None, we should set it.  If it conflicts, we are detecting that
in any case.

Change-Id: I223768e2898e843f953e910da1f9564b137d95e4
Fixes: #3811
doc/build/changelog/changelog_11.rst
lib/sqlalchemy/orm/strategies.py
test/orm/test_eager_relations.py