[PR #6616] #6613 #6614 correct handling of new elements added to an initialized (yet dirty) collection #10067

Open
opened 2026-01-22 16:06:19 +01:00 by admin · 0 comments
Owner

Original Pull Request: https://github.com/doctrine/orm/pull/6616

State: closed
Merged: Yes


Fixes #6613
Fixes #6614

This is a very bad bug. The fix introduces some ovehead, but the scenario is usually not that common, so it should be fine.

Ideally, we should keep new and dirty states completely separate, but that's not possible without completely changing also the base class (Doctrine\Common\Collections\AbstractLazyCollection)

**Original Pull Request:** https://github.com/doctrine/orm/pull/6616 **State:** closed **Merged:** Yes --- Fixes #6613 Fixes #6614 This is a *very* bad bug. The fix introduces some ovehead, but the scenario is usually not that common, so it should be fine. Ideally, we should keep `new` and `dirty` states completely separate, but that's not possible without completely changing also the base class (`Doctrine\Common\Collections\AbstractLazyCollection`)
admin added the pull-request label 2026-01-22 16:06:19 +01:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: doctrine/archived-orm#10067