The Ultimate Guide to High Availability with MariaDB

Release Notes 1.1.0

You are viewing an old version of this article. View the current version here.

Here is the list of important changes in 1.1.0 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.

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.