Avoid duplicate processing of entities in certain situations#91
Merged
Avoid duplicate processing of entities in certain situations#91
Conversation
mpdude
force-pushed
the
avoid-duplicate-eject
branch
from
81c9834 to
ec4ec8f
Compare
mpdude
added a commit
that referenced
this pull request
Apr 10, 2026
mpdude
added a commit
that referenced
this pull request
Apr 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In certain situations where Doctrine detectes new entities with
cascade: persistduring a flush operation, it might happen that the same entity ends up twice in the map of tracked entities, leading to duplicatePersistentTranslatable::eject()calls and failures (nothing left to eject after the first call).This can be avoided by making sure we track each object (instance) only once.