You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Oliver Heger (JIRA)" <ji...@apache.org> on 2010/03/18 08:38:27 UTC

[jira] Commented: (CONFIGURATION-412) Cannot use DatabaseConfiguration if the datasource has autocommit = false

    [ https://issues.apache.org/jira/browse/CONFIGURATION-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846783#action_12846783 ] 

Oliver Heger commented on CONFIGURATION-412:
--------------------------------------------

Would it be a solution to provide an implementation of {{setProperty()}} that issues a single UPDATE statement? Or should {{DatabaseConfiguration}} be extended to perform commits if configured?

> Cannot use DatabaseConfiguration if the datasource has autocommit = false
> -------------------------------------------------------------------------
>
>                 Key: CONFIGURATION-412
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-412
>             Project: Commons Configuration
>          Issue Type: Bug
>    Affects Versions: 1.2
>         Environment: Windows / Linux - Database Oracle 11
>            Reporter: Stefano Bertini
>            Priority: Critical
>
> If using a DatabaseConfiguration object with a datasource that has *autocommit = false*, the setProperty method fails with a *duplicate key* error.
> This happens because in the setProperty method the two calls _clearProperty(key)_ and _addProperty(key, value)_ can retrieve two different connections from the database.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.