<!-- 
RSS generated by JIRA (5.2.7#850-sha1:b2af0c8dc8537b36121c6a579fabbdf79fc919e5) at Sun May 19 12:42:21 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-952/DDC-952.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-952] Several features to batch eager selects more efficently</title>
                <link>http://www.doctrine-project.org/jira/browse/DDC-952</link>
                <project id="10032" key="DDC">Doctrine 2 - ORM</project>
                        <description>&lt;p&gt;This ticket aggregates several strategies to optimize batching of eager selects.&lt;/p&gt;</description>
                <environment></environment>
            <key id="12257">DDC-952</key>
            <summary>Several features to batch eager selects more efficently</summary>
                <type id="2" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/newfeature.png">New Feature</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="beberlei">Benjamin Eberlei</assignee>
                                <reporter username="beberlei">Benjamin Eberlei</reporter>
                        <labels>
                    </labels>
                <created>Mon, 27 Dec 2010 18:14:21 +0000</created>
                <updated>Mon, 4 Jul 2011 21:47:46 +0000</updated>
                                                    <fixVersion>2.x</fixVersion>
                                <component>ORM</component>
                        <due></due>
                    <votes>0</votes>
                        <watches>0</watches>
                        <comments>
                    <comment id="15074" author="beberlei" created="Fri, 31 Dec 2010 06:47:18 +0000"  >&lt;p&gt;Requirements for batching of eager loads:&lt;/p&gt;

&lt;p&gt;1. Since we are using an IN() query for this we can only support this feature for entities that have a single column primary key.&lt;br/&gt;
2. If we want to support composite keys we need to build it as WHERE ( (id1 = ? AND id2 = ?) OR (id1 = ? AND id2 = ?)) but this is currently not possible with the way how internally the $criteria array is used.&lt;/p&gt;</comment>
                    <comment id="15075" author="beberlei" created="Fri, 31 Dec 2010 07:38:56 +0000"  >&lt;p&gt;Next item to think about: What if an exception or event breaks the flow and &quot;triggerEagerLoads()&quot; is never called?&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
            <subtask id="11731">DDC-733</subtask>
            <subtask id="11736">DDC-734</subtask>
            <subtask id="10197">DDC-53</subtask>
            <subtask id="12249">DDC-914</subtask>
            <subtask id="12453">DDC-1060</subtask>
            <subtask id="12269">DDC-963</subtask>
            <subtask id="12076">DDC-865</subtask>
        </subtasks>
        </item>
</channel>
</rss>