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

Posted to dev@phoenix.apache.org by "Shehzaad Nakhoda (JIRA)" <ji...@apache.org> on 2016/09/01 19:31:21 UTC

[jira] [Commented] (PHOENIX-3219) RuntimeExceptions should be caught and thrown as SQLException

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

Shehzaad Nakhoda commented on PHOENIX-3219:
-------------------------------------------

[~jamestaylor] the issue in PHOENIX-3210. We have protection in the code for catching SQLExceptions coming out of executeUpdate, but this issue doesn't get wrapped into a SQLException, defeating our attempt at debug logging 

> RuntimeExceptions should be caught and thrown as SQLException
> -------------------------------------------------------------
>
>                 Key: PHOENIX-3219
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3219
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.7.0
>            Reporter: Shehzaad Nakhoda
>
> Guarding against SQLExceptions is how one usually defends against unexpected issues in a JDBC call. It would be nice if all exceptions thrown by JDBC calls (e.g. PreparedStatement.execute) would actually get caught and then rethrown as SQLExceptions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)