<!-- 
RSS generated by JIRA (5.2.7#850-sha1:b2af0c8dc8537b36121c6a579fabbdf79fc919e5) at Sun May 19 20:58:38 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/MODM-157/MODM-157.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>[MODM-157] Github-PR-151 by l3pp4rd: fixes triggering fatal error on preupdate event in case changeset is clea</title>
                <link>http://www.doctrine-project.org/jira/browse/MODM-157</link>
                <project id="10044" key="MODM">Doctrine MongoDB ODM</project>
                        <description>&lt;p&gt;This issue is created automatically through a Github pull request on behalf of &lt;/p&gt;
{username}
&lt;p&gt;:&lt;/p&gt;

&lt;p&gt;  Url: &lt;a href=&quot;https://github.com/doctrine/mongodb-odm/pull/151&quot; class=&quot;external-link&quot;&gt;https://github.com/doctrine/mongodb-odm/pull/151&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Message:&lt;/p&gt;

&lt;p&gt;fixes triggering fatal error on preupdate event in case changeset is cleared during onFlush&lt;/p&gt;

&lt;p&gt;similar issue is fixed in ORM it should be supported on ODM mongodb also&lt;/p&gt;</description>
                <environment></environment>
            <key id="12971">MODM-157</key>
            <summary>Github-PR-151 by l3pp4rd: fixes triggering fatal error on preupdate event in case changeset is clea</summary>
                <type id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/improvement.png">Improvement</type>
                                <priority id="3" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/major.png">Major</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="beberlei">Benjamin Eberlei</assignee>
                                <reporter username="beberlei">Benjamin Eberlei</reporter>
                        <labels>
                    </labels>
                <created>Thu, 25 Aug 2011 18:02:51 +0000</created>
                <updated>Mon, 19 Sep 2011 13:51:24 +0000</updated>
                                                                            <due></due>
                    <votes>0</votes>
                        <watches>2</watches>
                        <comments>
                    <comment id="16494" author="strygin" created="Mon, 19 Sep 2011 13:27:25 +0000"  >&lt;p&gt;Hmm... The bug is still actual for ORM layer in master. &lt;/p&gt;</comment>
                    <comment id="16495" author="vgarvardt" created="Mon, 19 Sep 2011 13:51:24 +0000"  >&lt;p&gt;Got the same issue for ORM in 2.1.1 and same in master. Made a fix based on fix for ODM and pull request on github.&lt;/p&gt;

&lt;p&gt;URL: &lt;a href=&quot;https://github.com/doctrine/doctrine2/pull/126&quot; class=&quot;external-link&quot;&gt;https://github.com/doctrine/doctrine2/pull/126&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;PS: maybe new issue should be created in Doctrine 2 - ORM project for this issue&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>
</channel>
</rss>