Skip to content

DDC-3221: Invalid binding for primary key of entity relation #4008

doctrinebot opened this Issue Jul 21, 2014 · 0 comments

2 participants


Jira issue originally created by user to0n1:


We use doctrine2 ORM with doctrine/doctrine-bundle in our symfony2 based project. We developed functionality which is similar to some kind of import process.

And we have an issue that appears from time to time in different points during the import.

Issue is following:
Lets imagine we have 3 entities Account, Contact, Contact Address.
Account has many to one relation on contact and contact has one to many relation on contact address.

Our import creates all 3 entities and persist only Account, contact and address are persisted via cascade persist.
We have writer that contains following code

    public function write(array $items)
        try {
            foreach ($items as $item) {
        } catch (\Exception $exception) {

            throw $exception;

So we clear EntityManager for each batch in order to avoid high memory consumption.
Import fails during different entities insert, but errors are very similar.
Example of error is

[error] An exception occurred while executing 'INSERT INTO ... VALUES (?, ?, ?, ?, ?)' with params ["start", "2014-07-21 00:55:35", 0, null, 21]:

SQLSTATE[23000]: Integrity constraint violation: 1452 Cannot add or update a child row: a foreign key constraint fails (DB.account, CONSTRAINT FK*B3D57B301023C4EE FOREIGN KEY (contact*id) REFERENCES contact (id) ON DELETE CASCADE)

After debugging I found that problem is in BasicEntityPersister#prepareUpdateData $uow->getEntityIdentifier($newVal);
returns oid that is real one, but UOW contains not the same ID as in $newVal entity. It seems like splobjecthash duplicates oid.

Any help is appreciated.
Thanks in advance.

@beberlei beberlei was assigned by doctrinebot Dec 6, 2015
@doctrinebot doctrinebot added the Bug label Dec 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.