The MySQL Users'Conference will be in April in Santa Clara (hope you can make it).

As chairperson of the ‘Java‘ track, I‘ve been able to persuade someone from each ‘camp‘ (Hibernate/EJB3, JDO and stock JDBC) in the Java persistence world to come and speak about their latest-and-greatest spec or implementation.

I‘m trying to put together an evening BOF/panel discussion with all of these ‘heads-of-state‘ (more on who they are when the conference schedule goes live, later this week, hopefully), and I will most likely be the moderator.

Therefore, I‘m looking for some debate-provoking questions from you guys out there, to get things started.

So, what would you ask the Java persistence heads-of-state?

The MySQL Users'Conference will be in April in Santa Clara (hope you can make it).

As chairperson of the 'Java' track, I've been able to persuade someone from each 'camp' (Hibernate/EJB3, JDO and stock JDBC) in the Java persistence world to come and speak about their latest-and-greatest spec or implementation.

I'm trying to put together an evening BOF/panel discussion with all of these 'heads-of-state' (more on who they are when the conference schedule goes live, later this week, hopefully), and I will most likely be the moderator.

Therefore, I'm looking for some debate-provoking questions from you guys out there, to get things started.

So, what would you ask the Java persistence heads-of-state?

The MySQL Users'Conference will be in April in Santa Clara (hope you can make it).

As chairperson of the ‘Java‘ track, I‘ve been able to persuade someone from each ‘camp‘ (Hibernate/EJB3, JDO and stock JDBC) in the Java persistence world to come and speak about their latest-and-greatest spec or implementation.

I‘m trying to put together an evening BOF/panel discussion with all of these ‘heads-of-state‘ (more on who they are when the conference schedule goes live, later this week, hopefully), and I will most likely be the moderator.

Therefore, I‘m looking for some debate-provoking questions from you guys out there, to get things started.

So, what would you ask the Java persistence heads-of-state?

As part of our build/qa process for Connector/J, we run around 20 thousand different tests across most JVM versions, and the latest shipping MySQL version(s) in the 3.23, 4.0, 4.1 and 5.0 lines.

We're looking into adding some integration testing into that mix, and we'd like to include the popular open source projects that use JDBC into our system. The idea here being that if you use any of these projects, you won't have to wonder whether or not MySQL works with it, and that you'll have a pleasant 'out-of-the-box' feeling with the combination of MySQL and the project in question.

My list would (and does) include the following, in no particular order, anybody care to add any more?

* DBCP
* Hibernate
* JBoss CMP
* Speedo
* Jonas CMP
* Torque
* OJB
* Cayenne
* OFBiz Entity Engine (maybe?)

As part of our build/qa process for Connector/J, we run around 20 thousand different tests across most JVM versions, and the latest shipping MySQL version(s) in the 3.23, 4.0, 4.1 and 5.0 lines.

We‘re looking into adding some integration testing into that mix, and we‘d like to include the popular open source projects that use JDBC into our system. The idea here being that if you use any of these projects, you won‘t have to wonder whether or not MySQL works with it, and that you‘ll have a pleasant ‘out-of-the-box‘ feeling with the combination of MySQL and the project in question.

My list would (and does) include the following, in no particular order, anybody care to add any more?

* DBCP
* Hibernate
* JBoss CMP
* Speedo
* Jonas CMP
* Torque
* OJB
* Cayenne
* OFBiz Entity Engine (maybe?)

A new feature we're trying out with Connector/J 3.1.5 is a 'replication-aware' connection, which is basically a wrapper of two connections, one to a master, and another that is connected to one of a list of read-only slaves.

By signalling that you want a transaction to be read-only by calling Connection.setReadOnly(true), a 'replication-aware' connection will use one of the slave connections, which are load-balanced per-vm using a round-robin scheme (a given connection is 'sticky' to a slave unless that slave is removed from service).

If you have a write transaction, or if you have a read that is 'time-sensitive' (remember, replication in MySQL is asynchronous), you just set the connection to be not read-only, by calling Connection.setReadOnly(false).

The driver takes care of propagating the current state of autocommit, isolation level, and catalog between all of the connections that it uses.

Here's a quick …

A new feature we‘re trying out with Connector/J 3.1.5 is a ‘replication-aware‘ connection, which is basically a wrapper of two connections, one to a master, and another that is connected to one of a list of read-only slaves.

By signalling that you want a transaction to be read-only by calling Connection.setReadOnly(true), a ‘replication-aware‘ connection will use one of the slave connections, which are load-balanced per-vm using a round-robin scheme (a given connection is ‘sticky‘ to a slave unless that slave is removed from service).

If you have a write transaction, or if you have a read that is ‘time-sensitive‘ (remember, replication in MySQL is asynchronous), you just set the connection to be not read-only, by calling Connection.setReadOnly(false).

The driver takes care of propagating the current state of autocommit, isolation level, and catalog between all of the connections that it uses.

…

A new feature we‘re trying out with Connector/J 3.1.5 is a ‘replication-aware‘ connection, which is basically a wrapper of two connections, one to a master, and another that is connected to one of a list of read-only slaves.

By signalling that you want a transaction to be read-only by calling Connection.setReadOnly(true), a ‘replication-aware‘ connection will use one of the slave connections, which are load-balanced per-vm using a round-robin scheme (a given connection is ‘sticky‘ to a slave unless that slave is removed from service).

If you have a write transaction, or if you have a read that is ‘time-sensitive‘ (remember, replication in MySQL is asynchronous), you just set the connection to be not read-only, by calling Connection.setReadOnly(false).

The driver takes care of propagating the current state of autocommit, isolation level, and catalog between all of the connections that it uses.

…

As part of our build/qa process for Connector/J, we run around 20 thousand different tests across most JVM versions, and the latest shipping MySQL version(s) in the 3.23, 4.0, 4.1 and 5.0 lines.

We‘re looking into adding some integration testing into that mix, and we‘d like to include the popular open source projects that use JDBC into our system. The idea here being that if you use any of these projects, you won‘t have to wonder whether or not MySQL works with it, and that you‘ll have a pleasant ‘out-of-the-box‘ feeling with the combination of MySQL and the project in question.

My list would (and does) include the following, in no particular order, anybody care to add any more?

* DBCP
* Hibernate
* JBoss CMP
* Speedo
* Jonas CMP
* Torque
* OJB
* Cayenne
* OFBiz Entity Engine (maybe?)