Driver specifications
- Last Updated: March 12, 2025
- 1 minute read
- DataDirect Connectors
- ODBC
- Documentation
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 driver for Teradata supports the Unicode data types in addition to
standard ODBC data types listed in "Data Types." The following table shows how the
Teradata data types map to the Unicode data types, but only when CharacterSet is set
to UTF-16.
Table 1. Teradata Unicode Data Types Teradata Unicode char () charset Unicode SQL_WCHAR clob charset Unicode SQL_WLONGVARCHAR varchar () charset Unicode SQL_WVARCHAR 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: Teradata supports
isolation levels 0 (read uncommitted) and 3 (serializable).
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 16 statements per connection to the Teradata database system.
- SQL Support: The driver supports the minimum SQL grammar.