http://www.doctrine-project.org/jira This file is an XML representation of an issue en-us 5.2.7 850 21-02-2013 http://www.doctrine-project.org/jira/browse/DDC-1900 Doctrine 2 - ORM <p>Doctrine doesn't allow to to create own SQL function for DQL if that function is already defined as "built-in". An example could be custom <tt>DATE_ADD</tt> implementation.<br/> Method <tt>FunctionDeclaration()</tt> in <em>Doctrine\ORM\Query\Parser</em> gives higher priority to built-in SQL functions, even if they are not<br/> usable for a specific situation, and registering of own datetime function doesn't help. This issue makes it impossible to use some advanced Doctrine extensions, <br/> for example <a href="https://github.com/beberlei/DoctrineExtensions" class="external-link">https://github.com/beberlei/DoctrineExtensions</a> that provide fuller implementations.<br/> Considering the fact that someone may want to use ready components provided by the community, and being new to Doctrine can't figure out the way to hack<br/> or workaround this, the issue is a major one.</p> Any DDC-1900

Impossibility to override built-in SQL functions

Bug Major Closed Fixed All Benjamin Eberlei Alex Oroshchuk Sat, 30 Jun 2012 20:00:28 +0000 Thu, 5 Jul 2012 19:57:12 +0000 Thu, 5 Jul 2012 19:57:12 +0000 Git Master 2.3 DQL 0 0 <p>Just name the method differently.</p> <p>To rename the method one has to <b>KNOW</b> that he has to rename it, i.e. to know about this issue. <br/> One has to <b>SPEND hours</b> (like me) on understanding that there are built-in implementations and other extensions that are meant<br/> to provide necessary features just don't work. IMHO it's just too cruel to leave it as is.</p> <p>As to the renaming: is it ok to go and edit source code (change class name at least) provided by someone else and then merge all the sources when new releases appear?<br/> Is that the only way flexible Doctrine provides? Also, I want DQL to be as close as possible to real SQL. I don't want to see weird stuff like MY_DATE_ADD or BETTER_DATE_ADD, or whatever it will be.<br/> Syntax matters, we are all writers, code writers...</p> <p>I re-open the issue in order to attract more attention, but you are free to decide how to treat it. Hope you'll find the best solution. A short line in documentation could notify about current limitations and save hours for people<br/> who want to be productive with Doctrine.</p> <p>Printing statements in bold isnt helpful. This is open-source.</p> <p>However, you are right that this could be more user-friendly. Its now throwing an exception when an internal function is attempted to be overwritten.</p>