Product Documentation

V11.5 Release Notes

Previous Topic

Next Topic

JDBC catalog handling in DatabaseMetaData was not compliant with JDBC standard

The return values from these functions was not correct and was causing issues using third-party reporting tools, such as Jasper Reports. The returns have been corrected as follows:

  • DatabaseMetaData.isCatalogAtStart() returns false indicating that c-tree does not support specifying catalog in fully-qualified table names (FQN).
  • DatabaseMetaData.getCatalogSeparator() returns "".
  • DatabaseMetaData.getMaxCatalogNameLength() returns 0.

TOCIndex