Developing ODBC Applications for Internationalization : Unicode and Non-Unicode ODBC Drivers : Function Calls : Unicode Application with the OpenAccess SDK ODBC Driver

Unicode Application with the OpenAccess SDK ODBC Driver

An operation involving a Unicode application and the OpenAccess SDK Unicode driver is more efficient because no function conversion is involved. If the application and the driver use different types of encoding, there is some conversion overhead.

Windows

1. The Unicode application sends UCS-2 or UTF-16 function calls to the Driver Manager.

2. The Driver Manager does not have to convert the UCS-2 or UTF-16 function calls to ANSI. It passes the Unicode function call to the OpenAccess driver.

3. The driver returns UCS-2 or UTF-16 argument values to the Driver Manager.

4. The Driver Manager returns UCS-2 or UTF-16 function calls to the application.

Linux/UNIX

1. The Unicode application sends function calls to the Driver Manager. The Driver Manager expects these function calls to be UTF-8 or UTF-16 based on the value of the SQL_ATTR_APP_UNICODE_TYPE attribute.

2. The Driver Manager passes the Unicode function call to the OpenAccess for ODBC driver. The Driver Manager must perform function call conversions if the SQL_ATTR_APP_UNICODE_TYPE is different from SQL_ATTR_DRIVER_UNICODE_TYPE.

3. The driver returns argument values to the Driver Manager. Whether these are UTF-8 or UTF-16 argument values is based on the value of the SQL_ATTR_DRIVER_UNICODE_TYPE attribute.

4. The Driver Manager returns appropriate function calls to the application, based on the SQL_ATTR_DRIVER_UNICODE_TYPE attribute. The Driver Manager must perform function call conversions if the SQL_ATTR_APP_UNICODE_TYPE is different from SQL_ATTR_DRIVER_UNICODE_TYPE.