Method, server/computer and data structure for implementation of complex objects in an object-oriented database

• US 6,401,101 B1
• Filed: 05/27/1999
• Issued: 06/04/2002
• Est. Priority Date: 06/01/1998
• Status: Expired due to Fees

• Current Assignee: Trident Systems, Inc. (Atlas Copco AB)
• Original Assignee: Trident Systems, Inc. (Atlas Copco AB)
• Inventors: Britton, David E., Kalafut, Thomas M., Kelly, Vasiliki Paraskevas, Karangelen, Nicholas E., Surowiec, Theresa, Stoddard, Michael
• Primary Examiner(s): ROBINSON, GRETA LEE
• Application Number:
  US09/320,983
• Time in Patent Office: 1,104 Days
• Field of Search: 707/103, 707/100, 707/10, 709/203
• US Class Current: 1/1
• CPC Class Codes: G06F 16/289 Object oriented databases
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure
• CPC Class Codes: Y10S 707/99946 Object-oriented database structure network

Abstract

The present invention provides a method, server/computer and data structure for reducing the overhead of dynamically linking attribute values across objects and minimizing memory requirements for storing cloned objects by utilizing a process of generating at least two Complex Objects, each having at least one Component Object, wherein each of said Complex Objects shares at least one Component Object with another Complex Object. By using a combination of Tailored Server and class methods (for construction, property access, copy, clone, delete, etc.) in handling the Complex Objects, the present invention hides the multiple Component Object complexity from the user and manages the generation and modification of Complex Objects including object schema definition and object instantiation. Thus, for example, Complex Object cloning permits a concomitant change for a common core property value to be accomplished for all clones that share the Shared Component Object.

Claims

1. An object-oriented database comprising:

at least two Complex Objects, each having at least one Component Object, wherein each of said Complex Objects shares at least one Component Object with another Complex Object.

2. A data structure comprising:

at least two Complex Objects, each having at least one Component Object, wherein each of said Complex Objects shares at least one Component Object with another Complex Object.

3. A server, comprising:

a memory having stored thereon executable instructions for generating at least two Complex Objects, each having at least one Component Object, wherein each of said Complex Objects shares at least one Component Object with another Complex Object, the memory also having an object-oriented database formed therein for storing object-oriented data; and

a processor, coupled to the memory, for utilizing the executable instructions to generate the Complex Objects.

4. The server of claim 3 wherein the executable instructions further include instructions for at least one of:

managing or modifying the Complex Objects.

5. The server of claim 3 wherein an Identity Component Class defines the executable instructions for accessing properties of the Complex Objects.

6. The server of claim 5 wherein the executable instructions include instructions for overloading a construction method of the Identity Component Class to provide a View and Shared Component Object and to generate a relationship from an Identity Component Object to the View and Shared Component Object tat is generated when the Identity Component Object is generated.

7. The server of claim 5 wherein the executable instructions include instructions for overloading a destructor method of the Identity Component Class to provide for destroying View Component Objects and a Shared Component Object where said View/Shared Component Objects are unshared by another Complex Object.

8. The server of claim 5 wherein a copy constructor/method of the Identity Component Class is defined to provide that, when a Complex Object is copied, Shared and selected View Component Objects are also copied.

9. The server of claim 5 wherein a clone constructor/method of the Identity Component Class is defined to provide that, when a Complex Object is cloned, only an Identity and selected View Component Objects are copied and a relationship is generated to reference Shared Component Object(s).

10. A computer in a network, comprising:

a memory having;

an object-oriented database stored thereon comprising at least two Complex Objects, each having at least one Component Object, wherein each of said Complex Objects shares at least one Component Object with another Complex Object; and

software loaded thereon, wherein said software includes executable instructions for providing service to other computers in the network and executable instructions for generating Complex Objects; and

a processor, coupled to the memory, for implementing executable instructions for providing service to other computers in the network and for utilizing executable instructions to generate Complex Objects.

11. The computer of claim 10 wherein the executable instructions further include instructions for at least one of:

managing or modifying the Complex Objects.

12. The computer of claim 10 wherein an Identity Component Class defines the executable instructions for accessing properties of the Complex Objects.

13. The computer of claim 12 wherein the executable instructions include instructions for overloading a construction method of the Identity Component Class to provide a View and Shared Component Object and to generate a relationship from an Identity Component Object to the View and Shared Component Object that is generated when the Identity Component Object is generated.

14. The computer of claim 12 wherein the executable instructions include instructions for overloading a destructor method of the Identity Component Class to provide for destroying View components and a Shared Component Object where said View/Shared Component Objects are unshared by another Object.

15. The computer of claim 12 wherein a copy constructor/method of the Identity Component Class is defined to provide that, when a Complex Object is copied, Shared and selected View Component Objects are also copied.

16. The computer of claim 12 wherein a clone constructor/method of the Identity Component Class is defined to provide that, when a Complex Object is cloned, only an Identity and selected View Component Objects are copied and a relationship is generated to reference Shared Component Object(s).

17. A computer in a network, comprising:

a memory having;

a first memory portion for storing data in a database; and

a second memory portion for storing executable instructions for generating at least two Complex Objects, each Complex Object having at least one Component Object and each Complex Object sharing at least one Component Object with another Complex Object; and

a processor, coupled to the memory, for utilizing the executable instructions to generate the Complex Objects.

18. The computer of claim 17 wherein the database is an object-oriented database for storing the at least two Complex Objects.

19. The computer of claim 17 wherein the executable instructions include instructions for providing service to other computers in the network.

20. The computer of claim 19 wherein the processor further implements the executable instructions for providing service to the other computers.

21. The computer of claim 17 wherein the executable instructions further include instructions for at least one of:

managing or modifying Complex Objects.

22. The computer of claim 17 wherein an Identity Component Class defines the executable instructions for accessing properties of the Complex Objects.

23. The computer of claim 22 wherein the executable instructions include instructions for overloading a construction method of the Identity Component Class to provide a View and Shared Component Object and to generate a relationship from an Identity Component Object to the View and Shared Component Object that is generated when the Identity Component Object is generated.

24. The computer of claim 22 wherein the executable instructions include instructions for overloading a destructor method of the Identity Component Class to provide for destroying View Component Objects and a Shared Component Object where said View/Shared Component Objects are unshared by another Complex Object.

25. The computer of claim 22 wherein a copy constructor/method of the Identity Component Class is defined to provide that, when a Complex Object is copied, Shared and selected View Component Objects arc also copied.

26. The computer of claim 22 wherein a clone constructor/method of the Identity Component Class is defined to provide that, when a Complex Object is cloned, only an Identity and selected View Component Objects are copied and a relationship is generated to reference Shared Component Object(s).

27. A method for providing an object-oriented database with Complex Objects in a network, comprising the steps of:

generating at least two Complex Objects, each having at least one Component Object, wherein each of said Complex Objects shares at least one Component Object with another Complex Object; and

storing the Complex Objects in an object oriented database.

28. The method of claim 27 wherein the method further includes providing service to computers in the network.

29. The method of claim 27 wherein the method further includes at least one of:

managing or modifying the Complex Objects.

30. The method of claim 27 wherein the method further includes a step of accessing properties of the Complex Objects defined by an Identity Component Class.

31. The method of claim 30 further including overloading a construction method of the Identity Component Class to provide a View and Shared Component Object and to generate a relationship from an Identity Component Object to the View and Shared Component Object that is generated when the Identity Component Object is generated.

32. The method of claim 30 further including overloading a destructor method of the Identity Component Class to provide for destroying View Component Objects and a Shared Component Object where said View/Shared Component Objects are unshared by another Complex Object.

33. The method of claim 30 further including defining a copy constructor/method of the Identity Component Class to provide that, when a Complex Object is copied, Shared and selected View Component Objects are also copied.

34. The method of claim 30 further including defining a clone constructor/method of the Identity Component Class to provide that, when a Complex Object is cloned, only an Identity and selected View Component Objects are copied and a relationship is generated to reference Shared Component Object(s).

35. A tailored server for reducing overhead of dynamically linking attribute values across objects and minimizing memory requirements for storing cloned objects, the tailored server comprising:

an object oriented database configured to utilize a processor to hide individual component classes of complex objects.

36. A system for reducing overhead of dynamically linking attribute values across objects and minimizing memory requirements for storing cloned objects, the system comprising:

a modified tailored server, coupled to a client computer, for utilizing class methods and an object oriented database to hide individual component classes of complex objects.

37. A system for reducing overhead of dynamically linking attribute values across objects and minimizing memory requirements for storing cloned objects, the system comprising:

a front-end server, coupled to an object oriented database and to a client computer, and configured to operate to hide individual component classes of complex objects.

38. A system for reducing overhead of dynamically linking attribute values across objects and minimizing memory requirements for storing cloned objects, the system comprising:

a client computer coupled to a server and including an object oriented database with object methods configured to utilize a processor to hide individual component classes of complex objects.

39. A method for managing a Complex Object having a plurality of Component Object Classes, the method comprising the steps of:

partitioning the plurality of Component Object Classes;

establishing relationships between the partitioned Component Object Classes; and

hiding the partitioned Component Object Classes behind a set of methods such the partitioned Component Object Classes appear as a single Component Object Class.