Consequences for Other Tables

See Also

In the relationships between parent and child tables, actions in one table may influence data in the other. In other words, you may create problems when you give a user group certain rights on a particular table. For example, if you give a user the right to delete information from a table called PERSON, and a relationship definition exists specifying a cascading delete rule between the PERSON table and another table called PERSON_ADDRESS, this will not work unless you have also given the user (background) delete rights on the PERSON_ADDRESS table as well.

You must also consider the fact that giving a user Delete rights in a child table could result in a parent table which contains entries with no related information, which is probably not what is wanted.

It is essential that you have a clear view of all the rights you are about to grant and the influence these rights will have on your data model, before you start defining them with the Authorizer.

If you have specified rights on tables that occur in the SQL statement of a logical view, these rights are also effective when selecting or manipulating data in the logical view.