<!-- 
RSS generated by JIRA (5.2.7#850-sha1:b2af0c8dc8537b36121c6a579fabbdf79fc919e5) at Sat May 18 11:25:08 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-72/PHPCR-72.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-72] persist cancels move</title>
                <link>http://www.doctrine-project.org/jira/browse/PHPCR-72</link>
                <project id="10060" key="PHPCR">Doctrine PHPCR</project>
                        <description>&lt;p&gt;If i have a node that i fetch from the repo using $dm-&amp;gt;find()&lt;/p&gt;

&lt;p&gt;If i change an attribute in it.&lt;br/&gt;
Then i call $dm-&amp;gt;move() on it&lt;/p&gt;

&lt;p&gt;Then i call $dm-&amp;gt;flush().&lt;/p&gt;

&lt;p&gt;It will work.&lt;/p&gt;

&lt;p&gt;However if i call $dm-&amp;gt;persist() on the node (that i already fetched from $dm-&amp;gt;find()) and then call $dm-&amp;gt;flush()&lt;br/&gt;
The $dm-&amp;gt;move() won&apos;t occur, it will be cancelled, but the attribute i changed will still be updated.&lt;/p&gt;</description>
                <environment></environment>
            <key id="13787">PHPCR-72</key>
            <summary>persist cancels move</summary>
                <type id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/bug.png">Bug</type>
                                <priority id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/minor.png">Minor</priority>
                    <status id="5" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/resolved.png">Resolved</status>
                    <resolution id="2">Won&apos;t Fix</resolution>
                                <assignee username="lsmith">Lukas Kahwe</assignee>
                                <reporter username="freddyh">Freddy H.</reporter>
                        <labels>
                    </labels>
                <created>Tue, 19 Jun 2012 15:43:52 +0000</created>
                <updated>Sat, 21 Jul 2012 07:54:08 +0000</updated>
                    <resolved>Sat, 21 Jul 2012 07:54:08 +0000</resolved>
                                                                    <due></due>
                    <votes>0</votes>
                        <watches>1</watches>
                        <comments>
                    <comment id="18360" author="lsmith" created="Fri, 20 Jul 2012 21:15:18 +0000"  >&lt;p&gt;i have to think about if this is a bug or a feature.&lt;br/&gt;
its certainly useful to have a way to &quot;cancel&quot; operations ..&lt;br/&gt;
f.e. persist() also cancels remove()&lt;/p&gt;

&lt;p&gt;then again persist() is i guess viewed by many as a non problematic operation since it commonly doesn&apos;t break anything if one persisted an object multiple times.&lt;/p&gt;</comment>
                    <comment id="18361" author="lsmith" created="Sat, 21 Jul 2012 07:54:08 +0000"  >&lt;p&gt;as i expected this is an intentional feature:&lt;br/&gt;
&lt;a href=&quot;https://github.com/doctrine/phpcr-odm/blob/master/lib/Doctrine/ODM/PHPCR/UnitOfWork.php#L518&quot; class=&quot;external-link&quot;&gt;https://github.com/doctrine/phpcr-odm/blob/master/lib/Doctrine/ODM/PHPCR/UnitOfWork.php#L518&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;we could think about adding a dedicated method to &quot;reset&quot; the state, but the ORM doesn&apos;t have something like that so i rather not introduce it.&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>
</channel>
</rss>