Relationships

Documentation/1.3/Relationships

-                      v6
+                      v7
 . n x SELECT * FROM author WHERE author_id = ''$book->getAuthorId()''
 While clearly this method works, it is not optimal to execute that second query for each iteration. Propel also generates methods in your base peer class to fetch both book and author information in a single query.
+While clearly this method works, it is not optimal to execute that second query for each iteration. Propel also generates methods in your base peer class to fetch both book and author information in a single query using a left join^*^.
 {{{
 …
 In the above case only a single query is performed:
 . SELECT * FROM book INNER JOIN author ON author.author_id = book.author_id
+. SELECT * FROM book LEFT JOIN author ON author.author_id = book.author_id
 Continue reading the [wiki:Documentation/1.3/ManyToManyRelationships Many-to-Many Relationships] page for a treatment of this more-advanced realtionship topic.
+^*^ Note that in Propel 1.3 the behavior changed from performing INNER JOIN to using LEFT JOIN by default.  Please see wiki:Documentation/1.3/Upgrading for more information and instructions on how to keep the original INNER JOIN behavior if your application depends on this.
 == Using Relationships in Criteria ==