KanjiEUC Example - Advanced SQL Engine - Teradata Database

For example, consider the following SELECT statement from a KanjiEUC session.

SELECT 'Âgé';

The string Âgé is translated internally to UCS2.

Because this is three characters, the expected-defaults exports at most six bytes, but the representation of Âgé in KanjiEUC requires seven bytes.

Therefore, the output must be truncated to six bytes.

Truncation occurs at a character boundary, so the output is truncated to Âg, which requires four bytes.

If this were a fixed width field, these four bytes would be padded with SPACE characters to produce six bytes. Because the field is not fixed width, only four bytes are output (excluding the length information which is always included in variable width data).