Affects Version/s: 2.2.1
Fix Version/s: None
When using a LIKE condition in a WHERE clause, I would like to be able to use the foreign key of a single value association. For example:
Imagine Product and Department are both entities. Department has the field Name with a unique index. Product is has a ManyToOne association called Department with the Department entity, referencing the field Name.
I would like to write:
SELECT FROM Product p WHERE p.Department LIKE '% Tools'
However, at present I need to write:
SELECT FROM Product p
JOIN p.Department d
WHERE d.name LIKE '% Tools'
The issue is one of performance. On large record sets the first query runs several magnatudes more quickly than the second, particularly when four or five joins are involved.
Looking at the DQL grammar from the online docs, the relveant lines are:
LikeExpression ::= StringExpression ["NOT"] "LIKE" string ["ESCAPE" char]
StringExpression ::= StringPrimary | "(" Subselect ")"
StringPrimary ::= StateFieldPathExpression | string | InputParameter | FunctionsReturningStrings | AggregateExpression
The problem is the StateFieldPathExpression in StringPrimary. When used with a LikeExpression a SingleValuedAssociationField should be allowed also.
|Field||Original Value||New Value|
|Issue Type||Bug [ 1 ]||Improvement [ 4 ]|
|Workflow||jira [ 13593 ]||jira-feedback [ 14043 ]|
|Workflow||jira-feedback [ 14043 ]||jira-feedback2 [ 15907 ]|
|Workflow||jira-feedback2 [ 15907 ]||jira-feedback3 [ 18162 ]|