Resolution of relationship source and target in a versioned database management system

• US 5,504,879 A
• Filed: 07/16/1992
• Issued: 04/02/1996
• Est. Priority Date: 07/16/1992
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Lehner, Mary C., Eisenberg, Neal R., Tribolet, Charles S., Huddleston, Robert L., Karasiuk, Gary R.
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): AMSBURY, WAYNE P
• Application Number:
  US07/914,903
• Time in Patent Office: 1,356 Days
• Field of Search: 395/600
• US Class Current: 1/1
• CPC Class Codes: G06F 16/288 Entity relationship models
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

A versioned data management system is provided with a method for resolving sources and targets of relationships. For each entity instance, a lifetime ID is recorded. When the add interface is used to add an entity, a value is assigned to the lifetime ID, which value has never been used before for an instance of the entity type. When the update interface is used to update an entity, the lifetime ID is maintained unchanged. If the update results in a new version, the new version is given the same lifetime ID value as that for the version that was the basis for the update. If the delete interface is then used to delete the entity, and the add interface is later used to add an instance with the same part key, that instance will have a different lifetime ID. For each relationship instance, lifetime IDs are recorded for the relationship, its source, and its target. When the add interface is used to add a relationship, a value is assigned to the lifetime ID, which value has never been used before for an instance of the relationship type. Also, the lifetime IDs of the source and target of the relationship are recorded in the relationship instance. The lifetime ID of the relationship and the lifetime IDs of the source and target are maintained unchanged. If an update results in a new version of the relationship, the new version is given the same lifetime ID value as that for the version that was the basis for the update.

Claims

1. A computer-implemented method for resolving relationships in a versioned entity relationship data management system, wherein a version of an entity represents a state of the entity, the method comprising the steps of:

providing lifetime IDs for entities in the data management system;

responsive to a request to add an entity, adding the entity and assigning a value for the lifetime ID to be used for all subsequent versions of the added entity, the assigned value being previously unused within the entity type represented by the entity version;

responsive to a request to update the entity, updating the entity and leaving the lifetime ID of the updated entity version unaltered; and

responsive to a request to update resulting in a new version of an entity, assigning for the lifetime ID of the new version the value of the lifetime ID of a previous version of the entity.

2. The method of claim 1, wherein the request to update includes a request to delete.

3. The method of claim 1, wherein every entity instance in the data management system is provided with a lifetime ID.

4. The method of claim 1, wherein the data management system includes multiple parts, each part comprising an entity or a relationship and being identified by a unique part key, the method further comprising the step of:

providing part keys for each entity to identify that entity among all entities in the data management system.

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

providing lifetime IDs for relationships in the data management system; and

responsive to a request to add a relationship, the request specifying a source and target,

assigning a value for the lifetime ID of a version of the resultant relationship version, the assigned value being previously unused within the relationship type represented by the relationship version, recording the lifetime IDs of the source and target of the relationship in the resultant relationship version.

6. The method of claim 5, further comprising the step of:

responsive to a request to delete the relationship, leaving the lifetime IDs of the relationship, its source, and its target unaltered in the resultant relationship version.

7. The method of claim 6, further comprising the step of:

responsive to a request to delete resulting in a new version of a relationship, assigning for the lifetime ID of the new version the value of the lifetime ID of a previous version of the relationship.

8. The method of claim 6, wherein every relationship instance in the data management system is provided with a lifetime ID.

9. The method of claim 8, wherein for a given first part type and a given second part type which are defined as source and target of a given relationship type, a single instance of the given relationship type connects versions of a part of the first part type which have not been deleted and whose lifetime IDs match the source lifetime ID recorded in the relationship instance with versions of a part of the second part type which have not been deleted and whose lifetime IDs match the target lifetime ID recorded in the relationship instance.

10. The method of claim 8, wherein

the assigned value for the lifetime ID of the entity version is previously unused within all entity types and relationship types,

the assigned value for the lifetime ID of the relationship instance is previously unused within all entity types and relationship types, and

a single instance of a given relationship type connects versions of a part which have not been deleted and whose lifetime IDs match the source lifetime ID recorded in the relationship instance with versions of a part which have not been deleted and whose lifetime IDs match the target lifetime ID recorded in the relationship instance.

11. The method of claim 5, further comprising the step of:

responsive to a request to update the relationship, leaving the lifetime IDs of the relationship, its source, and its target unaltered in the resultant relationship version.

12. The method of claim 5, wherein the assigned value for the lifetime ID of the relationship instance is previously unused within all entity types and relationship types.

13. The method of claim 1, wherein the request to update includes a request to delete.

14. The method of claim 1, wherein an assigned value for a lifetime ID of an entity version is previously unused within all entity types and relationship types.