mirror of
https://github.com/doctrine/orm.git
synced 2026-03-24 06:52:09 +01:00
Unit Of Work - entityIdentifiers Missing on cached OneToOne associations? #6262
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 @mverijdt on GitHub (Jun 25, 2019).
Originally assigned to: @mverijdt on GitHub.
Bug Report
Summary
Doctrine ORM is throwing Exceptions in UnitOfWork related to DefaultEntityCache
Current behavior
These are the errors:
prod environment:
dev environment:
How to reproduce
Reproducing the problem is also a problem, see this repository
Expected behavior
I'd expect that the UnitOfWork would be able to find an entityIdentifier for OneToOne associations
A little more information and context
I've tried to explain this issue at stackoverflow
I'm not sure if it's L2 cache, it could also be Query Cache. but it has to be some sort of cache, when I disable all cache configuration in the application my Importer commands work perfectly together with all other components. Even the symfony/validation component which is the last component added when the errors started occuring
One other thing, this might be related to this issue or any of the other issues reported with One To One associations and
@lcobucci commented on GitHub (Oct 2, 2019):
@maarten-shop4 I believe this should be solved by https://github.com/doctrine/orm/pull/7778, would you be able to update to
v2.6.4and try it out?@nicodemuz commented on GitHub (Oct 2, 2019):
@lcobucci I just updated to
v2.6.4and I'm also experiencing this issue.@lcobucci commented on GitHub (Oct 2, 2019):
@MrNicodemuz interesting, would you be up for sending us a PR with a failing functional test? That should help us a lot to identify and fix the issue.
@nicodemuz commented on GitHub (Oct 2, 2019):
@lcobucci Here is a stack trace to begin with, not sure if it will be helpful:
@lcobucci commented on GitHub (Oct 2, 2019):
The stack is not really helpful, sorry.