You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2017/07/18 18:05:00 UTC
[jira] [Resolved] (CALCITE-1886) Support "LIMIT [offset,]
row_count", per MySQL
[ https://issues.apache.org/jira/browse/CALCITE-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Hyde resolved CALCITE-1886.
----------------------------------
Resolution: Fixed
Fix Version/s: 1.14.0
Fixed in http://git-wip-us.apache.org/repos/asf/calcite/commit/bdb953fa. It is enabled in the MYSQL_5 and LENIENT conformances. Thanks for the fix, and the additional test cases, [~kaiwangchen]!
> Support "LIMIT [offset,] row_count", per MySQL
> ----------------------------------------------
>
> Key: CALCITE-1886
> URL: https://issues.apache.org/jira/browse/CALCITE-1886
> Project: Calcite
> Issue Type: Improvement
> Reporter: Chen Xin Yu
> Assignee: Julian Hyde
> Fix For: 1.14.0
>
>
> CALCITE support limit offset SQL grammar in CALCITE-43:
> {noformat}
> [LIMIT { count | ALL}]
> [OFFSET start { ROW | ROWS}]
> {noformat}
> Also
> {noformat}
> LIMIT {[offset,] row_count}
> {noformat}
> is popular used, especially in MySQL, such as:
> {code}
> select * from tableA order by id limit 100,10;
> {code}
> User should transform the existing SQLs until calcite support
> {noformat} LIMIT {[offset,] row_count}{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)