content_image/738686.jpg content_image/738685.jpg
} } } } } } 

Each predefined variable corresponds to a system variable. By writing a filter that tests a predefined variable, you can modify filter operation by setting the corresponding system variable, without having to redefine the filter. For example, by writing a filter that tests the value of the audit_log_connection_policy_value  predefined variable, you can modify filter operation by changing the value of the audit_log_connection_policy  system variable. 

The audit_log_ xxx _policy  system variables are used for the legacy mode audit log (see Section 6.4.5.9, “Legacy Mode Audit Log Filtering” ). With rule-based audit log filtering, those variables remain visible (for example, using SHOW VARIABLES ), but changes to them have no effect unless you write filters containing constructs that refer to them. 

The following list describes the permitted predefined variables for variable  items: 

• audit_log_connection_policy_value 

This variable corresponds to the value of the audit_log_connection_policy  system variable. The value is an unsigned integer. Table 6.34, “audit_log_connection_policy_value Values”  shows the permitted values and the corresponding audit_log_connection_policy  values. 

<img src='content_image/738686.jpg'>

The ":: xxx "  values are symbolic pseudo-constants that may be given instead of the literal numeric values. They must be quoted as strings and are case-sensitive. 

• audit_log_policy_value 

This variable corresponds to the value of the audit_log_policy  system variable. The value is an unsigned integer. Table 6.35, “audit_log_policy_value Values”  shows the permitted values and the corresponding audit_log_policy  values. 

<img src='content_image/738685.jpg'>

The ":: xxx "  values are symbolic pseudo-constants that may be given instead of the literal numeric values. They must be quoted as strings and are case-sensitive. 

• audit_log_statement_policy_value 

