-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There is the fail "UNIQUE constraint failed" with a LAZY collection #6613
Comments
@Sysaninster can you put this into a test case like the ones in https://github.com/doctrine/doctrine2/tree/bbe005837e51442e0d6037bafe70dc4b7712dac1/tests/Doctrine/Tests/ORM/Functional/Ticket please? |
Closing here, thanks for sending a failing test case! |
Ref: #6614 |
…g identifiers to reduce moving parts
…ng`), segregating phone creation away
…are restored in the dirty state of the collection
Reopening, since this will be closed once #6616 is merged. |
…toreNewObjectsInDirtyCollection` implementation
…ng identifiers to reduce moving parts
…ng`), segregating phone creation away
… are restored in the dirty state of the collection
…erifies basic dirty collection initialization semantics
…that are also coming from initialization data de-duplicates new and persisted items
… if all new items are contained in the initialized ones
…toreNewObjectsInDirtyCollection` implementation
@Sysaninster thanks for the bug report - this is fixed and will go into |
I have the User entity with the LAZY collection field. If I do this code:
I will get the error:
If I remove the $user->phones->toArray(); line then it will work without a problem.
The text was updated successfully, but these errors were encountered: