From 177a9ce4d21d33111c61b346c49086cbb0fee87f Mon Sep 17 00:00:00 2001 From: Benjamin Eberlei Date: Wed, 12 May 2010 23:53:09 +0200 Subject: [PATCH] Update Getting Started XML Edition to work with inversed-by attributes --- cookbook/en/getting-started-xml-edition.txt | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/cookbook/en/getting-started-xml-edition.txt b/cookbook/en/getting-started-xml-edition.txt index b5834ed5a..8669d0ba6 100644 --- a/cookbook/en/getting-started-xml-edition.txt +++ b/cookbook/en/getting-started-xml-edition.txt @@ -295,11 +295,11 @@ We then go on specifying the definition of a Bug: - + - + @@ -326,7 +326,9 @@ After the field definitions the two qualified references to the user entity are the `many-to-one` tag. The class name of the related entity has to be specified with the `target-entity` attribute, which is enough information for the database mapper to access the foreign-table. The `join-column` tags are used to specifiy how the foreign and referend columns are named, an information -Doctrine needs to construct joins between those two entities correctly. +Doctrine needs to construct joins between those two entities correctly. Since `reporter` and `engineer` +are on the owning side of a bi-direcitonal relation we also have to specify the `inversed-by` attribute. +They have to point to the field names on the inverse side of the relationship. The last missing property is the `Bug::$products` collection. It holds all products where the specific bug is occouring in. Again you have to define the `target-entity` and `field` attributes on the `many-to-many`