|
It is very important to guarantee that data adheres to certain rules which are determined by application
|
|
For example, assume that a business rule says that no row in the phone_list_table should be allowed unless its person_id value found in the person_id column in the person_info_table (this is to ensure that a person's entity must exist first before the phone number information can be established)
|
|
If an insert or update statement attempts to violate this integrity rule, Oracle must roll back the invalid statement and return an error to the application
|
|
In order to achieve this protection, Oracle provides integrity constraints
|
|
For example, a foreign key (see later) can be defined on the column person_id of phone_list_table which references to the primary key person_id of the person_info_table
|
