SQL Descriptor Fields - ODBC Driver for Teradata

ODBC Driver for Teradata® User Guide

Product
ODBC Driver for Teradata
Release Number
16.20
Published
August 2020
Language
English (United States)
Last Update
2020-08-25
dita:mapPath
fxv1527114222338.ditamap
dita:ditavalPath
Audience_PDF_product_legacy_odbc_include.ditaval
dita:id
B035-2526
lifecycle
previous
Product Category
Teradata Tools and Utilities

Starting with Teradata Database V2R6.2, support was added for improved metadata for parameters used in SQL requests and for columns in result sets. The improved metadata is collectively known as Extended Statement Information. ODBC Driver for Teradata uses the extended statement information if it is supported by Teradata Database, but the use of extended statement information in ODBC can also be explicitly disabled through a configuration option (Enable Extended Statement Information check box in the DSN setup dialog, and EnableExtendedStmtInfo in the odbc.ini file).

When extended statement information is available in ODBC Driver for Teradata, a conforming application should not experience any differences. The application can do the following:
  • Discover that SQLDescribeParam is supported and start using it
  • Receive SQL_UNKNOWN_TYPE when calling SQLGetDescField for some parameters in certain SQL expressions where the database cannot determine the type
  • Find that some descriptor fields that were not set are now set or have different values
  • Discover that information about datetime types and intervals is now more precise

The different values of some of the descriptor fields in ODBC Driver for Teradata when extended statement information is available might affect applications that rely on the old behavior. If necessary, such applications can obtain the old behavior by disabling extended statement information in the ODBC configuration.

The following sections describe differences in the values of descriptor fields when extended statement information is available.