http://www.doctrine-project.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+DCOM+AND+status+%3D+Reopened+ORDER+BY+priority+DESC An XML representation of a search request en-us 5.2.7 850 21-02-2013 http://www.doctrine-project.org/jira/browse/DCOM-67 Doctrine Common DCOM-67

Introduce immutable DateTime with __toString()

Improvement Major Reopened Unresolved Benjamin Eberlei Benjamin Eberlei Sat, 27 Aug 2011 12:53:42 +0000 Sun, 29 Jan 2012 16:30:23 +0000 2.3 0 1 <p>Implemented</p> <p>Though it is implemented once on <a href="https://github.com/doctrine/common/commit/7140ad3ba0ba2a94238976dd7f310ff92b478c96" class="external-link">https://github.com/doctrine/common/commit/7140ad3ba0ba2a94238976dd7f310ff92b478c96</a>,<br/> the class is removed on <a href="https://github.com/doctrine/common/commit/f845c1e267abf9069422eba8addfa976bc8d8685" class="external-link">https://github.com/doctrine/common/commit/f845c1e267abf9069422eba8addfa976bc8d8685</a>.</p> <p>I think this issue must be reopened.</p> <p>Code was removed due to implementation problems.</p> http://www.doctrine-project.org/jira/browse/DCOM-189 Doctrine Common <p>The Doctrine ProxyGenerator generates for a proxy a constructor. The documentation of Doctrine states that the constructor is never called. For a project, I created a group of entities with a interfaced constructor in order to enforce a common interface. This results in a incompatible proxy and so a fatal error.</p> DCOM-189

Doctrine Proxies may conflict with interfaced constructors

Documentation Major Reopened Unresolved Marco Pivetta Harmen M Fri, 3 May 2013 09:05:15 +0000 Fri, 3 May 2013 13:05:24 +0000 0 3 <p>Cannot fix this - the constructor is required to override instantiation logic</p> <p>Edit: added the correct description. I accidentially submitted the form before editing the description.</p> <p><a href="http://www.doctrine-project.org/jira/secure/ViewProfile.jspa?name=harmenm" class="user-hover" rel="harmenm">Harmen M</a> why do you have a constructor in an interface? That's a very bad practice, and it makes things quite hard to handle.</p> <p>I can think of a workaround, but I first want to be sure there's a real advantage in changing the current implementation to use </p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">unserialize()</pre> </div></div> <p> just to handle this specific use case.</p> <p>Adding __construct to an interface is an anti pattern and shouldn't be done.</p> <p>Ok, then I change my implementation.</p> <p>But, maybe it is an idea to update the documentation of the ORM and state that constructor interfacing is not possible?<br/> <a href="http://docs.doctrine-project.org/projects/doctrine-orm/en/latest/reference/architecture.html" class="external-link">http://docs.doctrine-project.org/projects/doctrine-orm/en/latest/reference/architecture.html</a></p>