http://www.doctrine-project.org/jira This file is an XML representation of an issue en-us 5.2.7 850 21-02-2013 http://www.doctrine-project.org/jira/browse/DDC-116 Doctrine 2 - ORM <p>I use a combined Primary Key for a User's Phonenumber entity (to match our existing DB model). The key is combined from a "Type" field and a "userId" field that references the User table. </p> <p>To mark the (referenced!) userId field and the type field as PK, I need to add "userId" to the model (adding @Id to User does not work). This works well when generating Users and Phonenumbers - but the delete command breaks:</p> <div class="panel" style="border-width: 1px;"><div class="panelContent"> <p>PHP Warning: array_combine(): Both parameters should have an equal number of elements in ..../lib/Doctrine/ORM/Persisters/StandardEntityPersister.php on line 274<br/> PHP Catchable fatal error: Argument 2 passed to Doctrine\DBAL\Connection::delete() must be an array, boolean given, called in ..../lib/Doctrine/ORM/Persisters/StandardEntityPersister.php on line 275 and defined in ..../lib/Doctrine/DBAL/Connection.php on line 372</p> </div></div> <p>Entities:<br/> <a href="http://pastebin.com/d51e021e2" class="external-link">http://pastebin.com/d51e021e2</a></p> <p>Test code:<br/> <a href="http://pastebin.com/m51d1f497" class="external-link">http://pastebin.com/m51d1f497</a></p> DDC-116

array_combine error when using combined Primary Key

Bug Critical Closed Fixed All Roman S. Borschel Nico Kaiser Thu, 5 Nov 2009 08:10:50 +0000 Mon, 14 Jun 2010 09:17:44 +0000 Fri, 6 Nov 2009 10:30:36 +0000 2.0-ALPHA3 ORM 0 0 <p>I attached a patch for Doctrine\Orm\Id\Assigned, there seems to be a runaway line which makes the class add each element twice...</p> <p>Whoops. Thanks for finding this! Does it fix this issue? I will need to add a testcase to the suite.</p> <p>Does not entirely fix it: if the $value is empty, too few elements are added again. <br/> Need to remove the "if (isset($value)) {" clause. I'll attach the fixed Assigned.php.</p> <p>I think the isset() is correct. That way the $identifier array remains empty if the PK is null and later if ( ! $identifier) evaluates to false on the empty array and raises the exception. If we remove the isset() we would "accept" PKs with null values. But it might be better to do:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> <span class="code-keyword">if</span> (!isset($value)) { <span class="code-keyword">throw</span> ORMException::entityMissingAssignedId($entity); } <span class="code-keyword">else</span> { $identifier[] = $value; } </pre> </div></div> <p>I will fix this and add some new tests for it.</p> <p>Should be fixed now.</p>