- C.6.7 Changes in MySQL Connector/J 1.2.x and lower
- C.6.7.1 Changes in MySQL Connector/J 1.2a (14 April 1999)
- C.6.7.2 Changes in MySQL Connector/J 1.1i (24 March 1999)
- C.6.7.3 Changes in MySQL Connector/J 1.1h (08 March 1999)
- C.6.7.4 Changes in MySQL Connector/J 1.1g (19 February 1999)
- C.6.7.5 Changes in MySQL Connector/J 1.1f (31 December 1998)
- C.6.7.6 Changes in MySQL Connector/J 1.1b (03 November 1998)
- C.6.7.7 Changes in MySQL Connector/J 1.1 (02 September 1998)
- C.6.7.8 Changes in MySQL Connector/J 1.0 (24 August 1998)
- C.6.7.9 Changes in MySQL Connector/J 0.9d (04 August 1998)
- C.6.7.10 Changes in MySQL Connector/J 0.9 (28 July 1998)
- C.6.7.11 Changes in MySQL Connector/J 0.8 (06 July 1998)
- C.6.7.12 Changes in MySQL Connector/J 0.7 (01 July 1998)
- C.6.7.13 Changes in MySQL Connector/J 0.6 (21 May 1998)
Implemented getTypeInfo(). Connection.rollback() now throws an SQLException per the JDBC spec.
Added PreparedStatement that supports all JDBC API methods for PreparedStatement including InputStreams. Please check this out and let me know if anything is broken.
Fixed a bug in ResultSet that would break some queries that only returned 1 row.
Fixed bugs in DatabaseMetaData.getTables(), DatabaseMetaData.getColumns() and DatabaseMetaData.getCatalogs().
Added functionality to Statement that allows executeUpdate() to store values for IDs that are automatically generated for AUTO_INCREMENT fields. Basically, after an executeUpdate(), look at the SQLWarnings for warnings like "LAST_INSERTED_ID = 'some number', COMMAND = 'your SQL query'". If you are using AUTO_INCREMENT fields in your tables and are executing a lot of executeUpdate()s on one Statement, be sure to clearWarnings() every so often to save memory.
User Comments
Add your own comment.