Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've been wondering about this for years, what is the purpose of the
Join::ON
constant? This constant seems completely useless, as the DQL parser doesn't even support theON
keyword in a join:I haven't found any issues related to this, nor any explanations regarding the original idea behind this constant.
Also, if it's decided to deprecate and remove this constant, the
$conditionType
parameters of theQueryBuilder::*Join()
methods andExpr\Join
class will become redundant since currently, the only two options areWITH
andON
. Therefore, it might be a good idea to consider deprecating them as well.orm/lib/Doctrine/ORM/QueryBuilder.php
Lines 1028 to 1052 in 23d36c0