Hi Feng,
You’re right, i get the same result with your suggestion, and either of the
following expressions is ok.
1. properties.put(CalciteConnectionProperty.LEX.camelName(), "MYSQL");
2. properties.put("lex", "MYSQL");
You’re familiar with Calcite :), and thanks for your help and
Hi, Juan Pan:
You may find the logic in *UnregisterDriver#connect(String url, Properties
info)*
It just parses the key-value pairs in url's prefix and adds into the copy
of "info".
Therefore, I think the below config
*properties.put(CalciteConnecti**onProperty.LEX, Lex.MYSQL); *
should be aligned
Hi Feng,
Thanks for your promote reply. :)
Lex is just what i want. But when i tried to use it, i encountered another
problem.
The first usage is ok, but the second one doesn’t work. ThoughLex are used in
different methods, the result will be same, i think. Do i misunderstand?
Hi, JuanPan,
You can refer to Lex, which decides how identifiers are quoted, whether
they are converted to upper-case
org.apache.calcite.config.Lex
Regards
Juan Pan 于2019年9月11日周三 下午8:05写道：
>
>
> Hi, all the committers and contributors,
>
>
> This email is for your help.
>
>
> I am now deep in
Hi, all the committers and contributors,
This email is for your help.
I am now deep in Apache Calcite, and it’s great. Now, i want to know whether it
is possible that unquoted identifiers are not implicitly converted to upper
case?
For example, a SQL is `select name from test`, when it
