PeriodStructOn Flag | Data Types and Literals | Teradata Vantage - PeriodStructOn Flag - Advanced SQL Engine - Teradata Database

SQL Data Types and Literals

Product
Advanced SQL Engine
Teradata Database
Release Number
17.05
17.00
Published
June 2020
Language
English (United States)
Last Update
2021-01-22
dita:mapPath
zsn1556242031050.ditamap
dita:ditavalPath
lze1555437562152.ditaval
dita:id
B035-1143
lifecycle
previous
Product Category
Teradata Vantageā„¢

The PeriodStructOn flag in the Options parcel allows the client to request PERIOD struct metadata, null indicator bits, and data values from the Teradata Database in response messages.

The PeriodStructOn flag is stored in pcloptlist_t (pcltoteq.h).

The client sending PERIOD struct values to Teradata Database in request messages is independent from the client setting the Option parcel flag to request that Teradata Database return PERIOD struct values in response messages.

Values

Value Description
Y Default.

Request PERIOD struct metadata, null indicator bits, and data values from Teradata Database.

The Period data type value is exported as its date/time/timestamp attributes.

Teradata Database accepts (but does not require) PERIOD struct metadata, null indicator bits, and PERIOD struct data values from the client.

N Do not request PERIOD struct metadata, null indicator bits, and data values from Teradata Database.

See Transforms Off and Period Data Type Support for more information on setting these values.

When either the BEGIN or END PERIOD attributes is null, the PERIOD value is null. Therefore, null PERIOD values sent from Teradata Database to the client have all three null indicator bits set to indicate that the PERIOD value is null, and that the BEGIN and END attributes are also null. If the client sends null BEGIN or END PERIOD attributes, Teradata Database considers the PERIOD value to be null.