The name of a constraint object that you want to define as a row-level security constraint column for table_name. The constraint object must exist in the database. See CREATE CONSTRAINT.
Each specified row-level security constraint name must be unique among column names for the table.
You cannot create a row-level security constraint column for a global temporary table or for a volatile table.
A security constraint object definition includes a name, data type, and nullability specification when it is created. You cannot assign any additional attributes to a security constraint column when creating a table.
You cannot compress a row-level security constraint column using either multivalue compression or algorithmic compression. However, there are no restrictions on using auto-compression or block compression for a row-level security table with column partitions.
You can define a maximum of 5 row-level security constraint columns for a table.