[jira] [Commented] (CALCITE-1352) Clarify documentation for avatica's max_row_totals

["Julian Hyde (JIRA)" <ji...@apache.org>]

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

Julian Hyde commented on CALCITE-1352:
--------------------------------------

That was what I intended when I designed the API. In my opinion, JDBC got it wrong in making 0 mean "unlimited", because sometimes people want to ask for 0 rows.

> Clarify documentation for avatica's max_row_totals
> --------------------------------------------------
>
>                 Key: CALCITE-1352
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1352
>             Project: Calcite
>          Issue Type: Improvement
>          Components: avatica
>    Affects Versions: avatica-1.8.0
>            Reporter: Francis Chuang
>            Priority: Minor
>
> The {{max_rows_total}} parameter in the protocol buffer definitions should be updated to include more information on values that result in unlimited rows being returned.
> When testing against calcite 1.8.0, I observed the following:
> {code}
> -1: Unlimited number of rows
> 0: 0 rows
> 1: 1 row
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)