Providing a consistent hierarchical abstraction of relational data

• US 7,051,033 B2
• Filed: 09/27/2002
• Issued: 05/23/2006
• Est. Priority Date: 09/28/2001
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Sedlar, Eric, Jain, Namit, Murthy, Ravi, Agarwal, Nipun
• Primary Examiner(s): Kindred, Alford W.
• Application Number:
  US10/260,384
• Publication Number:
  US 20030065659A1
• Time in Patent Office: 1,334 Days
• Field of Search: 707 1- 3, 707/8, 707/10, 715/853
• US Class Current: 1/1
• CPC Class Codes: G06F 16/284 Relational databases
• CPC Class Codes: G06F 16/86 Mapping to a database
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

A hierarchy may be explicitly or implicitly reflected in existing data maintained external to hierarchy structures. Such hierarchies are referred to herein as a “pre-existing hierarchies”. Techniques are described herein for capturing a pre-existing hierarchy in hierarchy structures. After a pre-existing hierarchy has been captured, there exist two independent sets of data that reflect the hierarchy: the external hierarchy definition and the internal hierarchy definition. Changing either hierarchy definition changes the hierarchy. Therefore, to maintain a consistent reflection of the hierarchy, the internal hierarchy definition must be modified in response to changes made to the external hierarchy definition, and the external hierarchy definition must be modified in response to changes made to the internal hierarchy definition. Various techniques are described for maintaining consistency between the two hierarchy definitions.

Claims

1. A method for managing data in a database system, comprising the steps of:

receiving at a database server

(a) data that identifies one or more relational tables as tables that store data associated with the content of resources that belong to an information hierarchy, and

(b) connection criteria that indicates what constitutes a relationship in the information hierarchy;

wherein said one or more relational tables include at least one table that stores, along with the data associated with the content of the resources, certain data that serves as an external hierarchy definition that establishes hierarchical relationships between said resources;

using said data that identifies said one or more relational tables, and said connection criteria, to capture the hierarchical relationships within said hierarchy by performing the steps of

executing one or more queries against the one or more relational tables to retrieve said certain data; and

based on said certain data and said connection criteria, storing information that captures said information hierarchy, as an internal hierarchy definition, in one or more hierarchy structures separate from said one or more relational tables.

2. The method of claim 1 wherein the step of staring information that captures said information hierarchy includes storing, within a resource table, a row for each node in said information hierarchy.

3. The method of claim 1 wherein the step of storing information that captures said information hierarchy includes storing, in one or more hierarchy structures, information that indicates parent-child relationships between said resources.

4. The method of claim 1 wherein:

the resources in the information hierarchy correspond to rows of a relational table; and

parent-child relationships between the resources are indicated by values stored in two or more columns of the relational table.

5. The method of claim 4 wherein the step of executing one or more queries includes executing a query that specifies a CONNECT BY relationship between said two or more columns.

6. The method of claim 5 wherein:

the two or more columns include a first column that contains data indicating a child in a relationship and a second column that contains data indicating a parent in the relationship; and

the step of executing a query includes executing a query that contains an expression in the form;

START WITH x IS NULL CONNECT BY PRIOR x=y;

wherein x represents the second column and y represents the first column.

7. The method of claim 1 wherein:

the resources associated with leaf nodes in the information hierarchy correspond to rows of a relational table; and

values associated with non-leaf nodes that, within the information hierarchy, are above a given leaf node are stored in the row that corresponds to the given leaf node.

8. The method of claim 7 wherein:

the values associated with non-leaf nodes are stored in one or more columns of said relational table; and

the step of storing information that captures said information hierarchy includes storing, within a resource table, a row for each distinct value, within said one or more columns, from rows that correspond to leaf nodes in the information hierarchy.

9. The method of claim 1 further comprising the step of establishing triggers to update the data that constitutes said internal hierarchy definition in response to changes made to data that constitutes the external hierarchy definition.

10. The method of claim 1 further comprising the step of establishing triggers to update the data that constitutes said external hierarchy definition in response to changes made to data that constitutes the internal hierarchy definition.

11. The method of claim 1 further comprising the step of automatically maintaining consistency between said external hierarchy definition and said internal hierarchy definition.

12. The method of claim 11 wherein the step of automatically maintaining consistency includes the steps of:

detecting when an operation on said one or more tables deletes a resource associated with a node in the information hierarchy;

in response to detecting said operation, automatically performing the steps of deleting, in a resource table, a row that corresponds to said node;

determining whether removal of said node from said information hierarchy causes one or more other nodes to dangle; and

if removal of said node from said information hierarchy causes one or more other nodes to dangle, then deleting, in the resource table, rows that correspond to said one or more other nodes.

13. The method of claim 11 wherein the step of automatically maintaining consistency includes the steps of:

detecting when an operation on said one or more tables deletes a resource associated with a leaf node in the information hierarchy;

in response to detecting said operation, automatically performing the steps of deleting, in a resource table, a row that corresponds to said node;

determining whether removal of said leaf node from said information hierarchy leaves a parent node of said leaf node with no remaining child nodes; and

if removal of said leaf node from said information hierarchy leaves a parent node of said leaf node with no remaining child nodes, then deleting, in the resource table, a row that corresponds to said parent node.

14. The method of claim 11 wherein the step of automatically maintaining consistency includes the steps of:

detecting when an operation on said one or more tables inserts a resource associated with a node in the information hierarchy;

in response to detecting said operation, automatically performing the steps of inserting, in a resource table, a row that corresponds to said node;

determining whether addition of said node from said information hierarchy causes the addition of one or more child nodes of said node to said information hierarchy; and

if addition of said node from said information hierarchy causes the addition of one or more child nodes of said node to said information hierarchy, then inserting, in the resource table, rows that correspond to said one or more child nodes.

15. A computer-readable medium carrying instructions for managing data in a database system, the instructions comprising instructions for performing the steps of:

receiving at a database server

(a) data that identifies one or more relational tables as tables that store data associated with the content of resources that belong to an information hierarchy, and

(b) connection criteria that indicates what constitutes a relationship in the information hierarchy;

wherein said one or more relational tables include at least one table that stores along with the data associated with the content of the resources, certain data that serves as an external hierarchy definition that establishes hierarchical relationships between said resources;

using said data that identifies said one or more relational tables, and said connection criteria, to capture the hierarchical relationships within said hierarchy by performing the steps of

executing one or more queries against the one or more relational tables to retrieve said certain data; and

based on said certain data and said connection criteria, storing information that captures said information hierarchy, as an internal hierarchy definition, in one or more hierarchy structures separate from said one or more relational tables.

16. The computer-readable medium of claim 15 wherein the step of storing information that captures said information hierarchy includes storing, within a resource table, a row for each node in said information hierarchy.

17. The computer-readable medium of claim 15 wherein the step of storing information that captures said information hierarchy includes storing, in one or more hierarchy structures, information that indicates parent-child relationships between said resources.

18. The computer-readable medium of claim 15 wherein:

the resources in the information hierarchy correspond to rows of a relational table; and

parent-child relationships between the resources are indicated by values stored in two or more columns of the relational table.

19. The computer-readable medium of claim 18 wherein the step of executing one or more queries includes executing a query that specifies a CONNECT BY relationship between said two or more columns.

20. The computer-readable medium of claim 19 wherein:

the two or more columns include a first column that contains data indicating a child in a relationship and a second column that contains data indicating a parent in the relationship; and

the step of executing a query includes executing a query that contains an expression in the form;

START WITH x IS NULL CONNECT BY PRIOR x=y;

wherein x represents the second column and y represents the first column.

21. The computer-readable medium of claim 15 wherein:

the resources associated with leaf nodes in the information hierarchy correspond to rows of a relational table; and

values associated with non-leaf nodes that, within the information hierarchy, are above a given leaf node are stored in the row that corresponds to the given leaf node.

22. The computer-readable medium of claim 21 wherein:

the values associated with non-leaf nodes are stored in one or more columns of said relational table; and

the step of storing information that captures said information hierarchy includes storing, within a resource table, a row for each distinct value, within said one or more columns, from rows that correspond to leaf nodes in the information hierarchy.

23. The computer-readable medium of claim 15 further comprising instructions for performing the step of establishing triggers to update the data that constitutes said internal hierarchy definition in response to changes made to data that constitutes the external hierarchy definition.

24. The computer-readable medium of claim 15 further comprising instructions for performing the step of establishing triggers to update the data that constitutes said external hierarchy definition in response to changes made to data that constitutes the internal hierarchy definition.

25. The computer-readable medium of claim 15 further comprising instructions for performing the step of automatically maintaining consistency between said external hierarchy definition and said internal hierarchy definition.

26. The computer-readable medium of claim 25 wherein the step of automatically maintaining consistency includes the steps of:

detecting when an operation on said one or more tables deletes a resource associated with a node in the information hierarchy;

in response to detecting said operation, automatically performing the steps of deleting, in a resource table, a row that corresponds to said node;

determining whether removal of said node from said information hierarchy causes one or more other nodes to dangle; and

if removal of said node from said information hierarchy causes one or more other nodes to dangle, then deleting, in the resource table, rows that correspond to said one or more other nodes.

27. The computer-readable medium of claim 25 wherein the step of automatically maintaining consistency includes the steps of:

detecting when an operation on said one or more tables deletes a resource associated with a leaf node in the information hierarchy;

in response to detecting said operation, automatically performing the steps of deleting, in a resource table, a row that corresponds to said node;

determining whether removal of said leaf node from said information hierarchy leaves a parent node of said leaf node with no remaining child nodes; and

if removal of said leaf node from said information hierarchy leaves a parent node of said leaf node with no remaining child nodes, then deleting, in the resource table, a row that corresponds to said parent node.

28. The computer-readable medium of claim 25 wherein the step of automatically maintaining consistency includes the steps of:

detecting when an operation on said one or more tables inserts a resource associated with a node in the information hierarchy;

in response to detecting said operation, automatically performing the steps of inserting, in a resource table, a row that corresponds to said node;

determining whether addition of said node from said information hierarchy causes the addition of one or more child nodes of said node to said information hierarchy; and

if addition of said node from said information hierarchy causes the addition of one or more child nodes of said node to said information hierarchy, then inserting, in the resource table, rows that correspond to said one or more child nodes.