This topic describes the permission classification in OceanBase AI Database.
Classification
Permissions are classified into the following three levels:
- Global permissions: Permissions that affect the entire tenant, such as modifying system settings and accessing all tables.
- Database permissions: Permissions that affect all objects in a specific database, such as creating and dropping tables in the database and accessing tables.
- Object permissions: Permissions that affect a specific object, such as accessing a specific table, view, or index.
The following table lists the permissions supported in OceanBase AI Database.
Permission category |
Permission |
Description |
|---|---|---|
| Object permissions | CREATE | Determines whether the user can execute the CREATE TABLE statement. |
| Object permissions | SELECT | Determines whether the user can query all columns or specified columns in the table. |
| Object permissions | INSERT | Determines whether the user can insert data into all columns or specified columns in the table. |
| Object permissions | UPDATE | Determines whether the user can update data in all columns or specified columns in the table. |
| Object permissions | DELETE | Determines whether the user can delete existing data. |
| Object permissions | DROP | Determines whether the user can execute the DROP TABLE, DROP VIEW, and other similar statements. |
| Object permissions | INDEX | Determines whether the user can create and drop table indexes. |
| Object permissions | ALTER | Determines whether the user can execute the RENAME TABLE, ALTER TABLE, CREATE POLICY, ALTER POLICY, DROP POLICY, and other similar statements. |
| Object permissions | CREATE VIEW | Determines whether the user can create views. |
| Object permissions | SHOW VIEW | Determines whether the user can view views or understand how views execute. |
| Object permissions | REFERENCES | Determines whether the user can create foreign keys. When creating a foreign key for a table, the user must have the REFERENCES permission on the parent table. |
| Object permissions | TRIGGER | Determines whether the user has the permission to activate trigger operations. The user must have this permission to create, view, and drop triggers. |
| Database permissions | SELECT | Determines whether the user can query data in the table. |
| Database permissions | INSERT | Determines whether the user can insert row data into the table. |
| Database permissions | UPDATE | Determines whether the user can modify existing data. |
| Database permissions | DELETE | Determines whether the user can delete existing data. |
| Database permissions | CREATE | Determines whether the user can execute the CREATE DATABASE, CREATE TABLE, CREATE SEQUENCE, and CREATE OUTLINE statements. |
| Database permissions | DROP | Determines whether the user can execute the DROP DATABASE, DROP TABLE, DROP VIEW, DROP SEQUENCE, and DROP OUTLINE statements. |
| Database permissions | INDEX | Determines whether the user can create and drop table indexes. |
| Database permissions | ALTER | Determines whether the user can execute the ALTER DATABASE, RENAME TABLE, ALTER TABLE, ALTER SEQUENCE, and ALTER OUTLINE statements. |
| Database permissions | CREATE VIEW | Determines whether the user can create views. |
| Database permissions | SHOW VIEW | Determines whether the user can view views or understand how views execute. |
| Database permissions | CREATE ROUTINE | Determines whether the user can create procedures and functions. |
| Database permissions | ALTER ROUTINE | Determines whether the user can modify or drop procedures and functions. |
| Database permissions | EXECUTE | Determines whether the user can execute procedures and functions. |
| Database permissions | REFERENCES | Determines whether the user can create foreign keys. |
| Database permissions | TRIGGER | Determines whether the user has the permission to activate trigger operations. The user must have this permission to create, view, and drop triggers. |
| Global permissions | CREATE | Determines whether the user can execute the CREATE DATABASE, CREATE TABLEGROUP, CREATE TABLE, CREATE SEQUENCE, and CREATE OUTLINE statements. |
| Global permissions | ALTER | Determines whether the user can execute the ALTER DATABASE, ALTER TABLEGROUP, RENAME TABLE, ALTER TABLE, ALTER SEQUENCE, and ALTER OUTLINE statements. |
| Global permissions | SELECT | Determines whether the user can query data in the table. |
| Global permissions | INSERT | Determines whether the user can insert rows into a table. |
| Global permissions | UPDATE | Determines whether the user can modify existing data. |
| Global permissions | DELETE | Determines whether the user can delete existing data. |
| Global permissions | DROP | Determines whether the user can execute the DROP DATABASE, DROP TABLEGROUP, DROP TABLE, DROP VIEW, DROP SEQUENCE, DROP OUTLINE, and other similar statements. |
| Global permissions | INDEX | Determines whether the user can create and drop table indexes. |
| Global permissions | CREATE VIEW | Determines whether the user can create views. |
| Global permissions | SHOW VIEW | Determines whether the user can view views or understand how views execute. |
| Global permissions | REFERENCES | Determines whether the user can create foreign keys. |
| Global permissions | ALTER TENANT | Grants the permission to modify tenant information. |
| Global permissions | ALTER SYSTEM | Grants the permission to execute the ALTER SYSTEM statement. |
| Global permissions | CREATE RESOURCE POOL | Grants the permission to create, modify, and drop resource pools. |
| Global permissions | CREATE RESOURCE UNIT | Grants the permission to create, modify, and drop resource units. |
| Global permissions | CREATE DATABASE LINK | Grants the permission to create database links. |
| Global permissions | DROP DATABASE LINK | Grants the permission to drop database links. |
| Global permissions | CREATE USER | Determines whether the user can execute the CREATE USER, ALTER USER, DROP USER, CREATE ROLE, and DROP ROLE statements. |
| Global permissions | CREATE ROUTINE | Determines whether the user can create stored procedures and functions. |
| Global permissions | ALTER ROUTINE | Determines whether the user can modify or drop stored procedures and functions. |
| Global permissions | CREATE TABLESPACE | Determines whether the user can execute the CREATE TABLESPACE, ALTER TABLESPACE, and DROP TABLESPACE statements. |
| Global permissions | CREATE ROLE | Determines whether the user can execute the CREATE ROLE statement. |
| Global permissions | DROP ROLE | Determines whether the user can execute the DROP ROLE statement. |
| Global permissions | EXECUTE | Determines whether the user can execute stored procedures and functions. |
| Global permissions | PROCESS | Determines whether the user can view other users' processes by using the SHOW PROCESSLIST statement. |
| Global permissions | TRIGGER | Determines whether the user can activate trigger operations. To create, view, or drop a trigger, the user must have this permission. |
| Global permissions | SHOW DATABASES | Determines whether the user can view the names of all databases on the server, including those to which the user has sufficient access permissions. |
| Global permissions | SHUTDOWN | Determines whether the user can execute the mysqladmin shutdown statement.
NoteYou can use the |
| Global permissions | RELOAD | Determines whether the user can execute flush operations.
NoteYou can use the |
| Global permissions | FILE | Determines whether the user can execute the SELECT INTO OUTFILE and LOAD DATA INFILE statements. |
| Global permissions | SUPER | Determines whether the user can perform powerful management functions, such as using the KILL statement to terminate user processes, using the SET GLOBAL statement to modify global MySQL variables, and executing various statements related to replication and logs.
Note
|
| Global permissions | BYPASSRLS | Determines whether the user can bypass all table-level row-level security (RLS) policies, including read filtering and write validation. When FORCE ROW LEVEL SECURITY is set for a table, a user holding this permission can still bypass the restriction. This permission can be granted only at the *.* level and cannot be granted at the database or table level. In the current version, it cannot be granted by using the CREATE USER or ALTER USER statement. The permission takes effect when a session is established. If the permission is granted or revoked, existing connections may not be updated immediately. You must reconnect and verify the permission again. |
| Global permissions | GRANT OPTION | Allows the user to grant the permissions that the user owns to other users. This permission is usually used with other permissions, such as SELECT, INSERT, and UPDATE. |
| Global permissions | ALL PRIVILEGES | Indicates that the user has all available permissions in the database.
NoteExcept for |
| Global permissions | ENCRYPT | Determines whether the user can call the ENHANCED_AES_ENCRYPT function. A user can call the encryption function in DML statements only when the user has both the ENCRYPT permission and the corresponding DML permissions. The GRANT/REVOKE ALL PRIVILEGES statement does not include this permission. |
| Global permissions | DECRYPT | Determines whether the user can call the ENHANCED_AES_DECRYPT function. A user can call the decryption function in DML statements only when the user has both the DECRYPT permission and the corresponding DML permissions. The GRANT/REVOKE ALL PRIVILEGES statement does not include this permission. |
| Global permissions | PROXY | Allows a user to connect and operate on behalf of another user without sharing the password. For example, user A can grant user B the permission to connect and operate on behalf of user A without sharing the password. Application scenarios include when an application requires accounts with different permission levels or when user permission delegation is implemented. |
| Global permissions | CREATE LOCATION | Determines whether the user can execute the CREATE LOCATION, ALTER LOCATION, and DROP LOCATION statements. |
| Catalog-level permissions | CREATE CATALOG | Determines whether the user can execute the CREATE EXTERNAL CATALOG and DROP CATALOG statements. |
| Catalog-level permissions | USE CATALOG | Determines whether the user can execute the SET CATALOG, SHOW CATALOGS, SHOW CREATE CATALOG, and SELECT FROM CATALOG statements. |
| Object permissions | CREATE AI MODEL | Determines whether the user can call the CREATE_AI_MODEL and CREATE_AI_MODEL_ENDPOINT procedures in the DBMS_AI_SERVICE system package. |
| Object permissions | ALTER AI MODEL | Determines whether the user can call the ALTER_AI_MODEL_ENDPOINT procedure in the DBMS_AI_SERVICE system package. |
| Object permissions | DROP AI MODEL | Determines whether the user can call the DROP_AI_MODEL and DROP_AI_MODEL_ENDPOINT procedures in the DBMS_AI_SERVICE system package. |
| Object permissions | ACCESS AI MODEL | Determines whether the user can call AI functions such as AI_COMPLETE, AI_EMBED, and AI_RERANK. |
| Global permissions | CREATE SENSITIVE RULE | Determines whether the user can execute the CREATE/DROP SENSITIVE RULE statement. The root user has this permission by default and it cannot be revoked. This permission is also automatically granted when a new cluster is created or after an upgrade. |
| Global permissions | PLAINACCESS | Determines whether the user can access all plaintext data, including sensitive data, without being restricted by sensitive rules. The GRANT/REVOKE ALL PRIVILEGES statement does not include this permission. The root user has this permission by default and it cannot be revoked. This permission is also automatically granted when a new cluster is created or after an upgrade. |
| Rule-level permissions | PLAINACCESS | Determines whether the user can access plaintext data in the columns associated with a specific rule. The user who creates a rule does not automatically have the PLAINACCESS permission for that rule. This permission must be granted separately. |