← Back to Patent Explorer
US5504879A Expired / Lapsed US ⏱️ 0.0 years remaining

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

Assignee: International Business Machines Corp
•
Filing: 1992-07-16
•
Granted: 1996-04-02
•
Expires: 2012-07-16
📄 Original PDF 🌐 Google Patents 🔄 Sync Now

Abstract

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.

Inventors

  • 👤 Neal R. Eisenberg
  • 👤 Robert L. Huddleston
  • 👤 Gary R. Karasiuk
  • 👤 Mary C. Lehner
  • 👤 Charles S. Tribolet

Bibliographic Details

Application Number —
Jurisdiction US
Data Source google_patents
Last Synchronized 2026-10-25 20:24
CPC Classifications
G; G06; G06F; G06F8/00; G06F8/70; G06F8/71; G06F16/00; G06F16/20; G06F16/28; G06F16/284; G06F16/288; Y; Y10; Y10S; Y10S707/00; Y10S707/99951; Y10S707/99952; Y10S707/99953

Claims Analysis

Total Claims: 15
Claim 1
Independent Claim 146 words
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.
Claim 2
Dependent Claim 146 words
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.
Claim 3
Dependent Claim 15 words
The method of claim 1, wherein the request to update includes a request to delete.
Claim 4
Dependent Claim 20 words
The method of claim 1, wherein every entity instance in the data management system is provided with a lifetime ID.
Claim 5
Dependent Claim 54 words
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.
Claim 6
Dependent Claim 83 words
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.
Claim 7
Dependent Claim 36 words
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.
Claim 8
Dependent Claim 46 words
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.
Claim 9
Dependent Claim 20 words
The method of claim 6, wherein every relationship instance in the data management system is provided with a lifetime ID.
Claim 10
Dependent Claim 96 words
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.
Claim 11
Dependent Claim 105 words
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.
Claim 12
Dependent Claim 36 words
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.
Claim 13
Dependent Claim 27 words
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.
Claim 14
Dependent Claim 15 words
The method of claim 1, wherein the request to update includes a request to delete.
Claim 15
Dependent Claim 27 words
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.

References Cited (Backward Citations)

US4646229A Cited
US4912637A Cited
US5317729A Cited
US5315709A Cited
US5303367A Cited
US5386559A Cited

USPTO Annuity & Maintenance Windows

Annuity Stage Window Opens Payment Deadline Surcharge Period Until Estimated Fee Status
3.5 Years (Year 4) 1999-04-02 1999-10-02 2000-04-02 $2000.00 Window Closed / Lapsed
7.5 Years (Year 8) 2003-04-02 2003-10-02 2004-04-02 $3760.00 Window Closed / Lapsed
11.5 Years (Year 12) 2007-04-02 2007-10-02 2008-04-02 $7700.00 Window Closed / Lapsed

Assigned Categories & Tags

No categories assigned to this patent yet.

Assign Category Tag