Skip to content
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

DDC-3976: [GH-1542] Failing test: Owned side of a oneToMany relation doesn't evict its collection cache #4835

Closed
doctrinebot opened this issue Nov 2, 2015 · 3 comments
Assignees
Labels
Milestone

Comments

@doctrinebot
Copy link

Jira issue originally created by user @doctrinebot:

This issue is created automatically through a Github pull request on behalf of guiwoda:

Url: #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
Copy link
Author

Comment created by @doctrinebot:

A related Github Pull-Request [GH-1542] was closed:
#1542

@doctrinebot
Copy link
Author

Issue was closed with resolution "Fixed"

@UFTimmy
Copy link

UFTimmy commented 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants