8000 minor #18539 [Doctrine] Fix line numbers in example (marco-pm) · symfony/symfony-docs@be073b5 · GitHub
[go: up one dir, main page]

Skip to content

Commit be073b5

Browse files
committed
minor #18539 [Doctrine] Fix line numbers in example (marco-pm)
This PR was submitted for the 6.3 branch but it was merged into the 6.2 branch instead. Discussion ---------- [Doctrine] Fix line numbers in example <!-- If your pull request fixes a BUG, use the oldest maintained branch that contains the bug (see https://symfony.com/releases for the list of maintained branches). If your pull request documents a NEW FEATURE, use the same Symfony branch where the feature was introduced (and `6.x` for features of unreleased versions). --> Commits ------- 82c1ce4 [Doctrine] Fix line numbers in example
2 parents 1ba5c7b + 82c1ce4 commit be073b5

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

doctrine.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -395,13 +395,13 @@ Take a look at the previous example in more detail:
395395
the controller method. This object is responsible for saving objects to, and
396396
fetching objects from, the database.
397397

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

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

404-
* **line 26** When the ``flush()`` method is called, Doctrine looks through
404+
* **line 24** When the ``flush()`` method is called, Doctrine looks through
405405
all of the objects that it's managing to see if they need to be persisted
406406
to the database. In this example, the ``$product`` object's data doesn't
407407
exist in the database, so the entity manager executes an ``INSERT`` query,

0 commit comments

Comments
 (0)
0