Method for synchronizing the schema of a database with its representation in an object-oriented repository

• US 6,026,408 A
• Filed: 01/28/1998
• Issued: 02/15/2000
• Est. Priority Date: 01/28/1998
• Status: Expired due to Term

• Current Assignee: Unisys Corporation
• Original Assignee: Unisys Corporation
• Inventors: Tardiveau, Max, Srinivasan, Uppili Rangarajan
• Primary Examiner(s): Amsbury, Wayne
• Assistant Examiner(s): HAVAN, THU THAO
• Application Number:
  US09/014,302
• Time in Patent Office: 748 Days
• Field of Search: 707/101, 707/102, 707/103, 707/104, 707/10, 707/501, 707/4, 707/7, 707/3, 707/202, 707/204, 707/8, 707/203, 707/201, 345/345, 345/346, 345/348, 709/248, 709/400, 709/303, 364/222, 364/285
• US Class Current: 1/1
• CPC Class Codes: G06F 16/289 Object oriented databases
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• 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

Abstract

The present invention is an object-oriented apparatus stored in the memory of a computer system for executing a method for synchronizing schemas between a database and an object-oriented repository. The method includes the steps of initializing a variable, object X, which is of type, Type, with the object on which this method was called and obtaining values for each attribute of the object X from the database. Next, for each attribute of the object X, a comparison is made of the value obtained in the preceding step with value of attribute stored in the repository. A determination is next made as to whether or not any differences were found in the preceding step. If no differences were found, then a determination is made as to whether or not there are more attributes in the object X, and if so, repeat all steps except the first one.

Claims

1. In an object-oriented apparatus stored in the memory of a computer system a method for synchronizing the schema of a database with its representation in an object-oriented repository, said method comprising the steps of:

a. initializing a variable, object X, which is of type, Type, with the object on which said method was called;

b. obtaining values for each attribute of said object X from said database;

c. for each attribute of said object X, comparing value obtained in the preceding step with value of attribute stored in said repository;

d. determining if any differences were found in the preceding step, and if not;

e. determining if there are more attributes in said object X, and if so;

f. repeating steps b through e hereof.

2. The method as in claim 1 wherein it is determined in step e thereof that there are no more attributes in said variable X, further including the steps of:

a. determining if said object X is a composite object, and if it is;

b. obtaining all objects of contained type, Ctype, from said database along with various associated properties and storing them in a first list;

c. obtaining all contained objects of type, Ctype, from said repository and storing them in a second list;

d. comparing each object in said first list with each object in said second list and for each new object found in said first list not in said second list;

e. versioning said object X on which said method is invoked if not already versioned;

f. constructing a persistent object of type, Ctype, in said repository and setting properties of said new persistent object by using properties of said new object found in step d hereof in said first list;

g. adding said persistent object to associated property on said object X; and

,

h. determining if there are more objects in said first list, and if so, returning to step d of claim 1.

3. The method as in claim 2 where it is determined in step a that this is not a composite object, further including the step of exiting said process.

4. The method as in claim 2 where in step d it is determined that no new objects were found in said first list that are not in said second list, further including the steps of:

a. determining if any object not found in said first list is found in said second list, and if so;

b. versioning said object X on which said method was called if it is not already versioned; and

,

c. removing each object not found in said first list from associated property on said object X.

5. The method as in claim 4 further including after step a thereof if there are more contained objects, and if so, repeating steps a through c of claim 4.

6. The method as in claim 5 where in step g it is determined that there are no more contained objects, further including the step of exiting said process.

7. The method as in claim 2 further including after step a thereof, if there are more contained objects, repeating steps b through g of claim 2.

8. The method as in claim 7 further including the step of repeating all steps of claim 1 for each contained object type, Type.

9. The method as in claim 1 when it is determined in step d that differences are found, further including the steps of:

a. if said object X initialized in step a of claim 1 is not already versioned, versioning said object X; and

,

b. setting said attribute in step c of claim 1 of said object X with a new value obtained from said database.

10. The method as in claim 1 further including the step of repeating all steps of claim 1 for each object of type, Ctype, in Type.