Restricting Access to Rows › Assigning Row-level Security to Data Tables › Assigning Row-level Security › WHERE Criteria Considerations

WHERE Criteria Considerations

The WHERE criteria specified must conform to the format of the selection criteria defined on the Data Selection screen. When specifying WHERE criteria, the following considerations apply:

• Omitting WHERE criteria permits access to the entire table.
• You can specify WHERE criteria for a view. When the view is accessed, the criteria specified for its source tables and its own criteria are combined. For example, suppose one source table has criteria of A LT B, the other source table has criteria of B GT C, and the view has criteria of F NE 10. At run time, the criteria for the view will be processed as: A LT B and B GT C and F NE 10.
• Columns that contain special characters (including hyphens, spaces, and periods) must be enclosed in parentheses following the literal column, which can be abbreviated to col. An example is:

  COL(EMP-ID)
  

At validation time, ASF checks to see if catalog entries actually exist and checks the format of the WHERE-CLAUSE.

Validate Once Only

At validation time, ASF validates all rows of the SRT that the user has access to. Due to this, you should wait until you have made all entries and changes to the SRT for all tables before validating anything. Then you need only perform the validation once in order for all these entries to be validated.