You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Alessandro Solimando (JIRA)" <ji...@apache.org> on 2018/01/12 21:14: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=16324563#comment-16324563 ]
Alessandro Solimando commented on CALCITE-508:
----------------------------------------------
Debugging _JdbcTest.testExtract_ I have seen that the concrete implementation of ResultSet is provided by Avatica here, and from the comment on converting runtime exceptions into _Cursor.Accessor.getXxx_ methods I assume that Avatica is the only access to JDBC drivers inside Calcite. Is it correct?
I see that Avatica is now a separate repo (calcite-avatica), so I guess this ticket should be handled inside avatica-core and the only modification here should be to update the tests accordingly. Is that correct?
> 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
> Reporter: Julian Hyde
> Assignee: Julian Hyde
> Labels: newbie
>
> 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
(v6.4.14#64029)