From 3e98fdb082006702f35ed7cb9f5fbe700df8c97a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Martin=20Schr=C3=B6der?= Date: Sun, 6 Nov 2016 13:37:07 +0100 Subject: [PATCH] Fixed typo regarding the id generator mandatory for composite primary keys 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/tutorials/composite-primary-keys.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/tutorials/composite-primary-keys.rst b/docs/en/tutorials/composite-primary-keys.rst index dd4e49e04..d8256db75 100644 --- a/docs/en/tutorials/composite-primary-keys.rst +++ b/docs/en/tutorials/composite-primary-keys.rst @@ -13,7 +13,7 @@ This tutorial shows how the semantics of composite primary keys work and how the General Considerations ~~~~~~~~~~~~~~~~~~~~~~ -Every entity with a composite key cannot use an id generator other than "ASSIGNED". That means +Every entity with a composite key cannot use an id generator other than "NONE". That means the ID fields have to have their values set before you call ``EntityManager#persist($entity)``. Primitive Types only