[
https://issues.apache.org/jira/browse/CALCITE-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16354592#comment-16354592
]
ASF GitHub Bot commented on CALCITE-508:
----------------------------------------
Github user asolimando commented on the issue:
https://github.com/apache/calcite-avatica/pull/23
Hi @vlsi,
I have update the PR according to your suggestions (modulo the more precise
error codes, as discussed above), can you please have a look?
I haven't managed to rebase my two commits for CALCITE-508 due to the
intermixed commit for CALCITE-2083, is that ok? If not, how do you usually
handle such situations?
> 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
> Priority: Major
> 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
(v7.6.3#76005)
