Jira issue originally created by user @doctrinebot:
This issue is created automatically through a Github pull request on behalf of flack:
This is somewhat related to
I'm not sure if it fixes that particular problem, but it certainly helps with some unrelated issues I'm seeing in my code. My theory is that doctrine doesn't even need to compute changesets when an entity is scheduled to be removed, because all that would accomplish is to insert an UPDATE statement immediately before the DELETE statement for the entity.
The test suite passes, but I have not added a test specifically for this change (mostly because I wouldn't know exactly what to test). I could try to create one if necessary, though
Comment created by @doctrinebot:
A related Github Pull-Request [GH-845] was closed:
Issue was closed with resolution "Fixed"
A related Github Pull-Request [GH-829] was closed: