___
> From: Gonzalo Ortiz Jaureguizar
> Sent: Thursday, February 22, 2024 11:53 PM
> To: dev@calcite.apache.org
> Subject: Re: Remove a specific type coersion rule
>
>> When I read CALCITE-6210 it wasn’t clear that you wanted Calcite to give
>
-6210 (after
I apply the suggested fixes from reviews).
Mihai
From: Gonzalo Ortiz Jaureguizar
Sent: Thursday, February 22, 2024 11:53 PM
To: dev@calcite.apache.org
Subject: Re: Remove a specific type coersion rule
> When I read CALCITE-6210 it wasn’t clear
[CALCITE-3550] provides a solution for them.
>
> Mihai
>
>
> From: Julian Hyde
> Sent: Thursday, February 22, 2024 4:16 PM
> To: dev@calcite.apache.org
> Subject: Re: Remove a specific type coersion rule
>
> When I read CALCITE-6210 it
: Remove a specific type coersion rule
When I read CALCITE-6210 it wasn’t clear that you wanted Calcite to give a
validation error when someone tries to cast a VARCHAR to a VARBINARY. I agree
that that is the desirable behavior. (And I believe it is consistent with the
SQL standard.) Can you amend the
When I read CALCITE-6210 it wasn’t clear that you wanted Calcite to give a
validation error when someone tries to cast a VARCHAR to a VARBINARY. I agree
that that is the desirable behavior. (And I believe it is consistent with the
SQL standard.) Can you amend the Jira case so that it clearly the
Hello there,
In the context of https://issues.apache.org/jira/browse/CALCITE-6210, the
Apache Pinot team is thinking about forbidding casting from VARCHAR to
VARBINARY.
I've been trying to implement that, but I'm not sure if it is possible or
not. Following the Javadoc of SqlTypeCoercionRule (whi
