Security Constraint Object Definition - Analytics Database - Teradata Vantage

SQL External Routine Programming

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
iiv1628111441820.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
B035-1147
lifecycle
latest
Product Category
Teradata Vantage™

This example defines two constraint objects which together comprise a sensitivity label.

   CREATE CONSTRAINT Classification_Level SMALLINT, NOT NULL,
      VALUES (TopSecret:4, Secret:3, Confidential:2, Unclassified:1),
         INSERT SYSLIB.InsertLevel,
         UPDATE SYSLIB.UpdateLevel,
         DELETE SYSLIB.DeleteLevel,
         SELECT SYSLIB.ReadLevel;

   CREATE CONSTRAINT Classification_Category BYTE(8),
   /* leave room for 64 categories, nulls are allowed */
      VALUES (NATO:1, UnitedStates:2, Canada:3, UnitedKingdom:4,
              France:5, Norway:6, Russia:7),
         INSERT SYSLIB.InsertCategory,
         UPDATE SYSLIB.UpdateCategory,
         DELETE SYSLIB.DeleteCategory,
         SELECT SYSLIB.ReadCategory;