<!-- 
RSS generated by JIRA (5.2.7#850-sha1:b2af0c8dc8537b36121c6a579fabbdf79fc919e5) at Sat May 25 02:20:02 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-937/DDC-937.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-937] doctrine-mapping.xsd sequence relation-entities </title>
                <link>http://www.doctrine-project.org/jira/browse/DDC-937</link>
                <project id="10032" key="DDC">Doctrine 2 - ORM</project>
                        <description>&lt;p&gt; I noticed some problems with &lt;br/&gt;
the doctrine-mapping.xsd (which apparently is not used to validate the &lt;br/&gt;
mapping, but only provided to support code completion in your xml- &lt;br/&gt;
editor) &lt;/p&gt;

&lt;p&gt;The order in which you define the elements like cascade and join- &lt;br/&gt;
column(s) for the relation-entities is currently important since it is &lt;br/&gt;
a sequence, but is this really desired? Why force this order? defining &lt;br/&gt;
cascade before join-column would make perfect sense as well, doesn&apos;t &lt;br/&gt;
it. &lt;/p&gt;</description>
                <environment></environment>
            <key id="12233">DDC-937</key>
            <summary>doctrine-mapping.xsd sequence relation-entities </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="1">Fixed</resolution>
                    <security id="10000">All</security>
                        <assignee username="guilhermeblanco">Guilherme Blanco</assignee>
                                <reporter username="lvanderree">Leon van der Ree</reporter>
                        <labels>
                    </labels>
                <created>Wed, 15 Dec 2010 10:55:40 +0000</created>
                <updated>Sat, 23 Jun 2012 04:31:23 +0000</updated>
                    <resolved>Sat, 23 Jun 2012 04:31:23 +0000</resolved>
                            <version>Git Master</version>
                                <fixVersion>2.3</fixVersion>
                                <component>Mapping Drivers</component>
                        <due></due>
                    <votes>0</votes>
                        <watches>0</watches>
                        <comments>
                    <comment id="16555" author="guilhermeblanco" created="Tue, 4 Oct 2011 05:22:46 +0000"  >&lt;p&gt;Is this issue still valid in the latest Doctrine (trunk)? It doesn&apos;t seem to be.&lt;/p&gt;</comment>
                    <comment id="18133" author="guilhermeblanco" created="Sat, 23 Jun 2012 04:31:22 +0000"  >&lt;p&gt;No reply from user and issue seems to be fixed already in master&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>
</channel>
</rss>