Skip to content

[Doctrine] Proper line numbers on Doctrine Persisting example #17251

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.

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

Merged
merged 1 commit into from
Sep 8, 2022
Merged
Changes from all commits
Commits
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
10 changes: 5 additions & 5 deletions doctrine.rst
Original file line number Diff line number Diff line change
Expand Up @@ -394,21 +394,21 @@ Take a look at the previous example in more detail:

.. _doctrine-entity-manager:

* **line 14** The ``ManagerRegistry $doctrine`` argument tells Symfony to
* **line 13** The ``ManagerRegistry $doctrine`` argument tells Symfony to
:ref:`inject the Doctrine service <services-constructor-injection>` into the
controller method.

* **line 16** The ``$doctrine->getManager()`` method gets Doctrine's
* **line 15** The ``$doctrine->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 18-21** In this section, you instantiate and work with the ``$product``
* **lines 17-20** In this section, you instantiate and work with the ``$product``
object like any other normal PHP object.

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

* **line 27** When the ``flush()`` method is called, Doctrine looks through
* **line 26** When the ``flush()`` method is called, Doctrine looks through
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