Message:
The following issue has been closed.
Resolver: Gavin King
Date: Thu, 11 Dec 2003 12:21 AM
I use MySQL + C3P0 with no problems. I think this may have been problematic in an old MySQL driver version.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-322
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-322
Summary: C3P0 autocommit property
Type: Patch
Status: Closed
Priority: Major
Resolution: REJECTED
Project: Hibernate2
Components:
core
Versions:
2.1
Assignee:
Reporter: Craig Raw
Created: Thu, 11 Sep 2003 4:54 AM
Updated: Thu, 11 Dec 2003 12:21 AM
Description:
As discussed in the Hibernate forum, this allows the setting of a C3P0 property, c3p0.autoCommitOnClose, as described in the C3P0 javadoc for com.mchange.v2.c3p0.PoolConfig.
If this property is not set to true, C3P0 will attempt to rollback any pending transactions on connection close. One would ordinarily call commit() on the connection before closing.
In the case of mySQL however, autocommit is turned on by default, and calling commit() results in an exception. C3P0 must be instructed in this case not to rollback any pending transactions, which setting this property to true allows.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
