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

Posted to issues@drill.apache.org by "Daniel Barclay (Drill) (JIRA)" <ji...@apache.org> on 2015/06/18 20:01:01 UTC

[jira] [Reopened] (DRILL-2489) Accessing Connection, Statement, PreparedStatement after they are closed should throw a SQLException

     [ https://issues.apache.org/jira/browse/DRILL-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Barclay (Drill) reopened DRILL-2489:
-------------------------------------------

Reopening because, although key methods check (so JDBC API client code can't get far without getting a direct, clear exception), not all methods check yet.


> 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)