<!--
RSS generated by JIRA (5.2.7#850-sha1:b2af0c8dc8537b36121c6a579fabbdf79fc919e5) at Fri May 24 05:35:19 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+priority+%3D+Trivial+ORDER+BY+key+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+priority+%3D+Trivial+ORDER+BY+key+DESC</link>
        <description>An XML representation of a search request</description>
                <language>en-us</language>
                        <issue start="0" end="14" total="14"/>
                <build-info>
            <version>5.2.7</version>
            <build-number>850</build-number>
            <build-date>21-02-2013</build-date>
        </build-info>
<item>
            <title>[DDC-1972] Throw an exception when setting cascade options which do not exist</title>
                <link>http://www.doctrine-project.org/jira/browse/DDC-1972</link>
                <project id="10032" key="DDC">Doctrine 2 - ORM</project>
                        <description>&lt;p&gt;I made the assumption that the way to define a cascading delete is to do (in YAML):&lt;/p&gt;

&lt;p&gt;cascade: &lt;span class=&quot;error&quot;&gt;&amp;#91;delete&amp;#93;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;When it is actually:&lt;/p&gt;

&lt;p&gt;cascade: &lt;span class=&quot;error&quot;&gt;&amp;#91;remove&amp;#93;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;It would be nice if Doctrine would throw an exception when the user sets a cascade option which does not exist.&lt;/p&gt;</description>
                <environment></environment>
            <key id="13949">DDC-1972</key>
            <summary>Throw an exception when setting cascade options which do not exist</summary>
                <type id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/improvement.png">Improvement</type>
                                <priority id="5" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/trivial.png">Trivial</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="beberlei">Benjamin Eberlei</assignee>
                                <reporter username="gzankevich">George Zankevich</reporter>
                        <labels>
                    </labels>
                <created>Wed, 8 Aug 2012 15:20:03 +0000</created>
                <updated>Wed, 8 Aug 2012 15:20:03 +0000</updated>
                                    <version>2.1.6</version>
                                                <component>ORM</component>
                        <due></due>
                    <votes>0</votes>
                        <watches>1</watches>
                                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[DDC-1765] SchemaTool Commands should accept both --force and --dump-sql</title>
                <link>http://www.doctrine-project.org/jira/browse/DDC-1765</link>
                <project id="10032" key="DDC">Doctrine 2 - ORM</project>
                        <description>&lt;p&gt;When running SchemaTool for schema operations you can get either a --dump-sql or make the changes using --force&lt;/p&gt;

&lt;p&gt;When you run with --force you get a generic &quot;1 query executed&quot; response, there should be a way to execute it receiving feedback of the queries and making the changes.&lt;/p&gt;

&lt;p&gt;This is good for example for my automated test env builder, as the return of this command would be logged. But i see no reason why the script can&apos;t take both options.&lt;/p&gt;</description>
                <environment></environment>
            <key id="13606">DDC-1765</key>
            <summary>SchemaTool Commands should accept both --force and --dump-sql</summary>
                <type id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/improvement.png">Improvement</type>
                                <priority id="5" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/trivial.png">Trivial</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="rdohms">Rafael Dohms</reporter>
                        <labels>
                    </labels>
                <created>Wed, 4 Apr 2012 15:16:27 +0000</created>
                <updated>Sat, 17 Nov 2012 15:21:38 +0000</updated>
                                                                    <component>ORM</component>
                        <due></due>
                    <votes>0</votes>
                        <watches>1</watches>
                        <comments>
                    <comment id="19004" author="nemek_zg" created="Sat, 17 Nov 2012 15:21:38 +0000"  >&lt;p&gt;Proposed fix: &lt;a href=&quot;https://github.com/doctrine/doctrine2/pull/517&quot; class=&quot;external-link&quot;&gt;https://github.com/doctrine/doctrine2/pull/517&lt;/a&gt;&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[DDC-1761] Small error on DQL documentation page</title>
                <link>http://www.doctrine-project.org/jira/browse/DDC-1761</link>
                <project id="10032" key="DDC">Doctrine 2 - ORM</project>
                        <description>&lt;p&gt;On this document page:&lt;br/&gt;
&lt;a href=&quot;http://docs.doctrine-project.org/projects/doctrine-orm/en/2.0.x/reference/dql-doctrine-query-language.html#dql-select-examples&quot; class=&quot;external-link&quot;&gt;http://docs.doctrine-project.org/projects/doctrine-orm/en/2.0.x/reference/dql-doctrine-query-language.html#dql-select-examples&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The following lines are present:&lt;br/&gt;
$query = $em-&amp;gt;createQuery(&apos;SELECT u.username, u.name FROM CmsUser u&apos;);&lt;br/&gt;
$users = $query-&amp;gt;getResults(); // array of CmsUser username and name values&lt;br/&gt;
echo $users&lt;span class=&quot;error&quot;&gt;&amp;#91;0&amp;#93;&lt;/span&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;&amp;#39;username&amp;#39;&amp;#93;&lt;/span&gt;;&lt;/p&gt;

&lt;p&gt;There is an error in:&lt;br/&gt;
$query-&amp;gt;getResults();&lt;/p&gt;

&lt;p&gt;It should read&lt;br/&gt;
$query-&amp;gt;getResult();&lt;/p&gt;</description>
                <environment></environment>
            <key id="13600">DDC-1761</key>
            <summary>Small error on DQL documentation page</summary>
                <type id="6" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/documentation.png">Documentation</type>
                                <priority id="5" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/trivial.png">Trivial</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="beberlei">Benjamin Eberlei</assignee>
                                <reporter username="superdweebie">Tim Roediger</reporter>
                        <labels>
                    </labels>
                <created>Tue, 3 Apr 2012 23:27:57 +0000</created>
                <updated>Tue, 3 Apr 2012 23:28:41 +0000</updated>
                                    <version>2.2.1</version>
                                                <component>DQL</component>
                        <due></due>
                    <votes>0</votes>
                        <watches>0</watches>
                                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[DDC-1614] On OneToOne mappings with Primary Key same as Foreign Key, using @Id in the foreign association does not carry over when running &quot;generate-entities&quot; with --generate-annotations=1</title>
                <link>http://www.doctrine-project.org/jira/browse/DDC-1614</link>
                <project id="10032" key="DDC">Doctrine 2 - ORM</project>
                        <description>&lt;p&gt;When having a OneToOne mapping that has a primary key that is the same as the foreign key, using the @Id attribute does not carry over when generating entities.&lt;/p&gt;

&lt;p&gt;Example code:&lt;/p&gt;

&lt;p&gt;class User&lt;br/&gt;
{&lt;br/&gt;
    /**&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;@Id @Column(type=&quot;integer&quot;, nullable=false, columnDefinition=&quot;INT UNSIGNED NOT NULL AUTO_INCREMENT&quot;)&lt;/li&gt;
	&lt;li&gt;@GeneratedValue(strategy=&quot;AUTO&quot;)&lt;br/&gt;
     */&lt;br/&gt;
    private $id;&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;    /**&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;@OneToOne(targetEntity=&quot;User_ExtraAttrs&quot;, cascade=
{&quot;persist&quot;,&quot;remove&quot;,&quot;detach&quot;,&quot;merge&quot;,&quot;refresh&quot;}
&lt;p&gt;, mappedBy=&quot;User&quot;)&lt;/p&gt;&lt;/li&gt;
	&lt;li&gt;@JoinColumn(name=&quot;id&quot;, referencedColumnName=&quot;id&quot;)&lt;br/&gt;
     */&lt;br/&gt;
    private $UserAttrs;&lt;br/&gt;
}&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;class User_ExtraAttrs&lt;br/&gt;
{&lt;br/&gt;
    /**&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;@OneToOne(targetEntity=&quot;User&quot;, cascade=
{&quot;all&quot;}
&lt;p&gt;, inversedBy=&quot;UserAttrs&quot;)&lt;/p&gt;&lt;/li&gt;
	&lt;li&gt;@Id&lt;/li&gt;
	&lt;li&gt;@JoinColumn(name=&quot;VehicleID&quot;, referencedColumnName=&quot;VehicleID&quot;)&lt;br/&gt;
     */&lt;br/&gt;
    private $User;&lt;br/&gt;
}&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;When running &quot;doctrine orm:generate-entities --regenerate-entities=1 --generate-annotations=1&quot;, the @Id in User_ExtraAttrs does not carry over.  It must be manually inserted.&lt;/p&gt;
</description>
                <environment>Fedora 15, php 5.3.8</environment>
            <key id="13379">DDC-1614</key>
            <summary>On OneToOne mappings with Primary Key same as Foreign Key, using @Id in the foreign association does not carry over when running &quot;generate-entities&quot; with --generate-annotations=1</summary>
                <type id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/improvement.png">Improvement</type>
                                <priority id="5" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/trivial.png">Trivial</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="rfink">Ryan Fink</reporter>
                        <labels>
                    </labels>
                <created>Sun, 22 Jan 2012 18:11:20 +0000</created>
                <updated>Wed, 23 Jan 2013 22:32:41 +0000</updated>
                                    <version>2.1.1</version>
                                                <component>Mapping Drivers</component>
                <component>ORM</component>
                <component>Tools</component>
                        <due></due>
                    <votes>0</votes>
                        <watches>0</watches>
                                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[DDC-1611] Tools Reference example is apparently wrong</title>
                <link>http://www.doctrine-project.org/jira/browse/DDC-1611</link>
                <project id="10032" key="DDC">Doctrine 2 - ORM</project>
                        <description>&lt;p&gt;I was reading &lt;a href=&quot;http://www.doctrine-project.org/docs/orm/2.1/en/reference/tools.html&quot; class=&quot;external-link&quot;&gt;http://www.doctrine-project.org/docs/orm/2.1/en/reference/tools.html&lt;/a&gt;&lt;br/&gt;
In 24.2.2. Configuration (Non-PEAR)&lt;/p&gt;

&lt;p&gt;The example seems to be wrong.&lt;/p&gt;

&lt;p&gt;use Doctrine\DBAL\Tools\Console\Helper\EntityManagerHelper;&lt;br/&gt;
should be&lt;br/&gt;
use Doctrine\ORM\Tools\Console\Helper\EntityManagerHelper;&lt;/p&gt;

&lt;p&gt;That&apos;s all.&lt;/p&gt;</description>
                <environment></environment>
            <key id="13373">DDC-1611</key>
            <summary>Tools Reference example is apparently wrong</summary>
                <type id="6" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/documentation.png">Documentation</type>
                                <priority id="5" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/trivial.png">Trivial</priority>
                    <status id="1" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/open.png">Open</status>
                    <resolution id="-1">Unresolved</resolution>
                                <assignee username="beberlei">Benjamin Eberlei</assignee>
                                <reporter username="tarcisio.fischer">Tarc&#237;sio Fischer</reporter>
                        <labels>
                    </labels>
                <created>Thu, 19 Jan 2012 05:15:54 +0000</created>
                <updated>Fri, 20 Jan 2012 09:19:14 +0000</updated>
                                                                    <component>Documentation</component>
                        <due></due>
                    <votes>0</votes>
                        <watches>0</watches>
                        <comments>
                    <comment id="17310" author="craz" created="Fri, 20 Jan 2012 09:19:14 +0000"  >&lt;p&gt;Yes, this is a real problem.&lt;/p&gt;

&lt;p&gt;fixation and helped me&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[DDC-1466] Entity ID hash generation improvement in UnitOfWork</title>
                <link>http://www.doctrine-project.org/jira/browse/DDC-1466</link>
                <project id="10032" key="DDC">Doctrine 2 - ORM</project>
                        <description>&lt;p&gt;Currently ID hash is generated using implode function with space character. I would like to point out that problems may raise if the ID column values are allowed to contain the space themselves - different objects could return equal ID hash values.&lt;/p&gt;

&lt;p&gt;The trivial one-line solution would be to serialize the array instead. Cheaper solution from performance perspective would be escaping the space character for ID values.&lt;/p&gt;</description>
                <environment></environment>
            <key id="13143">DDC-1466</key>
            <summary>Entity ID hash generation improvement in UnitOfWork</summary>
                <type id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/improvement.png">Improvement</type>
                                <priority id="5" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/trivial.png">Trivial</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="gedrox">Aigars Gedroics</reporter>
                        <labels>
                    </labels>
                <created>Thu, 3 Nov 2011 10:23:14 +0000</created>
                <updated>Thu, 3 Nov 2011 10:23:14 +0000</updated>
                                    <version>Git Master</version>
                                                <component>DQL</component>
                        <due></due>
                    <votes>0</votes>
                        <watches>0</watches>
                                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[DDC-1169] Entities outside of drivers&apos; namespaces only give &apos;is not a valid entity&apos;</title>
                <link>http://www.doctrine-project.org/jira/browse/DDC-1169</link>
                <project id="10032" key="DDC">Doctrine 2 - ORM</project>
                        <description>&lt;p&gt;Hi,&lt;br/&gt;
in a situation where entity, that EM is to work with, is not inside of any namespace (that should be specified in $chainDriverImpl-&amp;gt;addDriver($metadataDriver, &apos;someNamespace&apos;); )&lt;br/&gt;
-&amp;gt; gives error message &apos;Entity # is not a valid entity or mapped superclass&apos; instead of notifying that the entity&apos;s namespace is not added&lt;/p&gt;</description>
                <environment></environment>
            <key id="12666">DDC-1169</key>
            <summary>Entities outside of drivers&apos; namespaces only give &apos;is not a valid entity&apos;</summary>
                <type id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/improvement.png">Improvement</type>
                                <priority id="5" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/trivial.png">Trivial</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="noxart">Ji&#345;&#237; Petru&#382;elka</reporter>
                        <labels>
                    </labels>
                <created>Wed, 25 May 2011 17:41:12 +0000</created>
                <updated>Wed, 25 May 2011 17:41:12 +0000</updated>
                                    <version>2.1</version>
                                                <component>Mapping Drivers</component>
                        <due></due>
                    <votes>0</votes>
                        <watches>0</watches>
                                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[DDC-1076] It should be possible to supply EntityManager with a custom ProxyFactory</title>
                <link>http://www.doctrine-project.org/jira/browse/DDC-1076</link>
                <project id="10032" key="DDC">Doctrine 2 - ORM</project>
                        <description>&lt;p&gt;It is plausible that one might want to handle the loading of proxy classes in their own way, perhaps not using the filename/class scheme doctrine currently comes with.&lt;/p&gt;

&lt;p&gt;Currently the only way to provide your own implementation of ProxyFactory is to subclass EntityManager. Even this is not clean since one also must copy/paste the EntityManager::create factory method to get identical behavior.&lt;/p&gt;

&lt;p&gt;It would be nice if there was a ProxyFactory interface and one could provide an instance of it to Doctrine\ORM\Configuration when creating an EntityManager.&lt;/p&gt;
</description>
                <environment></environment>
            <key id="12493">DDC-1076</key>
            <summary>It should be possible to supply EntityManager with a custom ProxyFactory</summary>
                <type id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/improvement.png">Improvement</type>
                                <priority id="5" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/trivial.png">Trivial</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="putgeminmouth">David Reisch</reporter>
                        <labels>
                    </labels>
                <created>Thu, 24 Mar 2011 15:22:14 +0000</created>
                <updated>Fri, 25 Mar 2011 10:27:07 +0000</updated>
                                                                    <component>ORM</component>
                        <due></due>
                    <votes>2</votes>
                        <watches>2</watches>
                        <comments>
                    <comment id="15577" author="putgeminmouth" created="Thu, 24 Mar 2011 15:22:38 +0000"  >&lt;p&gt;I would be happy to contribute a patch to this end.&lt;/p&gt;</comment>
                    <comment id="15581" author="beberlei" created="Fri, 25 Mar 2011 04:26:27 +0000"  >&lt;p&gt;Can you elaborate on your use-case? proxies are sorft of a by product, to be genreated in a temporary cache directory. I don&apos;t see why one should bother about how it is done.&lt;/p&gt;</comment>
                    <comment id="15585" author="putgeminmouth" created="Fri, 25 Mar 2011 10:27:06 +0000"  >&lt;p&gt;Hi,&lt;br/&gt;
I think allowing users to specify their own implementations for things is pretty essential for a library, especially when there is no cost in complexity or implementation.&lt;/p&gt;

&lt;p&gt;Anyhow, here&apos;s my pitch:&lt;/p&gt;

&lt;p&gt;I personally do not like using inheritance for proxies (it feels hackish to me), preferring instead to have interfaces for my Business Objects which the proxies implement. To that end, I do not generate my proxies with doctrine, but maintain my own, in my code base, and the class files do not necessarily match up to the doctrine ProxyFactory&apos;s assumptions about where to find the classes.&lt;/p&gt;

&lt;p&gt;Regards,&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[DDC-1004] Option for mapping:import to not write Entity Files if they exist</title>
                <link>http://www.doctrine-project.org/jira/browse/DDC-1004</link>
                <project id="10032" key="DDC">Doctrine 2 - ORM</project>
                        <description>&lt;p&gt;There should be an option to omit the creation of allready existing entities:&lt;/p&gt;

&lt;p&gt;Use Case:&lt;/p&gt;

&lt;p&gt;if you develop your model in the database and create the entities with the cli and then go on with development and create new tables you would build the entities again with the cli. This will kill your allready existing and possible extended entities.&lt;/p&gt;

&lt;p&gt;Best would be if you have to set the option when you want the existing entities overwritten. so you cant accidently overwrite them&lt;/p&gt;</description>
                <environment></environment>
            <key id="12329">DDC-1004</key>
            <summary>Option for mapping:import to not write Entity Files if they exist</summary>
                <type id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/improvement.png">Improvement</type>
                                <priority id="5" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/trivial.png">Trivial</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="monofone">s.rohweder</reporter>
                        <labels>
                    </labels>
                <created>Thu, 27 Jan 2011 07:02:33 +0000</created>
                <updated>Thu, 27 Jan 2011 07:06:41 +0000</updated>
                                                                    <component>Tools</component>
                        <due></due>
                    <votes>0</votes>
                        <watches>0</watches>
                                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[DDC-1003] Documentation refers to EAGER loading as FETCH</title>
                <link>http://www.doctrine-project.org/jira/browse/DDC-1003</link>
                <project id="10032" key="DDC">Doctrine 2 - ORM</project>
                        <description>&lt;p&gt;Throughout the documentation found in the following link (&lt;a href=&quot;http://www.doctrine-project.org/docs/orm/2.0/en/reference/xml-mapping.html&quot; class=&quot;external-link&quot;&gt;http://www.doctrine-project.org/docs/orm/2.0/en/reference/xml-mapping.html&lt;/a&gt;) when mentioning eager or lazy loading the documentation says FETCH instead of EAGER.&lt;/p&gt;

&lt;p&gt;E.G. content says &quot;fetch - Either LAZY or FETCH&quot; which should read &quot;fetch - Either LAZY or EAGER&quot;&lt;/p&gt;

&lt;p&gt;This occurs in a few different areas on this page.&lt;/p&gt;</description>
                <environment></environment>
            <key id="12328">DDC-1003</key>
            <summary>Documentation refers to EAGER loading as FETCH</summary>
                <type id="6" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/documentation.png">Documentation</type>
                                <priority id="5" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/trivial.png">Trivial</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="jaredf">jared fraser</reporter>
                        <labels>
                    </labels>
                <created>Wed, 26 Jan 2011 20:13:14 +0000</created>
                <updated>Wed, 26 Jan 2011 20:13:14 +0000</updated>
                                    <version>2.0</version>
                                                <component>Documentation</component>
                        <due></due>
                    <votes>0</votes>
                        <watches>0</watches>
                                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[DDC-940] Entities can / can not have private properties</title>
                <link>http://www.doctrine-project.org/jira/browse/DDC-940</link>
                <project id="10032" key="DDC">Doctrine 2 - ORM</project>
                        <description>&lt;p&gt;In the note in&lt;br/&gt;
&lt;a href=&quot;http://www.doctrine-project.org/docs/orm/2.0/en/reference/working-with-objects.html#merging-entities&quot; class=&quot;external-link&quot;&gt;http://www.doctrine-project.org/docs/orm/2.0/en/reference/working-with-objects.html#merging-entities&lt;/a&gt;&lt;br/&gt;
It appears to state that private variables are not serialized for child objects&lt;/p&gt;

&lt;p&gt;If this is the only reason entities can&apos;t have private properties, then this restriction is no longer valid, or possibly be reconsidered.&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;&amp;lt;?php

class A {
    &lt;span class=&quot;code-keyword&quot;&gt;private&lt;/span&gt; $a = &lt;span class=&quot;code-keyword&quot;&gt;null&lt;/span&gt;;

    &lt;span class=&quot;code-keyword&quot;&gt;public&lt;/span&gt; function setValue($value) {
        $&lt;span class=&quot;code-keyword&quot;&gt;this&lt;/span&gt;-&amp;gt;a = $value;
    }
}

class B &lt;span class=&quot;code-keyword&quot;&gt;extends&lt;/span&gt; A {}

$b = &lt;span class=&quot;code-keyword&quot;&gt;new&lt;/span&gt; B();
$b-&amp;gt;setValue(&lt;span class=&quot;code-quote&quot;&gt;&quot;B&quot;&lt;/span&gt;);
var_dump($b);

$c = unserialize(serialize($b));
var_dump($c);
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;The output suggests private variables are serialized, and are restored fine&lt;/p&gt;</description>
                <environment>PHP 5.3.3 (cli) (built: Nov 14 2010 16:54:26)</environment>
            <key id="12236">DDC-940</key>
            <summary>Entities can / can not have private properties</summary>
                <type id="6" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/documentation.png">Documentation</type>
                                <priority id="5" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/trivial.png">Trivial</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="tech13">Ray Rehbein</reporter>
                        <labels>
                    </labels>
                <created>Wed, 15 Dec 2010 13:53:15 +0000</created>
                <updated>Wed, 15 Dec 2010 13:53:15 +0000</updated>
                                    <version>2.0-RC2</version>
                                                <component>Documentation</component>
                        <due></due>
                    <votes>0</votes>
                        <watches>0</watches>
                                <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[DDC-823] Errors  in 2.0 Cookbook Documentation</title>
                <link>http://www.doctrine-project.org/jira/browse/DDC-823</link>
                <project id="10032" key="DDC">Doctrine 2 - ORM</project>
                        <description>&lt;p&gt;&lt;a href=&quot;http://www.doctrine-project.org/projects/orm/2.0/docs/cookbook/getting-started-xml-edition/en#getting-started-xml-edition&quot; class=&quot;external-link&quot;&gt;http://www.doctrine-project.org/projects/orm/2.0/docs/cookbook/getting-started-xml-edition/en#getting-started-xml-edition&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Paragraph 1:&lt;br/&gt;
The benefit of Doctrine for the programmer is the possibility &lt;del&gt;can&lt;/del&gt; &lt;ins&gt;to&lt;/ins&gt; focus &lt;del&gt;soley&lt;/del&gt; &lt;ins&gt;solely&lt;/ins&gt; on the business and worry about persistence only as a secondary task. This doesn&apos;t mean persistence is not important to Doctrine 2, however it is our belief that there are considerable benefits for object-oriented programming, if persistence and entities are kept perfectly &lt;del&gt;seperated&lt;/del&gt; &lt;ins&gt;separated&lt;/ins&gt;.&lt;/p&gt;

&lt;p&gt;Paragraph 2:&lt;br/&gt;
Entities are &lt;del&gt;leightweight&lt;/del&gt; &lt;ins&gt;lightweight&lt;/ins&gt; PHP Objects that don&apos;t need to extend any abstract base class or interface. An entity class must not be final or contain final methods. Additionally it must not implement __clone nor __wakeup or &lt;ins&gt;it should&lt;/ins&gt; do so safely.&lt;/p&gt;


&lt;p&gt;What would be the best way to note other errors?&lt;/p&gt;</description>
                <environment></environment>
            <key id="11972">DDC-823</key>
            <summary>Errors  in 2.0 Cookbook Documentation</summary>
                <type id="3" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/task.png">Task</type>
                                <priority id="5" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/trivial.png">Trivial</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="ralfas">Ralfas Jegorovas</reporter>
                        <labels>
                    </labels>
                <created>Fri, 1 Oct 2010 20:34:03 +0000</created>
                <updated>Mon, 11 Jul 2011 17:38:41 +0000</updated>
                                                                    <component>Documentation</component>
                        <due></due>
                    <votes>0</votes>
                        <watches>2</watches>
                        <comments>
                    <comment id="14521" author="beberlei" created="Mon, 4 Oct 2010 05:20:50 +0000"  >&lt;p&gt;The best way for us would be if you fork the docs on github, change the stuff and commit it. Then issue a pull request. It sounds complicated, but should be minimal overhead of ~5 minutesn on your end, but then we can merge it with a mouse-click, so we dont need to duplicate the whole correction effort on our end.&lt;/p&gt;</comment>
                    <comment id="15192" author="jclermont" created="Thu, 27 Jan 2011 08:11:40 +0000"  >&lt;p&gt;I have fixed the typos from this ticket that were still present in the docs and issued a pull request on Github.&lt;/p&gt;</comment>
                    <comment id="16147" author="mridgway" created="Mon, 11 Jul 2011 17:38:41 +0000"  >&lt;p&gt;This issue should be closed: &lt;a href=&quot;https://github.com/doctrine/orm-documentation/pull/17&quot; class=&quot;external-link&quot;&gt;https://github.com/doctrine/orm-documentation/pull/17&lt;/a&gt;&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[DDC-605] Include Fowards Compatible Support for Scalar Type Hints Patch in ProxyFactory</title>
                <link>http://www.doctrine-project.org/jira/browse/DDC-605</link>
                <project id="10032" key="DDC">Doctrine 2 - ORM</project>
                        <description>&lt;p&gt;ProxyFactory needs foward compatible support for the scalar type hint patch:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://ilia.ws/archives/217-Scalar-Type-Hints-are-Here!.html&quot; class=&quot;external-link&quot;&gt;http://ilia.ws/archives/217-Scalar-Type-Hints-are-Here!.html&lt;/a&gt;&lt;/p&gt;</description>
                <environment></environment>
            <key id="11399">DDC-605</key>
            <summary>Include Fowards Compatible Support for Scalar Type Hints Patch in ProxyFactory</summary>
                <type id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/improvement.png">Improvement</type>
                                <priority id="5" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/trivial.png">Trivial</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="beberlei">Benjamin Eberlei</reporter>
                        <labels>
                    </labels>
                <created>Fri, 21 May 2010 04:14:07 +0000</created>
                <updated>Sun, 8 Aug 2010 09:20:23 +0000</updated>
                                                                    <component>ORM</component>
                        <due></due>
                    <votes>0</votes>
                        <watches>0</watches>
                        <comments>
                    <comment id="13051" author="romanb" created="Sun, 23 May 2010 10:13:53 +0000"  >&lt;p&gt;I would be surprised if that would not be reverted soon though &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>
                </comments>
                    <attachments>
                </attachments>
            <subtasks>
        </subtasks>
        </item>

<item>
            <title>[DDC-567] Foreign Key to Unique Field Update Failure</title>
                <link>http://www.doctrine-project.org/jira/browse/DDC-567</link>
                <project id="10032" key="DDC">Doctrine 2 - ORM</project>
                        <description>&lt;p&gt;I am getting an error: &apos;Notice: Undefined index: sysname in ./libraries/Doctrine/ORM/Persisters/BasicEntityPersister.php on line 434&apos; when I try to flush a change to a property that references a unique field on another object.&lt;/p&gt;

&lt;p&gt;From poking around in the _prepareUpdateData function, it seems that it only allows you to use identifier fields: &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;$newValId = $uow-&amp;gt;getEntityIdentifier($newVal);

..

$result[$owningTable][$sourceColumn] = $newValId[$targetClass-&amp;gt;fieldNames[$targetColumn]];
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;I&apos;ll see if I can get a test case for this set up.&lt;/p&gt;</description>
                <environment></environment>
            <key id="11310">DDC-567</key>
            <summary>Foreign Key to Unique Field Update Failure</summary>
                <type id="2" iconUrl="http://www.doctrine-project.org/jira/images/icons/issuetypes/newfeature.png">New Feature</type>
                                <priority id="5" iconUrl="http://www.doctrine-project.org/jira/images/icons/priorities/trivial.png">Trivial</priority>
                    <status id="4" iconUrl="http://www.doctrine-project.org/jira/images/icons/statuses/reopened.png">Reopened</status>
                    <resolution id="-1">Unresolved</resolution>
                    <security id="10000">All</security>
                        <assignee username="romanb">Roman S. Borschel</assignee>
                                <reporter username="mridgway">Michael Ridgway</reporter>
                        <labels>
                    </labels>
                <created>Mon, 3 May 2010 10:07:03 +0000</created>
                <updated>Mon, 8 Oct 2012 14:56:08 +0000</updated>
                                    <version>2.0-BETA2</version>
                                                <component>ORM</component>
                        <due></due>
                    <votes>2</votes>
                        <watches>2</watches>
                        <comments>
                    <comment id="12821" author="romanb" created="Mon, 3 May 2010 10:25:32 +0000"  >&lt;p&gt;Hi. That is right. Foreign keys (join columns) must point to primary keys, not arbitrary other columns, whether they&apos;re unique or not, Doctrine does not know.&lt;/p&gt;

&lt;p&gt;In other words, joinColumn must always refer to an identifier/pk. I&apos;m not sure but I think anything else would be a pretty strange relational model, too, but there may be usecases we have not yet encountered.&lt;/p&gt;

&lt;p&gt;I&apos;m afraid this will not be possible and would be very hard to implement. Of course if somebody has a patch we happily accept it (after reviewing).&lt;/p&gt;

&lt;p&gt;Leaving this open in the case somebody wants to work on it.&lt;/p&gt;</comment>
                    <comment id="12822" author="mridgway" created="Mon, 3 May 2010 10:25:48 +0000"  >&lt;p&gt;A minimal test case.  Removing the first flush produces the same error, so this seems to be a bug on inserts as well.&lt;/p&gt;</comment>
                    <comment id="12823" author="romanb" created="Mon, 3 May 2010 10:27:10 +0000"  >&lt;p&gt;Its not really a bug but rather a new feature &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; This was not intended to work so far.&lt;/p&gt;</comment>
                    <comment id="12824" author="mridgway" created="Mon, 3 May 2010 10:39:51 +0000"  >&lt;p&gt;Ah, ok.  Maybe it didn&apos;t work before. I don&apos;t know where I got the idea that it did.&lt;/p&gt;

&lt;p&gt;Thanks.&lt;/p&gt;</comment>
                    <comment id="12825" author="mridgway" created="Mon, 3 May 2010 10:40:55 +0000"  >&lt;p&gt;Oops, closed it before I noticed you said you wanted to leave it open.&lt;/p&gt;</comment>
                    <comment id="12826" author="romanb" created="Mon, 3 May 2010 10:50:32 +0000"  >&lt;p&gt;Thanks for the testcase though, it is useful. In your concrete example, is it not an option to make the sysname the @Id ?&lt;/p&gt;</comment>
                    <comment id="12827" author="mridgway" created="Mon, 3 May 2010 10:59:37 +0000"  >&lt;p&gt;Yes.  That is definitely the way it should be done in this case.  I can&apos;t really think of a case to have a reference to a unique key while still having an Id on it, except when you&apos;re working with an existing, poorly designed database (which is our case).&lt;/p&gt;

&lt;p&gt;The reason I assumed this was possible is that the references actually work for lazy loading, but as soon as you start changing the references it throws this error.&lt;/p&gt;</comment>
                    <comment id="12951" author="romanb" created="Fri, 14 May 2010 08:39:11 +0000"  >&lt;p&gt;Lowering priority.&lt;/p&gt;</comment>
                    <comment id="18809" author="dready" created="Mon, 8 Oct 2012 14:56:08 +0000"  >&lt;p&gt;although we would also need this i would suggest adding an error message if the associated column is not found in $newValId. (class BasicEntityPersister.php _prepareUpdateData)&lt;/p&gt;

&lt;p&gt;otherwise the field is populated with null leaving the developer debugging an hour :-/&lt;/p&gt;

&lt;p&gt;thx&lt;/p&gt;</comment>
                </comments>
                    <attachments>
                    <attachment id="10589" name="DDC567Test.php" size="1676" author="mridgway" created="Mon, 3 May 2010 10:25:48 +0000" />
                </attachments>
            <subtasks>
        </subtasks>
        </item>
</channel>
</rss>