DROP PERMIT Statement
Permission: You must own a table, view, database event, or procedure to drop a permission on it.
The DROP PERMIT statement removes permissions on tables, views, database events, and procedures.
This statement has the following format:
For tables and views:
[EXEC SQL] DROP PERMIT ON table_name
ALL | integer {, integer};
For procedures:
[EXEC SQL] DROP PERMIT ON PROCEDURE proc_name
ALL | integer {, integer};
For events:
[EXEC SQL] DROP PERMIT ON DBEVENT event_name
ALL | integer {, integer};
If the keyword ALL is used, Ingres removes all permissions defined on the specified table, view, database event, or procedure. To remove individual permissions, use the integer list. To obtain the integer values associated with specific permissions, use the HELP PERMIT statement.
Note: Permits cannot be dropped if there are dependent objects (views or database procedures) or permits. In this case, REVOKE...CASCADE must be used.
Embedded Usage: DROP PERMIT
In an embedded DROP PERMIT statement, no portion of the syntax can be replaced with host language variables.
Locking
The DROP PERMIT statement takes an exclusive lock on the base table and on pages in the iipermits system catalog.
DROP PERMIT Example
The following example drops all permissions on job:
DROP PERMIT ON job ALL;
In an application, drop the second permission on procedure addemp:
EXEC SQL DROP PERMIT ON PROCEDURE addemp 2;
Last modified date: 08/29/2024