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 2023/02/10 08:34:00 UTC

[jira] [Commented] (CALCITE-5524) JDBC adapter generates LIMIT, OFFSET in wrong order for Presto dialect

    [ https://issues.apache.org/jira/browse/CALCITE-5524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17686944#comment-17686944 ] 

Julian Hyde commented on CALCITE-5524:
--------------------------------------

The Presto dialect already has the correct behavior. Closing as invalid.  I'll add a test anyway.

> JDBC adapter generates LIMIT, OFFSET in wrong order for Presto dialect
> ----------------------------------------------------------------------
>
>                 Key: CALCITE-5524
>                 URL: https://issues.apache.org/jira/browse/CALCITE-5524
>             Project: Calcite
>          Issue Type: Bug
>            Reporter: Julian Hyde
>            Priority: Major
>
> JDBC adapter generates LIMIT, OFFSET in wrong order for Presto dialect.
> The presto paging statement should be:
> {code}
> SELECT * FROM db1.tb1 offset 100 limit 20;
> {code}
> The original version defaults to spelling limit first and then offset, which does not conform to presto syntax.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)