MySQL Connector/J 3.0.17(MySQL用のタイプ４のall-Java JDBCドライバ)が リリースされました。
バージョン3.0.17は、MySQL-4.1、MySQL-5.0を含んだいくつかのMySQLのバージョンでの使用にふさわしい安定版のバグ対処リリースです。 (それはMySQL-4.1、MySQL-5.0に最小の「新しい」機能性を提供しますがMySQL-4.1、MySQL-5.0に接続するユーザは、コネクター/J 3.1.xを使用するべきです)
バージョン3.0.17は、http://dev.mysql.com/downloads/connector/j/3.0.htmlおよびミラーサイトのConnector/Jダウンロードページからソースおよびバイナリ形式で入手可能です。(すべてのミラーサイトが現在において最新であるとは限らないかもしれないことに注意してください。あるミラーサイトでこのバージョンを見つけることができない場合は、再度確認を行うか、あるいは別のダウンロード・サイトを選択してください。)
以下は変更ログから。
06-22-05 – Version 3.0.17-ga
– Fixed BUG#5874, Timestamp/Time conversion goes in the
wrong ‘direction’ when useTimeZone=’true’ and server timezone differs from client timezone.
– Fixed BUG#7081, DatabaseMetaData.getIndexInfo()
ignoring ‘unique’ parameter.
– Support new protocol type ‘MYSQL_TYPE_VARCHAR’.
– Added ‘useOldUTF8Behavoior’ configuration property,
which causes JDBC driver to act like it did with MySQL-4.0.x and earlier when the character encoding is ‘utf-8’ when connected to MySQL-4.1 or newer.
– Fixed BUG#7316 – Statements created from a pooled
connection were returning physical connection instead of logical connection when getConnection() was called.
– Fixed BUG#7033 – PreparedStatements don’t encode Big5
(and other multibyte) character sets correctly in static SQL strings.
– Fixed BUG#6966, connections starting up failed-over
(due to down master) never retry master.
– Fixed BUG#7061, PreparedStatement.fixDecimalExponent()
adding extra ‘+’, making number unparseable by MySQL server.
– Fixed BUG#7686, Timestamp key column data needed
"_binary’" stripped for UpdatableResultSet.refreshRow().
– Backported SQLState codes mapping from Connector/J 3.1,
enable with ‘useSqlStateCodes=true’ as a connection property, it defaults to ‘false’ in this release, so that we don’t break legacy applications (it defaults to ‘true’ starting with Connector/J 3.1).
– Fixed BUG#7601, PreparedStatement.fixDecimalExponent()
adding extra ‘+’, making number unparseable by MySQL server.
– Escape sequence {fn convert(…, type)} now supports
ODBC-style types that are prepended by ‘SQL_’.
– Fixed duplicated code in configureClientCharset() that
prevented useOldUTF8Behavior=true from working properly.
– Handle streaming result sets with > 2 billion rows
properly by fixing wraparound of row number counter.
– Fixed BUG#7607 – MS932, SHIFT_JIS and Windows_31J not
recog. as aliases for sjis.
– Fixed BUG#6549 (while fixing #7607), adding ‘CP943’ to
aliases for sjis.
– Fixed BUG#8064, which requires hex escaping of binary
data when using multibyte charsets with prepared statements.
– Fixed BUG#8812, NON_UNIQUE column from
DBMD.getIndexInfo() returned inverted value.
– Workaround for server BUG#9098 – default values of
CURRENT_* for DATE/TIME/TIMESTAMP/TIMESTAMP columns can’t be distinguished from ‘string’ values, so UpdatableResultSet.moveToInsertRow() generates bad SQL for inserting default values.
– Fixed BUG#8629 – ‘EUCKR’ charset is sent as ‘SET NAMES
euc_kr’ which MySQL-4.1 and newer doesn’t understand.
– DatabaseMetaData.supportsSelectForUpdate() returns
correct value based on server version.
– Use hex escapes for PreparedStatement.setBytes() for
double-byte charsets including ‘aliases’ Windows-31J, CP934, MS932.
– Added support for the "EUC_JP_Solaris" character
encoding, which maps to a MySQL encoding of "eucjpms" (backported from 3.1 branch). This only works on servers that support eucjpms, namely 5.0.3 or later.