MariaDB Java Client 1.1.0 Release Notes

Download | Release Notes | Changelog

Release date: 15 Jan 2013

MariaDB Java Client 1.1.0 is a Stable (GA) release. In general this means that there are no known serious bugs, except for those marked as feature requests, that no bugs were fixed since last release that caused a notable code changes, and that we believe the code is ready for general usage (based on bug inflow).

For a list of changes made in this release, with links to detailed information on each push, see the changelog.

Here is a list of the important changes in this release

• Implemented several missing methods in DatabaseMetaData (CONJ-11) Implementation for these methods was missing in the past and is now corrected :
  • DatabaseMetaData.getTypeInfo()
  • DatabaseMetaData.getProcedures()
  • DatabaseMetaData.getFunctions()
  • DatabaseMetaData.getProcedureColumns()
  • DatabaseMetaData.getFunctionColumns()
  • DatabaseMetaData.getSuperTables() (implementation returns 0 rows,but correct result set metadata)
  • DatabaseMetaData.getSuperTypes() (implementation returns 0 rows, but correct result set metadata)

• Consistent, compatible with ConnectorJ handling of JDBC catalogs vs schemas vs databases (CONJ-10, CONJ-9, CONJ-8) All DatabaseMetaData methods that return catalog or schema name, or accept catalog or schema as input parameter, will handle catalog input parameter as database name, and will return current database name in the "TABLE_CAT" column and null for "TABLE_SCHEM" column. This handling is consistent with ConnectorJ handling for catalogs. Here is the list of affected methods :
  • DatabaseMetaData.getTables()
  • DatabaseMetaData.getColumns()
  • DatabaseMetaData.getColumnPrivileges()
  • DatabaseMetaData.getTablePrivileges()
  • DatabaseMetaData.getPrimaryKeys()
  • DatabaseMetaData.getImportedKeys()
  • DatabaseMetaData.getExportedKeys()
  • DatabaseMetaData.getCrossReference()
  • DatabaseMetaData.getIndexInfo()
  • ResultSetMetaData.getCatalogName() will now return database name
  • ResultSetMetaData.getSchemaName() will return an empty string.
  • Methods DatabaseMetaData.supportsSchemasInDataManipulation(), DatabaseMetaData.supportsSchemasInTableDefinitions(), DatabaseMetaData.supportsSchemasInPrivilegeDefinitions() will return false indicating that schemas are not supported. DatabaseMetaData.supportsCatalogsInDataManipulation(), DatabaseMetaData.supportsCatalogsInTableDefinitions(), DatabaseMetaData.supportsCatalogsInPrivilegeDefinitions() all return true (catalogs are supported).

• Handling of statement timeout is now fixed (CONJ-1) Prior implementation was based on socket timeouts and did not work well due to a Java bug (socket can't recover after a timeout)

• Driver can be used in OSGi environments now - it includes OSGi-specific entries in MANIFEST.MF (CONJ-2)

• Support dumpQueriesOnException=true in the JDBC URL (CONJ-12) . The effect of this parameter is such that query text is included into exception message. Additionally, query text is dumped on MySQL syntax errors, no matter if this parameter is set or not.

• It is now possible to use IPv6 addresses with the connector using RFC2732 syntax with square brakets, for example jdbc:mysql:[::1]:3306 for IPv6-capable server running on local machine, port 3306 (CONJ-7)

• SSL support. useSSL=true parameter is now functional. Additionally, trustServerCertificates=true can be set, to avoid checking server certificate validity.

• sessionVariables driver URL parameter is now supported.
• LOAD DATA LOCAL INFILE can use generic URLs (e.g http) for file specification
• SQL Comments are not stripped anymore off PreparedStatements.
• Fixed ArrayOutOfBounds exception when parsing JDBC (CONJ-4)
• Fixed exception in Connection.getWarnings(), which was throws is connection was closed