Using The DateForm Setting | Data Types & Literals | VantageCloud Lake - The DateForm Setting

Using The DateForm Setting | Data Types & Literals | VantageCloud Lake - The DateForm Setting - Teradata Vantage

Teradata® VantageCloud Lake

Deployment

VantageCloud

Edition

Lake

Product

Teradata Vantage

Published

January 2023

ft:locale

en-US

ft:lastEdition

2024-12-11

dita:mapPath

phg1621910019905.ditamap

dita:ditavalPath

pny1626732985837.ditaval

dita:id

phg1621910019905

Before you change the DateForm setting, you need to consider the effect the change has on the following:

Export data type of DATE values.
Changing the DateForm setting changes the export data type of DATE values.
Data-entry format for dates.
Changing the DateForm setting changes the data entry format of dates for new tables, but not for existing tables. To avoid data entry problems, however, you can enter all dates as ANSI DATE literals.
Display format of DATE columns.
Changing the DateForm setting changes the display of DATE values in new tables, but not in existing tables. Therefore, DATE values display differently for new tables than for old tables. Because views are based on the underlying table, this is true for views of tables too.
String-to-DATE comparisons and conversions.
To compare or convert strings to DATE values, the strings must have the same format as the DATE values. Such comparisons can fail after you change the DateForm setting because the DATE format for new tables, views of new tables, and existing macros changes. To avoid format errors in string-to-DATE comparisons, however, you can specify dates as ANSI DATE literals.
Format of DATE values in macros being run.
Changing the DateForm setting can change the format of DATE values in macros, which can cause the macro to fail.

Changing the DateForm setting does not change the DATE format for the following: