Issue Details (XML | Word | Printable)

Key: NUCCONPOOL-4
Type: Task Task
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Andy Jefferson
Reporter: Andy Jefferson
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
DataNucleus ConnectionPool (ARCHIVED)

Default to autocommit=false for DBCP to cater for primary use-cases

Created: 14/Jun/10 01:42 PM   Updated: 13/Nov/10 12:17 PM   Resolved: 14/Jun/10 02:17 PM
Component/s: DBCP
Affects Version/s: None
Fix Version/s: 2.0.3


 Description  « Hide
The majority of operations for JDO/JPA ought to be transactional. Therefore we should default to having autoCommit as false (for DBCP which allows us to set it).

Andy Jefferson made changes - 14/Jun/10 02:08 PM
Field Original Value New Value
Summary Default to autocommit=false (DBCP), and to have a value for number of prepared statements Default to autocommit=false for DBCP to cater for primary use-cases
Fix Version/s 2.0.3 [ 10998 ]
Description The majority of operations for JDO/JPA ought to be transactional. Therefore we should default to having autoCommit as false (for DBCP which allows us to set it).

Also we ought to default to caching PreparedStatements
The majority of operations for JDO/JPA ought to be transactional. Therefore we should default to having autoCommit as false (for DBCP which allows us to set it).
Component/s DBCP [ 10194 ]
Andy Jefferson added a comment - 14/Jun/10 02:17 PM
SVN trunk has this enabled. Proxool and C3P0 don't seem to provide a way of setting the default "autoCommit" value

Andy Jefferson made changes - 14/Jun/10 02:17 PM
Status Open [ 1 ] Resolved [ 5 ]
Resolution Fixed [ 1 ]
Andy Jefferson made changes - 13/Nov/10 12:17 PM
Status Resolved [ 5 ] Closed [ 6 ]