<!-- 
RSS generated by JIRA (5.2.7#850-sha1:b2af0c8dc8537b36121c6a579fabbdf79fc919e5) at Thu Jun 20 03:39:52 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-769/DDC-769.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-769] Disabling discriminator column in WHERE clause</title>
                <link>http://www.doctrine-project.org/jira/browse/DDC-769</link>
                <project id="10032" key="DDC">Doctrine 2 - ORM</project>
                        <description>&lt;p&gt;Per default Doctrine 2 adds an IN(...)-part to the query when hydrating an entity where a discriminator column is defined. While this makes sense as a default behavior, it would be pretty helpful if one could disable the WHERE-clause for discriminator columns alltogether for performance optimization.&lt;/p&gt;</description>
                <environment></environment>
            <key id="11830">DDC-769</key>
            <summary>Disabling discriminator column in WHERE clause</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>
                    <security id="10000">All</security>
                        <assignee username="romanb">Roman S. Borschel</assignee>
                                <reporter username="lstrojny">Lars Strojny</reporter>
                        <labels>
                    </labels>
                <created>Thu, 26 Aug 2010 10:41:56 +0000</created>
                <updated>Tue, 7 Sep 2010 06:49:13 +0000</updated>
                                    <version>2.0-BETA3</version>
                                                        <due></due>
                    <votes>1</votes>
                        <watches>1</watches>
                        <comments>
                    <comment id="14094" author="romanb" created="Thu, 26 Aug 2010 12:39:43 +0000"  >&lt;p&gt;That would obviously produce wrong results. Maybe you can elaborate more with an example.&lt;/p&gt;</comment>
                    <comment id="14299" author="lstrojny" created="Tue, 7 Sep 2010 06:49:13 +0000"  >&lt;p&gt;I use ENUM(&quot;foo&quot;,&quot;bar&quot;) as discriminator columns. That means, the column will contain the right values out of the box, no further result set limiting required with WHERE.&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>
</channel>
</rss>