[
https://issues.apache.org/jira/browse/CALCITE-712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14538852#comment-14538852
]
Julian Hyde commented on CALCITE-712:
-------------------------------------
I find JDBC's 1-based maxRows irksome just as I find its 1-based column
ordinals (in ResultSet.getXxx and PreparedStatement.setXxx) irksome. Most
implementations of Meta do not go to JDBC and so don't need to abide by JDBC's
silly interpretation of limit 0.
> Avatica statement execute return all resultset instead of MaxRows from
> setMaxRows
> ---------------------------------------------------------------------------------
>
> Key: CALCITE-712
> URL: https://issues.apache.org/jira/browse/CALCITE-712
> Project: Calcite
> Issue Type: Bug
> Affects Versions: 1.3.0-incubating
> Reporter: Xavier FH Leong
> Assignee: Julian Hyde
> Labels: avatica
> Fix For: next
>
>
> setMaxRows is supported, but after moving to JdbcMeta, max row was ignore and
> full result set is return instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
