[
https://issues.apache.org/jira/browse/CALCITE-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16084308#comment-16084308
]
Julian Hyde commented on CALCITE-1886:
--------------------------------------
I see, this is a non-standard MySQL syntax. (Jeez, I wish those guys had read
the standard, or at least looked at what other DBs were doing, once in a while.)
I don't see a problem with supporting this, enabled in SqlConformance = {
MYSQL, LENIENT }.
> Support LIMIT [offset,] row_count
> ---------------------------------
>
> Key: CALCITE-1886
> URL: https://issues.apache.org/jira/browse/CALCITE-1886
> Project: Calcite
> Issue Type: Improvement
> Reporter: Chen Xin Yu
> Assignee: Julian Hyde
>
> CALCITE support limit offset SQL grammar in CALCITE-43 :
> [LIMIT { count | ALL}]
> [OFFSET start { ROW | ROWS}]
> LIMIT {[offset,] row_count} is also popular used, especially in MySQL, such
> as:
> select * from tableA order by id limit 100,10;
> User should transform the existing sqls until calcite support LIMIT
> {[offset,] row_count}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
