From: Mike Bayer <mike_mp@zzzcomputing.com>
Date: Fri, 28 Feb 2014 19:23:44 +0000 (-0500)
Subject: add a migration for this one
X-Git-Tag: rel_0_9_4~96
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=e58fdadb9ba264cac14e4e7287d5cdaac6f40942;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git

add a migration for this one
---

diff --git a/doc/build/changelog/migration_09.rst b/doc/build/changelog/migration_09.rst
index f318b0346c..5039c54d04 100644
--- a/doc/build/changelog/migration_09.rst
+++ b/doc/build/changelog/migration_09.rst
@@ -6,10 +6,10 @@ What's New in SQLAlchemy 0.9?
 
     This document describes changes between SQLAlchemy version 0.8,
     undergoing maintenance releases as of May, 2013,
-    and SQLAlchemy version 0.9, which is expected for release
-    in late 2013.
+    and SQLAlchemy version 0.9, which had its first production
+    release on December 30, 2013.
 
-    Document last updated: January 8, 2014
+    Document last updated: February 28, 2014
 
 Introduction
 ============
@@ -1214,6 +1214,39 @@ Generates (everywhere except SQLite)::
 
 :ticket:`2369` :ticket:`2587`
 
+Right-nested inner joins available in joined eager loads
+---------------------------------------------------------
+
+As of version 0.9.4, the above mentioned right-nested joining can be enabled
+in the case of a joined eager load where an "outer" join is linked to an "inner"
+on the right side.
+
+Normally, a joined eager load chain like the following::
+
+    query(User).options(joinedload("orders", innerjoin=False).joinedload("items", innerjoin=True))
+
+Would not produce an inner join; because of the LEFT OUTER JOIN from user->order,
+joined eager loading could not use an INNER join from order->items without changing
+the user rows that are returned, and would instead ignore the "chained" ``innerjoin=True``
+directive.  How 0.9.0 should have delivered this would be that instead of::
+
+    FROM users LEFT OUTER JOIN orders ON <onclause> LEFT OUTER JOIN items ON <onclause>
+
+the new "right-nested joins are OK" logic would kick in, and we'd get::
+
+    FROM users LEFT OUTER JOIN (orders JOIN items ON <onclause>) ON <onclause>
+
+Since we missed the boat on that, to avoid further regressions we've added the above
+functionality by specifying the string ``"nested"`` to :paramref:`.joinedload.innerjoin`::
+
+    query(User).options(joinedload("orders", innerjoin=False).joinedload("items", innerjoin="nested"))
+
+This feature is new in 0.9.4.
+
+:ticket:`2976`
+
+
+
 ORM can efficiently fetch just-generated INSERT/UPDATE defaults using RETURNING
 -------------------------------------------------------------------------------