InterBase Features Not Available through InterClient or JDBC
Go Up to InterClient/JDBC Compliance Specifications
The following table lists InterBase features that are currently unavailable to InterClient developers.
| Unsupported InterBase Feature | Description |
|---|---|
|
Arrays |
InterClient does not support arrays. |
|
Events and Triggers |
InterClient does not support InterBase events and triggers. A trigger or stored procedure posts an event to signal a database change (for example: inserts, updates, deletes). |
|
Generators |
Used to produce unique values to insert into a column as a primary key. InterClient does not allow setting of generator values. |
|
Multiple transactions |
InterClient does not allow more than one transaction on a single connection. |
|
BLOB filters |
A Blob is used to store large amounts of data of various types. A Blob filter is a routine that translates Blob data from one user-defined subtype to another. |
|
Query plan |
InterBase uses a query optimizer to determine the most efficient plan for retrieving data. InterClient does not allow you to view a query plan. |
|
International character sets |
InterClient does not support multiple international character sets. *JDBC does support some. |
|
Transaction locking |
InterClient does not support some transaction options, such as two-lock resolution modes, and explicit table-level locks. |