Skip to content

Update doctrine.rst #8334

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 3 commits into from
Closed

Update doctrine.rst #8334

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
267ffeb
Update doctrine.rst
atailouloute Sep 1, 2017
c8f84e4
Update doctrine.rst
atailouloute Sep 1, 2017
8e3d986
Update doctrine.rst
atailouloute Sep 2, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions doctrine.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -539,17 +539,17 @@ Take a look at the previous example in more detail:

.. _doctrine-entity-manager:

* **line 13** The ``$this->getDoctrine()->getManager()`` method gets Doctrine's
* **line 12** The ``$this->getDoctrine()->getManager()`` method gets Doctrine's
*entity manager* object, which is the most important object in Doctrine. It's
responsible for saving objects to, and fetching objects from, the database.

* **lines 15-18** In this section, you instantiate and work with the ``$product``
* **lines 14-17** In this section, you instantiate and work with the ``$product``
object like any other normal PHP object.

* **line 21** The ``persist($product)`` call tells Doctrine to "manage" the
* **line 20** The ``persist($product)`` call tells Doctrine to "manage" the
``$product`` object. This does **not** cause a query to be made to the database.

* **line 24** When the ``flush()`` method is called, Doctrine looks through
* **line 22** When the ``flush()`` method is called, Doctrine looks through
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, one mistake: This should have bee 23 :)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@wouterj you're right, I fixed it

all of the objects that it's managing to see if they need to be persisted
to the database. In this example, the ``$product`` object's data doesn't
exist in the database, so the entity manager executes an ``INSERT`` query,
Expand Down