mirror of
https://github.com/doctrine/orm.git
synced 2026-03-24 06:52:09 +01:00
DDC-866: The EBNF definition for DQL needs to be updated #1073
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @doctrinebot on GitHub (Nov 8, 2010).
Originally assigned to: @beberlei on GitHub.
Jira issue originally created by user dalvarez:
This is a summary replacing bugs 857, 863 and 864, which I hereby close.
In summary, deep path expressions like
SingleValuedAssociationPathExpression ::= IdentificationVariable "." {SingleValuedAssociationField "."}* SingleValuedAssociationField
are not suppored by the current implementation, but are documented to work in the EBNF definition for DQL (http://www.doctrine-project.org/projects/orm/2.0/docs/reference/dql-doctrine-query-language/en#dql-doctrine-query-language). The EBNF definitions need to be fixed, because currently they are factually wrong and thus misleading.
(Obviously, actually having the feature would be preferrable IMO)
@doctrinebot commented on GitHub (Nov 9, 2010):
Comment created by @beberlei:
This feature was removed for technical reasons. I updated the docs accordingly.
@doctrinebot commented on GitHub (Nov 15, 2010):
Comment created by dalvarez:
The online documentation (http://www.doctrine-project.org/projects/orm/2.0/docs/reference/dql-doctrine-query-language/en#dql-doctrine-query-language) is still listing the factually wrong EBNF, specifically:
/** "u.Group" */
SingleValuedAssociationPathExpression ::= IdentificationVariable "." {SingleValuedAssociationField "."} SingleValuedAssociationField
/** "u.Group.Permissions" */
CollectionValuedPathExpression ::= IdentificationVariable "." {SingleValuedAssociationField "."} CollectionValuedAssociationField
I cleared my local web cache, of course, before viewing, but to no effect. It's possibly that the fix was done internally in a SCM Tool, but was not published. As of now, the documentation fix did not become effective for the docs that are now visible online. I reopen this as a reminder.
@doctrinebot commented on GitHub (Nov 15, 2010):
Comment created by @beberlei:
we dont render the docs all the time, it takes some time.
@doctrinebot commented on GitHub (Nov 15, 2010):
Issue was closed with resolution "Fixed"