DDC-3827: [GH-1461] Spl_object_hash conflict on Merge #4686

New Issue

admin · 2026-01-22T14:47:36+01:00

admin commented

2026-01-22 14:47:36 +01:00

Originally created by @doctrinebot on GitHub (Jul 15, 2015).

Originally assigned to: @Majkl578 on GitHub.

Jira issue originally created by user @doctrinebot:

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

Url: https://github.com/doctrine/doctrine2/pull/1461

Message:

Hi,

First of all, this is just a proposal and I'm sure there is a better solution for the problem described here. As this is my first hack into doctrine source code I'm not sure consequences that might be cause by my modification (even all unit tests passes).

I have encounter a problem due to spl_object_hash. I have written a functional test in order to reveal my issue.

The problem is when I merge an entity, here $user, UOW keep data on the original entity identified by it's spl_object_hash. Then if I unset this $user the spl_object_hash is now available for new object. So I experimented in my case reuse of previous hash which cause a managed+dirty entity error.

So I see two solutions

UOW keep reference to the entity given as even the given variable is unset there is remaining reference in UOW so the spl_hash will not be released.
Do not store data about the given entity, as merge operation isn't supposed to modified given entity.

I tried to implement the second solution as the first may consume a much more memory.

I don't why the merge operation need to do this, so I encapsulated it to prevent unwanted bug :)

Originally created by @doctrinebot on GitHub (Jul 15, 2015). Originally assigned to: @Majkl578 on GitHub. Jira issue originally created by user @doctrinebot: This issue is created automatically through a Github pull request on behalf of moroine: Url: https://github.com/doctrine/doctrine2/pull/1461 Message: Hi, First of all, this is just a proposal and I'm sure there is a better solution for the problem described here. As this is my first hack into doctrine source code I'm not sure consequences that might be cause by my modification (even all unit tests passes). I have encounter a problem due to spl_object_hash. I have written a functional test in order to reveal my issue. The problem is when I merge an entity, here `$user`, UOW keep data on the original entity identified by it's spl_object_hash. Then if I unset this `$user` the spl_object_hash is now available for new object. So I experimented in my case reuse of previous hash which cause a `managed+dirty entity` error. So I see two solutions - UOW keep reference to the entity given as even the given variable is unset there is remaining reference in UOW so the spl_hash will not be released. - Do not store data about the given entity, as merge operation isn't supposed to modified given entity. I tried to implement the second solution as the first may consume a much more memory. I don't why the merge operation need to do this, so I encapsulated it to prevent unwanted bug :)

admin added the Bug Duplicate labels 2026-01-22 14:47:36 +01:00

admin closed this issue

2026-01-22 14:47:37 +01:00

admin commented

2026-01-22 14:47:38 +01:00

@Majkl578 commented on GitHub (Dec 19, 2017):

Duplicate of #3037, also merge will be removed in Doctrine 3.0.

@Majkl578 commented on GitHub (Dec 19, 2017): Duplicate of #3037, also merge will be removed in Doctrine 3.0.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: doctrine/archived-orm#4686