DDC-3: Support for CASE expressions in DQL #2

Closed
opened 2026-01-22 12:23:53 +01:00 by admin · 8 comments
Owner

Originally created by @doctrinebot on GitHub (Sep 9, 2009).

Originally assigned to: @guilhermeblanco on GitHub.

Jira issue originally created by user romanb:

CASE expressions should be supported in DQL similarly to the definition found in 4.6.17.3 of the JPA 2.0 specification.

Steps: 1) Adjust the BNF
2) Adjust the Parser according to the changed BNF
3) Adjust the SqlWalker? to produce the correct SQL

Originally created by @doctrinebot on GitHub (Sep 9, 2009). Originally assigned to: @guilhermeblanco on GitHub. Jira issue originally created by user romanb: CASE expressions should be supported in DQL similarly to the definition found in 4.6.17.3 of the JPA 2.0 specification. Steps: 1) Adjust the BNF 2) Adjust the Parser according to the changed BNF 3) Adjust the SqlWalker? to produce the correct SQL
admin added the Improvement label 2026-01-22 12:23:53 +01:00
admin closed this issue 2026-01-22 12:23:53 +01:00
Author
Owner

@doctrinebot commented on GitHub (Sep 9, 2009):

@doctrinebot commented on GitHub (Sep 9, 2009): - is required for [DDC-1071: CASE expressions do not work as documented in EBNF](http://www.doctrine-project.org/jira/browse/DDC-1071)
Author
Owner

@doctrinebot commented on GitHub (Apr 16, 2010):

Comment created by romanb:

test

@doctrinebot commented on GitHub (Apr 16, 2010): Comment created by romanb: test
Author
Owner

@doctrinebot commented on GitHub (Jun 21, 2010):

Comment created by romanb:

The BNF and Parser has already been largely prepared for that.

@doctrinebot commented on GitHub (Jun 21, 2010): Comment created by romanb: The BNF and Parser has already been largely prepared for that.
Author
Owner

@doctrinebot commented on GitHub (Aug 12, 2010):

Comment created by @guilhermeblanco:

Added all Lexer keywords to it. It was breaking some use cases.

Parsing can be easily done. How far is Walker generation far from an acceptable state?

@doctrinebot commented on GitHub (Aug 12, 2010): Comment created by @guilhermeblanco: Added all Lexer keywords to it. It was breaking some use cases. Parsing can be easily done. How far is Walker generation far from an acceptable state?
Author
Owner

@doctrinebot commented on GitHub (Aug 12, 2010):

Comment created by @beberlei:

its a 2.1 change, so we can delay that for now or not? adding the keyword is a good idea though, maybe we should think about some other keywords that we potentially need in the future?

@doctrinebot commented on GitHub (Aug 12, 2010): Comment created by @beberlei: its a 2.1 change, so we can delay that for now or not? adding the keyword is a good idea though, maybe we should think about some other keywords that we potentially need in the future?
Author
Owner

@doctrinebot commented on GitHub (Dec 24, 2010):

Comment created by romanb:

I will try to finish this for 2.1.

@doctrinebot commented on GitHub (Dec 24, 2010): Comment created by romanb: I will try to finish this for 2.1.
Author
Owner

@doctrinebot commented on GitHub (Aug 8, 2011):

Comment created by @guilhermeblanco:

In this commit: 816ce41f63
And documented in this commit: 189c729f15

This support was FINALLY included. =)

@doctrinebot commented on GitHub (Aug 8, 2011): Comment created by @guilhermeblanco: In this commit: https://github.com/doctrine/doctrine2/commit/816ce41f638d28934c79a12ef27f954124b2639e And documented in this commit: https://github.com/doctrine/orm-documentation/commit/189c729f15d2fafecf92662cad9553c2ec3dccd7 This support was FINALLY included. =)
Author
Owner

@doctrinebot commented on GitHub (Aug 8, 2011):

Issue was closed with resolution "Fixed"

@doctrinebot commented on GitHub (Aug 8, 2011): Issue was closed with resolution "Fixed"
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: doctrine/archived-orm#2