Home
SQL programmingYou can use the HCL OneDB™ implementation of the SQL language to develop applications for HCL OneDB™ database servers.
Guide to SQL: SyntaxThe HCL OneDB™ Guide to SQL: Syntax describes the syntax of the statements, data types, expressions, operators, and built-in functions of the HCL OneDB™ dialect of the SQL language.
SQL statementsThis chapter describes the syntax and semantics of SQL statements that are recognized by HCL OneDB™.
GRANT statementUse the GRANT statement to assign access privileges and roles to users and to other roles. Users who hold the DBSECADM role can use this statement to assign user security labels and exemptions from label-based access control (LBAC) security rules.
Routine-Level PrivilegesWhen you create a user-defined routine (UDR), you become owner of the UDR and you automatically receive the Execute privilege on that UDR.
Granting the Execute privilege to PUBLICThe GRANT statement supports syntax for granting access to the PUBLIC group, which includes all users who hold the Connect privilege on the database.

Granting the Execute privilege to PUBLIC

The GRANT statement supports syntax for granting access to the PUBLIC group, which includes all users who hold the Connect privilege on the database.

Figure 1: GRANT EXECUTE TO PUBLIC


Element	Description	Restrictions	Syntax
grantor	Owner of the UDR	Cannot be a role	Owner name

This statement enables everyone in the PUBLIC group to execute the specified routine. It overrides the NODEFDAC environment variable, if that is set to prevent the PUBLIC group from receiving Execute privilege on the routine by default. This statement also enables users who do not hold the DBA privilege to execute the specified routine, whether that routine was created with the DBA keyword.

Only users who hold the DBA privilege can specify the AS grantor clause. The specified grantor must be the owner of the specified routine, as listed in the owner column of the sysprocedures system catalog table. The grantor cannot be the name of a role or the PUBLIC keyword.

In an ANSI-compliant database, the AS grantor clause is required, rather than optional, if the DBA who issues the GRANT EXECUTE statement is not the owner of the specified routine.

Only the user specified in the optional AS grantor clause can use the REVOKE statement of SQL to revoke the Execute privilege from the PUBLIC group

The user specified in the optional AS grantor clause can use the REVOKE statement to revoke the Execute privilege from the PUBLIC group.

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.