[
https://issues.apache.org/jira/browse/CONFIGURATION-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846986#action_12846986
]
Stefano Bertini commented on CONFIGURATION-412:
---
I think that the DatabaseConfiguration should always perform a commit,
otherwise the class would not be usable without autocommit = true.
Infact, without autocommit = true, sql statements issued by the code would
never be committed to the database.
> 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.
