[
https://issues.apache.org/jira/browse/CALCITE-6731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17947642#comment-17947642
]
Julian Hyde commented on CALCITE-6731:
--------------------------------------
Since this is a feature, and a feature that will be conditionally enabled, can
you describe which flags will enable the feature.
Remove the stuff from the description about syntax error. Obviously if the
feature is missing you will get a syntax error. It's like me describing all the
things that go wrong if I drive my car into a lake, when the feature request is
"Allow my car to drive underwater".
For testing, this is an exceptional case, you should try to use the existing
framework without bending it too much (or affecting existing tests). Is there a
way to create a {{StringAndPos}} instance directly, generalizing its
constructor to use a different delimiter, and then call a variant of the
{{checkFails}} method that uses {{StringAndPos}}?
> Add support for ^ operator in Calcite
> -------------------------------------
>
> Key: CALCITE-6731
> URL: https://issues.apache.org/jira/browse/CALCITE-6731
> Project: Calcite
> Issue Type: Improvement
> Reporter: zhengyu
> Assignee: krooswu
> Priority: Major
>
> version :
> org.apache.calcite:calcite-core:1.35.0
> config :
>
> private static final SqlParser.Config MYSQL_CONFIG = SqlParser.config()
> .withCaseSensitive(false)
> .withUnquotedCasing(Casing.UNCHANGED)
> .withConformance(SqlConformanceEnum.LENIENT)
> .withQuoting(Quoting.BACK_TICK)
> .withLex(Lex.MYSQL)
> .withIdentifierMaxLength(512);
> sql： SELECT 5 ^ 3
>
> SqlNode sqlNode;
> try {
> sqlNode = SqlParser.create(sql, MYSQL_CONFIG).parseStmt();
> } catch (SqlParseException e) {}
>
> error :
> Encountered "^" at line 1, column 10.
> Was expecting one of:
> <EOF>
> "AS" ...
> "EXCEPT" ...
> "FETCH" ...
> "FROM" ...
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
