Specifying RECURSIVE For a Non-Recursive View - Analytics Database - Teradata Vantage

SQL Data Definition Language Detailed Topics

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-07-11
dita:mapPath
vuk1628111288877.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
B035-1184
lifecycle
latest
Product Category
Teradata Vantage™

The system does not require a view defined explicitly with the keyword RECURSIVE to have a recursive reference. As long as such a view definition is otherwise correct syntactically, the system creates the view as specified without returning an error to the requestor. However, the resulting database object is not a recursive view.

This is analogous to the situation in which you explicitly define an outer join in your query, but, because the Optimizer evaluates the query text as if you had defined an inner join, and rewrites it accordingly. In that situation, the system makes an inner join on the specified tables, but does not return an error or a warning to the requestor. See Teradata Vantage™ - SQL Data Manipulation Language, B035-1146 for an extended analysis of the outer join specification issue.