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 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)
  • DatabaseMetaData.getSuperTypes() (implementation returns 0 rows)

• Consistent, compatible with ConnectorJ handling of JDBC catalogs vs schemas vs databases. 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 current database name
  • ResultSetMetaData.getSchemaName() will return an empty string.