Avoid cast numbers to string in filter about arrow-datafusion HOT 4 OPEN

Yes, I'm afraid we have to provide both behaviors controlled by a configuration. Otherwise this breaks lots of things.

from arrow-datafusion.

PG won't do the cast even if the column type is string and literal is number:

postgres=# select * from t where column2 > 1;
ERROR:  operator does not exist: text > integer
LINE 1: select * from t where column2 > 1;
                                      ^
HINT:  No operator matches the given name and argument types. You might need to add explicit type casts.

from arrow-datafusion.

Exprs like SELECT '1' IN ('a','b',1) from datafusion/sqllogictest/test_files/expr.slt would also fail

from arrow-datafusion.

Given I suspect there is no one agreed upon "standard" for this particular behavior, perhaps we can add a configuration option to control if strings are coerced to numeric types 🤔

from arrow-datafusion.