<!--
RSS generated by JIRA (5.2.7#850-sha1:b2af0c8dc8537b36121c6a579fabbdf79fc919e5) at Sun May 19 21:51:04 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/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=project+%3D+DDC+AND+resolution+%3D+Unresolved+AND+fixVersion+%3D+%222.0%22+ORDER+BY+priority+DESC&tempMax=1000&field=key&field=summary
-->
<!-- If you wish to do custom client-side styling of RSS, uncomment this:
<?xml-stylesheet href="http://www.doctrine-project.org/jira/styles/jiraxml2html.xsl" type="text/xsl"?>
-->
<rss version="0.92">
    <channel>
        <title>Doctrine Project</title>
        <link>http://www.doctrine-project.org/jira/secure/IssueNavigator.jspa?reset=true&amp;jqlQuery=project+%3D+DDC+AND+resolution+%3D+Unresolved+AND+fixVersion+%3D+%222.0%22+ORDER+BY+priority+DESC</link>
        <description>An XML representation of a search request</description>
                <language>en-us</language>
                        <issue start="0" end="4" total="4"/>
                <build-info>
            <version>5.2.7</version>
            <build-number>850</build-number>
            <build-date>21-02-2013</build-date>
        </build-info>
<item>
            <title>[DDC-585] Create a coding standards document</title>
                <link>http://www.doctrine-project.org/jira/browse/DDC-585</link>
                <project id="10032" key="DDC">Doctrine 2 - ORM</project>
                        <description>&lt;p&gt;We need a new coding standards document for Doctrine 2.&lt;/p&gt;</description>
                <environment></environment>
            <key id="11353">DDC-585</key>
            <summary>Create a coding standards document</summary>
                <type id="3" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/task.png">Task</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="jwage">Jonathan H. Wage</assignee>
                                <reporter username="romanb">Roman S. Borschel</reporter>
                        <labels>
                    </labels>
                <created>Thu, 13 May 2010 06:42:33 +0000</created>
                <updated>Mon, 11 Feb 2013 17:04:20 +0000</updated>
                                                    <fixVersion>2.0</fixVersion>
                                        <due></due>
                    <votes>0</votes>
                        <watches>2</watches>
                        <comments>
                    <comment id="19435" author="benjamin" created="Tue, 29 Jan 2013 13:12:04 +0000"  >&lt;p&gt;Has there been any work on a coding standards document yet?&lt;br/&gt;
I&apos;m currently working on fixing documentation on this project, and it might be a good time to define a standard.&lt;br/&gt;
I&apos;ve started compiling a few recommendations based on various feedbacks I&apos;ve got in my pull requests, and I can post them here.&lt;br/&gt;
Please let me know if there have been previous attempts so far!&lt;/p&gt;</comment>
                    <comment id="19436" author="ocramius" created="Tue, 29 Jan 2013 13:20:58 +0000"  >&lt;p&gt;&lt;a href=&quot;http://www.doctrine-project.org/jira/secure/ViewProfile.jspa?name=benjamin&quot; class=&quot;user-hover&quot; rel=&quot;benjamin&quot;&gt;Benjamin Morel&lt;/a&gt; &lt;a href=&quot;http://www.doctrine-project.org/jira/secure/ViewProfile.jspa?name=guiblanco&quot; class=&quot;user-hover&quot; rel=&quot;guiblanco&quot;&gt;Guilherme Blanco&lt;/a&gt; may have a CS ruleset, but it&apos;s not ready yet. Perfect timing btw, we really need to automate this to avoid having all these useless CS fix comments in pull requests&lt;/p&gt;</comment>
                    <comment id="19437" author="benjamin" created="Tue, 29 Jan 2013 14:00:43 +0000"  >&lt;p&gt;Ok, I&apos;ll post my document here once ready, and &lt;a href=&quot;http://www.doctrine-project.org/jira/secure/ViewProfile.jspa?name=guiblanco&quot; class=&quot;user-hover&quot; rel=&quot;guiblanco&quot;&gt;Guilherme Blanco&lt;/a&gt; will be able to compare it with his ruleset!&lt;/p&gt;</comment>
                    <comment id="19443" author="benjamin" created="Wed, 30 Jan 2013 20:35:35 +0000"  >&lt;p&gt;Here is a first draft: &lt;a href=&quot;https://gist.github.com/4676670&quot; class=&quot;external-link&quot;&gt;https://gist.github.com/4676670&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Please comment!&lt;/p&gt;</comment>
                    <comment id="19531" author="benjamin" created="Mon, 11 Feb 2013 17:03:41 +0000"  >&lt;p&gt;&lt;a href=&quot;http://www.doctrine-project.org/jira/secure/ViewProfile.jspa?name=guiblanco&quot; class=&quot;user-hover&quot; rel=&quot;guiblanco&quot;&gt;Guilherme Blanco&lt;/a&gt;, if you don&apos;t have time to compare your ruleset with my draft, maybe you could publish your current ruleset so that others can have a look?&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[DDC-536] Remove the _ prefix from private and protected members</title>
                <link>http://www.doctrine-project.org/jira/browse/DDC-536</link>
                <project id="10032" key="DDC">Doctrine 2 - ORM</project>
                        <description>&lt;p&gt;The reasoning is simple: The prefix &quot;_&quot; is usually either used for easier distinction of instance variables from other, i.e. local variables, instead of always using &quot;this.&quot; (often seen in C#), or it is used to signal that a member is not meant to be accessed from outside of the class when the language does not have visibility modifiers (PHP4).&lt;/p&gt;

&lt;p&gt;Since you always have to use &quot;$this-&amp;gt;&quot; in PHP5+ when accessing instance members and there are visibility modifiers, the &quot;_&quot; is largely superfluous and just makes the verbose OO code even more verbose.&lt;/p&gt;

&lt;p&gt;Maybe the following find/replace steps will do the job almost completely:&lt;/p&gt;

&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;&lt;span class=&quot;code-quote&quot;&gt;&quot;&lt;span class=&quot;code-keyword&quot;&gt;private&lt;/span&gt; $_&quot;&lt;/span&gt; =&amp;gt; &lt;span class=&quot;code-quote&quot;&gt;&quot;&lt;span class=&quot;code-keyword&quot;&gt;private&lt;/span&gt; $&quot;&lt;/span&gt;
&lt;span class=&quot;code-quote&quot;&gt;&quot;&lt;span class=&quot;code-keyword&quot;&gt;protected&lt;/span&gt; $_&quot;&lt;/span&gt; =&amp;gt; &lt;span class=&quot;code-quote&quot;&gt;&quot;&lt;span class=&quot;code-keyword&quot;&gt;protected&lt;/span&gt; $&quot;&lt;/span&gt;
&lt;span class=&quot;code-quote&quot;&gt;&quot;$&lt;span class=&quot;code-keyword&quot;&gt;this&lt;/span&gt;-&amp;gt;_&quot;&lt;/span&gt; =&amp;gt; &lt;span class=&quot;code-quote&quot;&gt;&quot;$&lt;span class=&quot;code-keyword&quot;&gt;this&lt;/span&gt;-&amp;gt;&quot;&lt;/span&gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</description>
                <environment></environment>
            <key id="11261">DDC-536</key>
            <summary>Remove the _ prefix from private and protected members</summary>
                <type id="3" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/task.png">Task</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="romanb">Roman S. Borschel</reporter>
                        <labels>
                    </labels>
                <created>Fri, 23 Apr 2010 09:26:24 +0000</created>
                <updated>Fri, 19 Nov 2010 00:00:39 +0000</updated>
                                                    <fixVersion>2.0</fixVersion>
                                        <due></due>
                    <votes>1</votes>
                        <watches>3</watches>
                        <comments>
                    <comment id="12761" author="beberlei" created="Tue, 27 Apr 2010 05:50:39 +0000"  >&lt;p&gt;i just found a possible BC issue with this.&lt;/p&gt;

&lt;p&gt;EntityRepository is allowed to be extended by us, it has several variables that are underscore prefixed. How to proceed in this case?&lt;/p&gt;</comment>
                    <comment id="12762" author="romanb" created="Tue, 27 Apr 2010 05:56:06 +0000"  >&lt;p&gt;I know but its not really a problem I think. We should just decide whether we make them private in the first place and provide getters instead (which would have avoided this problem in the first place).&lt;/p&gt;</comment>
                    <comment id="12763" author="romanb" created="Tue, 27 Apr 2010 05:56:59 +0000"  >&lt;p&gt;Leaving the prefixes on the repository class only is also an option... but I dont think thats necessary.&lt;/p&gt;</comment>
                    <comment id="12764" author="beberlei" created="Tue, 27 Apr 2010 06:28:59 +0000"  >&lt;p&gt;can we commit getters for Beta 1 then? We could give everyone a period until Beta 2 to fix their code and then make the change.&lt;/p&gt;

&lt;p&gt;EntityRepository is the only class that is meant to be userland extendable to my knowledge, so this should be the only problem to adress&lt;/p&gt;</comment>
                    <comment id="12766" author="romanb" created="Tue, 27 Apr 2010 09:25:21 +0000"  >&lt;p&gt;Yes, you can add getters and commit right away if you want. Plus adding a note on the upgrade document that direct access of these properties is deprecated.&lt;/p&gt;</comment>
                    <comment id="12767" author="romanb" created="Tue, 27 Apr 2010 09:26:22 +0000"  >&lt;p&gt;Persisters will be also extensible some day in userland but they need more polish for that, I&apos;ve already started with it &lt;img class=&quot;emoticon&quot; src=&quot;http://www.doctrine-project.org/jira/images/icons/emoticons/smile.gif&quot; height=&quot;20&quot; width=&quot;20&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/p&gt;</comment>
                    <comment id="14785" author="johnnypeck" created="Fri, 19 Nov 2010 00:00:39 +0000"  >&lt;p&gt;Is this still planned? Searching the code base finds this is not being implemented. It would be a good idea to implement the change sooner than later if it will be done at all.  Also, +1 for the change. It makes complete sense.&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[DDC-530] Create tests and documentation for possibilities of mixing inheritance mapping strategies</title>
                <link>http://www.doctrine-project.org/jira/browse/DDC-530</link>
                <project id="10032" key="DDC">Doctrine 2 - ORM</project>
                        <description>&lt;p&gt;It is (theoretically) possible to use different inheritance mapping strategies in the same class hierarchy as long as the different subtrees that use different mapping strategies do not have a common ancestor entity. We should add some tests for that and mention it in the docs about inheritance mapping in a new subsection &quot;Mixing Inheritance Mapping Strategies&quot;.&lt;/p&gt;</description>
                <environment></environment>
            <key id="11244">DDC-530</key>
            <summary>Create tests and documentation for possibilities of mixing inheritance mapping strategies</summary>
                <type id="3" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/task.png">Task</type>
                                <priority id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/minor.png">Minor</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="romanb">Roman S. Borschel</reporter>
                        <labels>
                    </labels>
                <created>Mon, 19 Apr 2010 05:37:55 +0000</created>
                <updated>Mon, 19 Apr 2010 05:37:55 +0000</updated>
                                    <version>2.0-BETA1</version>
                                <fixVersion>2.0</fixVersion>
                                <component>ORM</component>
                        <due></due>
                    <votes>0</votes>
                        <watches>0</watches>
                                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[DDC-473] Inadequate description for @MappedSuperclass in Annotations Reference</title>
                <link>http://www.doctrine-project.org/jira/browse/DDC-473</link>
                <project id="10032" key="DDC">Doctrine 2 - ORM</project>
                        <description>&lt;p&gt;See: &lt;a href=&quot;http://www.doctrine-project.org/documentation/manual/2_0/en/annotations-reference#ann_mappedsuperclass&quot; class=&quot;external-link&quot;&gt;http://www.doctrine-project.org/documentation/manual/2_0/en/annotations-reference#ann_mappedsuperclass&lt;/a&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;@MappedSuperclass&lt;/p&gt;

&lt;p&gt;An mapped superclass is an abstract or concrete class that provides persistent entity state and mapping information for its subclasses, but which is not itself an entity. This annotation is specified on the Class docblock and has no additional attributes.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;This doesn&apos;t adequately communicate how to use it. It took me several minutes of failing before I downloaded the PDF and did a search for @MappedSuperclass to find an example of how it&apos;s used.&lt;/p&gt;

&lt;p&gt;Specifically the following were unclear:&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;Is this defined on the superclass or on the children classes?&lt;/li&gt;
	&lt;li&gt;If it&apos;s defined on the child classes, does it take parameters? The name of the super class?&lt;/li&gt;
	&lt;li&gt;It was not at all apparent to me that it was mutually exclusive with the @Entity tag&lt;/li&gt;
&lt;/ul&gt;
</description>
                <environment></environment>
            <key id="11133">DDC-473</key>
            <summary>Inadequate description for @MappedSuperclass in Annotations Reference</summary>
                <type id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/improvement.png">Improvement</type>
                                <priority id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/minor.png">Minor</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="jwage">Jonathan H. Wage</assignee>
                                <reporter username="hobodave">David Abdemoulaie</reporter>
                        <labels>
                    </labels>
                <created>Thu, 25 Mar 2010 14:09:54 +0000</created>
                <updated>Thu, 26 Aug 2010 08:02:03 +0000</updated>
                                    <version>2.0-ALPHA4</version>
                                <fixVersion>2.0</fixVersion>
                                <component>Documentation</component>
                        <due></due>
                    <votes>0</votes>
                        <watches>0</watches>
                        <comments>
                    <comment id="12462" author="hobodave" created="Thu, 25 Mar 2010 14:14:30 +0000"  >&lt;p&gt;Apparently it&apos;s also incompatible with several other tag as well.&lt;/p&gt;

&lt;p&gt;I thought it made sense to try the following and see if the @InheritanceType and @Discriminator___ tags would apply to the children classes:&lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;/**
 * @MappedSuperclass
 * @InheritanceType(&quot;SINGLE_TABLE&quot;)
 * @DiscriminatorColumn(name=&quot;type&quot;, type=&quot;string&quot;)
 * @DiscriminatorMap({&quot;User&quot; = &quot;User&quot;, &quot;Group&quot; = &quot;Group&quot;})
 */
abstract class Principal
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;But apparently this flags D2 to treat it as an Entity anyway, resulting in the following error:&lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table &apos;sentact5.principal&apos;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</comment>
                    <comment id="12482" author="beberlei" created="Sun, 28 Mar 2010 06:53:24 +0000"  >&lt;p&gt;I updated the documentation, the question is if we should check for the mapped superclass attribute and throw exceptions if other entity level annotations are specified.&lt;/p&gt;</comment>
                    <comment id="12678" author="romanb" created="Thu, 15 Apr 2010 13:14:01 +0000"  >&lt;p&gt;A mapped superclass has not many restrictions and these are mentioned in the docs (i.e. only unidirectional associations), what David mentions above should work, if it doesnt its a bug, I think &lt;a href=&quot;http://www.doctrine-project.org/jira/browse/DDC-511&quot; title=&quot;Schema tool does not support STI - attempts to create a table per subclass&quot;&gt;&lt;del&gt;DDC-511&lt;/del&gt;&lt;/a&gt; looks like that same issue.&lt;/p&gt;</comment>
                    <comment id="12679" author="romanb" created="Thu, 15 Apr 2010 13:20:55 +0000"  >&lt;p&gt;David,&lt;/p&gt;

&lt;p&gt;@&quot;Is this defined on the superclass or on the children classes?&quot;&lt;/p&gt;

&lt;p&gt;It doesnt matter. A @MappedSuperclass can be anywhere in an inheritance hierarchy and it always does the same thing, inherit its mapping information to subclasses (but its not itself an entity). The docs say:&lt;/p&gt;

&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;Mapped superclasses, just as regular, non-mapped classes, can appear in the middle of an otherwise mapped inheritance hierarchy (through Single Table Inheritance or &lt;span class=&quot;code-object&quot;&gt;Class&lt;/span&gt; Table Inheritance).
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;as well as&lt;/p&gt;

&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;Entities support inheritance, polymorphic associations, and polymorphic queries. Both &lt;span class=&quot;code-keyword&quot;&gt;abstract&lt;/span&gt; and concrete classes can be entities. Entities may extend non-entity classes as well as entity classes, and non-entity classes may extend entity classes.
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;So entities, mapped superclasses and plain non-mapped classes can appear mixed in an inheritance hierarchy. Nevertheless all the classes in a hierarchy that are entities must use 1 inheritance strategy, you can not mix inheritance mapping strategies in a single class hierarchy.&lt;/p&gt;

&lt;p&gt;@&quot;If it&apos;s defined on the child classes, does it take parameters? The name of the super class?&quot;&lt;/p&gt;

&lt;p&gt;No, it doesnt. The docs dont mention any parameters either which is correct.&lt;/p&gt;

&lt;p&gt;@&quot;It was not at all apparent to me that it was mutually exclusive with the @Entity tag&quot;&lt;/p&gt;

&lt;p&gt;OK, that needs to be made clearer in the docs then.&lt;/p&gt;
</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>
</channel>
</rss>