[
https://issues.apache.org/jira/browse/CALCITE-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492685#comment-14492685
]
Julian Hyde commented on CALCITE-585:
-------------------------------------
Yes.
Rather than throwing directly, can you please call a method: {code}throw
connection.helper.unsupported();{code}. Then we can add more info by
refactoring that method. Also, please add a test for one or two of the methods
to make sure they continue to throw.
> Calcite throw UnsupportedOperationException instead of
> SQLFeatureNotSupportedException
> --------------------------------------------------------------------------------------
>
> Key: CALCITE-585
> URL: https://issues.apache.org/jira/browse/CALCITE-585
> Project: Calcite
> Issue Type: Bug
> Reporter: Ng Jiunn Jye
> Assignee: Julian Hyde
> Priority: Minor
>
> The unsupported JDBC method are throwing UnsupportedOperationException.
> This cause calcite jdbc client program fail to catch the exception and goes
> to unhandled exception routine.
> For example
> AvaticaStatement.java
> public boolean getMoreResults() throws SQLException {
> throw new UnsupportedOperationException();
> }
> The expected exception for this is SQLFeatureNotSupportedException (a
> subclass of SQLException).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
