Dynamic object persistence

• US 6,591,277 B2
• Filed: 12/27/2000
• Issued: 07/08/2003
• Est. Priority Date: 12/27/1999
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Kurlow, Stephen, Spence, John Stanley
• Primary Examiner(s): Coby, Frantz
• Application Number:
  US09/749,188
• Publication Number:
  US 20010018689A1
• Time in Patent Office: 923 Days
• Field of Search: 707/103.R, 707/8, 707/100, 707/101, 707/102, 707/104.1, 395/683, 395/701, 395/702, 395/705, 395/708, 714/20, 717/3
• US Class Current: 707/792
• CPC Class Codes: G06F 16/289 Object oriented databases
• CPC Class Codes: G06F 9/4493 Object persistence
• CPC Class Codes: Y10S 707/955 Object-oriented
• 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/99944 Object-oriented database structure
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

Methods and apparatus for persisting objects to a database are disclosed. A set of meta-level objects (120) are defined, each object also having defined a persistence strategy. Each object also has a set of attributes which have their own respective persistence strategy. An object also can have an association with other objects each carrying respective persistence and attribute definitions. Upon a persistence request occurring, a run-time instance of an object is created carrying attributes and attached persistence strategies. The instantiated object is then executed. By defining objects, attributes and persistence strategies at a meta-level that only are populated at run-time, they each are able to be readily modified to give effect to a desired change in persistence strategy, including which attributes are to be persisted.

Claims

1. A method for persisting objects to a database, the method comprising the steps of:

(a) defining a meta-level object;

(b) defining an object persistence strategy for said object for persistence of the object into a plurality of different persistent store types with a plurality of different persistance physical structures;

(c) defining one or more attributes for said objects;

(d) defining an attribute persistence strategy for one or more of said attributes;

(e) instantiating the object, said object carrying the object persistence strategy and one or more of the attributes, each of the carried attributes having one or more attribute persistence strategies; and

(f) servicing said instantiated object.

2. The method of claim 1, whereby said persistence strategy includes both storage and retrieval actions.

3. A method, in a computer network system, for specifying a persistance framework for objects, the method comprising the steps of:

(a) defining, in said system, a meta-level object;

(b) defining, in said system, a persistence strategy for said object for persistence of the object into a plurality of different persistent store types with a plurality of different persistence physical structures;

(c) defining, in said system, one or more attributes for said object; and

(d) defining, in said system, a persistence strategy for one or more of said attributes.

4. The method of claim 3, whereby said persistence strategy includes both storage and retrieval actions.

5. The method of claim 4, comprising the further steps of:

(e) for each said persistence strategy, defining separate strategies for definition time and run time.

6. An object persistence framework, in a computer network system, comprising:

means, in said system, providing an object definition;

means, in said system, providing an object persistence definition for the object for persistence of the object into a plurality of persistence store types with a plurality of different persistence physical structures;

means, in said system, providing one or more attributes for each object; and

means, in said system, providing a persistence strategy definition for one or more of said attributes.

7. The framework of claim 6, further comprising an intermediary definition linking said object definition with said attribute definitions.

8. The framework of claim 7, further comprising one or more additional object definitions associated with the first object definition, each said additional object definition having respective persistence definitions and attributes.

9. A client-server computing system, comprising:

(a) a plurality of client computers each having

processor means implementing an application layer, and a memory storing a set of meta-level objects, a persistence strategy definition for each said object for persistence of the object into a plurality of persistent store types with a plurality of different persistence physical structures, one or more attributes for each said object, and a persistence strategy for one or more of said attributes;

(b) a plurality of server computers, each having processor means implementing an application layer, and a memory storing a set of meta-level objects, a persistence strategy definition for each said object, one or more attributes for each said object, and a persistence strategy for one or more of said attributes;

(c) a database being accessible by said server computers; and

(d) a communications link interconnecting said

client machines with said server machines; and

wherein, in response to a persistence command, one or either said client computers and/or server computers instantiates an object from amongst said set that carries with said object (i) the object'"'"'s persistence strategy and its attributes with their respective persistence strategies, to be persisted in said database.