From: Mike Bayer Date: Fri, 2 Mar 2018 15:45:42 +0000 (-0500) Subject: Fix enable_relationship_loading() works fine w/ one-to-many X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=cbd9ea6785d5cbbb315ab5461400e41c33d5ad2b;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git Fix enable_relationship_loading() works fine w/ one-to-many Change-Id: I6efb62afa02be4d42482cfdbec739a5c6ab32bd7 (cherry picked from commit fde2f77fd1978d4162ab01bc05bb5c793bc733b2) --- diff --git a/lib/sqlalchemy/orm/session.py b/lib/sqlalchemy/orm/session.py index 1527fcab37..979da0754c 100644 --- a/lib/sqlalchemy/orm/session.py +++ b/lib/sqlalchemy/orm/session.py @@ -1991,9 +1991,9 @@ class Session(_SessionClassMethods): Accesses of attributes mapped with :func:`.relationship` will attempt to load a value from the database using this :class:`.Session` as the source of connectivity. The values - will be loaded based on foreign key values present on this - object - it follows that this functionality - generally only works for many-to-one-relationships. + will be loaded based on foreign key and primary key values + present on this object - if not present, then those relationships + will be unavailable. The object will be attached to this session, but will **not** participate in any persistence operations; its state @@ -2014,6 +2014,8 @@ class Session(_SessionClassMethods): To make a transient object associated with a :class:`.Session` via :meth:`.Session.enable_relationship_loading` pending, add it to the :class:`.Session` using :meth:`.Session.add` normally. + If the object instead represents an existing idenity in the database, + it should be merged using :meth:`.Session.merge`. :meth:`.Session.enable_relationship_loading` does not improve behavior when the ORM is used normally - object references should be