Complied objective referential constraints in a relational database having dual chain relationship descriptors linked in data record tables

• US 5,133,068 A
• Filed: 08/28/1991
• Issued: 07/21/1992
• Est. Priority Date: 09/23/1988
• Status: Expired due to Term

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Engles, Robert W., Dockter, Michael J., Crus, Richard A., Haderle, Donald J.
• Primary Examiner(s): Lee, Thomas C.
• Assistant Examiner(s): Lim, Krisna
• Application Number:
  US07/754,227
• Time in Patent Office: 328 Days
• Field of Search: 364/200 MS File, 364/900 MS File
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity

Abstract

An implementation of referential integrity in which descriptions of referential constraints are compiled into meta-data descriptions of the constraint rules and specifications. The meta-data descriptions of the constraints are stored in the form of objects called relationship descriptors. Each relationship descriptor contains a complete description of a referential constraint, either directly or by means of pointers to other objects such as record and index descriptors which contain information comprised in the constraint'"'"'s specification. The relationship descriptors are linked into two types of chains by symbolic pointers. One type of relationship descriptor chain connects all relationship descriptors which have a common parent table. The other type of relationship descriptor chain connects relationship descriptors with common dependent tables. Both types of chains are anchored in respective fields in the tables'"'"' record descriptors. The use of meta-data descriptors facilitates both ready modification of the constraints, and speedy enforcement of the constraints by a single, shared procedure which may be embedded in the data base manager.

Claims

1. A computer-implemented, relational data base management system comprising:

(a) a first table containing data records;

(b) a second table containing data records;

(c) a third table containing data records;

(d) a first relationship descriptor, having pointer connections to the first table and the second table, for describing meta-data of a first referential constraint between the first and second tables, the meta-data including the first constraint'"'"'s parent and dependent tables and primary and foreign keys, the first relationship descriptor being a separate object internal to the data base management system;

(e) a second relationship descriptor, having pointer connections to one of the first two tables and the third table, for describing meta-data of a second referential constraint between one of the first two tables and the third table, the meta-data including the second constraint'"'"'s parent and dependent tables and primary and foreign keys, the second relationship descriptor being a separate object internal to the data base management system;

(f) a first chain for connecting the first and second relationship descriptors to their respective parent tables;

(g) a second chain for connecting the first and second relationship descriptors to their respective dependent tables;

(h) means for accessing the first and second relationship descriptors when any of the tables is to be modified; and

(i) means for enforcing the referential constraints described by the first and second relationship descriptors upon such modification.

2. The system of claim 1, wherein the first relationship descriptor is stored within the data base system in compiled form.

3. The system of claim 1, further comprising:

a first record descriptor for describing the data records of the first table, the first record descriptor being a separate object within the data base system which can be modified individually; and

wherein the means for accessing the first relationship descriptor comprises a logical connection between the first relationship descriptor and the first record descriptor.

4. The system of claim 3, wherein the logical connection between the first record descriptor and the first relationship descriptor comprises a symbolic pointer from the first record descriptor to the first relationship descriptor.

5. The system of claim 4, wherein the first table is the parent table of the constraint and the second table is the dependent table of the constraint.

6. The system of claim 5, further including:

a second record descriptor for describing the records of the second table, the second record descriptor being a separate object within the data base system which can be modified individually; and

wherein the means for accessing the first relationship descriptor further comprises a logical connection between the second record descriptor and the first relationship descriptor.

7. The system of claim 6, wherein the logical connection between the second record descriptor and the first relationship descriptor comprises a symbolic pointer from the second record descriptor to the first relationship descriptor.

8. The system of claim 1, further comprising:

an index descriptor for describing a primary key index of the first table; and

wherein the first relationship descriptor identifies the constraint'"'"'s primary key by referencing the index descriptor.

9. The system of claim 8, where the first relationship descriptor references the index descriptor by a logical connection from the first relationship descriptor to the index descriptor.

10. The system of claim 9, wherein the logical connection from the first relationship descriptor to the index descriptor comprises a symbolic pointer.

11. The system of claim 1, wherein the first and second relationship descriptors each include a delete rule having a value equal to any of "restrict," "set null," and "cascade," and wherein any relationship descriptor having a delete rule value of "restrict" precedes in the first and second chains any relationship descriptor having any other delete rule value.

12. The system of claim 11, wherein any relationship descriptor having a delete rule value of "set null" precedes in the first and second chains any relationship descriptor having a delete rule value of "cascade."