RetailCRM-Mirror/doctrine2
1
0
Fork 0
mirror of synced 2025-02-10 17:29:27 +03:00
Code Issues Projects Releases Wiki Activity

Merge pull request #6120 from mschroeder/patch-3

Browse Source 
Fixed typos regarding the strategy for composite keys (xml mapping)
This commit is contained in:
Marco Pivetta 2016-11-06 18:50:00 +01:00 committed by GitHub
commit 05e77868ab
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/en/reference/xml-mapping.rst
View File

@ -321,12 +321,12 @@ Using the simplified definition above Doctrine will use no
identifier strategy for this entity. That means you have to identifier strategy for this entity. That means you have to
manually set the identifier before calling manually set the identifier before calling
``EntityManager#persist($entity)``. This is the so called ``EntityManager#persist($entity)``. This is the so called
``ASSIGNED`` strategy. ``NONE`` strategy.
If you want to switch the identifier generation strategy you have If you want to switch the identifier generation strategy you have
to nest a ``<generator />`` element inside the id-element. This of to nest a ``<generator />`` element inside the id-element. This of
course only works for surrogate keys. For composite keys you always course only works for surrogate keys. For composite keys you always
have to use the ``ASSIGNED`` strategy. have to use the ``NONE`` strategy.
.. code-block:: xml .. code-block:: xml