JDBC Driver
The JDBC Driver is a pure Java implementation of the JDBC 4.1 API released with Oracle Java Platform SE 7. The driver supports application, applet, and servlet access to Ingres data sources through the Data Access Server.
The JDBC Driver supports the following JDBC features.
JDBC 4.1 features:
The following new methods are fully supported:
• Connection.abort()
• Connection.getNetworkTimeout() and Connection.setNetworkTimeout()
• DatabaseMetaData.generatedKeyAlwaysReturned()
• Statement.isCloseOnCompletion() and Statement.closeOnCompletion()
• CallableStatement.getObject( int, Class<T> ) and CallableStatement.getObject( String, Class<T> )
• ResultSet.getObject( int, Class<T> ) and ResultSet.getObject( String, Class<T> )
The following new methods are implemented with restrictions:
• Driver.getParentLogger() and DataSource.getParentLogger()
The JDBC Driver does not directly support Java Logging and these methods throw a SQLFeatureNotSupportedException. JDBC Driver tracing can be output through Java Logging. For details, see
JDBC Tracing (see page
JDBC Tracing).
• Connection.getSchema() and Connection.setSchema()
Ingres and Vector support schema names as the owner of the referenced object and do not support a general SET SCHEMA statement. In accordance with JDBC standards when schemas are not supported, setSchema() does nothing and getSchema() returns null.
• DatabaseMetaData.getPseudoColumns()
The only pseudo column supported by Ingres is 'tid'. The method parameters are used to query the iitables system catalog and then column information for a 'tid' column is returned for each resulting table.
JDBC 4.0 features:
• Auto-loading of the driver
• National Character Set Support
• Support for createBlob(), createClob(), and createNClob Methods
• Support for java.sql.Wrapper Interface
JDBC 3.0 features:
• Updatable ResultSets
• Scrollable ResultSets
• Transaction savepoints
• Named procedure parameters
• Auto-generated keys
• Parameter metadata
• Blob and clob data objects
The JDBC Driver is delivered as a single Java archive file, named iijdbc.jar, located in the library directory (lib) of the Ingres instance. Depending on the Java environment used, access to the driver requires adding the Java archive to the CLASSPATH environment setting or as a resource in the appropriate utility. For browser/applet access, the Java archive must be copied to the Web Server directories.