<!-- 
RSS generated by JIRA (5.2.7#850-sha1:b2af0c8dc8537b36121c6a579fabbdf79fc919e5) at Sun May 19 10:17:17 UTC 2013

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary add field=key&field=summary to the URL of your request.
For example:
http://www.doctrine-project.org/jira/si/jira.issueviews:issue-xml/PHPCR-98/PHPCR-98.xml?field=key&field=summary
-->
<rss version="0.92" >
<channel>
    <title>Doctrine Project</title>
    <link>http://www.doctrine-project.org/jira</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>5.2.7</version>
        <build-number>850</build-number>
        <build-date>21-02-2013</build-date>
    </build-info>

<item>
            <title>[PHPCR-98] replace child document</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-98</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;this happens at &lt;a href=&quot;https://github.com/doctrine/phpcr-odm/blob/master/lib/Doctrine/ODM/PHPCR/UnitOfWork.php#L1912&quot; class=&quot;external-link&quot;&gt;https://github.com/doctrine/phpcr-odm/blob/master/lib/Doctrine/ODM/PHPCR/UnitOfWork.php#L1912&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;for multiple children, i am less sure how it should work, if it is possible the same way: &lt;br/&gt;
&lt;a href=&quot;https://github.com/doctrine/phpcr-odm/blob/master/lib/Doctrine/ODM/PHPCR/UnitOfWork.php#L935&quot; class=&quot;external-link&quot;&gt;https://github.com/doctrine/phpcr-odm/blob/master/lib/Doctrine/ODM/PHPCR/UnitOfWork.php#L935&lt;/a&gt;&lt;/p&gt;</description>
                <environment></environment>
            <key id="14542">PHPCR-98</key>
            <summary>replace child document</summary>
                <type id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/bug.png">Bug</type>
                                <priority id="3" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/major.png">Major</priority>
                    <status id="6" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/closed.png">Closed</status>
                    <resolution id="1">Fixed</resolution>
                                <assignee username="lsmith">Lukas Kahwe</assignee>
                                <reporter username="dbu">David Buchmann</reporter>
                        <labels>
                    </labels>
                <created>Fri, 22 Feb 2013 09:50:01 +0000</created>
                <updated>Sat, 2 Mar 2013 11:59:43 +0000</updated>
                    <resolved>Sat, 2 Mar 2013 11:59:43 +0000</resolved>
                                                                    <due></due>
                    <votes>0</votes>
                        <watches>1</watches>
                        <comments>
                    <comment id="19672" author="dbu" created="Fri, 22 Feb 2013 14:53:09 +0000"  >&lt;p&gt;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 &lt;a href=&quot;https://github.com/doctrine/DoctrinePHPCRBundle/pull/37&quot; class=&quot;external-link&quot;&gt;https://github.com/doctrine/DoctrinePHPCRBundle/pull/37&lt;/a&gt;&lt;/p&gt;</comment>
                    <comment id="19791" author="dbu" created="Sat, 2 Mar 2013 11:59:43 +0000"  >&lt;p&gt;the PR got merged &lt;a href=&quot;https://github.com/doctrine/phpcr-odm/pull/253&quot; class=&quot;external-link&quot;&gt;https://github.com/doctrine/phpcr-odm/pull/253&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;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&apos;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)&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>
</channel>
</rss>