[
https://issues.apache.org/jira/browse/CALCITE-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17759325#comment-17759325
]
Julian Hyde commented on CALCITE-5958:
--------------------------------------
I think it’s taking compatibility too far to try to have exactly the same
keywords as Postgres.
In summaries (and elsewhere) please uppercase keywords. Your sentence doesn’t
parse when “value” is lower case.
In English there is always a space before “(“.
> Make the value be nonReservedKeywords(consistent with Postgres)
> ---------------------------------------------------------------
>
> Key: CALCITE-5958
> URL: https://issues.apache.org/jira/browse/CALCITE-5958
> Project: Calcite
> Issue Type: Improvement
> Reporter: LakeShen
> Priority: Major
> Attachments: image-2023-08-27-12-33-24-000.png,
> image-2023-08-27-12-34-53-322.png
>
>
> Now in the Postgres, value could be field alias,for example:
> {code:java}
> select 1 + 1 as value {code}
> The above SQL was successfully executed in PG:
> !image-2023-08-27-12-33-24-000.png|width=275,height=210!
> In Calcite, the above SQL throws a parse error:
> !image-2023-08-27-12-34-53-322.png|width=554,height=197!
> I don't confirm whether this is a problem
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
