Rules for Writing UDFs that Compress/Decompress TIME, TIMESTAMP, Period, ARRAY, and non-LOB UDT Data - Advanced SQL Engine - Teradata Database

SQL External Routine Programming

Product
Advanced SQL Engine
Teradata Database
Release Number
17.05
17.00
Published
June 2020
Language
English (United States)
Last Update
2021-01-24
dita:mapPath
qwr1571437338192.ditamap
dita:ditavalPath
lze1555437562152.ditaval
dita:id
B035-1147
lifecycle
previous
Product Category
Teradata Vantage™

Follow these guidelines to write scalar UDFs that compress/decompress column data which have the following data types: TIME, TIMESTAMP, Period, ARRAY, or supported distinct non-LOB UDT.

  • The compress UDF should have the following signature:
    • The UDF must declare a single input parameter which has a data type of TIME, TIMESTAMP, Period, ARRAY or supported distinct non-LOB UDT.
    • The parameter data type and column data type should be the same.
    • The return type should be VARBYTE(64000).
  • The decompress UDF should have the following signature:
    • The UDF must declare a single VARBYTE(64000) input parameter.
    • The output of the decompress UDF should be identical to the column type.