JDBC Features Not Implemented in InterClient
Go Up to InterClient/JDBC Compliance Specifications
Although all JDBC classes and methods must be implemented in order to create a JDBC-compliant driver, some features are not actually supported.
InterBase XE3U3 introduces a new connection property in the JDBC driver, returnColumnLabelAsColumnName. Pentaho requires ResultSetMetaData.getColumnName() to actually return the alias/label name (if provided by the application). In order to comply with JDBC specifications, and to keep backward compatibility for existing InterBase JDBC apps, this new connection property will be FALSE by default.
If you want to use the new property for the Pentaho-type behavior, set the following connection property:
properties.put(“returnColumnLabelAsColumnName”, “true”)
Unsupported features throw a SQLException error message.
The following table lists the JDBC classes, methods, and features not supported by this version of InterClient.
java.sql Subclass | Feature | Description |
---|---|---|
CallableStatement |
OUT parameters |
InterBase does not support OUT parameters in stored procedures. |
Escape processing for stored |
InterClient does not support escape syntax with a result parameter. | |
Statement, |
Escape processing: |
InterClient does not support. |
Statement, |
Escape processing: |
time escape clause not supported. |
Connection |
|
InterBase does not support catalogs. |
|
Not supported. | |
|
Login timeouts are not supported in this release. | |
|
Asynchronous cancels are not supported in this release. | |
Types |
BIT<br/> TINYINT<br/> BIGINT |
InterBase does not support these data types. |
DatabaseMetaData |
|
InterBase does not support catalogs or schemas. |
PreparedStatement |
|
InterClient does not support Unicode. |
ResultSetMetaData |
|
InterBase does not support catalogs or schemas. |