Argument Types and Rules - Advanced SQL Engine - Teradata Database

SQL Functions, Expressions, and Predicates

Product
Advanced SQL Engine
Teradata Database
Release Number
17.05
17.00
Published
June 2020
Language
English (United States)
Last Update
2021-01-30
dita:mapPath
tpt1555966086716.ditamap
dita:ditavalPath
lze1555437562152.ditaval
dita:id
B035-1145
lifecycle
previous
Product Category
Teradata Vantageā„¢
BITXOR is an overloaded scalar function. The data type of the target_arg parameter can be one of the following:
  • BYTEINT
  • SMALLINT
  • INTEGER
  • BIGINT
  • VARBYTE(n)

The data type of the bit_mask_arg parameter varies depending upon the data type of the target_arg parameter. The following (target_arg, bit_mask_arg) input combinations are permitted.

target_arg type bit_mask_arg type
BYTEINT BYTE(1)
BYTEINT BYTEINT
SMALLINT BYTE(2)
SMALLINT SMALLINT
INTEGER BYTE(4)
INTEGER INTEGER
BIGINT BYTE(8)
BIGINT BIGINT
VARBYTE(n) VARBYTE(n)

The maximum supported size (n) for VARBYTE is 8192 bytes.

All expressions passed to this function must either match these declared data types or can be converted to these types using the implicit data type conversion rules that apply to UDFs. For example, BITXOR(BYTEINT, INTEGER) is allowed because it can be implicitly converted to BITXOR(INTEGER,INTEGER).

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

If any argument cannot be converted to one of the declared data types, an error is returned indicating that no function exists that matches the DML UDF expression submitted.