Mailing-List: contact dev-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Tue, 14 Apr 2015 17:51:12 +0000 (UTC)
From: "Daniel Barclay (Drill) (JIRA)" <jira@apache.org>
To: dev@drill.apache.org
Message-ID: <JIRA.12820884.1429033836000.83272.1429033872454@Atlassian.JIRA>
In-Reply-To: <JIRA.12820884.1429033836000@Atlassian.JIRA>
References: <JIRA.12820884.1429033836000@Atlassian.JIRA>
 <JIRA.12820884.1429033836698@arcas>
Subject: [jira] [Created] (DRILL-2782) Decide, implement behavior for
 transaction-related JDBC methods
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Daniel Barclay (Drill) created DRILL-2782:
---------------------------------------------

             Summary: Decide, implement behavior for transaction-related JDBC methods
                 Key: DRILL-2782
                 URL: https://issues.apache.org/jira/browse/DRILL-2782
             Project: Apache Drill
          Issue Type: Bug
            Reporter: Daniel Barclay (Drill)


Officially, JDBC requires transaction support. Because of that, the JDBC specification (PDF document and Javadoc) addresses the behavior of transaction-related methods only for the case in which transactions are supported.


In particular, JDBC does not specify the behavior when transactions are not supported


 (since it assumes that the driver and database support transactions, since, of course, that is required)--as is the case in Drill.  

Therefore, it is not clear what driver behavior a JDBC client tool will expect or be able to handle.


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