System and method for querying data for implicit hierarchies

• US 7,801,913 B2
• Filed: 05/30/2003
• Issued: 09/21/2010
• Est. Priority Date: 12/07/1998
• Status: Expired due to Term

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Srinivasan, Uppili, Shrivastava, Saurabh
• Primary Examiner(s): Robinson; Greta L
• Application Number:
  US10/449,946
• Publication Number:
  US 20040243576A1
• Time in Patent Office: 2,671 Days
• Field of Search: 707/102, 707/3, 707/100, 707/2, 707/4, 707/10, 707/5, 707/101, 707/104.1, 707/200, 707/205, 707/103.R, 707/103.X, 707/103.Y, 707/103.Z, 707/6, 707/705, 707/706, 707/713, 707/714, 707/716, 707/718, 707/736, 707/754, 707/764, 707/769, 707/778, 707/779, 715/224, 715/225, 715/234, 715/235, 715/243
• US Class Current: 707/779
• CPC Class Codes: G06F 16/2452 Query translation
• CPC Class Codes: G06F 16/24534 Query rewriting; Transformation
• CPC Class Codes: G06F 16/289 Object oriented databases

Abstract

A method, system, and article of manufacture for querying an implicit hierarchy is disclosed. According to one approach, implicit hierarchies can be queried by accessing the relevant catalog tables for the attribute relevant to the query. Each identified entry in the relevant catalog table is followed through its implied hierarchical chains until all relevant entries have been identified. The catalog table containing the normalized form of the DN for each user can be consulted to identify the entry identifier for each entry corresponding to implicit hierarchy being queried, which can be searched in the appropriate catalog table to search the chain of entries for the implied hierarchy. In an approach, one or more templates may be used to generate a query language statement to perform the query upon the implicit hierarchy.

Claims

1. A method for generating a statement in a database query language to search against an implicit hierarchy of directory information objects stored in a relational database, comprising:

receiving a search request that searches for directory information pertaining to an implicit hierarchy, wherein the implicit hierarchy is a hierarchical relationship that is not explicitly represented in a directory information tree for the directory information and in which the statement comprises a SQL statement;

generating a statement in a database query language that searches for the directory information objects stored in the relational database, the statement being generated from one or more templates corresponding to search conditions in the search request, wherein the act of generating the statement is performed by a processor; and

storing the statement in a volatile or non-volatile computer readable medium or displaying the statement on a display apparatus.

2. The method of claim 1 in which the implicit hierarchy does not correspond to the pathname of the directory information objects.

3. The method of claim 1 in which the directory information objects comprise group objects.

4. The method of claim 3 in which attribute information for the members of the group objects are queried.

5. The method of claim 4 in which the attribute information comprise email information.

6. The method of claim 4 in which the attribute information comprise authorization or authentication information.

7. The method of claim 1 in which the search request seeks both direct and indirect relationships within the implicit hierarchy.

8. The method of claim 1 in which the statement comprises at most one SQL statement.

9. The method of claim 1 in which the directory information objects comprise LDAP objects.

10. The method of claim 1 in which the search request is an LDAP search filter.

11. The method of claim 1 in which the one or more templates comprise a base template comprising a header section, a body section, and a closing section, and the method further comprising:

generating a first set of query statements to fill in the header section;

generating a second set of query statements to fill in the body section; and

generating a third set of query statements to fill in the closing section.

12. The method of claim 11 in which the first set of query statements identifies database tables to be accessed.

13. The method of claim 12 in which the database tables include a database table that stored object attribute information.

14. The method of claim 12 in which the database tables include a database table that stores distinguished names information.

15. The method of claim 11 in which the second set of query statements identifies one or more catalog tables to access.

16. The method of claim 1 in which the one or more templates access a normalized name table to identify an identifier for a subject of the search request.

17. The method of claim 1 in which one or more catalog tables are accessed by the statement.

18. The method of claim 17 in which multiple identifiers for subjects are sought in the one or more catalog tables to query indirect attributes in the implicit hierarchy.

19. The method of claim 1 in which at least one of the one or more templates have the form:

SELECT [HINT COND] [SELECT LIST] FROM [FROM TABLES] WHERE [ENTRYID CLAUSE] AND  

[DNCOND] AND  

[REQD ATTRIBUTE].

20. The method of claim 19 in which [HINT COND] specifies one or more hints for a SQL optimizer.

21. The method of claim 19 in which [SELECT LIST] specifies the columns to be fetched.

22. The method of claim 19 in which [FROM TABLES] specifies a list of tables in the query.

23. The method of claim 19 in which [ENTRYID CLAUSE] specifies condition for selecting appropriate objects in a main attribute storage table.

24. The method of claim 19 in which [DNCOND] specifies a condition so that appropriate scope condition can be enforced.

25. The method of claim 19 in which [REQD ATTR] specifies a list of attributes that is requested in the query.

26. The method of claim 19 in which [SUBQUERY] specifies a subquery condition based on results for fetched objects.

27. A volatile or non-volatile computer usable medium, the volatile or non-volatile computer usable medium comprising a sequence of instructions which, when executed, causes the execution of a process for generating a statement in a database query language to search against an implicit hierarchy of directory information objects stored in a relational database, the process comprising:

receiving a search request that searches for directory information pertaining to an implicit hierarchy, wherein the implicit hierarchy is a hierarchical relationship that is not explicitly represented in a directory information tree for the directory information and in which the statement comprises a SQL statement; and

generating a statement in a database query language that searches for the directory information objects stored in the relational database, the statement being generated from one or more templates corresponding to search conditions in the search request, wherein the act of generating the statement is performed by a processor; and

storing the statement in a volatile or non-volatile computer readable medium or displaying the statement on a display apparatus.

28. The volatile or non-volatile computer usable medium of claim 27 in which the implicit hierarchy does not correspond to the pathname of the directory information objects.

29. The volatile or non-volatile computer usable medium of claim 27 in which the directory information objects comprise group objects.

30. The volatile or non-volatile computer usable medium of claim 27 in which the search request seeks both direct and indirect relationships within the implicit hierarchy.

31. The volatile or non-volatile computer usable medium of claim 27 in which the directory information objects comprise LDAP objects.

32. The volatile or non-volatile computer usable medium of claim 27 in which the search request is an LDAP search filter.

33. The volatile or non-volatile computer usable medium of claim 27 in which the one or more templates comprise a base template comprising a header section, a body section, and a closing section, and the method further comprising:

generating a first set of query statements to fill in the header section;

generating a second set of query statements to fill in the body section; and

generating a third set of query statements to fill in the closing section.

34. The volatile or non-volatile computer usable medium of claim 27 in which the one or more templates access a normalized name table to identify an identifier for a subject of the search request.

35. The volatile or non-volatile computer usable medium of claim 27 in which one or more catalog tables are accessed by the statement.

36. A system for generating a statement in a database query language to search against an implicit hierarchy of directory information objects stored in a relational database, comprising:

means for receiving a search request that searches for directory information pertaining to an implicit hierarchy, wherein the implicit hierarchy is a hierarchical relationship that is not explicitly represented in a directory information tree for the directory information and in which the statement comprises a SQL statement;

means for generating a statement in a database query language that searches for the directory information objects stored in the relational database, the statement being generated from one or more templates corresponding to search conditions in the search request, wherein the means for generating the statement comprises a processor; and

a volatile or non-volatile computer readable medium configured for storing the statement-or a display apparatus configured for displaying the statement.

37. The system of claim 36 the implicit hierarchy does not correspond to the pathname of the directory information objects.

38. The system of claim 36 in which the directory information objects comprise group objects.

39. The system of claim 36 in which the search request seeks both direct and indirect relationships within the implicit hierarchy.

40. The system of claim 36 in which the directory information objects comprise LDAP objects.

41. The system of claim 36 in which the search request is an LDAP search filter.

42. The system of claim 36 in which the one or more templates comprise a base template comprising a header section, a body section, and a closing section, and the system further comprising:

means for generating a first set of query statements to fill in the header section;

means for generating a second set of query statements to fill in the body section; and

means for generating a third set of query statements to fill in the closing section.

43. The system of claim 36 in which the one or more templates access a normalized name table to identify an identifier for a subject of the search request.

44. The system of claim 36 in which one or more catalog tables are accessed by the statement.