[
https://issues.apache.org/jira/browse/CALCITE-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hongze Zhang updated CALCITE-3010:
----------------------------------
Description:
Below is the syntax definition of {{JsonValueExpression}} from ISO/SEC 19075-6:
{code:java}
<JSON value expression> ::=
<value expression> [ <JSON input clause> ]
<JSON input clause> ::=
FORMAT <JSON representation>
<JSON representation> ::=
JSON [ ENCODING { UTF8 | UTF16 | UTF32 } ]
| <implementation-defined JSON representation option>
{code}
Currently it's an individual syntax standing out of {{Expression}} for easily
implementing the behavior of "implicit JSON format". As the amount of JSON
functions is getting larger, the design could definitely be improved. For
example, it can be categorized as a PostfixOperator[1].
[1]
[https://github.com/apache/calcite/blob/master/core/src/main/java/org/apache/calcite/sql/SqlPostfixOperator.java]
was:
Below is the syntax definition of {{JsonValueExpression}} from ISO/SEC 19075-6:
{code:java}
<JSON value expression> ::=
<value expression> [ <JSON input clause> ]
<JSON input clause> ::=
FORMAT <JSON representation>
<JSON representation> ::=
JSON [ ENCODING { UTF8 | UTF16 | UTF32 } ]
| <implementation-defined JSON representation option>
{code}
> In SQL parser, move JsonValueExpression into Expression
> -------------------------------------------------------
>
> Key: CALCITE-3010
> URL: https://issues.apache.org/jira/browse/CALCITE-3010
> Project: Calcite
> Issue Type: Sub-task
> Reporter: Hongze Zhang
> Assignee: Hongze Zhang
> Priority: Major
>
> Below is the syntax definition of {{JsonValueExpression}} from ISO/SEC
> 19075-6:
> {code:java}
> <JSON value expression> ::=
> <value expression> [ <JSON input clause> ]
> <JSON input clause> ::=
> FORMAT <JSON representation>
> <JSON representation> ::=
> JSON [ ENCODING { UTF8 | UTF16 | UTF32 } ]
> | <implementation-defined JSON representation option>
> {code}
> Currently it's an individual syntax standing out of {{Expression}} for easily
> implementing the behavior of "implicit JSON format". As the amount of JSON
> functions is getting larger, the design could definitely be improved. For
> example, it can be categorized as a PostfixOperator[1].
> [1]
> [https://github.com/apache/calcite/blob/master/core/src/main/java/org/apache/calcite/sql/SqlPostfixOperator.java]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
