You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/03/01 23:08:00 UTC

[jira] [Commented] (CALCITE-508) Reading from ResultSet before calling next() should throw SQLException not NoSuchElementException

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

ASF GitHub Bot commented on CALCITE-508:
----------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/calcite-avatica/pull/23


> Reading from ResultSet before calling next() should throw SQLException not NoSuchElementException
> -------------------------------------------------------------------------------------------------
>
>                 Key: CALCITE-508
>                 URL: https://issues.apache.org/jira/browse/CALCITE-508
>             Project: Calcite
>          Issue Type: Bug
>          Components: avatica
>            Reporter: Julian Hyde
>            Assignee: Julian Hyde
>            Priority: Major
>              Labels: newbie
>             Fix For: avatica-1.11.0
>
>
> Reading from ResultSet before calling next() should throw SQLException not NoSuchElementException.
> Each of the Cursor.Accessor.getXxx methods should convert runtime exceptions to SQLException.
> JdbcTest.testExtract currently demonstrates this problem; it passes if there is a NoSuchElementException, but should look for a SQLException.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)