<html>
<head>
<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Chapter 6. Access Control</title>
<link href="../docbook.css" type="text/css" rel="stylesheet">
<meta content="DocBook XSL-NS Stylesheets V1.76.1" name="generator">
<meta name="keywords" content="Hsqldb, HyperSQL, SQL">
<meta name="keywords" content="Hsqldb, HyperSQL, Database, JDBC, Java">
<link rel="home" href="index.html" title="HyperSQL User Guide">
<link rel="up" href="index.html" title="HyperSQL User Guide">
<link rel="prev" href="texttables-chapt.html" title="Chapter 5. Text Tables">
<link rel="next" href="dataaccess-chapt.html" title="Chapter 7. Data Access and Change">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<div class="navheader">
<table summary="Navigation header" width="100%">
<tr>
<td align="left" width="30%"><a accesskey="p" href="texttables-chapt.html"><img src="../images/db/prev.png" alt="Prev"></a> </td><td align="center" width="40%" style="font-weight:bold;">Chapter 6. Access Control</td><td align="right" width="30%"> <a accesskey="n" href="dataaccess-chapt.html"><img src="../images/db/next.png" alt="Next"></a></td>
</tr>
<tr>
<td valign="top" align="left" width="30%">Chapter 5. Text Tables </td><td align="center" width="40%"><a accesskey="h" href="index.html"><img src="../images/db/home.png" alt="Home"></a></td><td valign="top" align="right" width="30%"> Chapter 7. Data Access and Change</td>
</tr>
</table>
</div>
<HR>
<div class="chapter" title="Chapter 6. Access Control">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a name="accesscontrol-chapt"></a>Chapter 6. Access Control</h2>
</div>
<div>
<div class="authorgroup">
<div class="author">
<h3 class="author">
<span class="firstname">Fred</span> <span class="surname">Toussi</span>
</h3>
<div class="affiliation">
<span class="orgname">The HSQL Development Group<br>
</span>
</div>
</div>
</div>
</div>
<div>
<p class="releaseinfo">$Revision: 3096 $</p>
</div>
<div>
<div class="legalnotice" title="Legal Notice">
<a name="N11E2E"></a>
<p>Copyright 2010-2016 Fred Toussi. Permission is granted to
distribute this document without any alteration under the terms of the
HSQLDB license. Additional permission is granted to the HSQL Development
Group to distribute this document with or without alterations under the
terms of the HSQLDB license.</p>
</div>
</div>
<div>
<p class="pubdate">2017-04-09 14:14:09-0400</p>
</div>
</div>
</div>
<div class="toc">
<p>
<b>Table of Contents</b>
</p>
<dl>
<dt>
<span class="section"><a href="accesscontrol-chapt.html#acc_overview">Overview</a></span>
</dt>
<dt>
<span class="section"><a href="accesscontrol-chapt.html#acc_auth_and_access_ctrl">Authorizations and Access Control</a></span>
</dt>
<dd>
<dl>
<dt>
<span class="section"><a href="accesscontrol-chapt.html#acc_built_in_roles_users">Built-In Roles and Users</a></span>
</dt>
<dt>
<span class="section"><a href="accesscontrol-chapt.html#acc_listing">Listing Users and Roles</a></span>
</dt>
<dt>
<span class="section"><a href="accesscontrol-chapt.html#acc_access_rights">Access Rights</a></span>
</dt>
</dl>
</dd>
<dt>
<span class="section"><a href="accesscontrol-chapt.html#acc_statements">Statements for
Authorization and Access Control</a></span>
</dt>
</dl>
</div>
<div class="section" title="Overview">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both">
<a name="acc_overview"></a>Overview</h2>
</div>
</div>
</div>
<p>This chapter is about access control to database objects such as
tables, inside the database engine. Other issues related to security
include user authentication, password complexity and secure connections
are covered in the <a class="link" href="management-chapt.html" title="Chapter 11. System Management">System Management</a> chapter and the <a class="link" href="listeners-chapt.html" title="Chapter 14. HyperSQL Network Listeners (Servers)">HyperSQL Network Listeners
(Servers)</a>
chapter.</p>
<p>Apart from schemas and their object, each HyperSQL catalog has USER
and ROLE objects. These objects are collectively called
<span class="emphasis"><em>authorizations</em></span>. Each AUTHORIZATION has some access
rights on some of the schemas or the objects they contain. The persistent
elements of an SQL environment are database objects</p>
<p>Authorizations names are stored in the database in the case-normal
form. When connecting to a database via JDBC, the user name and password
must match the case of this case-normal form.</p>
<p>When a user is created with the CREATE USER statement, if the user
name is enclosed in double quotes, the exact name is used as the
case-normal form. But if it is not enclosed in double quotes, the name is
converted to uppercase and this uppercase version is stored in the
database as the case-normal form.</p>
</div>
<div class="section" title="Authorizations and Access Control">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both">
<a name="acc_auth_and_access_ctrl"></a>Authorizations and Access Control</h2>
</div>
</div>
</div>
<p>In general, ROLE and USER objects simply control access to schema
objects. This is the scope of the SQL Standard. However, there are special
roles that allow the creation of USER and ROLE objects and also allow some
special operations on the database as a whole. These roles are not defined
by the Standard, which has left it to implementers to define such roles as
they are needed for the particular SQL implementation.</p>
<p>A ROLE has a name a collection of zero or more other roles, plus
some privileges (access rights). A USER has a name and a password. It
similarly has a collection of zero or more roles plus some
privileges.</p>
<p>USER objects existed in the SQL-92, but ROLE objects were introduced
in SQL:1999. Originally it was intended that USER objects would normally
be the same as the operating system USER objects and their authentication
would be handled outside the SQL environment. The co-existence of ROLE and
USER objects results in complexity. With the addition of ROLE objects,
there is no rationale, other than legacy support, for granting privileges
to USER objects directly. It is better to create roles and grant
privileges to them, then grant the roles to USER objects.</p>
<p>The Standard effectively defines a special ROLE, named PUBLIC. All
authorization have the PUBLIC role, which cannot be removed from them.
Therefore any access right assigned to the PUBLIC role applies to all
authorizations in the database. For many simple databases, it is adequate
to create a single, non-admin user, then assign access rights to the
pre-existing PUBLIC role. Access to INFORMATION_SCHEMA views is granted to
PUBLIC, therefore these views are accessible to all. However, the contents
of each view depends on the ROLE or USER (AUTHORIZATION) that is in force
while accessing the view.</p>
<p>Each schema has a single AUTHORIZATION. This is commonly known as
the <span class="emphasis"><em>owner</em></span> of the schema. All the objects in the
schema inherit the schema owner. The schema owner can add objects to the
schema, drop them or alter them.</p>
<p>By default, the objects in a schema can only be accessed by the
schema owner. The schema owner can grant access rights on the objects to
other users or roles.</p>
<a name="N11E5C" class="indexterm"></a>
<p>
<span class="bold"><strong>authorization
identifier</strong></span>
</p>
<p>
<span class="emphasis"><em>authorization identifier</em></span>
</p>
<p>
<code class="literal"><authorization identifier> ::= <role name> |
<user name></code>
</p>
<p>Authorization identifiers share the same name-space within the
database. The same name cannot be used for a USER and a ROLE.</p>
<div class="section" title="Built-In Roles and Users">
<div class="titlepage">
<div>
<div>
<h3 class="title">
<a name="acc_built_in_roles_users"></a>Built-In Roles and Users</h3>
</div>
</div>
</div>
<p>There are some pre-defined roles in each database; some defined by
the SQL Standard, some by HyperSQL. These roles can be assigned to users
(directly or via other, user-defined roles). In addition, there is the
initial SYS user created with each new database. The initial user name
and password is defined in the connection properties when the first
connection to the database is made. In older versions of HSQLDB, this
name was always SA. But in the latest version, the name can be defined
as a different string.</p>
<a name="N11E73" class="indexterm"></a>
<p>
<span class="bold"><strong>PUBLIC</strong></span>
</p>
<p>
<span class="emphasis"><em>the PUBLIC role</em></span>
</p>
<p>The role that is assigned to all authorizations (roles and
users) in the database. This role has access rights to all objects in
the INFORMATION_SCHEMA. Any roles or rights granted to this role, are in
effect granted to all users of the database.</p>
<a name="N11E81" class="indexterm"></a>
<p>
<span class="bold"><strong>_SYSTEM</strong></span>
</p>
<p>
<span class="emphasis"><em>the _SYSTEM role</em></span>
</p>
<p>This role is the authorization for the pre-defined (system)
objects in the database, including the INFORMATION_SCHEMA. This role
cannot be assigned to any authorization.</p>
<a name="N11E8F" class="indexterm"></a>
<p>
<span class="bold"><strong>DBA</strong></span>
</p>
<p>
<span class="emphasis"><em>the DBA role (HyperSQL-specific)</em></span>
</p>
<p>This is a special role in HyperSQL. A user that has this role
can perform all possible administrative tasks on the database. The DBA
role can also act as a proxy for all the roles and users in the
database. This means it can do everything the authorization for a schema
can do, including dropping the schema or its objects, or granting rights
on the schema objects to a grantee.</p>
<a name="N11E9D" class="indexterm"></a>
<p>
<span class="bold"><strong>CREATE_SCHEMA</strong></span>
</p>
<p>
<span class="emphasis"><em>the CREATE_SCHEMA role
(HyperSQL-specific)</em></span>
</p>
<p>An authorization that has this role, can create schemas. The
DBA authorization has this role and can grant it to other
authorizations.</p>
<a name="N11EAB" class="indexterm"></a>
<p>
<span class="bold"><strong>CHANGE_AUTHORIZATION</strong></span>
</p>
<p>
<span class="emphasis"><em>the CHANGE_AUTHORIZATION role
(HyperSQL-specific)</em></span>
</p>
<p>A user that has this role, can change the authorization for the
current session to another user. The other user cannot have the DBA role
(otherwise, the original user would gain DBA privileges). The DBA
authorization has this role and can grant it to other
authorizations.</p>
<a name="N11EB9" class="indexterm"></a>
<p>
<span class="bold"><strong>SYS User</strong></span>
</p>
<p>
<span class="emphasis"><em>the SYS user (HyperSQL-specific)</em></span>
</p>
<p>This user is automatically created with a new database and has
the DBA role. This user name and its password are defined in the
connection properties when connecting to the new database to create the
database. As this user, it is possible to change the password, create
other users and created new schema objects. The initial SYS user can be
dropped by another user that has the DBA role. As a result, there is
always at least one SYS user in the database.</p>
</div>
<div class="section" title="Listing Users and Roles">
<div class="titlepage">
<div>
<div>
<h3 class="title">
<a name="acc_listing"></a>Listing Users and Roles</h3>
</div>
</div>
</div>
<p>Tables in the INFORMATION_SCHEMA contain the list of users and
roles for the database.</p>
<p>The SYSTEM_USERS tables contains the list of users, with some
extra settings for each user. The AUTHORIZATIONS table contains a list
of both users and roles.</p>
<p>Several other INFORMATION_SCHEMA tables list the privileges
granted to users and roles on different database objects. Refer to the
<a class="link" href="databaseobjects-chapt.html" title="Chapter 4. Schemas and Database Objects">Schemas and Database Objects</a> chapter for a list and
description of the tables. Example below:</p>
<div class="informalexample">
<pre class="programlisting"> SELECT * FROM INFORMATION_SCHEMA.SYSTEM_USERS
SELECT * FROM INFORMATION_SCHEMA.TABLE_PRIVILEGES
</pre>
</div>
</div>
<div class="section" title="Access Rights">
<div class="titlepage">
<div>
<div>
<h3 class="title">
<a name="acc_access_rights"></a>Access Rights</h3>
</div>
</div>
</div>
<p>By default, the objects in a schema can only be accessed by the
schema owner. But the schema owner can grant privileges (access rights)
on the objects to other users or roles.</p>
<p>Things can get far more complex, because the grant of privileges
can be made WITH GRANT OPTION. In this case, the role or user that has
been granted the privilege can grant the privilege to other roles and
users.</p>
<p>Privileges can also be revoked from users or roles.</p>
<p>The statements for granting and revoking privileges normally
specify which privileges are granted or revoked. However, there is a
shortcut, ALL PRIVILEGES, which means all the privileges that the
<code class="literal"><grantor></code> has on the schema object. The
<code class="literal"><grantor></code> is normally the CURRENT_USER of the
session that issues the statement.</p>
<p>The user or role that is granted privileges is referred to as
<code class="literal"><grantee></code> for the granted privileges.</p>
<p>
<span class="bold"><strong>Table</strong></span>
</p>
<p>For tables, including views, privileges can be granted with
different degrees of granularity. It is possible to grant a privilege on
all columns of a table, or on specific columns of the table.</p>
<p>The DELETE privilege applies to the table, rather than its
columns. It applies to all DELETE statements.</p>
<p>The SELECT, INSERT and UPDATE privileges may apply to all
columns or to individual columns. These privileges determine whether the
<code class="literal"><grantee></code> can execute SQL data statements on
the table.</p>
<p>The SELECT privilege designates the columns that can be
referenced in SELECT statements, as well as the columns that are read in
a DELETE or UPDATE statement, including the search condition.</p>
<p>The INSERT privilege designates the columns into which explicit
values can be inserted. To be able to insert a row into the table, the
user must therefore have the INSERT privilege on the table, or at least
all the columns that do not have a default value.</p>
<p>The UPDATE privilege simply designates the table or the
specific columns that can be updated.</p>
<p>The REFERENCES privilege allows the
<code class="literal"><grantee></code> to define a FOREIGN KEY constraint on
a different table, which references the table or the specific columns
designated for the REFERENCES privilege.</p>
<p>The TRIGGER privilege allows adding a trigger to the
table.</p>
<p>
<span class="bold"><strong>Sequence, Type, Domain, Character Set,
Collation, Transliteration,</strong></span>
</p>
<p>For these objects, only USAGE can be granted. The USAGE
privilege is needed when object is referenced directly in an SQL
statement.</p>
<p>
<span class="bold"><strong>Routine</strong></span>
</p>
<p>For routines, including procedures or functions, only EXECUTE
privilege can be granted. This privilege is needed when the routine is
used directly in an SQL statement.</p>
<p>
<span class="bold"><strong>Other Objects</strong></span>
</p>
<p>Other objects such as constraints and assertions are not used
directly and there is no grantable privilege that refers to
them.</p>
</div>
</div>
<div class="section" title="Statements for Authorization and Access Control">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both">
<a name="acc_statements"></a>Statements for
Authorization and Access Control</h2>
</div>
</div>
</div>
<p>The statements listed below allow creation and destruction of USER
and ROLE objects. The GRANT and REVOKE statements allow roles to be
assigned to other roles or to users. The same statements are also used in
a different form to assign privileges on schema objects to users and
roles.</p>
<a name="N11F23" class="indexterm"></a>
<p>
<a name="create_user-sql"></a><span class="bold"><strong>CREATE
USER</strong></span>
</p>
<p>
<span class="emphasis"><em>user definition (HyperSQL)</em></span>
</p>
<p>
<code class="literal"><user definition> ::= CREATE USER <user
name> PASSWORD <password> [ ADMIN ]</code>
</p>
<p>Define a new user and its password. <code class="literal"><user
name></code> is an SQL identifier. If it is double-quoted it is
case-sensitive, otherwise it is turned to uppercase.
<code class="literal"><password></code> is a string enclosed with single quote
characters and is case-sensitive. If <code class="literal">ADMIN</code> is
specified, the DBA role is granted to the new user. Only a user with the
DBA role can execute this statement.</p>
<a name="N11F3E" class="indexterm"></a>
<p>
<span class="bold"><strong>DROP USER</strong></span>
</p>
<p>
<span class="emphasis"><em>drop user statement (HyperSQL)</em></span>
</p>
<p>
<code class="literal"><drop user statement> ::= DROP USER <user
name></code>
</p>
<p>Drop (destroy) an existing user. If the specified user is the
authorization for a schema, the schema is destroyed.</p>
<p>Only a user with the DBA role can execute this
statement.</p>
<a name="N11F51" class="indexterm"></a>
<p>
<span class="bold"><strong>ALTER USER ... SET
PASSWORD</strong></span>
</p>
<p>
<span class="emphasis"><em>set the password for a user
(HyperSQL)</em></span>
</p>
<p>
<code class="literal"><alter user set password statement> ::= ALTER USER
<user name> SET PASSWORD <password></code>
</p>
<p>Change the password of an existing user. <code class="literal"><user
name></code> is an SQL identifier. If it is double-quoted it is
case-sensitive, otherwise it is turned to uppercase.
<code class="literal"><password></code> is a string enclosed with single quote
characters and is case-sensitive.</p>
<p>Only a user with the DBA role can execute this command.</p>
<a name="N11F6A" class="indexterm"></a>
<p>
<span class="bold"><strong>ALTER USER ... SET INITIAL
SCHEMA</strong></span>
</p>
<p>
<span class="emphasis"><em>set the initial schema for a user
(HyperSQL)</em></span>
</p>
<p>
<code class="literal"><alter user set initial schema statement> ::=
ALTER USER <user name> SET INITIAL SCHEMA <schema name> |
DEFAULT</code>
</p>
<p>Change the initial schema for a user. The initial schema is the
schema used by default for SQL statements issued during a session. If
<code class="literal">DEFAULT</code> is used, the default initial schema for all
users is used as the initial schema for the user. The SET SCHEMA command
allows the user to change the schema for the duration of the
session.</p>
<p>Only a user with the DBA role can execute this
statement.</p>
<a name="N11F80" class="indexterm"></a>
<p>
<span class="bold"><strong>ALTER USER ... SET
LOCAL</strong></span>
</p>
<p>
<span class="emphasis"><em>set the user authentication as local
(HyperSQL)</em></span>
</p>
<p>
<code class="literal"><alter user set local> ::= ALTER USER <user
name> SET LOCAL { TRUE | FALSE }</code>
</p>
<p>Sets the authentication method for the user as local. This
statement has an effect only when external authentication with role names
is enabled. In this method of authentication, users created in the
database are ignored and an external authentication mechanism, such as
LDAP is used. This statement is used if you want to use local, password
authentication for a specific user.</p>
<p>Only a user with the DBA role can execute this
statement.</p>
<a name="N11F93" class="indexterm"></a>
<p>
<a name="set_password-sql"></a><span class="bold"><strong>SET
PASSWORD</strong></span>
</p>
<p>
<span class="emphasis"><em>set password statement (HyperSQL)</em></span>
</p>
<p>
<code class="literal"><set password statement> ::= SET PASSWORD
<password></code>
</p>
<p>Set the password for the current user.
<code class="literal"><password></code> is a string enclosed with single quote
characters and is case-sensitive.</p>
<a name="N11FA8" class="indexterm"></a>
<p>
<span class="bold"><strong>SET INITIAL SCHEMA</strong></span>
</p>
<p>
<span class="emphasis"><em>set the initial schema for the current user
(HyperSQL)</em></span>
</p>
<p>
<code class="literal"><set initial schema statement> ::= SET INITIAL
SCHEMA <schema name> | DEFAULT</code>
</p>
<p>Change the initial schema for the current user. The initial
schema is the schema used by default for SQL statements issued during a
session. If <code class="literal">DEFAULT</code> is used, the default initial schema
for all users is used as the initial schema for the current user. The
separate SET SCHEMA command allows the user to change the schema for the
duration of the session. See also the <a class="link" href="sessions-chapt.html" title="Chapter 3. Sessions and Transactions">Sessions and Transactions</a> chapter.</p>
<a name="N11FC1" class="indexterm"></a>
<p>
<span class="bold"><strong>SET DATABASE DEFAULT INITIAL
SCHEMA</strong></span>
</p>
<p>
<span class="emphasis"><em>set the default initial schema for all users
(HyperSQL)</em></span>
</p>
<p>
<code class="literal"><set database default initial schema statement>
::= SET DATABASE DEFAULT INITIAL SCHEMA <schema
name></code>
</p>
<p>Sets the initial schema for new users. This schema can later be
changed with the <code class="literal"><set initial schema statement></code>
command.</p>
<a name="N11FD5" class="indexterm"></a>
<p>
<span class="bold"><strong>CREATE ROLE</strong></span>
</p>
<p>
<span class="emphasis"><em>role definition</em></span>
</p>
<p>
<code class="literal"><role definition> ::= CREATE ROLE <role
name> [ WITH ADMIN <grantor> ]</code>
</p>
<p>Defines a new role. Initially the role has no rights, except
those of the PUBLIC role. Only a user with the DBA role can execute this
command.</p>
<a name="N11FE6" class="indexterm"></a>
<p>
<span class="bold"><strong>DROP ROLE</strong></span>
</p>
<p>
<span class="emphasis"><em>drop role statement</em></span>
</p>
<p>
<code class="literal"><drop role statement> ::= DROP ROLE <role
name></code>
</p>
<p>Drop (destroy) a role. If the specified role is the authorization
for a schema, the schema is destroyed. Only a user with the DBA role can
execute this statement.</p>
<a name="N11FF7" class="indexterm"></a>
<p>
<span class="bold"><strong>GRANTED BY</strong></span>
</p>
<p>
<span class="emphasis"><em>grantor determination</em></span>
</p>
<p>
<code class="literal">GRANTED BY <grantor></code>
</p>
<p>
<code class="literal"><grantor> ::= CURRENT_USER |
CURRENT_ROLE</code>
</p>
<p>The authorization that is granting or revoking a role or
privileges. The optional <code class="literal">GRANTED BY <grantor></code>
clause can be used in various statements that perform GRANT or REVOKE
actions. If the clause is not used, the authorization is CURRENT_USER.
Otherwise, it is the specified authorization.</p>
<a name="N1200E" class="indexterm"></a>
<p>
<span class="bold"><strong>GRANT</strong></span>
</p>
<p>
<span class="emphasis"><em>grant privilege statement</em></span>
</p>
<p>
<code class="literal"><grant privilege statement> ::= GRANT
<privileges> TO <grantee> [ { <comma> <grantee>
}... ] [ WITH GRANT OPTION ] [ GRANTED BY <grantor>
]</code>
</p>
<p>Assign privileges on schema objects to roles or users. Each
<code class="literal"><grantee></code> is a role or a user. If <code class="literal">[ WITH
GRANT OPTION ]</code> is specified, then the
<code class="literal"><grantee></code> can assign the privileges to other
<code class="literal"><grantee></code> objects.</p>
<p>
<code class="literal"><privileges> ::= <object privileges> ON
<object name></code>
</p>
<p>
<code class="literal"><object name> ::= [ TABLE ] <table name> |
DOMAIN <domain name> | COLLATION <collation name> | CHARACTER
SET <character set name> | TRANSLATION <transliteration name>
| TYPE <user-defined type name> | SEQUENCE <sequence generator
name> | <specific routine designator> | ROUTINE <routine
name> | FUNCTION <function name> | PROCEDURE <procedure
name></code>
</p>
<p>
<code class="literal"><object privileges> ::= ALL PRIVILEGES |
<action> [ { <comma> <action> }... ]</code>
</p>
<p>
<code class="literal"><action> ::= SELECT | SELECT <left paren>
<privilege column list> <right paren> | DELETE | INSERT [
<left paren> <privilege column list> <right paren> ] |
UPDATE [ <left paren> <privilege column list> <right
paren> ] | REFERENCES [ <left paren> <privilege column
list> <right paren> ] | USAGE | TRIGGER |
EXECUTE</code>
</p>
<p>
<code class="literal"><privilege column list> ::= <column name
list></code>
</p>
<p>
<code class="literal"><grantee> ::= PUBLIC | <authorization
identifier></code>
</p>
<p>The <code class="literal"><object privileges></code> that can be used
depend on the type of the <code class="literal"><object name></code>. These
are discussed in the previous section. For a table, if
<code class="literal"><privilege column list></code> is not specified, then
the privilege is granted on the table, which includes all of its columns
and any column that may be added to it in the future. For routines, the
name of the routine can be specified in two ways, either as the generic
name as the specific name. HyperSQL allows referencing all overloaded
versions of a routine at the same time, using its name. This differs from
the SQL Standard which requires the use of <code class="literal"><specific routine
designator></code> to grant privileges separately on each different
signature of the routine.</p>
<p>Each <code class="literal"><grantee></code> is the name of a role or
a user. Examples of GRANT statement are given below:</p>
<div class="informalexample">
<pre class="programlisting"> GRANT ALL ON SEQUENCE aSequence TO roleOrUser
GRANT SELECT ON aTable TO roleOrUser
GRANT SELECT, UPDATE ON aTABLE TO roleOrUser1, roleOrUser2
GRANT SELECT(columnA, columnB), UPDATE(columnA, columnB) ON TABLE aTable TO roleOrUser
GRANT EXECUTE ON SPECIFIC ROUTINE aroutine_1234 TO rolOrUser
</pre>
</div>
<p>As mentioned in the general discussion, it is better to define a
role for the collection of all the privileges required by an application.
This role is then granted to any user. If further changes are made to the
privileges of this role, they are automatically reflected in all the users
that have the role.</p>
<a name="N12055" class="indexterm"></a>
<p>
<span class="bold"><strong>GRANT</strong></span>
</p>
<p>
<span class="emphasis"><em>grant role statement</em></span>
</p>
<p>
<code class="literal"><grant role statement> ::= GRANT <role name>
[ { <comma> <role name> }... ] TO <grantee> [ {
<comma> <grantee> }... ] [ WITH ADMIN OPTION ] [ GRANTED BY
<grantor> ]</code>
</p>
<p>Assign roles to roles or users. One or more roles can be assigned
to one or more <code class="literal"><grantee></code> objects. A
<code class="literal"><grantee></code> is a user or a role. If the <code class="literal">[
WITH ADMIN OPTION ]</code> is specified, then each
<code class="literal"><grantee></code> can grant the newly assigned roles to
other grantees. An example of user and role creation with grants is given
below:</p>
<div class="informalexample">
<pre class="programlisting"> CREATE USER appuser
CREATE ROLE approle
GRANT approle TO appuser
GRANT SELECT, UPDATE ON TABLE atable TO approle
GRANT USAGE ON SEQUENCE asequence to approle
GRANT EXECUTE ON ROUTINE aroutine TO approle
</pre>
</div>
<a name="N12075" class="indexterm"></a>
<p>
<span class="bold"><strong>REVOKE privilege</strong></span>
</p>
<p>
<span class="emphasis"><em>revoke statement</em></span>
</p>
<p>
<code class="literal"><revoke privilege statement> ::= REVOKE [ GRANT
OPTION FOR ] <privileges> FROM <grantee> [ { <comma>
<grantee> }... ] [ GRANTED BY <grantor> ] RESTRICT |
CASCADE</code>
</p>
<p>Revoke privileges from a user or role.</p>
<a name="N12086" class="indexterm"></a>
<p>
<span class="bold"><strong>REVOKE role</strong></span>
</p>
<p>
<span class="emphasis"><em>revoke role statement</em></span>
</p>
<p>
<code class="literal"><revoke role statement> ::= REVOKE [ ADMIN OPTION
FOR ] <role revoked> [ { <comma> <role revoked> }... ]
FROM <grantee> [ { <comma> <grantee> }... ] [ GRANTED BY
<grantor> ] RESTRICT | CASCADE</code>
</p>
<p>
<code class="literal"><role revoked> ::= <role
name></code>
</p>
<p>Revoke a role from users or roles.</p>
</div>
</div>
<HR xmlns:xi="http://www.w3.org/2001/XInclude">
<P xmlns:xi="http://www.w3.org/2001/XInclude" class="svnrev">$Revision: 5675 $</P>
<div class="navfooter">
<hr>
<table summary="Navigation footer" width="100%">
<tr>
<td align="left" width="40%"><a accesskey="p" href="texttables-chapt.html"><img src="../images/db/prev.png" alt="Prev"></a> </td><td align="center" width="20%"> </td><td align="right" width="40%"> <a accesskey="n" href="dataaccess-chapt.html"><img src="../images/db/next.png" alt="Next"></a></td>
</tr>
<tr>
<td valign="top" align="left" width="40%">Chapter 5. Text Tables </td><td align="center" width="20%"><a accesskey="h" href="index.html"><img src="../images/db/home.png" alt="Home"></a></td><td valign="top" align="right" width="40%"> Chapter 7. Data Access and Change</td>
</tr>
</table>
</div>
</body>
</html>
