<!-- 
RSS generated by JIRA (5.2.7#850-sha1:b2af0c8dc8537b36121c6a579fabbdf79fc919e5) at Wed Jun 19 16:05:29 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/DDC-2090/DDC-2090.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>[DDC-2090] MultiTableUpdateExecutor works incorrect with query cache enabled</title>
                <link>http://www.doctrine-project.org/jira/browse/DDC-2090</link>
                <project id="10032" key="DDC">Doctrine 2 - ORM</project>
                        <description>&lt;p&gt;Doctrine\ORM\Query\Exec\MultiTableUpdateExecutor works incorrect with query cache enabled.&lt;br/&gt;
I execute two similar update-queries with different parameters, but the second query is never executed in database.&lt;/p&gt;

&lt;p&gt;There is todo-task in code:&lt;/p&gt;

&lt;p&gt;//FIXME (URGENT): With query cache the parameter is out of date. Move to execute() stage.&lt;/p&gt;

&lt;p&gt;This is important issue. Much time spent in debugging.&lt;/p&gt;</description>
                <environment></environment>
            <key id="14147">DDC-2090</key>
            <summary>MultiTableUpdateExecutor works incorrect with query cache enabled</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="5" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/resolved.png">Resolved</status>
                    <resolution id="1">Fixed</resolution>
                    <security id="10000">All</security>
                        <assignee username="fabio.bat.silva">Fabio B. Silva</assignee>
                                <reporter username="feedbee">Valera Leontyev</reporter>
                        <labels>
                    </labels>
                <created>Fri, 19 Oct 2012 13:39:45 +0000</created>
                <updated>Sun, 17 Mar 2013 20:50:48 +0000</updated>
                    <resolved>Sun, 17 Mar 2013 20:40:44 +0000</resolved>
                            <version>Git Master</version>
                                <fixVersion>2.4</fixVersion>
                <fixVersion>2.3.3</fixVersion>
                                <component>ORM</component>
                        <due></due>
                    <votes>0</votes>
                        <watches>3</watches>
                        <comments>
                    <comment id="18852" author="feedbee" created="Fri, 19 Oct 2012 13:40:49 +0000"  >&lt;p&gt;Workaround is to disable query cache per every multitable update query: &lt;a href=&quot;http://stackoverflow.com/questions/12969460/doctrine-query-cache-update&quot; class=&quot;external-link&quot;&gt;http://stackoverflow.com/questions/12969460/doctrine-query-cache-update&lt;/a&gt;&lt;/p&gt;</comment>
                    <comment id="19870" author="fabio.bat.silva" created="Sun, 17 Mar 2013 20:40:44 +0000"  >&lt;p&gt;Fixed : &lt;a href=&quot;https://github.com/doctrine/doctrine2/commit/60b8bc63a1a4819cf112cfbbc7cca06b5792aba6&quot; class=&quot;external-link&quot;&gt;https://github.com/doctrine/doctrine2/commit/60b8bc63a1a4819cf112cfbbc7cca06b5792aba6&lt;/a&gt;&lt;/p&gt;</comment>
                    <comment id="19871" author="beberlei" created="Sun, 17 Mar 2013 20:50:48 +0000"  >&lt;p&gt;Merged into 2.3 for release with 2.3.3&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>
</channel>
</rss>