Neoview JDBC Type 4 Driver Programmer's Reference (R2.2, R2.3, R2.4, R2.5)
Mimics the
DatabaseMetaData.getBestRowIdentifier()
method because Neoview SQL does not support
SQL_ROWVER (a columns function that returns the
column or columns in the specified table, if any, that are
automatically updated by the data source when any value
in the row is updated by any transaction).
java.sql.DatabaseMetaData.getVersionColumns()
The Type 4 driver does not support the scroll-sensitive
result set type, so an SQLWarning is issued if an
application requests that type. The result set is changed to
a scroll-insensitive type.
java.sql.Connection.createStatement(...)
java.sql.Connection.prepareStatement(...)
The fetch direction attribute is ignored.
java.sql.ResultSet.setFetchDirection(...)
In some instances, drops the connection to the server
instead of just cancelling the query. You must then
reconnect to the server. Note that the connection is dropped
if cancel() is issued for a statement that is being
processed. Otherwise the connection is maintained.
java.sql.Statement.cancel()
Because Neoview SQL parses the escape syntax, disabling
escape processing has no effect.
java.sql.Statement.setEscapeProcessing(...)
The fetch direction attribute is ignored.
java.sql.Statement.setFetchDirection(...)
HP Extensions
The HP extensions to the JDBC standard implemented in the Type 4 driver are:
• “Internationalization of Messages”
• “Additional DatabaseMetaData APIs”
• “Additional Connection APIs”
Internationalization of Messages
The Type 4 driver is designed so that Java messages can be adopted for various languages. The
error messages are stored outside the source code in a separate property file and retrieved
dynamically based on the locale setting. The error messages in different languages are stored in
separate property files based on the language and country. This extension does not apply to all
messages that can occur when running JDBC applications.
For details, see “Localizing Error Messages and Status Messages” (page 32).
Additional DatabaseMetaData APIs
APIs added to the HPT4DatabaseMetaData class provide these capabilities:
• Get a description of a table's synonyms.
public java.sql.ResultSet getSynonymInfo(String catalog,
String schema, String table) throws SQLException
• Get a description of a table's materialized views.
public java.sql.ResultSet getMaterializedViewInfo(String catalog,
String schema, String table) throws SQLException
Additional Connection APIs
APIs added to the HPT4Connection class provide these capabilities:
• Sets the current service name for this Connection object.
public void setServiceName(String serviceName) throws SQLException
• Gets (retrieves) the current service name of this Connection object. Default return value:
HP_DEFAULT_SERVICE.
68 Type 4 Driver Compliance