Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Tue, 25 Aug 2015 22:28:47 +0000 (UTC)
From: "Daniel Barclay (Drill) (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.12782723.1426635338000.164420.1440541727056@Atlassian.JIRA>
In-Reply-To: <JIRA.12782723.1426635338000@Atlassian.JIRA>
References: <JIRA.12782723.1426635338000@Atlassian.JIRA>
 <JIRA.12782723.1426635338492@arcas>
Subject: [jira] [Updated] (DRILL-2489) Accessing Connection, Statement,
 PreparedStatement after they are closed should throw a SQLException
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Daniel Barclay (Drill) updated DRILL-2489:
------------------------------------------
    Assignee: Mehant Baid  (was: Daniel Barclay (Drill))

> 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: Mehant Baid
>             Fix For: 1.2.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)