16.20 - Argument Types and Rules - Advanced SQL Engine - Teradata Database

Teradata Vantage™ - SQL Functions, Expressions, and Predicates

Product
Advanced SQL Engine
Teradata Database
Release Number
16.20
Published
March 2019
Language
English (United States)
Last Update
2020-03-25
dita:mapPath
xzf1512079057909.ditamap
dita:ditavalPath
TD_DBS_16_20_Update1.ditaval
dita:id
kby1472250656485

Expressions passed to this function must have the following data types:

  • instring = VARCHAR or CLOB
  • name_to_search = VARCHAR
  • name_delimiters = VARCHAR
  • value_delimiters = VARCHAR
  • occurrence = INTEGER

The character set of instring, name_to_search, name_delimiters, and value_delimiters can be LATIN or UNICODE. If the parameter character sets are mixed, then all the parameters are converted to UNICODE.

You can also pass arguments with data types that can be converted to the above 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 Teradata Database. If an argument cannot be converted to the required data type following the UDF implicit conversion rules, it must be explicitly cast.

If a delimiter is part of a longer delimiter, the longer delimiter has precedence in the matching process.

Adjacent delimiters are treated as a single delimiter.