Considerations For Revoke Schema; Authorization And Availability Requirements; Examples Of Revoke Schema - HP Neoview SQL Reference Manual

Hide thumbs Also See for Neoview SQL:
Table of Contents

Advertisement

grantee is authid | PUBLIC
authid specifies an authorization ID from which you revoke privileges. Authorization IDs
identify roles during the processing of SQL statements. The authorization ID must be a valid
role name, enclosed in double quotes. authid is not case-sensitive.
SQL:1999 specifies two special authorization IDs: PUBLIC and SYSTEM.
PUBLIC specifies all present and future authorization IDs.
SYSTEM specifies the implicit grantor of privileges to the creators of objects.
You cannot specify SYSTEM as an authid in a REVOKE statement.
drop-behavior
REVOKE SCHEMA supports only the RESTRICT behavior.

Considerations for REVOKE SCHEMA

When a revoke is issued on a schema, it does not take effect until the query referencing an object
in the schema is re-prepared. For objects, the revoke action is immediate.

Authorization and Availability Requirements

You can revoke only those privileges that you have previously granted to the role. If one or more
of the privileges does not exist, the system returns a warning.
You cannot revoke privileges from a role if you have granted privileges to PUBLIC.

Examples of REVOKE SCHEMA

This example revokes one role's SELECT privileges on a schema:
REVOKE SELECT ON SCHEMA persnl
FROM "role.dev";
This example revokes the privileges of granting SELECT and DELETE privileges on a schema
from two roles:
REVOKE GRANT OPTION FOR SELECT, DELETE
ON SCHEMA sales FROM "role.payroll", "role.finance";
REVOKE SCHEMA Statement
139

Advertisement

Table of Contents
loading

Table of Contents