EntityQueryOperator is not changed to correct operator value in condition

Created on 17 January 2023, over 1 year ago

Updated 20 February 2023, over 1 year ago

Any operator used in entityQuery for conditions is not changed (normalised) to the correct value for use in condition what causes SQL Syntax errors.

F.e.
If you will build query like:
entityQuery(entityType: NODE, limit: 100, filter: {conditions: [{field: "field_integer", operator: GREATER_THAN, value: "0"}]})

In SQL query the original enum value (`GREATER_THAN`) will be added instead of `>` and corresponding error will be fired:
SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'GREATER_THAN '0')....

🐛 Bug report

Status

Fixed

Version

1.0

Component

Code

Created by

🇱🇹Lithuania Evaldas Užkuras Kaunas, LT

Live updates comments and jobs are added and updated live.

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment over 1 year ago →
🇺🇸United States dbouman
I'm experiencing the same issue. Here is a patch, however, I'm not very familiar with the project so there may be a much better way of doing this.
Comment over 1 year ago →
🇨🇭Switzerland ayalon
Thanks for the patch. It fixes the issue in a clean way. Will be committed.

Comment over 1 year ago →

System Message

ayalon → committed fbf01e9d on 1.0.x

Issue #3334202 by dbouman, ayalon: EntityQueryOperator is not changed to...

Status changed to Fixed over 1 year ago1:11pm 20 February 2023
Comment over 1 year ago →
🇨🇭Switzerland ayalon
Status changed to Fixed over 1 year ago1:11pm 20 February 2023
Comment over 1 year ago →
🇨🇭Switzerland ayalon

contrib.social Blog FAQ Discussions

Production build 0.69.0 2024