Getting Started : Product and installation package information : solidDB® server package : ODBC, JDBC, and proprietary programming interfaces
  
ODBC, JDBC, and proprietary programming interfaces
The solidDB® server provides ODBC, JDBC and proprietary interfaces for clients. For more details, see the solidDB® Programmer Guide.
solidDB® JDBC Driver 2.0 key information
Compatibility
JDBC 2.0, with selected features of JDBC 2.0 Optional Package
Driver location
<solidDB® installation directory>/jdbc/SolidDriver2.0.jar
JDBC URL format
jdbc:solid://<hostname>:<port>/<username>/<password>[?<property-name>=<value>]...
For example:
"jdbc:solid://localhost:1964/dba/dba"
Driver class name
solid.jdbc.SolidDriver
Standard compliance
The solidDB® JDBC 2.0 Driver supports the JDBC 2.0 specification. Additionally, Connection Pooling, JNDI Data Sources, and Rowsets of the JDBC 2.0 Optional Package (known before as Standard Extension) are supported too.
Non-standard features include support for IBM WebSphere and timeout control extensions.
The following features of the Optional Package are currently supported by the solidDB® JDBC 2.0 driver:
Connection pooling (class solid.jdbc.ConnectionPoolDataSource)
Connected RowSet (class solid.jdbc.rowset.SolidJDBCRowSet)
Implemented JDBC data sources:
– solid.jdbc.DataSource (implements javax.sqlDataSource)
– solid.jdbc.SolidConnectionPoolDataSource (implements javax.sql.ConnectionPoolDataSource)
JTA (Java Transaction API) – XA interface for Java (implements javax.transaction.xa.XAResource and javax.transaction.xa.Xid)
Full documentation for the solidDB® JDBC Driver is included in the solidDB® Programmer Guide.
solidDB® JDBC Driver extensions
The solidDB® JDBC Driver supports the following non-standard extensions. For more information, see the solidDB® Programmer Guide.
JDBC URL format
You can set the connection property values in the URL string.
Connection timeout
Connection timeout refers to the response timeout of any JDBC call that invokes data transmission over a connection socket. If the response message is not received within the time that is specified, an I/O exception is thrown. The JDBC standard (2.0/3.0) does not support setting of the connection timeout. The solidDB® product has two ways for doing that: one using a non-standard driver manager extension method and the other using the property mechanisms. The time unit in either case is 1 ms.
Login timeout
The timeout fires at the connect time. The setting is implemented with a connection property. The property overrides the login timeout for JDBC specified by other means (like login timeout parameter in Driver Manager).
Connection idle timeout
If the connection is inactive for the amount of time specified with the idle timeout property, the server closes the connection. The connection idle timeout property overrides the server parameter setting for the session.
Statement cache
You can set the size of the statement cache for a connection.
Transparent Connectivity Support
solidDB® JDBC driver fully supports solidDB® Transparent Connectivity (TC) including transparent failover and load balancing. See the solidDB® High Availability User Guide for more information about usage of Transparent Connectivity.
Shared memory access (SMA) connection property
The SMA connection property defines that the driver connects to a SMA server with a local connection, bypassing network protocols.
Catalog and schema name connection properties
You can set the catalog and schema names for the connection.
WebSphere support
To support WebSphere, a data source adapter SolidDataStoreHelper is provided in a separate file SolidDataStoreHelper.jar, in the 'jdbc' directory of the solidDB® package.
solidDB® ODBC Driver 3.5.x
solidDB® provides two ODBC drivers, one for Unicode and one for ASCII character sets. For more information about these drivers, see the solidDB® Programmer Guide.
The following functions are not supported:
SQLBrowseConnect
SQLSetScrollOptions
SQLParamOptions
SQLNativeSql
SQLMoreResults
ODBC extensions
solidDB® ODBC driver incorporates several extensions for, for example, timeout controls, statement cache behavior, and support for Transparent Connectivity. For more information, see the solidDB® Programmer Guide.
Proprietary interfaces
The solidDB® Application Programming Interface (SA API) and solidDB® Server Control API (SSC API) allow, for example, C programs to directly call functions inside the database server. These proprietary interfaces are provided with the solidDB® shared memory access (SMA) and linked library access (LLA) libraries.
See also
solidDB® server package