You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Every repository i configure in my yaml conf file, using the factory method getRepository() of @doctrine.orm.default_entity_manager get a differente instance of EntityManager causing impossibility to save Entity with mapping associations
I really can't understand why using factory: ["@doctrine.orm.default_entity_manager", getRepository] generate inconsistent EntityManager instances across the repositories while using factory: ["@doctrine.orm.container_repository_factory", getRepository] have better stability.
TL;DR this story is very long, please go to my SO question here STACKOVERFLOW
PHP 7.2.7
| Version | v2.6.1
| Version | v2.6.2
The text was updated successfully, but these errors were encountered:
Looking at the issue @xabbuh linked as well as symfony/symfony#30091 and symfony/symfony#30096, I'd agree that this is not caused by the bundle but rather by the container. Closing here as there's nothing we can fix.
Every repository i configure in my yaml conf file, using the factory method
getRepository()
of@doctrine.orm.default_entity_manager
get a differente instance of EntityManager causing impossibility to save Entity with mapping associationsI really can't understand why using factory: ["@doctrine.orm.default_entity_manager", getRepository] generate inconsistent EntityManager instances across the repositories while using factory: ["@doctrine.orm.container_repository_factory", getRepository] have better stability.
TL;DR this story is very long, please go to my SO question here STACKOVERFLOW
PHP 7.2.7
| Version | v2.6.1
| Version | v2.6.2
The text was updated successfully, but these errors were encountered: