[
https://issues.apache.org/jira/browse/CALCITE-5013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17495055#comment-17495055
]
Julian Hyde edited comment on CALCITE-5013 at 2/19/22, 9:41 PM:
----------------------------------------------------------------
Can you give a SQL example in the description? Capitalize SQL keywords in
subject and description. Use Jira links for related Jira cases and the PR.
Also, say which component has the bug. ("... should be retained" is passive
voice, "ComponentX should retain..." is active voice and better, "ComponentX
alters semantics when generating SQL for UNION ... LIMIT" is even better
because it describes the crime and the culprit.)
was (Author: julianhyde):
Can you give a SQL example in the description? Capitalize SQL keywords in
subject and description. Use Jira links for related Jira cases and the PR.
> Parentheses should be retained when the operand of SetOp has limit or offset
> ----------------------------------------------------------------------------
>
> Key: CALCITE-5013
> URL: https://issues.apache.org/jira/browse/CALCITE-5013
> Project: Calcite
> Issue Type: Bug
> Components: core
> Reporter: Jiajun Xie
> Priority: Major
>
> - In standard SQL, the operand of union should not have limit or order by.So
> parse will fail in SqlParserTetest#testLimitUnion and
> SqlParserTetest#OrderUnion.
> - When users use parentheses, most engines allow it. See the
> discussion:[CALCITE-1892|https://issues.apache.org/jira/browse/CALCITE-1892].
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
