Standard Type Mappings (deprecated in 16.20) - 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

The following transformations of standard Teradata types are deprecated as of 16.20.

Teradata Data Type Legacy Transformation by Teradata ODBC
BIGINT When used with early databases that did not support BIGINT the Teradata ODBC driver would map BIGINT to DECIMAL(18,0).

All Teradata database releases supported by ODBC 15.10 now support the native BIGINT type and this mapping is obsolete.

DATE ANSI Date mode is the default and is what an application should use.

In Integer Date mode, the DATE type, when used in a column definition or type cast will be replaced by:

DATE FORMAT 'YYYY-MM-DD'

The replacement occurs only if no FORMAT phrase has explicitly been used.

The Integer Date mode is supported by the database and the default database format is ‘YY/MM/DD’, which is different from the standard ODBC and ANSI format. An application that uses Integer Date mode and relies on ODBC to set the date FORMAT in the SQL text previously could use the EnableLegacyParser option, but this has been deprecated. Your application needs to use ANSI Date mode (preferred default) or set explicit FORMATs.

TIME[(n)] If Integer Time mode is used then the TIME type when used in a column definition or type cast will be replaced by:
INTEGER FORMAT '99:99:99'

Any precision is ignored.

The Integer Time mode is an ODBC TIME type implementation for database versions not supporting true ANSI TIME types.

Integer Time mode is deprecated in ODBC 15.00 and is not recommended for use.