-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
SecondCacheLevel association and inheritance update problem #5793
Comments
Looks for me similar to the problem reported here: |
Yes i think the the problem is the same thing since both is related to inheritance and second level cache. |
Hi all, is there any update on this bug? |
I believe that #6028 fixes this. |
No it doesn't |
@mpoiriert weird, what kind of associations do you have? I can investigate this today. |
Sorry for the delay really busy at the time. This is the class override I have to fix the issue on my side
and
As you can see the only thing I had to change is to use
instead of
I never did a pull request with that fix since I didn't have time to follow protocol and I did want to make sure it's working. We are using this fix since the 20th April |
@mpoiriert did you try your mapping with You could also send us the mapping you have so we can try it out and find the problem. |
@mpoiriert sorry, you were right that the problem wasn't solved. |
Great thanks. We are planning to upgrade all our stack in the next couples of months so I'll be glad to remove all my factory/override when I'll pass to 2.6.0 |
@mpoiriert nice, I'll close this issue since we merged #6244. |
I have a entities like this (I just document the minimum needed):
When changing the ChildClass->associations value and persisting it the data in the cache is not removed.
Investigating I found that the Doctrine\ORM\Cache\Persister\Entity\AbstractEntityPersister is using the entityName (that will be ChildClass) but that the Doctrine\ORM\Cache\Persister\Collection\NonStrictReadWriteCachedCollectionPersister is using the $this->sourceEntity->rootEntityName (that will be BaseClass) So it doesn't clear the proper key entry.
Pretty easy to change but might be risky...
If you consider that I am on the good track I can give it a try to make the unit test for it.
The text was updated successfully, but these errors were encountered: