Argument Types and Rules - 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ā„¢
Expressions passed to this function must have the following data types:
  • instring = VARCHAR or CLOB
  • in_encoding = VARCHAR(64)

The character sets of two input parameters to TO_BYTES can be either Latin or Unicode.

If in_encoding is not one of the supported encodings, an error is returned.

If either instring or in_encoding is NULL, the result is NULL.

You can also pass arguments with data types that can be converted to these data types using the implicit data type conversion rules that apply to UDFs.

The UDF implicit type conversion rules are more restrictive than the implicit type conversion rules normally used by Vantage. If an argument cannot be converted to the required data type following the UDF implicit conversion rules, it must be explicitly cast.

The maximum input or output for CLOB or BLOB size is 2 GB. An error is reported if the size is exceeded.

The TO_BYTES function converts from a character string to a VARBYTE. The character strings are treated as positive unless there is an explicit negative sign. Byte strings are interpreted as negative if the high order bit is 1.

TO_BYTES should not be used for byte to byte encodings, since TO_BYTES tries to interpret the sign of the byte string.

If you must use byte to byte conversion, use the two TO_BYTE functions. (Note the syntax is TO_BYTE, not TO_BYTES.)