MySQL Lists are EOL. Please join:

List:Announcements« Previous MessageNext Message »
From:Mark Matthews Date:May 19 2004 7:53pm
Subject:MySQL Connector/J 3.0.12 (Production) Has Been Released
View as plain text  
Hash: SHA1


MySQL Connector/J 3.0.12, a new version of the Type-IV all-Java JDBC
driver for MySQL has been released.

Version 3.0.12 is a bugfix release for the production tree that is
suitable for use with any MySQL version including MySQL-4.1 or MySQL-5.0.

It is now available in source and binary form from the Connector/J
download pages at
and mirror sites (note that not all mirror sites may be up to date at
this point of time - if you can't find this version on some mirror,
please try again later or choose another download site.)


- From the changelog:

    - Add unsigned attribute to DatabaseMetaData.getColumns() output in
the TYPE_NAME column.
    - Added 'failOverReadOnly' property, to allow end-user to configure
state of connection (read-only/writable) when failed over.
    - Backported 'change user' and 'reset server state' functionality
      from 3.1 branch, to allow clients of MysqlConnectionPoolDataSource
      to reset server state on getConnection() on a pooled connection.
    - Don't escape SJIS/GBK/BIG5 when using MySQL-4.1 or newer.
    - Allow 'url' parameter for MysqlDataSource and MysqlConnectionPool
      DataSource so that passing of other properties is possible from
      inside appservers.
    - Map duplicate key and foreign key errors to SQLState of
    - Backport documentation tooling from 3.1 branch.
    - Return creating statement for ResultSets created by
      getGeneratedKeys() (BUG#2957)
    - Allow java.util.Date to be sent in as parameter to
      PreparedStatement.setObject(), converting it to a Timestamp
      to maintain full precision (BUG#3103).
    - Don't truncate BLOBs/CLOBs when using setBytes() and/or
      setBinary/CharacterStream() (BUG#2670).
    - Dynamically configure character set mappings for field-level
      character sets on MySQL-4.1.0 and newer using 'SHOW COLLATION'
      when connecting.
    - Map 'binary' character set to 'US-ASCII' to support DATETIME
      charset recognition for servers >= 4.1.2
    - Use 'SET character_set_results" during initialization to allow any
      charset to be returned to the driver for result sets.
    - Use charsetnr returned during connect to encode queries before
      issuing 'SET NAMES' on MySQL >= 4.1.0.
    - Add helper methods to ResultSetMetaData (getColumnCharacterEncoding()
      and getColumnCharacterSet()) to allow end-users to see what
charset the driver thinks it should be using for the column.
    - Only set character_set_results for MySQL >= 4.1.0.
    - Fixed BUG#3511, StringUtils.escapeSJISByteStream() not covering
all eastern double-byte charsets correctly.
    - Renamed StringUtils.escapeSJISByteStream() to more appropriate
    - Fixed BUG#3554 - Not specifying database in URL caused
MalformedURL exception.
    - Auto-convert MySQL encoding names to Java encoding names if used
      for characterEncoding property.
    - Added encoding names that are recognized on some JVMs to fix case
      where they were reverse-mapped to MySQL encoding names incorrectly.
    - Use junit.textui.TestRunner for all unit tests (to allow them to
be run from the command line outside of Ant or Eclipse).
    - Fixed BUG#3557 - UpdatableResultSet not picking up default values
      for moveToInsertRow().
    - Fixed BUG#3570 - inconsistent reporting of column type. The server
      still doesn't return all types for *BLOBs *TEXT correctly, so the
      driver won't return those correctly.
    - Fixed BUG#3520 -- DBMD.getSQLStateType() returns incorrect value.
    - Fixed regression in PreparedStatement.setString() and eastern
character encodings.
    - Made StringRegressionTest 4.1-unicode aware.
Version: GnuPG v1.2.3 (MingW32)
Comment: Using GnuPG with Thunderbird -

MySQL Connector/J 3.0.12 (Production) Has Been ReleasedMark Matthews19 May