commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Thomas (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DBCP-405) getAutoCommit in PoolableConnectionFactory
Date Mon, 02 Dec 2013 22:46:36 GMT

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

Mark Thomas resolved DBCP-405.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0
                   1.5.1
                   1.4.1
                   1.3.1

Fixed in svn. Will be included in the versions listed in Fix versions onwards.

> getAutoCommit in PoolableConnectionFactory
> ------------------------------------------
>
>                 Key: DBCP-405
>                 URL: https://issues.apache.org/jira/browse/DBCP-405
>             Project: Commons Dbcp
>          Issue Type: Improvement
>            Reporter: Steeve Beroard
>            Priority: Trivial
>             Fix For: 1.3.1, 1.4.1, 1.5.1, 2.0
>
>
> In passivateObject() method of PoolableConnectionFactory, getAutoCommit() is called twice.
I am working with Sybase JDBC driver, in their implementation, getAutoCommit() makes a call
to database so there are two roundtrips to database. I would like to understand if there is
anything that prevent you to call getAutoCommit() once and store the result in a local variable
to use it again?



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message