Automatic enforcement of relationships in a database schema

• US 8,458,124 B2
• Filed: 12/09/2011
• Issued: 06/04/2013
• Est. Priority Date: 07/27/2004
• Status: Active Grant

• Current Assignee: Infoblox Incorporated
• Original Assignee: Infoblox Incorporated
• Inventors: Bailey, Stuart, Gutti, Srinath, Pulleyn, Ivan
• Primary Examiner(s): Ehichioya, Fred I
• Assistant Examiner(s): Mobin, Hasanul
• Application Number:
  US13/316,036
• Publication Number:
  US 20120150914A1
• Time in Patent Office: 543 Days
• Field of Search: None
• US Class Current: 707/609
• CPC Class Codes: G06F 16/211 Schema design and management
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity

Abstract

A technique for enforcing a database relationship is disclosed. The technique includes specifying within a database schema a reference type that associates two structures and specifies the relationship between the two structures, and automatically generating code that checks the relationship between the two structures based on the specified reference in the database schema.

Claims

1. A method of enforcing a database relationship, comprising:

specifying using a markup language within a database schema a host structure and a reference type for the host structure that indicates an association between the host structure and a parent structure to which the host structure refers and specifies the relationship between the host structure and the parent structure, wherein the reference type is specified using the markup language and selected from at least a first reference type, a second reference type, and a third reference type;

automatically generating code that enforces the relationship between the host structure and the parent structure based on the reference type specified in the database schema;

enforcing the relationship using the automatically generated code, including determining whether the reference type for the host structure is of the first reference type, the second reference type, or the third reference type;

in the event that the reference type for the host structure is of the first reference type and a request to delete a host in a database for which the database schema has been defined is received,

disallowing deletion of the host if the host refers to a child instance, and

allowing deletion of the host if the host does not refer to a child instance;

in the event that the reference type for the host structure is of the second reference type and a request to delete a host in a database for which the database schema has been defined is received, deleting an instance referring to the host; and

in the event that the reference type for the host structure is of the third reference type and a request to delete a host in a database for which the database schema has been defined is received, nullifying a reference of an instance referring to the host.

2. The method as recite in claim 1, wherein in the event the reference type for the host structure is of the first reference type, ensuring that an instance of the parent structure cannot be deleted when an instance of the host structure exists.

3. The method as recite in claim 1, wherein in the event the reference type for the host structure is of the second reference type, ensuring that when an instance of the parent structure does not exist, an instance of the host structure cannot exist.

4. The method as recite in claim 1, wherein in the event the reference type for the host structure is of the second reference type:

receiving a request to insert a host into a database for which the database schema has been defined, wherein the host is an instance of the child structure and the host refers to an instance of a parent structure; and

determining whether the instance of the parent structure exists in the database, wherein the instance of the parent structure is a Domain Name System (DNS) zone of a network.

5. The method as recite in claim 4, wherein in the event that the instance of the parent structure does not exist in the database, disallowing insertion of the instance of the child structure into the database, wherein the insert of the host is disallowed if the DNS zone does not exist.

6. The method as recited in claim 1, wherein if the third reference type is selected, it is not necessary for the parent structure to exist for the host structure to exist;

and it is not necessary for a child structure of the host structure to exist for the host structure to exist.

7. The method as recited in claim 1, wherein the code includes a function that checks the relationship between the two structures.

8. The method as recited in claim 1, wherein the code is SQL code.

9. The method as recited in claim 1, wherein the code is associated with a relational database.

10. The method as recited in claim 1, wherein the code is associated with an object oriented database.

11. The method as recited in claim 1, wherein

generating includes:

translating the markup language specification into an in memory representation; and

generating the code from the in memory representation in a specific database language.

12. The method as recited in claim 11, wherein the markup language is based on XML.

13. The method as recited in claim 11, wherein translating includes compiling a structure in an intermediate language.

14. The method as recited in claim 11, wherein the database language is associated with a relational database.

15. The method as recited in claim 11, wherein the database language is associated with an object oriented database.

16. The method as recited in claim 11, wherein the generated code includes a function.

17. The method as recited in claim 11, wherein the structure includes a reference that indicates a parent of the structure.

18. The method as recited in claim 11, wherein the structure includes a key that uniquely identifies the structure.

19. The method as recited in claim 1, wherein the request to insert the host into the database includes a zone name for the zone, a host name for the host, and an IP address for the host.

20. A system for enforcing a database relationship, comprising:

a processor configured to;

specify using a markup language within a database schema a host structure and a reference type for the host structure that indicates an association between the host structure and a parent structure to which the host structure refers and specifies the relationship between the host structure and the parent structure, wherein the reference type is specified using the markup language and selected from at least a first reference type, a second reference type, and a third reference type;

automatically generate code that enforces the relationship between the host structure and the parent structure based on the reference type specified in the database schema;

enforce the relationship using the automatically generated code, including determining whether the reference type for the host structure is of the first reference type, the second reference type, or the third reference type;

in the event that the reference type for the host structure is of the first reference type and a request to delete a host in a database for which the database schema has been defined is received,

disallow deletion of the host if the host refers to a child instance, and

allow deletion of the host if the host does not refer to a child instance;

in the event that the reference type for the host structure is of the second reference type and a request to delete a host in a database for which the database schema has been defined is received, delete an instance referring to the host; and

in the event that the reference type for the host structure is of the third reference type and a request to delete a host in a database for which the database schema has been defined is received, nullify a reference of an instance referring to the host; and

a memory that is coupled with the processor, wherein the memory provides the processor with instructions.

21. A computer program product for enforcing a database relationship, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions executable to:

specifying using a markup language within a database schema a host structure and a reference type for the host structure that indicates an association between the host structure and a parent structure to which the host structure refers and specifies the relationship between the host structure and the parent structure, wherein the reference type is specified using the markup language and selected from at least a first reference type, a second reference type, and a third reference type;

automatically generating code that enforces the relationship between the host structure and the parent structure based on the reference type specified in the database schema;

enforcing the relationship using the automatically generated code, including determining whether the reference type for the host structure is of the first reference type, the second reference type, or the third reference type;

in the event that the reference type for the host structure is of the first reference type and a request to delete a host in a database for which the database schema has been defined is received,

disallowing deletion of the host if the host refers to a child instance, and

allowing deletion of the host if the host does not refer to a child instance;

in the event that the reference type for the host structure is of the second reference type and a request to delete a host in a database for which the database schema has been defined is received, deleting an instance referring to the host; and

in the event that the reference type for the host structure is of the third reference type and a request to delete a host in a database for which the database schema has been defined is received, nullifying a reference of an instance referring to the host.