ANSI ODBC Applications - ODBC Driver for Teradata

In the following section, assume that the ANSI application is limited to SQL_C_CHAR data binding and a non-Unicode session character set is used. Figure 1 depicts the programming model for ODBC Driver for Teradata:

Figure 1: Programming Model for ANSI Applications

1 SQL-Text and SQL_C_CHAR character data flows between the ODBC Application and the ODBC Driver Manager

2 The ODBC Driver Manager:

Converts the SQL-Text to Unicode and passes it to the ODBC Driver

Does not convert the SQL_C_CHAR data and passes it as is to the ODBC Driver

3 The ODBC Driver for Teradata Database:

Converts the SQL-Text from Unicode to Session Character Set

Does not convert the SQL_C_CHAR data and passes it as is to Teradata Database