16.20 - Truncation Exceptions in Teradata Mode - Teradata Vantage NewSQL Engine

Teradata Vantageā„¢ NewSQL Engine International Character Set Support

prodname
Teradata Database
Teradata Vantage NewSQL Engine
vrm_release
16.20
created_date
March 2019
category
Configuration
User Guide
featnum
B035-1125-162K

In Teradata mode, truncation can occur without error in many operations, for example:

  • If, during external-to-internal or explicit conversions, the data to be placed in a fixed character column expands so that the column length is exceeded, Teradata Database truncates on the logical character boundary, and if necessary, pads to the full length of the column. Padding is done with the pad character of the target column type and occurs only on fix columns.
  • If data to be placed in a varying column expands so that the maximum column length is exceeded, Teradata Database truncates the input on the logical character boundary so that the maximum length of the column is not exceeded.
  • During internal-to-external conversion, a truncation exception can occur due to the limited output length imposed by the defined export width. Those exceptions are ignored as they were in previous releases.
  • Suppose the length designated by the export width is defined to be l. If during internal-to-external conversion data expands so that l is exceeded, then the Teradata Database truncates on the logical character boundary and for fixed characters, pads to length l. Truncation on the logical boundary is with respect to the client form-of-use. Padding is done with the pad character of the client form-of-use.

For an illustration of truncation with padding, see Example: KanjiEUC. For other truncation examples, see Example: KanjiEBCDIC and Example: KanjiSJIS.