Postgres: Search everywhere should ignore boolean columns

[prokoma]

Adminer version: 5.4.1
Compiled: single file
Driver: PgSQL
Database version: 18.1
Plugins used:

When searching everywhere (both the entire database and a single table) with the = operator, an error is shown when the table has boolean columns when an invalid boolean value is searched for.

SELECT * FROM "table" WHERE ("col1" = 'aaa' OR "col2" = 'aaa' OR "col3" = 'aaa' OR "col4" = 'aaa' OR "booleancol" = 'aaa') LIMIT 50 (0.001 s)

ERROR: invalid input syntax for type boolean: "aaa"
LINE 3: ..."col3" = 'aaa' OR "col4" = 'aaa' OR "booleancol" = 'aaa' OR "...

The column type is boolean NULL.

[Letme]

Isn't this SQL error? Not adminer...

[prokoma]

Yes, but is caused by Adminer including "booleancol" = 'aaa' in the SQL statement, which is invalid. This condition should be probably updated to allow only valid boolean values:

Boolean constants can be represented in SQL queries by the SQL key words TRUE, FALSE, and NULL.

The datatype input function for type boolean accepts these string representations for the “true” state:

true
yes
on
1

and these representations for the “false” state:

false
no
off
0

Unique prefixes of these strings are also accepted, for example t or n. Leading or trailing whitespace is ignored, and case does not matter.

https://www.postgresql.org/docs/current/datatype-boolean.html

[Letme]

There is no datatype boolean in mysql: http://dev.mysql.com/doc/refman/8.4/en/data-types.html . It is usually represented as TINYINT(1) and what is more fun is that A would be a perfectly legal value (its a number) for a True (as anything not 0 is considered True). So... Can you go now one by one what you meant by Adminer including stuff in SQL statement? Are you proposing that Adminer somehow limits user inputs?

[prokoma]

This issue is about PostgreSQL, not MySQL.