From c3abfe50645abdb27e41639701a68d2e6eaeff2c Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Mon, 3 Oct 2016 16:55:54 -0400 Subject: 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 | 12 ++++++++++++ 1 file changed, 12 insertions(+) (limited to 'doc') diff --git a/doc/build/changelog/changelog_11.rst b/doc/build/changelog/changelog_11.rst index a3cc96f99..be104e4f2 100644 --- a/doc/build/changelog/changelog_11.rst +++ b/doc/build/changelog/changelog_11.rst @@ -21,6 +21,18 @@ .. changelog:: :version: 1.1.0 + .. change:: + :tags: bug, orm + :tickets: 3811 + + Made an adjustment to the bug fix first introduced in [ticket:3431] + that involves an object appearing in multiple contexts in a single + result set, such that an eager loader that would set the related + object value to be None will still fire off, thus satisfying the + load of that attribute. Previously, the adjustment only honored + a non-None value arriving for an eagerly loaded attribute in a + secondary row. + .. change:: :tags: bug, orm :tickets: 3808 -- cgit v1.2.1