[DDC-2168] [GH-523] [DDC-2074] Bugfix regarding clearing cloned PersistentCollections Created: 25/Nov/12 Updated: 25/Nov/12 Resolved: 25/Nov/12
|Project:||Doctrine 2 - ORM|
|Reporter:||Benjamin Eberlei||Assignee:||Benjamin Eberlei|
This issue is created automatically through a Github pull request on behalf of jankramer:
When calling clear on a PC that has no owner (e.g. because it was cloned), it can't be deleted as there is no metadata available (that's essentially the exception mentioned in the ticket). In these cases, I think it shouldn't be scheduled for deletion, but please have a look as my knowledge of the ORM internals is limited.
|Comment by Benjamin Eberlei [ 25/Nov/12 ]|
A related Github Pull-Request [GH-523] was closed