@@ -394,21 +394,21 @@ Take a look at the previous example in more detail:
394
394
395
395
.. _doctrine-entity-manager :
396
396
397
- * **line 14 ** The ``ManagerRegistry $doctrine `` argument tells Symfony to
397
+ * **line 13 ** The ``ManagerRegistry $doctrine `` argument tells Symfony to
398
398
:ref: `inject the Doctrine service <services-constructor-injection >` into the
399
399
controller method.
400
400
401
- * **line 16 ** The ``$doctrine->getManager() `` method gets Doctrine's
401
+ * **line 15 ** The ``$doctrine->getManager() `` method gets Doctrine's
402
402
*entity manager * object, which is the most important object in Doctrine. It's
403
403
responsible for saving objects to, and fetching objects from, the database.
404
404
405
- * **lines 18-21 ** In this section, you instantiate and work with the ``$product ``
405
+ * **lines 17-20 ** In this section, you instantiate and work with the ``$product ``
406
406
object like any other normal PHP object.
407
407
408
- * **line 24 ** The ``persist($product) `` call tells Doctrine to "manage" the
408
+ * **line 23 ** The ``persist($product) `` call tells Doctrine to "manage" the
409
409
``$product `` object. This does **not ** cause a query to be made to the database.
410
410
411
- * **line 27 ** When the ``flush() `` method is called, Doctrine looks through
411
+ * **line 26 ** When the ``flush() `` method is called, Doctrine looks through
412
412
all of the objects that it's managing to see if they need to be persisted
413
413
to the database. In this example, the ``$product `` object's data doesn't
414
414
exist in the database, so the entity manager executes an ``INSERT `` query,
0 commit comments