Failed parse the condition in ORDER BY #6187

New Issue

Closed

opened 2026-01-22 15:28:29 +01:00 by admin · 14 comments

admin commented 2026-01-22 15:28:29 +01:00

Owner

Copy Link

Originally created by @peter-gribanov on GitHub (Feb 26, 2019).

Originally assigned to: @Ocramius on GitHub.

Bug Report

I want calculate the number of occurrences of a char in string. But DQL is failed parse to SQL.

Q	A
BC Break	no
Version	2.6.3

Summary

$ composer show --latest 'doctrine/*'
doctrine/annotations                v1.6.0  v1.6.0  Docblock Annotations Parser
doctrine/cache                      v1.8.0  v1.8.0  Caching library offering an object-oriented API for many cache backends
doctrine/collections                v1.5.0  v1.5.0  Collections Abstraction library
doctrine/common                     v2.10.0 v2.10.0 PHP Doctrine Common project is a library that provides additional functionality that other Doctrine p...
doctrine/dbal                       v2.9.0  v2.9.2  Powerful PHP database abstraction layer (DBAL) with many features for database schema introspection a...
doctrine/doctrine-bundle            1.10.0  1.10.2  Symfony DoctrineBundle
doctrine/doctrine-cache-bundle      1.3.5   1.3.5   Symfony Bundle for Doctrine Cache
doctrine/doctrine-migrations-bundle v1.3.2  v2.0.0  Symfony DoctrineMigrationsBundle
doctrine/event-manager              v1.0.0  v1.0.0  Doctrine Event Manager component
doctrine/inflector                  v1.3.0  v1.3.0  Common String Manipulations with regard to casing and singular/plural rules.
doctrine/instantiator               1.1.0   1.1.0   A small, lightweight utility to instantiate objects in PHP without invoking their constructors
doctrine/lexer                      v1.0.1  v1.0.1  Base library for a lexer that can be used in Top-Down, Recursive Descent Parsers.
doctrine/migrations                 v1.8.1  v2.0.0  Database Schema migrations using Doctrine DBAL
doctrine/orm                        v2.6.3  v2.6.3  Object-Relational-Mapper for PHP
doctrine/persistence                v1.1.0  v1.1.0  The Doctrine Persistence project is a set of shared interfaces and functionality that the different D...
doctrine/reflection                 v1.0.0  v1.0.0  Doctrine Reflection component

How to reproduce

DQL

SELECT (LENGTH(e.path) - LENGTH(REPLACE(e.path, :path_separator, :empty_string))) s FROM Category e

Result SQL

SELECT (LENGTH(e.path) - LENGTH(REPLACE(e.path, ".", ""))) AS s FROM shop__category e

DQL

SELECT LENGTH(e.path) - LENGTH(REPLACE(e.path, :path_separator, :empty_string)) FROM Category e

Result SQL

SELECT LENGTH(e.path) - LENGTH(REPLACE(e.path, ".", "")) FROM shop__category e

DQL

SELECT e FROM Category e ORDER BY LENGTH(e.path) - LENGTH(REPLACE(e.path, :path_separator, :empty_string)) ASC

Current behavior

[Syntax Error] line 0, col 82: Error: Expected end of string, got '-'

Expected SQL

SELECT e.* FROM shop__category e ORDER BY LENGTH(e.path) - LENGTH(REPLACE(e.path, ".", "")) ASC

DQL

SELECT e FROM Category e ORDER BY (LENGTH(e.path) - LENGTH(REPLACE(e.path, :path_separator, :empty_string))) ASC

Current behavior

[Syntax Error] line 0, col 99: Error: Expected Doctrine\ORM\Query\Lexer::T_IDENTIFIER, got '('

Expected SQL

SELECT e.* FROM shop__category e ORDER BY (LENGTH(e.path) - LENGTH(REPLACE(e.path, ".", ""))) ASC

Originally created by @peter-gribanov on GitHub (Feb 26, 2019). Originally assigned to: @Ocramius on GitHub. ### Bug Report <!-- Fill in the relevant information below to help triage your issue. --> I want [calculate the number of occurrences of a char in string](http://bookofzeus.com/articles/mysql/count-the-number-of-occurrences-of-a-char-in-mysql/). But DQL is failed parse to SQL. | Q | A |------------ | ------ | BC Break | no | Version | 2.6.3 ### Summary <!-- Provide a summary describing the problem you are experiencing. --> ``` $ composer show --latest 'doctrine/*' doctrine/annotations v1.6.0 v1.6.0 Docblock Annotations Parser doctrine/cache v1.8.0 v1.8.0 Caching library offering an object-oriented API for many cache backends doctrine/collections v1.5.0 v1.5.0 Collections Abstraction library doctrine/common v2.10.0 v2.10.0 PHP Doctrine Common project is a library that provides additional functionality that other Doctrine p... doctrine/dbal v2.9.0 v2.9.2 Powerful PHP database abstraction layer (DBAL) with many features for database schema introspection a... doctrine/doctrine-bundle 1.10.0 1.10.2 Symfony DoctrineBundle doctrine/doctrine-cache-bundle 1.3.5 1.3.5 Symfony Bundle for Doctrine Cache doctrine/doctrine-migrations-bundle v1.3.2 v2.0.0 Symfony DoctrineMigrationsBundle doctrine/event-manager v1.0.0 v1.0.0 Doctrine Event Manager component doctrine/inflector v1.3.0 v1.3.0 Common String Manipulations with regard to casing and singular/plural rules. doctrine/instantiator 1.1.0 1.1.0 A small, lightweight utility to instantiate objects in PHP without invoking their constructors doctrine/lexer v1.0.1 v1.0.1 Base library for a lexer that can be used in Top-Down, Recursive Descent Parsers. doctrine/migrations v1.8.1 v2.0.0 Database Schema migrations using Doctrine DBAL doctrine/orm v2.6.3 v2.6.3 Object-Relational-Mapper for PHP doctrine/persistence v1.1.0 v1.1.0 The Doctrine Persistence project is a set of shared interfaces and functionality that the different D... doctrine/reflection v1.0.0 v1.0.0 Doctrine Reflection component ``` ### How to reproduce **DQL** ```sql SELECT (LENGTH(e.path) - LENGTH(REPLACE(e.path, :path_separator, :empty_string))) s FROM Category e ``` **Result SQL** ```sql SELECT (LENGTH(e.path) - LENGTH(REPLACE(e.path, ".", ""))) AS s FROM shop__category e ``` **DQL** ```sql SELECT LENGTH(e.path) - LENGTH(REPLACE(e.path, :path_separator, :empty_string)) FROM Category e ``` **Result SQL** ```sql SELECT LENGTH(e.path) - LENGTH(REPLACE(e.path, ".", "")) FROM shop__category e ``` **DQL** ```sql SELECT e FROM Category e ORDER BY LENGTH(e.path) - LENGTH(REPLACE(e.path, :path_separator, :empty_string)) ASC ``` **Current behavior** ``` [Syntax Error] line 0, col 82: Error: Expected end of string, got '-' ``` **Expected SQL** ```sql SELECT e.* FROM shop__category e ORDER BY LENGTH(e.path) - LENGTH(REPLACE(e.path, ".", "")) ASC ``` **DQL** ```sql SELECT e FROM Category e ORDER BY (LENGTH(e.path) - LENGTH(REPLACE(e.path, :path_separator, :empty_string))) ASC ``` **Current behavior** ``` [Syntax Error] line 0, col 99: Error: Expected Doctrine\ORM\Query\Lexer::T_IDENTIFIER, got '(' ``` **Expected SQL** ```sql SELECT e.* FROM shop__category e ORDER BY (LENGTH(e.path) - LENGTH(REPLACE(e.path, ".", ""))) ASC ```

admin added the Won't FixQuestion labels 2026-01-22 15:28:29 +01:00

admin closed this issue 2026-01-22 15:28:29 +01:00

admin commented 2026-01-22 15:28:29 +01:00

Author

Owner

Copy Link

@peter-gribanov commented on GitHub (Feb 26, 2019):

I can solve the problem using a hidden field, but this is not a solution.

SELECT e, LENGTH(e.path) - LENGTH(REPLACE(e.path, :path_separator, :empty_string)) HIDDEN path_level FROM Category e ORDER BY path_level ASC

@peter-gribanov commented on GitHub (Feb 26, 2019): I can solve the problem using a hidden field, but this is not a solution. ```sql SELECT e, LENGTH(e.path) - LENGTH(REPLACE(e.path, :path_separator, :empty_string)) HIDDEN path_level FROM Category e ORDER BY path_level ASC ```

admin commented 2026-01-22 15:28:30 +01:00

Author

Owner

Copy Link

@Ocramius commented on GitHub (Feb 26, 2019):

Duplicate of #7628

@Ocramius commented on GitHub (Feb 26, 2019): Duplicate of #7628

admin commented 2026-01-22 15:28:31 +01:00

Author

Owner

Copy Link

@peter-gribanov commented on GitHub (Feb 26, 2019):

This is not a question. This is a bug report.
As i said before, this is not a solution. This is a crutch.
@Ocramius please explain to me what prevents the use of expressions in sorting?

@peter-gribanov commented on GitHub (Feb 26, 2019): This is not a question. This is a bug report. As i [said before](https://github.com/doctrine/orm/issues/7626#issuecomment-467370371), [this](https://github.com/doctrine/orm/issues/7628#issuecomment-467531153) is not a solution. This is a crutch. @Ocramius please explain to me what prevents the use of expressions in sorting?

admin commented 2026-01-22 15:28:31 +01:00

Author

Owner

Copy Link

@secit-pl commented on GitHub (Feb 27, 2019):

I'm also interested the explanation of the question asked by @peter-gribanov

@secit-pl commented on GitHub (Feb 27, 2019): I'm also interested the explanation of the question asked by @peter-gribanov

admin commented 2026-01-22 15:28:31 +01:00

Author

Owner

Copy Link

@peter-gribanov commented on GitHub (May 14, 2019):

@Ocramius will there be any answer to the question related to this bug?

@peter-gribanov commented on GitHub (May 14, 2019): @Ocramius will there be any answer to the question related to this bug?

admin commented 2026-01-22 15:28:31 +01:00

Author

Owner

Copy Link

@Ocramius commented on GitHub (May 14, 2019):

I think I referenced the wrong issue while closing, hence the confusion, sorry.

Lemme re-open here.

@Ocramius commented on GitHub (May 14, 2019): I think I referenced the wrong issue while closing, hence the confusion, sorry. Lemme re-open here.

admin commented 2026-01-22 15:28:31 +01:00

Author

Owner

Copy Link

@Ocramius commented on GitHub (May 14, 2019):

Ah, no, the closing is correct: the other issue explains that expressions in ORDER BY are indeed to be used by putting them in the SELECT clause and then re-using them (in SQL only) via the HIDDEN clause and an alias.

@Ocramius commented on GitHub (May 14, 2019): Ah, no, the closing is correct: the other issue explains that expressions in `ORDER BY` are indeed to be used by putting them in the `SELECT` clause and then re-using them (in SQL only) via the `HIDDEN` clause and an alias.

admin commented 2026-01-22 15:28:32 +01:00

Author

Owner

Copy Link

@peter-gribanov commented on GitHub (May 15, 2019):

@Ocramius thank. I know this and wrote about it in the description of the problem. Me and @secit-pl are interested in why such a non-standard implementation is chosen?
The standard SQL allows the use of expressions in sorting, but the Doctrine does not allow it. Why?

@peter-gribanov commented on GitHub (May 15, 2019): @Ocramius thank. I know this and wrote about it in the description of the problem. Me and @secit-pl are interested in why such a non-standard implementation is chosen? The standard SQL allows the use of expressions in sorting, but the Doctrine does not allow it. Why?

admin commented 2026-01-22 15:28:32 +01:00

Author

Owner

Copy Link

@Ocramius commented on GitHub (May 27, 2019):

Hmm, indeed, looked at support in downstream DBs, and they seem to be all supporting expressions in ORDER BY (unless I'm mistaken - maybe @morozov knows more here).

The DQL definitions affecting this (as of this writing) are:

OrderByClause       ::= "ORDER" "BY" OrderByItem {"," OrderByItem}*
OrderByItem ::= (SimpleArithmeticExpression | SingleValuedPathExpression | ScalarExpression | ResultVariable | FunctionDeclaration) ["ASC" | "DESC"]
SimpleArithmeticExpression ::= ArithmeticTerm {("+" | "-") ArithmeticTerm}*
ArithmeticTerm             ::= ArithmeticFactor {("*" | "/") ArithmeticFactor}*
ArithmeticFactor           ::= [("+" | "-")] ArithmeticPrimary
ArithmeticPrimary          ::= SingleValuedPathExpression | Literal | "(" SimpleArithmeticExpression ")"
                               | FunctionsReturningNumerics | AggregateExpression | FunctionsReturningStrings
                               | FunctionsReturningDatetime | IdentificationVariable | ResultVariable
                               | InputParameter | CaseExpression

Now, in theory this would parse this pretty much OK:

ORDER BY LENGTH(e.path) - LENGTH(REPLACE(e.path, :path_separator, :empty_string)) ASC

Since that is a:

OrderByClause(
  SimpleArithmeticExpression(
    ArithmeticTerm(ArithmeticPrimary(FunctionsReturningNumerics("LENGTH", ...)),
    "-",
    ArithmeticTerm(ArithmeticPrimary(FunctionsReturningNumerics("LENGTH", ...)))
  )
),
"ASC"

I guess I turned a long standing parser bug into an intentional limitation, sorry!

@Ocramius commented on GitHub (May 27, 2019): Hmm, indeed, looked at support in downstream DBs, and they seem to be all supporting expressions in `ORDER BY` (unless I'm mistaken - maybe @morozov knows more here). The DQL definitions affecting this (as of this writing) are: ``` OrderByClause ::= "ORDER" "BY" OrderByItem {"," OrderByItem}* OrderByItem ::= (SimpleArithmeticExpression | SingleValuedPathExpression | ScalarExpression | ResultVariable | FunctionDeclaration) ["ASC" | "DESC"] SimpleArithmeticExpression ::= ArithmeticTerm {("+" | "-") ArithmeticTerm}* ArithmeticTerm ::= ArithmeticFactor {("*" | "/") ArithmeticFactor}* ArithmeticFactor ::= [("+" | "-")] ArithmeticPrimary ArithmeticPrimary ::= SingleValuedPathExpression | Literal | "(" SimpleArithmeticExpression ")" | FunctionsReturningNumerics | AggregateExpression | FunctionsReturningStrings | FunctionsReturningDatetime | IdentificationVariable | ResultVariable | InputParameter | CaseExpression ``` Now, in theory this would parse this pretty much OK: ``` ORDER BY LENGTH(e.path) - LENGTH(REPLACE(e.path, :path_separator, :empty_string)) ASC ``` Since that is a: ``` OrderByClause( SimpleArithmeticExpression( ArithmeticTerm(ArithmeticPrimary(FunctionsReturningNumerics("LENGTH", ...)), "-", ArithmeticTerm(ArithmeticPrimary(FunctionsReturningNumerics("LENGTH", ...))) ) ), "ASC" ``` I guess I turned a long standing parser bug into an intentional limitation, sorry!

admin commented 2026-01-22 15:28:32 +01:00

Author

Owner

Copy Link

@morozov commented on GitHub (May 28, 2019):

As long as the two values can be compared and are deterministic, there shouldn’t be any problems.

@morozov commented on GitHub (May 28, 2019): As long as the two values can be compared and are deterministic, there shouldn’t be any problems.

admin commented 2026-01-22 15:28:33 +01:00

Author

Owner

Copy Link

@lcobucci commented on GitHub (Oct 2, 2019):

Using a HIDDEN field is mandatory according to our design. It's fine to discuss modifying this but it falls into Improvement and not Bug and should be implemented for v2.7 or v3.0 only

@lcobucci commented on GitHub (Oct 2, 2019): Using a `HIDDEN` field is mandatory according to our design. It's fine to discuss modifying this but it falls into `Improvement` and not `Bug` and should be implemented for `v2.7` or `v3.0` only

admin commented 2026-01-22 15:28:33 +01:00

Author

Owner

Copy Link

@Ocramius commented on GitHub (Oct 2, 2019):

Closing here: I think @lcobucci's approach is simple and already solves the issue without introducing further questions about supported syntax.

@Ocramius commented on GitHub (Oct 2, 2019): Closing here: I think @lcobucci's approach is simple and already solves the issue without introducing further questions about supported syntax.

admin commented 2026-01-22 15:28:33 +01:00

Author

Owner

Copy Link

@ipernet commented on GitHub (Sep 19, 2020):

Ah, no, the closing is correct: the other issue explains that expressions in ORDER BY are indeed to be used by putting them in the SELECT clause and then re-using them (in SQL only) via the HIDDEN clause and an alias.

If I'm not mistaken, this cannot be a workaround when using window functions with Postgres or MySQL8.

This works with such as parser:

SELECT ROW_NUMBER() OVER(ORDER BY alias.field ASC) FROM Entity alias

But this does not due to the reported issue:

SELECT ROW_NUMBER() OVER(ORDER BY SOME_COMPLEX_EXPRESSION() ASC) FROM Entity alias

And the suggested workaround is not applicable then:

SELECT 
SOME_COMPLEX_EXPRESSION() as HIDDEN foo,
ROW_NUMBER() OVER(ORDER BY foo ASC)
FROM Entity alias

@ipernet commented on GitHub (Sep 19, 2020): > Ah, no, the closing is correct: the other issue explains that expressions in `ORDER BY` are indeed to be used by putting them in the `SELECT` clause and then re-using them (in SQL only) via the `HIDDEN` clause and an alias. If I'm not mistaken, this cannot be a workaround when using window functions with Postgres or MySQL8. This works with such as [parser](https://gist.github.com/B0ulzy/0603c08074d4e7bd3f6c641631a2d730): ```sql SELECT ROW_NUMBER() OVER(ORDER BY alias.field ASC) FROM Entity alias ``` But this does not due to the reported issue: ```sql SELECT ROW_NUMBER() OVER(ORDER BY SOME_COMPLEX_EXPRESSION() ASC) FROM Entity alias ``` And the suggested workaround is not applicable then: ```sql SELECT SOME_COMPLEX_EXPRESSION() as HIDDEN foo, ROW_NUMBER() OVER(ORDER BY foo ASC) FROM Entity alias ```

admin commented 2026-01-22 15:28:33 +01:00

Author

Owner

Copy Link

@ipernet commented on GitHub (Sep 19, 2020):

The parser bug may be that in the case of OrderByItem(), a function will be detected before an expression, while it should be the opposite: expression can contain functions and thus they should be match first.

ANd due to that, if the first term after the GROUP BY is a function, the expression is not parsed and this fails:

ORDER BY LENGTH(e.path) - LENGTH(REPLACE(e.path, :path_separator, :empty_string)) ASC

But if it is something else, the expression is parsed successfully:

ORDER BY e.path - LENGTH(REPLACE(e.path, :path_separator, :empty_string)) ASC

A fix could be as simple as changing the "priority" of the switch statement used when iterating over tokens for OrderByItem():

diff --git a/lib/Doctrine/ORM/Query/Parser.php b/lib/Doctrine/ORM/Query/Parser.php
index 3fe1eb04f4..340dadbb55 100644
--- a/lib/Doctrine/ORM/Query/Parser.php
+++ b/lib/Doctrine/ORM/Query/Parser.php
@@ -1510,10 +1510,6 @@ public function OrderByItem()
         $glimpse = $this->lexer->glimpse();
 
         switch (true) {
-            case ($this->isFunction()):
-                $expr = $this->FunctionDeclaration();
-                break;
-
             case ($this->isMathOperator($peek)):
                 $expr = $this->SimpleArithmeticExpression();
                 break;
@@ -1526,6 +1522,10 @@ public function OrderByItem()
                 $expr = $this->ScalarExpression();
                 break;
 
+            case ($this->isFunction()):
+                $expr = $this->FunctionDeclaration();
+                break;
+
             default:
                 $expr = $this->ResultVariable();
                 break;

This needs more testing of course but this fix works well for the current issue and when using window functions.

@ipernet commented on GitHub (Sep 19, 2020): The parser bug may be that in the case of `OrderByItem()`, a **function** will be detected before an **expression**, while it should be the opposite: expression can contain **functions** and thus they should be match first. ANd due to that, if the first term after the **GROUP BY** is a **function**, the expression is not parsed and this fails: ```sql ORDER BY LENGTH(e.path) - LENGTH(REPLACE(e.path, :path_separator, :empty_string)) ASC ``` But if it is something else, the expression is parsed successfully: ```sql ORDER BY e.path - LENGTH(REPLACE(e.path, :path_separator, :empty_string)) ASC ``` A fix could be as simple as changing the "priority" of the switch statement used when iterating over tokens for `OrderByItem()`: ```diff diff --git a/lib/Doctrine/ORM/Query/Parser.php b/lib/Doctrine/ORM/Query/Parser.php index 3fe1eb04f4..340dadbb55 100644 --- a/lib/Doctrine/ORM/Query/Parser.php +++ b/lib/Doctrine/ORM/Query/Parser.php @@ -1510,10 +1510,6 @@ public function OrderByItem() $glimpse = $this->lexer->glimpse(); switch (true) { - case ($this->isFunction()): - $expr = $this->FunctionDeclaration(); - break; - case ($this->isMathOperator($peek)): $expr = $this->SimpleArithmeticExpression(); break; @@ -1526,6 +1522,10 @@ public function OrderByItem() $expr = $this->ScalarExpression(); break; + case ($this->isFunction()): + $expr = $this->FunctionDeclaration(); + break; + default: $expr = $this->ResultVariable(); break; ``` This needs more testing of course but this fix works well for the current issue and when using window functions.

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

3.6.x

2.20.x

dependabot/github_actions/2.20.x/doctrine/dot-github/dot-github/workflows/composer-lint.yml-14.0.0

3.7.x

4.0.x

2.21.x

old-prototype-3.x

3.6.2

3.6.1

3.6.0

2.20.9

3.5.8

3.5.7

3.5.6

3.5.5

2.20.8

3.5.4

3.5.3

2.20.7

3.5.2

2.20.6

3.5.1

3.5.0

3.4.4

3.4.3

3.4.2

2.20.5

3.4.1

3.4.0

3.3.4

2.20.4

3.3.3

2.20.3

3.3.2

2.20.2

3.3.1

2.20.1

3.3.0

3.2.3

2.20.0

2.19.8

3.2.2

2.19.7

3.2.1

2.19.6

3.2.0

3.1.4

3.1.3

2.19.5

3.1.2

2.19.4

3.1.1

2.19.3

2.19.2

2.19.1

3.1.0

2.19.0

3.0.3

2.18.3

3.0.2

2.18.2

3.0.1

2.18.1

3.0.0

2.18.0

2.17.5

3.0.0-RC1

2.17.4

2.17.3

2.17.2

2.17.1

3.0.0-beta2

2.17.0

2.16.3

3.0.0-beta1

2.16.2

2.16.1

2.16.0

2.15.5

2.15.4

2.15.3

2.15.2

2.15.1

2.15.0

2.14.3

2.14.2

2.14.1

2.14.0

2.13.5

2.13.4

2.13.3

2.13.2

2.13.1

2.13.0

2.12.4

2.12.3

2.12.2

2.12.1

2.12.0

2.11.3

2.11.2

2.11.1

2.11.0

2.10.5

2.10.4

2.10.3

2.10.2

2.10.1

2.10.0

2.9.6

2.9.5

2.9.4

2.9.3

2.9.2

2.9.1

2.9.0

2.8.5

2.8.4

2.8.3

2.8.2

2.8.1

2.8.0

2.7.5

2.7.4

v2.7.3

v2.7.2

v2.7.1

v2.7.0

v2.6.6

v2.6.5

v2.6.4

v2.6.3

v2.6.2

v2.6.1

v2.6.0

v2.5.14

v2.5.13

v2.5.12

v2.5.11

v2.5.10

v2.5.9

v2.5.8

v2.5.7

v2.5.6

v2.5.5

v2.5.4

v2.5.3

v2.5.2

v2.4.8

v2.5.1

v2.5.0

v2.5.0-RC2

v2.5.0-RC1

v2.5.0-beta1

v2.5.0-alpha2

v2.5.0-alpha1

v2.4.7

v2.4.6

v2.4.5

v2.4.4

v2.4.3

v2.3.6

v2.4.2

2.3.5

v2.4.1

v2.4.0

2.4.0-RC2

2.4.0-RC1

2.4.0-BETA2

2.3.4

2.3.3

2.4.0-BETA1

2.3.2

2.3.1

2.3.0

2.3.0-RC4

2.3.0-RC3

2.3.0-RC2

2.2.3

2.3.0-RC1

2.3.0-BETA1

2.1.7

2.2.2

2.2.1

2.1.6

2.2.0

2.2.0-RC1

2.2.0-BETA2

2.2.0-BETA1

2.1.5

2.1.4

2.1.3

2.1.2

2.1.1

2.0.7

2.1.0

2.1.0RC3

2.1.0RC2

2.1.0RC1

2.0.6

2.1.0BETA1

2.0.5

2.0.4

2.0.3

2.0.2

2.0.1

2.0.0

2.0.0RC2

2.0.0RC1

2.0.0-BETA4

2.0.0-BETA3

2.0.0-BETA2

2.0.0-BETA1

Labels

Clear labels

BC Break

Bug

Can't Fix

Deprecation

Documentation

DQL

Duplicate

Failing Test

Hacktoberfest

Improvement

Improvement

Incomplete

Invalid

Missing Tests

New Feature

PR Created

pull-request

Mirrored from GitHub Pull Request

Question

Regression

Status: Waiting feedback

Waiting feedback

WIP

Won't Fix

No Label Question Won't Fix

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

admin

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: doctrine/archived-orm#6187