babelfish-for-postgresql / babelfish_extensions / 7650903956
74%
BABEL_5_X_DEV: 77%

LAST BUILD BRANCH: BABEL-5577
DEFAULT BRANCH: BABEL_5_X_DEV
Ran
Jobs 1
Files 113
Run time 9s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 72.761% (+0.2%) from 72.536%
7650903956

push

github

web-flow 
Support GRANT .. ON SCHEMA .. in Babelfish (#2215)

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

Note: A new PR will be raised to block function overloading.

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: BABEL-4344

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

40921 of 56240 relevant lines covered (72.76%)

56827.52 hits per line

Jobs
ID Job ID Ran Files Coverage
1 7650903956.1 113
72.76
 GitHub Action Run
Source Files on build 7650903956