|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
Hi Steve,
Hibernate until 4.1.7 was not requiring JDBC4. We have been using 4.1.6 (could not use 4.1.7 because of a memory leak) with c3p0 that is only supporting JDBC 3 for months on production systems without any issue. The JDBC 4 requirement has just been recently introduced in 4.1.8 by
HHH-7698.Changing back org.hibernate.engine.jdbc.CharacterStream.getLength() and org.hibernate.engine.jdbc.BinaryStream.getLength() to return an int rather than a long (like it use to before
HHH-7698) would remove the JDBC 4 requirement.