RetailCRM-Mirror/doctrine2
1
0
Fork 0
mirror of synced 2025-03-23 08:23:51 +03:00
Code Issues Projects Releases Wiki Activity

Updated method documentation to use # for instance methods instead of ::

Browse Source
This commit is contained in:
Christian Morgan 2013-07-26 22:21:27 +01:00
parent 7bc18d7888
commit bc7d06fe59
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/en/tutorials/getting-started.rst
View File

@ -394,7 +394,7 @@ new script for this:
echo sprintf("-%s\n", $product->getName()); echo sprintf("-%s\n", $product->getName());
} }
The ``EntityManager::getRepository()`` method can create a finder object (called The ``EntityManager#getRepository()`` method can create a finder object (called
a repository) for every entity. It is provided by Doctrine and contains some a repository) for every entity. It is provided by Doctrine and contains some
finder methods such as ``findAll()``. finder methods such as ``findAll()``.
@ -728,14 +728,14 @@ methods are only used for ensuring consistency of the references.
This approach is my personal preference, you can choose whatever This approach is my personal preference, you can choose whatever
method to make this work. method to make this work.
You can see from ``User::addReportedBug()`` and You can see from ``User#addReportedBug()`` and
``User::assignedToBug()`` that using this method in userland alone ``User#assignedToBug()`` that using this method in userland alone
would not add the Bug to the collection of the owning side in would not add the Bug to the collection of the owning side in
``Bug::$reporter`` or ``Bug::$engineer``. Using these methods and ``Bug::$reporter`` or ``Bug::$engineer``. Using these methods and
calling Doctrine for persistence would not update the collections calling Doctrine for persistence would not update the collections
representation in the database. representation in the database.
Only using ``Bug::setEngineer()`` or ``Bug::setReporter()`` Only using ``Bug#setEngineer()`` or ``Bug#setReporter()``
correctly saves the relation information. We also set both correctly saves the relation information. We also set both
collection instance variables to protected, however with PHP 5.3's collection instance variables to protected, however with PHP 5.3's
new features Doctrine is still able to use Reflection to set and new features Doctrine is still able to use Reflection to set and
@ -1071,7 +1071,7 @@ Since we only have one user and product, probably with the ID of 1, we can call
php create_bug.php 1 1 1 php create_bug.php 1 1 1
This is the first contact with the read API of the EntityManager, This is the first contact with the read API of the EntityManager,
showing that a call to ``EntityManager::find($name, $id)`` returns a showing that a call to ``EntityManager#find($name, $id)`` returns a
single instance of an entity queried by primary key. Besides this single instance of an entity queried by primary key. Besides this
we see the persist + flush pattern again to save the Bug into the we see the persist + flush pattern again to save the Bug into the
database. database.
@ -1373,7 +1373,7 @@ should be able to close a bug. This looks like:
When retrieving the Bug from the database it is inserted into the When retrieving the Bug from the database it is inserted into the
IdentityMap inside the UnitOfWork of Doctrine. This means your Bug IdentityMap inside the UnitOfWork of Doctrine. This means your Bug
with exactly this id can only exist once during the whole request with exactly this id can only exist once during the whole request
no matter how often you call ``EntityManager::find()``. It even no matter how often you call ``EntityManager#find()``. It even
detects entities that are hydrated using DQL and are already detects entities that are hydrated using DQL and are already
present in the Identity Map. present in the Identity Map.