Optimized fetching for customization object attributes

• US 8,171,054 B1
• Filed: 12/21/2007
• Issued: 05/01/2012
• Est. Priority Date: 12/21/2007
• Status: Active Grant

• Current Assignee: Open Text Corporation
• Original Assignee: EMC Corporation (Dell Technologies Inc.)
• Inventors: Wei, Shu-Shang Sam, Kilday, Roger W., Spivak, Victor, Amiel, Meir, Chandrasekaran, Venkat, Li, Yik-Ping, Ma, Xiaofeng
• Primary Examiner(s): LE, THU NGUYET T
• Application Number:
  US12/005,167
• Time in Patent Office: 1,593 Days
• Field of Search: 707/609, 707791-804, 707955-956
• US Class Current: 707/793
• CPC Class Codes: G06F 16/282 Hierarchical databases, e.g. IMS, LDAP data stores or Lotus Notes
• CPC Class Codes: G06F 16/289 Object oriented databases

Abstract

An attribute of a hierarchical class-based object is received. The attribute in a database is stored both in a first location in a first table at a first level of a hierarchy of database tables which table hierarchy is based at least in part on a class hierarchy associated with the hierarchical class-based object and in a second location in a second table at a second level of the table hierarchy which second level is higher than the first level.

Claims

1. A method for storing an attribute, comprising:

receiving an attribute of a hierarchical class-based object,

wherein the attribute is associated with a customization object that is not part of a hierarchy of class-based objects but is attached to an instance of the hierarchical class-based object to result in adding the attribute to the instance of the hierarchical class-based object, wherein the attribute comprises a new attribute not defined in a class associated with the hierarchical class-based object; and

storing the attribute in a database both in a location in a first table and in a location in a second table, wherein the first table is associated with a first level of a hierarchy of database tables based at least in part on a class hierarchy associated with the hierarchical class-based object and the second table is associated with a second level of the hierarchy of database tables, wherein the second level is higher than the first level and is accessed faster than the first level, wherein the first table is associated with the customization object, wherein the stored attribute in the location in the second table is accessed as a set of attributes.

2. A method as in claim 1, wherein the customization object is not described by the hierarchical classed-based object.

3. A method as in claim 2, wherein the customization object is designated as fetch optimized.

4. A method as in claim 2, wherein the attribute of the customization object is designated as fetch optimized.

5. A method as in claim 1, wherein the second level of the table hierarchy corresponds to the top level of the hierarchical class-based object.

6. A method as in claim 1, wherein the attribute that is stored in the location in the second table at the second level of the table hierarchy is accessible faster than the attribute that is stored in the location in the first table at the first level of the of the table hierarchy.

7. A method as in claim 1, wherein the attribute stored in the location in the second table is stored with one or more other attributes as a set of attributes.

8. A system for storing an attribute, comprising:

a memory;

a network interface for receiving an attribute of a hierarchical class-based object,

wherein the attribute is associated with a customization object that is not part of a hierarchy of class-based objects but is attached to an instance of the hierarchical class-based object to result in adding the attribute to the instance of the hierarchical class-based object, wherein the attribute comprises a new attribute not defined in a class associated with the hierarchical class-based object; and

a database for storing the attribute in a database both in a location in a first table and in a location in a second table, wherein the first table is associated with a first level of a hierarchy of database tables based at least in part on a class hierarchy associated with the hierarchical class-based object and the second table is associated with a second level of the hierarchy of database tables, wherein the second level is higher than the first level and is accessed faster than the first level, wherein the first table is associated with the customization object, wherein the stored attribute in the location in the second table is accessed as a set of attributes.

9. A system as in claim 8, wherein the customization object is not described by the hierarchical classed-based object.

10. A system as in claim 9, wherein the customization object is designated as fetch optimized.

11. A system as in claim 9, wherein the attribute of the customization object is designated as fetch optimized.

12. A system as in claim 8, wherein the second level of the table hierarchy corresponds to the top level of the hierarchical class-based object.

13. A system as in claim 8, wherein the attribute that is stored in the location in the second table at the second level of the table hierarchy is accessible faster than the attribute that is stored in the first location in the first table at the first level of the of the table hierarchy.

14. A system as in claim 8, wherein the attribute stored in the location in the second table is stored with one or more other attributes as a set of attributes.

15. A computer program product for storing an attribute, the computer program product being embodied in a computer readable storage medium and comprising computer instruction for:

receiving an attribute of a hierarchical class-based object,

wherein the attribute is associated with a customization object that is not part of a hierarchy of class-based objects but is attached to an instance of the hierarchical class-based object to result in adding the attribute to the instance of the hierarchical class-based object, wherein the attribute comprises a new attribute not defined in a class associated with the hierarchical class-based object; and

storing the attribute in a database both in a location in a first table and in a location in a second table, wherein the first table is associated with a first level of a hierarchy of database tables based at least in part on a class hierarchy associated with the hierarchical class-based object and the second table is associated with a second level of the hierarchy of database tables, wherein the second level is higher than the first level and is accessed faster than the first level, wherein the first table is associated with the customization object, wherein the stored attribute in the location in the second table is accessed as a set of attributes.

16. The computer program product recited in claim 15, wherein the customization object is not described by the hierarchical classed-based object.

17. The computer program product recited in claim 16, wherein the customization object is designated as fetch optimized.

18. The computer program product recited in claim 16, wherein the attribute of the customization object is designated as fetch optimized.

19. The computer program product recited in claim 15, wherein the second level of the table hierarchy corresponds to the top level of the hierarchical class-based object.

20. The computer program product recited in claim 15, wherein the attribute stored in the location in the second table is stored with one or more other attributes as a set of attributes.