From: Mike Bayer <mike_mp@zzzcomputing.com>
Date: Mon, 4 Sep 2006 23:55:38 +0000 (+0000)
Subject: update
X-Git-Tag: rel_0_2_8~4
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=5bcb6e786f0c5848ba01b5115beb9d0d995f2e84;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git

update
---

diff --git a/CHANGES b/CHANGES
index 24898b0275..c011c6285b 100644
--- a/CHANGES
+++ b/CHANGES
@@ -23,6 +23,9 @@ step in case the given property references a non-compiled mapper
 (as it is using the sessioncontext plugin, etc), a lazy load operation
 will use that session by default if the parent object is not 
 persistent with a session already.
+- lazy loads will not fire off for an object that does not have a 
+database identity (why?  
+see http://www.sqlalchemy.org/trac/wiki/WhyDontForeignKeysLoadData)
 - unit-of-work does a better check for "orphaned" objects that are
 part of a "delete-orphan" cascade, for certain conditions where the 
 parent isnt available to cascade from.