2010YOUY01 commented on PR #16798:
URL: https://github.com/apache/datafusion/pull/16798#issuecomment-3082274998
what about using explicit casting in applications? For example:
```sh
> select not(arrow_cast(1, 'Boolean'));
+------------------------------------------+
| NOT arrow_cast(Int64(1),Utf8("Boolean")) |
+------------------------------------------+
| false |
+------------------------------------------+
```
IIRC, PostgreSQL doesn't support such comparisons, while DuckDB does.
I think this rule may feel natural primarily to C++ programmers (perhaps
that’s why DuckDB allows such coercion), but SQL is more application-oriented.
Many SQL users might not be familiar with this convention, so introducing this
coercion rule might make the application more error-prone.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org
For additional commands, e-mail: github-h...@datafusion.apache.org
