The Unicode X views and compatibility X views contain security constraints in their definition to limit the result set to only the rows associated with the requesting user, such as:
- Databases
- Users
- Objects owned or created by the user
- Objects on which the user has been granted privileges
The following Unicode X views and compatibility X views also return rows associated with the current role of the user and any nested roles of that current role.
|
|
|
For example, the DBC.TablesVX and DBC.TablesX views provide the following information for each table to which the role of the user has access:
- If the role has privilege on all in TVMs
- If the role has privilege on this specific TVM
It also depends on the current session role of the user to determine what roles are used to verify privileges.
| If the current role is. . . | Then . . . |
|---|---|
| not NULL or ALL | the current role and its nested role are used for security checks. |
| ALL | all the role(s) directly granted to the user and all their nested role(s) are used for security checks. |
X views run slower than their corresponding non-X versions because the X views have security checks.
Compatibility X views are named the same as their corresponding non-X views followed by the character X.
Unicode X views are named the same as their corresponding non-X views followed by the character V.