[
https://issues.apache.org/jira/browse/CALCITE-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16753270#comment-16753270
]
Hongze Zhang commented on CALCITE-2791:
---------------------------------------
Thanks for the explanition [~x1q1j1], I personally think the MySQL's JSON
functions like JSON_TYPE can be very useful, they can do a lot more on JSON
than standard's implementation. And if you are writing the MySQL's
implementation, I can see maybe the multiple parameter syntax in PR (
[https://github.com/apache/calcite/pull/1013/files#diff-3969d844f7ecd2b3d324bf8b0e5a1e9aR5259])
is more like a mistake, If so it is a detailed problem and not a big deal.
> Add the JSON_TYPE function
> --------------------------
>
> Key: CALCITE-2791
> URL: https://issues.apache.org/jira/browse/CALCITE-2791
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: xuqianjin
> Assignee: Julian Hyde
> Priority: Major
> Labels: https://github.com/apache/calcite/pull/1013
>
> The data in json can be =, <, <=, >, >=, <>,! =, and <=>. But the data types
> in json can be diverse, so when you compare different types, you have a
> priority, and the high priority is greater than the low priority (you can
> view the types with the JSON_TYPE() function). The priorities are as follows:
> BOOLEAN
> ARRAY
> OBJECT
> STRING
> INTEGER
> LONG
> DOUBLE
> NULL
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
