From 155672af4078fe8e45db9647ab00a0e8eadc515d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Martin=20Schr=C3=B6der?= Date: Sun, 6 Nov 2016 14:05:50 +0100 Subject: [PATCH] Fixed typos regarding the strategy for composite keys (xml mapping reference) The strategy for composite primary keys must be "NONE" although the id generator class is \Doctrine\ORM\Id\AssignedGenerator. Calling the strategy "ASSIGNED" is misleading. --- docs/en/reference/xml-mapping.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/en/reference/xml-mapping.rst b/docs/en/reference/xml-mapping.rst index dbf97dc0a..5f0131527 100644 --- a/docs/en/reference/xml-mapping.rst +++ b/docs/en/reference/xml-mapping.rst @@ -321,12 +321,12 @@ Using the simplified definition above Doctrine will use no identifier strategy for this entity. That means you have to manually set the identifier before calling ``EntityManager#persist($entity)``. This is the so called -``ASSIGNED`` strategy. +``NONE`` strategy. If you want to switch the identifier generation strategy you have to nest a ```` element inside the id-element. This of 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