The Easysoft ODBC-InterBase Driver provides ODBC 3.5 access to Borland's InterBase version 6, 6.5, 7, 7.5, 2009 and XE. It can also be used with older versions back to 4. The Easysoft ODBC-InterBase Driver is available on a variety of platforms and is compatible with the Windows ODBC Driver Manager and unixODBC, the open source ODBC driver manager.
Native InterBase data types such as BLOB, SUB, TYPE and TEXT are mapped to the correct ODBC data type (SQL_LONGVARCHAR in this case), but the native format is still available. The InterBase 7 BOOLEAN datatype is also implemented to the SQL 99 standard. and is available when the driver is connected to a InterBase 7 database via the InterBase 7 GDS library.
Support is provided for Roles, both via the DSN setup and as an option to the SQLDriverConnect function.
Default character sets may be configured and all conversions are done transparently and automatically. ANSI only applications such as Microsoft Query will only "see" 8 Bit ANSI data, while Unicode applications such as Microsoft Access are provided with direct access to 16-Bit Unicode data.
Due to changes in the metadata storage for older (pre 6.0) InterBase databases, the Easysoft ODBC-InterBase Driver will detect the InterBase database version in use at run time and transparently adjust its operation to match the available data.
For example, if the InterBase rollback_retaining function is available, it will be used by the Easysoft ODBC-InterBase Driver (with potential performance improvements), but if it is absent the driver will adjust its operation in such a way that the calling application is unaware of the change in server capability.
The InterBase interface libraries prior to version 7 were not thread safe, so if the driver detects it is being used with a version of the library before 7, the driver will ensure thread safe operation by employing exclusion primitives to only allow single thread access to the library. Because of this multi threaded applications may show performance improvements when using the driver with the InterBase7 GDS library.
The required SQL Dialect may be configured, and the Easysoft ODBC-InterBase Driver will adjust its operation to ensure that only SQL that matches the selected dialect is passed to the InterBase server.
The driver maps the ODBC transaction interface to the provided InterBase model in a transparent and efficient manner. There is also provision to select the behavior on detection of lock conflicts. The driver provides "wait" and "no wait" operations.
The driver supports InterBase stored procedures and provides mapping from the ODBC call methods to the native InterBase calls. Provision is made for both the "SELECT" and "EXEC PROCEDURE" calling methods and the driver will pick the correct translation. A manual override on this selection is provided for unusual procedures.