mirror of
https://github.com/doctrine/orm.git
synced 2026-03-23 22:42:18 +01:00
DDC-3976: [GH-1542] Failing test: Owned side of a oneToMany relation doesn't evict its collection cache #4853
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @doctrinebot on GitHub (Nov 2, 2015).
Originally assigned to: @guilhermeblanco on GitHub.
Jira issue originally created by user @doctrinebot:
This issue is created automatically through a Github pull request on behalf of guiwoda:
Url: https://github.com/doctrine/doctrine2/pull/1542
Message:
oneToMany Associations always have collections on the inversed side, and these collections are getting cached but never get evicted.
This also happens on bidirectional manyToMany associations, on the inverse side as well. Only owning side of an association gets its collections evicted.
@doctrinebot commented on GitHub (Nov 10, 2015):
Comment created by @doctrinebot:
A related Github Pull-Request [GH-1542] was closed:
https://github.com/doctrine/doctrine2/pull/1542
@doctrinebot commented on GitHub (Nov 12, 2015):
Issue was closed with resolution "Fixed"
@UFTimmy commented on GitHub (Sep 19, 2016):
Am I reading this correctly that this won't be included in a release until 2.6? Apologies, it's a bit hard to follow with the links to JIRA now being 404s.
Is there any work around in the mean time? I am running into this bug all over the place when adding a new item to a collection.