ODBC API Conformance - ODBC Driver for Teradata

ODBC Driver for Teradata® User Guide

Product
ODBC Driver for Teradata
Release Number
17.00
Published
June 2020
Language
English (United States)
Last Update
2020-08-22
dita:mapPath
xbl1544831938754.ditamap
dita:ditavalPath
nkw1500504256726.ditaval
dita:id
B035-2526
lifecycle
previous
Product Category
Teradata Tools and Utilities
Starting with the 16.20 version of the driver, ODBC Driver for Teradata adheres to a different level of ODBC API conformance for the following functions:
  • SQLExecute and SQLExecDirect, when no rows are affected by the statement.

    In 16.10 and previous versions of the driver, when a statement affects 0 rows, ODBC Driver for Teradata returned SQL_SUCCESS.

    Starting with 16.20, when a statement affects 0 rows, ODBC Driver for Teradata returns SQL_SUCCESS when using ODBC 2.x, and returns SQL_NO_DATA when using ODBC 3.x.

    For more information, see "SQL_NO_DATA" in the ODBC Programmers' Reference.

  • SQLPrepare, SQLExecute, and SQLExecDirect, when an empty statement is passed in.

    In 16.10 and previous versions, when an empty SQL statement is passed into SQLPrepare, SQLExecute, or SQLExecDirect, ODBC Driver for Teradata returned SQL_SUCCESS.

    Starting with 16.20, When an empty SQL statement is passed into SQLPrepare, SQLExecute, or SQLExecDirect, ODBC Driver for Teradata returns SQL_ERROR with SQLState 42000.