From aab2303c373336d060af1526a2c9568244e5adf4 Mon Sep 17 00:00:00 2001 From: Benjamin Eberlei Date: Sat, 26 Feb 2011 11:12:58 +0100 Subject: [PATCH] Fix Getting Started. --- en/tutorials/getting-started-xml-edition.rst | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/en/tutorials/getting-started-xml-edition.rst b/en/tutorials/getting-started-xml-edition.rst index 430a6756a..093386159 100644 --- a/en/tutorials/getting-started-xml-edition.rst +++ b/en/tutorials/getting-started-xml-edition.rst @@ -455,7 +455,7 @@ We then go on specifying the definition of a Bug: /** * @ManyToMany(targetEntity="Product") */ - private $products = null; // Set private for encapsulation + private $products; } .. code-block:: xml @@ -521,14 +521,13 @@ After the field definitions the two qualified references to the user entity are defined. They are created by 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 specify how the foreign and -referenced columns are named, an information Doctrine needs to -construct joins between those two entities correctly. Since +the database mapper to access the foreign-table. Since ``reporter`` and ``engineer`` are on the owning side of a bi-directional 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. +side of the relationship. We will see in the next example that the ``inversed-by`` +attribute has a counterpart ``mapped-by`` which makes that +the inverse side. The last missing property is the ``Bug::$products`` collection. It holds all products where the specific bug is occurring in. Again