[
https://issues.apache.org/jira/browse/CALCITE-5184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde resolved CALCITE-5184.
----------------------------------
Fix Version/s: 1.36.0
Resolution: Fixed
Fixed in
[161e2203|https://github.com/apache/calcite/commit/161e220384dfbd85f896a95cac40cca23141583e];
thanks for the PR, [~hongyuguo]!
> In parser, allow "LIMIT start, ALL"
> -----------------------------------
>
> Key: CALCITE-5184
> URL: https://issues.apache.org/jira/browse/CALCITE-5184
> Project: Calcite
> Issue Type: Bug
> Reporter: Julian Hyde
> Assignee: hongyu guo
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.36.0
>
>
> In parser, allow "LIMIT start, ALL". For example,
> {code:sql}
> SELECT *
> FROM Emp
> ORDER BY sal DESC
> LIMIT 10, ALL
> {code}
> would be equivalent to
> {code:sql}
> SELECT *
> FROM Emp
> ORDER BY sal DESC
> OFFSET 10
> {code}
> No other database supports this syntax, but Calcite supports Postgres' "LIMIT
> ALL" and MySQL's "LIMIT start, count" so it makes sense to combine them.
> See the original discussion in CALCITE-5086.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
