RetailCRM-Mirror/doctrine2
1
0
Fork 0
mirror of synced 2024-12-05 03:06:05 +03:00
Code Issues Projects Releases Wiki Activity

Merge pull request #1341 from javiereguiluz/patch-6

Browse Source 
[doc] Minor fixes and typos
This commit is contained in:
Marco Pivetta 2015-03-18 22:02:15 +00:00
commit 05db65d034
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -338,7 +338,7 @@ uses the database platforms native id generation strategy (for
example AUTO INCREMENT in the case of MySql or Sequences in the
case of PostgreSql and Oracle).
Now that we have defined our first entity, lets update the database:
Now that we have defined our first entity, let's update the database:
::
@ -375,7 +375,7 @@ Call this script from the command-line to see how new products are created:
What is happening here? Using the ``Product`` is pretty standard OOP.
The interesting bits are the use of the ``EntityManager`` service. To
notify the EntityManager that a new entity should be inserted into the database
you have to call ``persist()``. To intiate a transaction to actually perform
you have to call ``persist()``. To initiate a transaction to actually perform
the insertion, You have to explicitly call ``flush()`` on the ``EntityManager``.
This distinction between persist and flush is allows to aggregate all writes
@ -1547,4 +1547,3 @@ will be added to this tutorial incrementally, topics will include:
Additional details on all the topics discussed here can be found in
the respective manual chapters.