Implicit Expression/Function Argument Translation | Teradata Vantage - SQL Rules for Implicit Translation for Expression and Function Arguments - Teradata Vantage - Analytics Database

SQL Data Types and Literals

Deployment
VantageCloud
VantageCore
Edition
VMware
Enterprise
IntelliFlex
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
ft:locale
en-US
ft:lastEdition
2025-11-06
dita:mapPath
uds1628112204571.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
exs1472253032394
lifecycle
latest
Product Category
Teradata Vantage™

The following are the rules for implicit translation between types of expressions and function arguments.

For string functions that produce a character result, the results are summarized by the following table.

FOR this function … The result is …
TRIM converted back to the type of the main string argument (last argument).
|| (concatenation) not translated and remains with the character data type of the arguments after any implicit translation.

Note that the other string functions either do not involve conversion or the type of the result is based on the function and not the server character set of the argument.

For example, in the following TRIM function, <unicode-literal> is first translated to Latin, and then the trim operation is performed.

...
TRIM(<unicode-literal> FROM <latin-value>)

The result is Latin.