[
https://issues.apache.org/jira/browse/CALCITE-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde updated CALCITE-813:
--------------------------------
Summary: Upgrade updateCount, maxRows from int to long (was: Long values
for updateCount, maxRows)
> Upgrade updateCount, maxRows from int to long
> ---------------------------------------------
>
> Key: CALCITE-813
> URL: https://issues.apache.org/jira/browse/CALCITE-813
> Project: Calcite
> Issue Type: Bug
> Reporter: Julian Hyde
> Assignee: Julian Hyde
>
> JDK 1.8 introduced methods exposing updateCount and maxRows as long values,
> where previously they were int values. The methods are:
> * long Statement.executeLargeUpdate(String)
> * long Statement.getLargeUpdateCount()
> * long Statement.getLargeMaxRows()
> * void Statement.setLargeMaxRows(long)
> AvaticaStatement should implement these methods.
> This will require changing corresponding fields:
> ResultSetResponse.updateCount, PrepareAndExecuteRequest.maxRowCount,
> ExecuteRequest.maxRowCount, PrepareRequest.maxRowCount. Also
> FetchRequest.offset.
> But note that Statement.setFetchSize(int) and .getFetchSize() remain int
> methods, and FetchRequest.fetchMaxRowCount remains an int.
> JdbcMeta should use these methods in the underlying JDBC driver, and if they
> throw UnsupportedOperationException, fall back to the int version.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
