Hi Saikat!
The dependencies have been updated, and the merge conflicts resolved.
Kind regards
On Sat, 28 Dec 2019, 23:27 Saikat Maitra, wrote:
> Hi Emmanouil,
>
> Thank you for making the changes. I have merged my PR changes in master.
> Can you please take the latest from master branch and
Hi Emmanouil,
Thank you for making the changes. I have merged my PR changes in master.
Can you please take the latest from master branch and resolve the conflicts
in your PR.
I have also reviewed the changes in your PR and requested minor changes
specific to dependencies version and license
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
Hi Saikat!
Thank you on this one! I tried it and it worked as expected [1]
Kind regards
Emmanouil
[1]
https://ci.ignite.apache.org/viewLog.html?buildId=4888357=buildLog&_focus=2046#_state=2046
*Emmanouil Gkatziouras*
https://egkatzioura.com/ | https://www.linkedin.com/in/gkatziourasemmanouil/
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
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