Inconsistnecy is showed in the below queries, it's better to keep the behavior consistent (PostgreSQL reject them all during planning)
> select +true, +false;
+---------------+----------------+
| Boolean(true) | Boolean(false) |
+---------------+----------------+
| true | false |
+---------------+----------------+
1 row(s) fetched.
Elapsed 0.008 seconds.
> select -true;
Error during planning: Negation only supports numeric, interval and timestamp types
> select -false;
Error during planning: Negation only supports numeric, interval and timestamp types
PostgreSQL behavior:
postgres=# select +true;
ERROR: operator does not exist: + boolean
LINE 1: select +true;
^
HINT: No operator matches the given name and argument type. You might need to add an explicit type cast.
postgres=# select -true;
ERROR: operator does not exist: - boolean
LINE 1: select -true;
Describe the bug
Inconsistnecy is showed in the below queries, it's better to keep the behavior consistent (PostgreSQL reject them all during planning)
PostgreSQL behavior:
To Reproduce
No response
Expected behavior
No response
Additional context
No response