replace child document

Details

Type: Bug

Status:Closed

Priority: Major

Resolution:
Fixed

Labels:

None

Description

when replacing a mapped child with a new document, we get the cannotMoveByAssignment exception, which imo is a) the wrong message as its not about setting a tracked document to become a child somewhere else but what we should do is delete the existing child document and add the new one.

David Buchmann
added a comment - 22/Feb/13 2:53 PM there is a PR to add a form element for an image. when using this, the containing class needs to work around this bug for now https://github.com/doctrine/DoctrinePHPCRBundle/pull/37

as a side note: what speaks against moving the issues to github and drop this jira project? it would be much more user friendly for reporting bugs, and easier to integrate. and i don't think we use any of the fancy jira features really. (github has tags and now even milestones, if we would want to use them)

David Buchmann
added a comment - 02/Mar/13 11:59 AM the PR got merged https://github.com/doctrine/phpcr-odm/pull/253
as a side note: what speaks against moving the issues to github and drop this jira project? it would be much more user friendly for reporting bugs, and easier to integrate. and i don't think we use any of the fancy jira features really. (github has tags and now even milestones, if we would want to use them)

David Buchmann
added a comment - 21/Jun/13 4:13 PM note that as of this time, this is not fully fixed: if the child has children of its own, there is an error about detached documents. see https://github.com/doctrine/phpcr-odm/pull/262