My humble opinion here is that we should strive for one and only
dialect. I understand concerns about supporting a backward compatible
dialect. But I personally do not know whether it is practical with
Calcite. Regarding multiples dialects my forecast is that supporting
multiple dialects close by m
Hello!
I think we may eventually need at least two dialects.
One is "H2 compatible" for users migrating from older versions of AI. We
may need to add a few tweaks there to make most of existing SQL code work.
Other is "modern" in which we will remove these tweaks to get the best,
vanilla Ignite+C
Hi all!
Calcite can parse queries using a couple of dozens built-in SQL dialects
[1]. But as I can see it doesn't mean that Calcite's PG or Oracle
dialects are fully compliant with original PG or Oracle dialects.
Calcite's dialect contains only the main features of the original SQL
dialect like de
Forgot to mention, it's better to set chosen dialect per session, for
example by a command
"alter session sed dialect=ORACLE"
Or a part of connection url.
Global configuration parameter isn't a good choice.
сб, 28 дек. 2019 г., 11:02 Seliverstov Igor :
> I guess you are thinking about transpar
I guess you are thinking about transparent migration from Oracle for
example.
>From user perspective it's really cool, but we will be forced to maintain
all these dialects and fully test them. Also I heard about several
inconsistencies between how it should and how it actually works. All these
iss
Igor,
When you are saying that we should not allow the dialect changing, are you
referring to changes in runtime when a node is already up-and-running?
Generally, it will be more than enough if a dialect can be set statically
and globally -- the user selects the dialect for the entire cluster via
Denis,
> Is it true that Calcite can parse MySQL, Oracle
Yes, it can.
> Do I need to select a dialect globally or can it be set on a per-query
> level?
Technically a parser, a validator, a planner, other components are created and
configured for each query call (because they are stateful). So
Igor S., Roman and others who involved in Calcite prototyping,
Is it true that Calcite can parse MySQL, Oracle, ANSI-99 and other dialects
as suggested by this page?
https://calcite.apache.org/apidocs/org/apache/calcite/sql/validate/SqlConformanceEnum.html
Do I need to select a dialect globally o
