Access logging is to be discontinued on the row-level security constraint specified by constraint_name.
The following list of operations applies to row-level security logging.
If the END LOGGING statement is for row-level security logging (a FOR CONSTRAINT constraint_name specification), and you do not specify an operation type, the statement stops logging of all row-level security related SQL operation types:
- OVERRIDE DELETE
- OVERRIDE DUMP
- OVERRIDE INSERT
- OVERRIDE RESTORE
- OVERRIDE SELECT
- OVERRIDE UPDATE
If you do not want to end logging of all of these operation types (excluding OVERRIDE DUMP and OVERRIDE RESTORE, which are not logged by default), you must specify the each operation type for which you want to END LOGGING.
If you specify an ON clause for an END LOGGING of row-level security operations, then the only valid object types you can specify are row-level security tables, databases or users.
- If you specify a database or user, then Teradata Database ends logging of all tables in the specified database or user that contain the constraint specified by constraint_name.
- If you specify a table, then that table must contain a row-level security column that matches constraint_name.
- If you do not specify an object, the system ends logging of privilege checks on the specified operations for all tables in which the constraint_name appears.
- Name of the row-level security constraint.