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
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 :)
The text was updated successfully, but these errors were encountered:
Jira issue originally created by user @doctrinebot:
This issue is created automatically through a Github pull request on behalf of moroine:
Url: #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 amanaged+dirty entity
error.So I see two solutions
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 :)
The text was updated successfully, but these errors were encountered: