Skip to content


DDC-866: The EBNF definition for DQL needs to be updated #5388

doctrinebot opened this Issue · 4 comments

2 participants


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 ( 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)


Comment created by @beberlei:

This feature was removed for technical reasons. I updated the docs accordingly.


Comment created by dalvarez:

The online documentation ( is still listing the factually wrong EBNF, specifically:

/** "u.Group" */
SingleValuedAssociationPathExpression ::= IdentificationVariable "." {SingleValuedAssociationField "."}

/** "u.Group.Permissions" */
CollectionValuedPathExpression ::= IdentificationVariable "." {SingleValuedAssociationField "."}

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.


Comment created by @beberlei:

we dont render the docs all the time, it takes some time.


Issue was closed with resolution "Fixed"

@beberlei beberlei was assigned by doctrinebot
@doctrinebot doctrinebot added this to the 2.0-RC1 milestone
@doctrinebot doctrinebot closed this
@doctrinebot doctrinebot added the Bug label
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.