explicit casting in the above case and we
need to maintain the CAST in our dialect.
Calcite removes the cast in SqlImplementor's stripCastFromString() method. I
would like to understand why Calcite removes the CAST and shall we go ahead
and make the changes in Calcite to maintain the CAST.
Thanks & Regards,
Soma Mondal
HERE hire_date > CAST('2015-01-01' AS TIMESTAMP(0)) AND (position_title =
'SDE' OR position_title = 'SDM')
GROUP BY store_id, position_title
Can I go ahead and make changes where calls to stripCastFromString() will
be skipped for specific dialects?
Regards,
ers doesn’t sound like it’s solving the root cause of the
> problem.
>
> Julian
>
>
> > On Aug 26, 2019, at 7:49 AM, Soma Mondal
> wrote:
> >
> > Hi Julian,
> >
> > 2 tests failed when I made the stripCastFromString() no-op.
> &
or every sql dialect, it would be a
> huge work, we should think of a flexible way.
>
> Best,
> Danny Chan
> 在 2019年8月28日 +0800 PM4:56,Soma Mondal ,写道:
> > Hi Julian,
> >
> > After some further analysis, it seems that the mandatory cast is only
> > required in S
do
so or do you have other thoughts regarding this?
*Regards,*
*Soma Mondal*
Soma Mondal created CALCITE-3318:
Summary: Preserving CAST of STRING operands in comparison operator
Key: CALCITE-3318
URL: https://issues.apache.org/jira/browse/CALCITE-3318
Project: Calcite