Modified:
branches/branch_5_0/CHANGES
Log:
Update changelog for 5.0.9 release.
Modified: branches/branch_5_0/CHANGES
===================================================================
--- branches/branch_5_0/CHANGES 2007-11-16 16:50:29 UTC (rev 6667)
+++ branches/branch_5_0/CHANGES 2007-11-16 16:53:29 UTC (rev 6668)
@@ -1,8 +1,16 @@
# Changelog
# $Id$
-nn-nn-07 - Version 5.0.8
+nn-nn-07 - Version 5.0.9
+ - Driver now calls SocketFactory.afterHandshake() at appropriate time.
+
+ - Fixed an issue where PreparedStatement.setObject(int, Object, int)
+ didn't handle String values of "1" or "0" for the target SQL type
+ of BIT properly.
+
+10-09-07 - Version 5.0.8
+
- Fixed BUG#30550, executeBatch() would fail with an ArithmeticException
and/or NullPointerException when the batch had zero members and
"rewriteBatchedStatements" was set to "true" for the connection.
@@ -64,10 +72,33 @@
- Fixed Bug#30892 setObject(int, Object, int, int) delegate in
PreparedStatmentWrapper delegates to wrong method.
- - Fixed an issue where PreparedStatement.setObject(int, Object, int)
- didn't handle String values of "1" or "0" for the target SQL type
- of BIT properly.
+ - XAConnections now start in auto-commit mode (as per JDBC-4.0 specification
+ clarification).
+
+ - Fixed Bug#27412 - cached metadata with PreparedStatement.execute()
+ throws NullPointerException.
+ - Driver will now fall back to sane defaults for max_allowed_packet and
+ net_buffer_length if the server reports them incorrectly (and will log
+ this situation at WARN level, since it's actually an error condition).
+
+ - Fixed BUG#27916 - UNSIGNED types not reported via DBMD.getTypeInfo(), and
+ capitalization of type names is not consistent between DBMD.getColumns(),
+ RSMD.getColumnTypeName() and DBMD.getTypeInfo().
+
+ This fix also ensures that the precision of UNSIGNED MEDIUMINT
+ and UNSIGNED BIGINT is reported correctly via DBMD.getColumns().
+
+ - Fixed BUG#31053 - Connections established using URLs of the form
+ "jdbc:mysql:loadbalance://" weren't doing failover if they tried to
+ connect to a MySQL server that was down. The driver now attempts
+ connections to the next "best" (depending on the load balance strategy
+ in use) server, and continues to attempt connecting to the next "best"
+ server every 250 milliseconds until one is found that is up and running
+ or 5 minutes has passed.
+
+ If the driver gives up, it will throw the last-received SQLException.
+
07-19-07 - Version 5.0.7
- Setting the configuration parameter "useCursorFetch" to "true" for
| Thread |
|---|
| • Connector/J commit: r6668 - branches/branch_5_0 | mmatthews | 16 Nov |