[BUG]: Issue using model columns starting with not*

[wurst-hans]

Currently using v4.1.0, so I don't know, if this issue persists in newer versions.

I have some database models using a colum, for example notification_date. When querying database using

$result = Orders::find([
    'conditions' => 'notification_date IS NULL',
]);

I get an error from Phalcon, saying (you can see, that Phalcon cuts off not):

"Column 'ification_date' doesn't belong to any of the selected models (1), when preparing: SELECT [App\\Models\\Orders].* FROM [App\\Models\\Orders] WHERE notification_date IS NULL"

Even when using backticks in conditions `notification_date` I'm getting another error:

"Scanning error before 'notification_date...' when parsing: SELECT [App\\Models\\Orders].* FROM [App\\Models\\Orders] WHERE `notification_date` IS NULL"

The only solution is to rename column to anything not starting with not.

[dcolt]

You can fix it by doing the PHQL "escaping" in your queries

$result = Orders::find([
    'conditions' => '[notification_date] IS NULL',
]);

[wurst-hans]

I'm only aware of the backticks used by MySQL, so I'm wondering about the square brackets. So this is a Phalcon specific thing?

BTW: I understand that keywords like NOT, LIKE and UPDATE have to be escaped. Nevertheless, Phalcon (i.e. PHQL) seems to ignore word boundaries, because an error on using notification_date is nothing I would expect.

[ALameLlama]

reported in #14641

[niden]

Closing this as duplicate #14641