Object hash in UoW #6217

New Issue

admin · 2026-01-22T15:29:02+01:00

admin commented

2026-01-22 15:29:02 +01:00

Originally created by @sweiguny on GitHub (Apr 9, 2019).

Originally assigned to: @Ocramius on GitHub.

Q	A
Version	doctrine/orm v2.6.3

Question

Hello,

I have some questions about the internals of Doctrine, which are primarily for my understanding.

The UnitOfWork has a collection of all entities under management and therefore also a list of their states (private $entityStates = [];). Here is an assignment of a new Entity. As you can see there, the object hash is taken as key and the value is the state ("managed").

Isn't somewhere the primary key of the entity checked, too?
Because, if only the object hash is checked, I can clone my entity which gives me another object hash, pass it to EntityManager::persist() and have basically the same entity twice in the UnitOfWork.

Or did I miss something?

Thank you in advance for your answer.

Originally created by @sweiguny on GitHub (Apr 9, 2019). Originally assigned to: @Ocramius on GitHub. | Q | A |------------ | ----- | Version | doctrine/orm v2.6.3 ### Question Hello, I have some questions about the internals of Doctrine, which are primarily for my understanding. The `UnitOfWork` has a collection of all entities under management and therefore also a list of their states (`private $entityStates = [];`). [Here is an assignment of a new Entity.](https://github.com/doctrine/orm/blob/ebb53acda96e304a6f91d4a5a2d76378a4e1d210/lib/Doctrine/ORM/UnitOfWork.php#L858) As you can see there, the object hash is taken as key and the value is the state ("managed"). **Isn't somewhere the primary key of the entity checked, too?** Because, if only the object hash is checked, I can clone my entity which gives me another object hash, pass it to `EntityManager::persist()` and have basically the same entity twice in the `UnitOfWork`. Or did I miss something? Thank you in advance for your answer.

admin added the Question label 2026-01-22 15:29:02 +01:00

admin referenced this issue

2026-01-22 16:05:46 +01:00

[PR #6217] Handle AssociationCacheEntry identifier #9900

admin referenced this issue

2026-01-22 16:05:52 +01:00

[PR #6284] #6217 when hydrating an entity with a composite primary key that is both an `EAGER` and a `LAZY` association and also cached, the `DefaultQueryCache` tries to pass L2 cache implementation detail objects to the `UnitOfWork` #9929

admin referenced this issue

2026-01-22 16:06:21 +01:00

[PR #6640] #6217 #6284 when hydrating an entity with a composite primary key that is both an `EAGER` and a `LAZY` association and also cached, the `DefaultQueryCache` tries to pass L2 cache implementation detail objects to the `UnitOfWork` #10079

Sign in to join this conversation.