- C.5.7 Changes in MySQL Connector/J 1.2.x and lower
- C.5.7.1 Changes in MySQL Connector/J 1.2a (14 April 1999)
- C.5.7.2 Changes in MySQL Connector/J 1.1i (24 March 1999)
- C.5.7.3 Changes in MySQL Connector/J 1.1h (08 March 1999)
- C.5.7.4 Changes in MySQL Connector/J 1.1g (19 February 1999)
- C.5.7.5 Changes in MySQL Connector/J 1.1f (31 December 1998)
- C.5.7.6 Changes in MySQL Connector/J 1.1b (03 November 1998)
- C.5.7.7 Changes in MySQL Connector/J 1.1 (02 September 1998)
- C.5.7.8 Changes in MySQL Connector/J 1.0 (24 August 1998)
- C.5.7.9 Changes in MySQL Connector/J 0.9d (04 August 1998)
- C.5.7.10 Changes in MySQL Connector/J 0.9 (28 July 1998)
- C.5.7.11 Changes in MySQL Connector/J 0.8 (06 July 1998)
- C.5.7.12 Changes in MySQL Connector/J 0.7 (01 July 1998)
- C.5.7.13 Changes in MySQL Connector/J 0.6 (21 May 1998)
Got rid of "ugly hack" in MysqlIO.nextRow(). Rather than catch an exception, Buffer.isLastDataPacket() was fixed.
Connection.getCatalog() and Connection.setCatalog() should work now.
Statement.setMaxRows() works, as well as setting by property maxRows. Statement.setMaxRows() overrides maxRows set via properties or url parameters.
Automatic re-connection is available. Because it has to "ping" the database before each query, it is turned off by default. To use it, pass in "autoReconnect=true" in the connection URL. You may also change the number of reconnect tries, and the initial timeout value via "maxReconnects=n" (default 3) and "initialTimeout=n" (seconds, default 2) parameters. The timeout is an exponential backoff type of timeout; for example, if you have initial timeout of 2 seconds, and maxReconnects of 3, then the driver will timeout 2 seconds, 4 seconds, then 16 seconds between each re-connection attempt.
