We‘re changing the version number on all connectivity libraries at MySQL (ODBC, ADO.Net, JDBC) to match the latest version of the server they work with, so the “next“ version of Connector/J will be 5.0.0.

5.0.0 should be released in the next week or so, but if you want to try out XA (the major new feature that it includes), head on over to http://downloads.mysql.com/snapshots.php#connector-j

The 5.0.x series of Connector/J is really the latest 3.1 with XA and support for server-side cursor-based row fetching backported into it, so it should progress to “stable“ quite quickly.

Connector/J 5.0 also has a neat feature in that you can integrate it with Connector/MXJ (the JMX and/or POJO object wrapper for MySQL server) as simply as putting the .jar for Connector/MXJ and the .jar for the JDBC driver in your classpath, and using “jdbc:mysql:mxj://“ for your URL prefix. That feature, in combination with the …

We're changing the version number on all connectivity libraries at MySQL (ODBC, ADO.Net, JDBC) to match the latest version of the server they work with, so the "next" version of Connector/J will be 5.0.0.

5.0.0 should be released in the next week or so, but if you want to try out XA (the major new feature that it includes), head on over to http://downloads.mysql.com/snapshots.php#connector-j

The 5.0.x series of Connector/J is really the latest 3.1 with XA and support for server-side cursor-based row fetching backported into it, so it should progress to "stable" quite quickly.

Connector/J 5.0 also has a neat feature in that you can integrate it with Connector/MXJ (the JMX and/or POJO object wrapper for MySQL server) as simply as putting the .jar for Connector/MXJ and the .jar for the JDBC driver in your classpath, and using "jdbc:mysql:mxj://" for your URL prefix. That feature, in combination with the …

We‘re changing the version number on all connectivity libraries at MySQL (ODBC, ADO.Net, JDBC) to match the latest version of the server they work with, so the “next“ version of Connector/J will be 5.0.0.

5.0.0 should be released in the next week or so, but if you want to try out XA (the major new feature that it includes), head on over to http://downloads.mysql.com/snapshots.php#connector-j

The 5.0.x series of Connector/J is really the latest 3.1 with XA and support for server-side cursor-based row fetching backported into it, so it should progress to “stable“ quite quickly.

Connector/J 5.0 also has a neat feature in that you can integrate it with Connector/MXJ (the JMX and/or POJO object wrapper for MySQL server) as simply as putting the .jar for Connector/MXJ and the .jar for the JDBC driver in your classpath, and using “jdbc:mysql:mxj://“ for your URL prefix. That feature, in combination with the …

We‘re on the cusp of releasing Connector/J 5.0.0, which will replace the Connector/J 3.2 version (which never made it out of alpha). We‘re synchronizing the version numbers of the various connectors at MySQL (JDBC, ODBC, ADO.Net) so that‘s it‘s easier to tell what version of the server a given connector version works best with (no we‘re not going to have an internal version number of 3.5 and call the JDBC driver Connector/J 5.0 either like some other vendor we know ;) ).

Basically, Connector/J 5.0 is Connector/J 3.1 (which is already in production for some time now), with the XA functionality of 3.2 backported into it, which is why we‘re releasing it as a BETA out of the gate.

The 5.0 codebase also had some house cleaning done to the Ant build files. Some of that house cleaning involved getting the multi-jvm, multi-mysql-server-version Emma coverage reports working again. We‘re going to start bundling these reports, …

We're on the cusp of releasing Connector/J 5.0.0, which will replace the Connector/J 3.2 version (which never made it out of alpha). We're synchronizing the version numbers of the various connectors at MySQL (JDBC, ODBC, ADO.Net) so that's it's easier to tell what version of the server a given connector version works best with (no we're not going to have an internal version number of 3.5 and call the JDBC driver Connector/J 5.0 either like some other vendor we know ;) ).

Basically, Connector/J 5.0 is Connector/J 3.1 (which is already in production for some time now), with the XA functionality of 3.2 backported into it, which is why we're releasing it as a BETA out of the gate.

The 5.0 codebase also had some house cleaning done to the Ant build files. Some of that house cleaning involved getting the multi-jvm, multi-mysql-server-version Emma coverage reports working again. We're going to start bundling these reports, along with the …

We‘re on the cusp of releasing Connector/J 5.0.0, which will replace the Connector/J 3.2 version (which never made it out of alpha). We‘re synchronizing the version numbers of the various connectors at MySQL (JDBC, ODBC, ADO.Net) so that‘s it‘s easier to tell what version of the server a given connector version works best with (no we‘re not going to have an internal version number of 3.5 and call the JDBC driver Connector/J 5.0 either like some other vendor we know ;) ).

Basically, Connector/J 5.0 is Connector/J 3.1 (which is already in production for some time now), with the XA functionality of 3.2 backported into it, which is why we‘re releasing it as a BETA out of the gate.

The 5.0 codebase also had some house cleaning done to the Ant build files. Some of that house cleaning involved getting the multi-jvm, multi-mysql-server-version Emma coverage reports working again. We‘re going to start bundling these reports, …

This series began at Part the First, which is still in rough draft form. Be sure to read the first article before continuing with this article.

The following sync programs were installed with the MySQL MaxDB
server in the first article:

$ file `sudo find /opt/sdb/ -iname "*sync*" | head -4`
/opt/sdb/programs/bin/syncmanjconf: Bourne shell script text executable
/opt/sdb/programs/bin/syncservice:  Bourne shell script text executable
/opt/sdb/programs/bin/syncmanacc:   Bourne shell script text executable
/opt/sdb/programs/bin/syncmangui:   Bourne shell script text executable

These applications require the j2ee sdk in order to run. You can
download the version presented in this article from …

Looking at the referers for this weblog, it seems a lot of you out there upgrading to Connector/J 3.1 are having issues with the two following changes:

Connector/J 3.1 now detects data truncation, and throws exceptions when it happens

Connector/J 3.1 doesn‘t silently convert all-zero date/time/timestamp/datetime values to NULL like Connector/J 3.0.x and older did.

Since we‘re trying to make Connector/J be JDBC-compliant out-of-the-box without any special configuration values, it sometimes surprises users when these changes happen (they‘re documented in the CHANGES file that comes with the driver, and we‘ve started to do a better job of categorizing them in an ‘For Upgraders‘ section in our manual).

Let‘s deal with data truncation first. The MySQL server started to be able to do something meaningful with truncation in version 4.1. Before that, it would tell you that data for some columns was …

Looking at the referers for this weblog, it seems a lot of you out there upgrading to Connector/J 3.1 are having issues with the two following changes:

Connector/J 3.1 now detects data truncation, and throws exceptions when it happens

Connector/J 3.1 doesn't silently convert all-zero date/time/timestamp/datetime values to NULL like Connector/J 3.0.x and older did.

Since we're trying to make Connector/J be JDBC-compliant out-of-the-box without any special configuration values, it sometimes surprises users when these changes happen (they're documented in the CHANGES file that comes with the driver, and we've started to do a better job of categorizing them in an 'For Upgraders' section in our manual).

Let's deal with data truncation first. The MySQL server started to be able to do something meaningful with truncation in version 4.1. Before that, it would tell you that data for some columns was truncated, but …

Looking at the referers for this weblog, it seems a lot of you out there upgrading to Connector/J 3.1 are having issues with the two following changes:

Connector/J 3.1 now detects data truncation, and throws exceptions when it happens

Connector/J 3.1 doesn‘t silently convert all-zero date/time/timestamp/datetime values to NULL like Connector/J 3.0.x and older did.

Since we‘re trying to make Connector/J be JDBC-compliant out-of-the-box without any special configuration values, it sometimes surprises users when these changes happen (they‘re documented in the CHANGES file that comes with the driver, and we‘ve started to do a better job of categorizing them in an ‘For Upgraders‘ section in our manual).

Let‘s deal with data truncation first. The MySQL server started to be able to do something meaningful with truncation in version 4.1. Before that, it would tell you that data for some columns was …