You could do something that substitutes RexCalls or SqlCalls of unsupported
function calls with calls to supported functions.
But be sure to remember that the semantics of functions does not depend on the
target dialect. Function semantics are always in terms of Calcite’s dialect.
This matters
Joey Moore created CALCITE-5724:
---
Summary: Generated SQL uses literal values in ORDER BY clauses
Key: CALCITE-5724
URL: https://issues.apache.org/jira/browse/CALCITE-5724
Project: Calcite
Hey Askar,
Hope you are doing well. If and when time permits please share your
feedback. It would be really helpful!
Thanks and Regards,
Soumyadeep.
On Wed, May 10, 2023 at 2:17 AM Soumyadeep Mukhopadhyay <
soumyamy...@gmail.com> wrote:
> Hey Askar,
>
> I am happy to inform that I could make a
Hello Everyone,
I wanted to know how one can leverage existing dialects to add new
functions or rename the occurrence of a specific function (or an operator).
For example, a query in Spark SQL - "SELECT EXPLODE(ARRAY['1', '2'])" will
only work in Postgres if it is rewritten as "SELECT
thanks for you response
Zhe Hu 于2023年5月23日周二 15:02写道：
> Hi Jacky.
> The following website will provide more useful information you need.
> https://calcite.apache.org/community/#mailing-lists
>
> Best
> ZheHu
> Replied Message
> From Francis Chuang
> Date 05/23/2023 14:59
> To dev ,
>
ZheHu created CALCITE-5723:
--
Summary: Oracle dialect generates SQL that cannot be recoginized
by lower version Oracle Server(<12) when unparsing OffsetFetch
Key: CALCITE-5723
URL:
