[
https://issues.apache.org/jira/browse/CALCITE-712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14541259#comment-14541259
]
Xavier FH Leong commented on CALCITE-712:
-----------------------------------------
Seem like I'm not able to convince you to be consistent with JDBC "irkiness"
maxRowCount :)
https://github.com/xhoong/incubator-calcite/commit/05d1a6bd51e6a4a5e939b5a899122008da7bd189
Please find the 0 row count implementation with JdbcMeta.prepareAndExecute,
complete with test of course.
> 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)
