Contents Index Permissions of groups Groups without passwords

ASA Database Administration Guide
  Managing User IDs and Permissions
    Managing groups

Referring to tables owned by groups


Groups are used for finding tables and procedures in the database. For example, the query

SELECT * FROM SYSGROUPS

always finds the table SYSGROUPS, because all users belong to the PUBLIC group, and PUBLIC belongs to the SYS group which owns the SYSGROUPS table. (The SYSGROUPS table contains a list of group_name, member_name pairs representing the group memberships in your database.)

If a table named employees is owned by the user ID personnel, and if M_Haneef is a member of the personnel group, then M_Haneef can refer to the employees table simply as employees in SQL statements. Users who are not members of the personnel group need to use the qualified name personnel.employees.

Creating a group to own the tables 

A good practice to follow that allows everyone to access the tables without qualifying names, is to create a group whose only purpose is to own the tables. Do not grant any permissions to this group, but make all users members of the group. You can then create permission groups and grant users membership in these permission groups as warranted.

For an example, see the section Database object names and prefixes.


Contents Index Permissions of groups Groups without passwords