15.10 - Appendix F Deprecated SQL Transformations - ODBC Driver for Teradata

ODBC Driver for Teradata User Guide

prodname
ODBC Driver for Teradata
vrm_release
15.10
category
User Guide
featnum
B035-2509-035K

The deprecated SQL Transformations described in this appendix only work with the legacy parser until they were completely removed, and with the default new parser these transformations were not supported. Any application using these deprecated transformations needs to enable the legacy parser:

  • To enable the legacy parser through odbc.ini in UNIX/Linux and Apple OS X platforms, refer to the "EnableLegacyParser=[Yes|No]" option in Table 23 on page 66.
  • To enable the legacy parser through ODBC Administrator in the Windows platform, refer to the description of the "Enable Legacy Parser" check box in Table 12 on page 41.
  • To enable the legacy parser through ODBC Administrator in the Apple OS X platform, refer to the description of the "Enable Legacy Parser" check box in Table 3 on page 5.
  • The Teradata ODBC driver contains an SQL parser that replaces ODBC escape sequences in the SQL text with their corresponding Teradata SQL equivalents. Teradata ODBC 15.10 includes a new parser, which is smaller, better performing, and more closely integrated with the driver.

    The original parser in the ODBC driver performed some non-standard transformation of the SQL text in order to work around shortcomings both in early applications and in the database at the time. These legacy transformations are no longer needed, and in some cases conflict with the evolution of standard SQL, standard ODBC, and the Teradata database. Some of the transformations have already been deprecated in release 15.0 and older versions of the ODBC Driver for Teradata.

    The following sections describe the deprecated transformations which will only work with the legacy parser as mentioned above.