17.05 - item_to_lock - Advanced SQL Engine - Teradata Database

Teradata Vantage™ - SQL Data Definition Language Syntax and Examples

Product
Advanced SQL Engine
Teradata Database
Release Number
17.05
Release Date
January 2021
Content Type
Programming Reference
Publication ID
B035-1144-175K
Language
English (United States)
DATABASE
Specifies that a lock is to be placed at the database level for this view definition.
database_name_2
user_name_2
Name of the database or user to be locked.
TABLE
Specifies that a lock is to be placed at the table or view level for this view definition.
table_name
Name of a user base table to be locked for this view definition.
You can create views that reference global temporary tables and volatile tables.
A view can reference a global temporary trace table, but such a view is not updatable. See CREATE GLOBAL TEMPORARY TRACE TABLE.
A recursive view definition can reference both row-level security-protected (RLS) tables and non-RLS tables, or other views that are based upon RLS tables, but all RLS base tables referenced in the view must have the same RLS constraints. It is not necessary to specify the row-level security constraint columns in the view definition. However when users access the view, the system enforces row-level security constraints for base tables regardless of whether the constraints are part of the view definition.
database_name_3
user_name_3
Name of the containing database or user for table_name if different from the current database or user.
VIEW
Specifies that a lock is to be placed at the view level for this view definition.
view_name_2
Name of a view to be locked for this view definition.
database_name_4
user_name_4
Name of the containing database or user for view_name if different from the current database or user.
ROW
Specifies that a lock is to be placed at the row hash level for this view definition.