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/04/14 20:30:12 UTC
[jira] [Updated] (DRILL-2782) Decide, implement behavior for transaction-related JDBC methods

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

Daniel Barclay (Drill) updated DRILL-2782:
------------------------------------------
    Description: 
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.

Therefore, it is not clear what behavior a JDBC client tool would expect, or be programmed to handle, from a JDBC driver and back end that do not support transactions (that is, Drill).

In turn, that means that it is not clear exactly what Drill's JDBC driver's transaction-related methods should do.  , 









[IN PROGRESS--Why the heck does Jira intercept some magic keystroke and submit things without confirmation?!]



  was:
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.






> 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.
> Therefore, it is not clear what behavior a JDBC client tool would expect, or be programmed to handle, from a JDBC driver and back end that do not support transactions (that is, Drill).
> In turn, that means that it is not clear exactly what Drill's JDBC driver's transaction-related methods should do.  , 
> [IN PROGRESS--Why the heck does Jira intercept some magic keystroke and submit things without confirmation?!]



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