babelfish-for-postgresql / babelfish_extensions / 7740793357 / 1
76%
BABEL_5_X_DEV: 77%

Ran 01 Feb 2024 12:32PM UTC

Files 113

Run time 3s

Badge

Committed 01 Feb 2024 11:54AM UTC coverage: 72.302% (+0.3%) from 72.049%

Job # 7740793357.1

Build Type

push

github

Committed by

Commit Message

Support GRANT .. ON SCHEMA .. in Babelfish (#2326)

Support GRANT/REVOKE .. ON SCHEMA .. in Babelfish

PLEASE NOTE: This change is with the assumption that we are going to restrict function overloading. Based on any other decision made otherwise, the catalog implementation would be extended to store the arguments in another PR.

Supported syntax GRANT <permission> ON SCHEMA::<schema_name> TO <user_name>
Supported syntax REVOKE <permission> ON SCHEMA::<schema_name> FROM <user_name>
Added one SQL statement PLTSQL_STMT_GRANTSCHEMA to store relevant information to execute GRANT/REVOKE .. ON SCHEMA .. statements.
Created one catalog table sys.babelfish_schema_permissions to hold the details for each GRANT/REVOKE statements.
GRANT on schema/objects adds a row in the catalog table if not exists already.
REVOKE on schema/objects removes the corresponding row in the catalog table if it exists already.
REVOKE on schema internally grants permission to all the objects if there are explicit permissions granted to the objects belonging to the same schema.
GRANT ALL on objects work as it is and add rows in the catalog for each relevant permission depending on the object type.
REVOKE ALL on object should do nothing, if the relevant schema permission exists in the catalog. But, it should remove the rows from the catalog if the object level permission is granted.
Drop statement for OBJECT/SCHEMA removes all the relevant object entries from the catalog.

Issues Resolved
Task: BABEL-4344, BABEL-4485

Signed-off-by: Shalini Lohia lshalini@amazon.com

Run Details

40733 of 56337 relevant lines covered (72.3%)

59582.08 hits per line

Source Files on job 7740793357.1