This section describes the general functionality supported by the driver.

  • ODBC compliance: The driver is Level 1 compliant, that is, it supports all ODBC Core and Level 1 functions.
    In addition, the following functions are supported:
    • SQLColumnPrivileges
    • SQLForeignKeys
    • SQLTablePrivileges

    Refer to ODBC API and scalar functions in the Progress DataDirect for ODBC Drivers Reference for a list of supported API functions.

  • Unicode support: When connected to a Unicode database, the Sybase IQ Wire Protocol driver supports the Unicode data types listed in the following table, in addition to standard ODBC data types listed in "Data Types."
    Table 1. Mapping Sybase IQ Data Types to Unicode Data Types
    Sybase IQ Data Type. . . Maps to Unicode Data Type. . .
    CHAR 1 SQL_WCHAR
    LONG VARCHAR SQL_WLONGVARCHAR
    TEXT 2 SQL_WLONGVARCHAR
    UNIQUEIDENTIFIERSTR SQL_WCHAR
    VARCHAR 3 SQL_WVARCHAR

    For data types that require the UTF-8 character set, set the Charset connection option. See "Charset" for information about using this connection option.

    The driver supports the Unicode ODBC W (Wide) function calls, such as SQLConnectW. This allows the Driver Manager to transmit these calls directly to the driver. Otherwise, the Driver Manager would incur the additional overhead of converting the W calls to ANSI function calls, and vice versa.

    See "UTF-16 applications on UNIX and Linux" for related details.

    Refer to Internationalization, localization, and Unicode in the Progress DataDirect for ODBC Drivers Reference for details.

  • Isolation and lock levels: The driver supports isolation levels 0 (read uncommitted), 1 (read committed, the default), 2 (repeatable read), and 3 (serializable). It supports page-level locking.

    Refer to Locking and isolation levels in the Progress DataDirect for ODBC Drivers Reference for details.

  • Connections and statements supported: The driver supports multiple connections and multiple statements per connection.
1 This data type is available only if the data source is configured to use the UTF-8 character set.
2 This data type is available only if the data source is configured to use the UTF-8 character set.
3 This data type is available only if the data source is configured to use the UTF-8 character set.