[ https://issues.apache.org/jira/browse/DRILL-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14379339#comment-14379339 ]
Daniel Barclay (Drill) commented on DRILL-2489: ----------------------------------------------- When fixing this bug: - Create a specific subclass of SQLException for the "object already closed" condition (perhaps AlreadyClosedSQLException). Having a dedicated exception subclass will simplify test code (which probably will already be bulky because of the large number of methods involved). - Make that new SQLException subclass a subclass of Drill's existing JdbcApiSqlException. - Move JdbcApiSqlException from being a direct subclass of SQLException to being a subclass of SQLNonTransientException. > Accessing Connection, Statement, PreparedStatement after they are closed > should throw a SQLException > ---------------------------------------------------------------------------------------------------- > > Key: DRILL-2489 > URL: https://issues.apache.org/jira/browse/DRILL-2489 > Project: Apache Drill > Issue Type: Bug > Components: Client - JDBC > Reporter: Rahul Challapalli > Assignee: Daniel Barclay (Drill) > Fix For: 1.1.0 > > > git.commit.id.abbrev=7b4c887 > According to JDBC spec we should throw a SQLException when we access methods > on a closed Connection, Statement, or PreparedStatement. Drill is currently > not doing it. > I can raise multiple JIRA's if the developer wishes to work on them > independently -- This message was sent by Atlassian JIRA (v6.3.4#6332)