Database row version differentiation process

• US 5,950,210 A
• Filed: 01/29/1997
• Issued: 09/07/1999
• Est. Priority Date: 01/29/1996
• Status: Expired due to Term

• Current Assignee: Hanger Solutions, LLC (IP Investments Group LLC)
• Original Assignee: Paul M. Nelson
• Inventors: Nelson, Paul M.
• Primary Examiner(s): Lintz, Paul R.
• Assistant Examiner(s): FLEURANTIN, JEAN B
• Application Number:
  US08/790,165
• Time in Patent Office: 951 Days
• Field of Search: 364/300, 707/203, 707/1
• US Class Current: 1/1
• CPC Class Codes: G06F 16/219 Managing data history or versioning querying versioned data G06F16/2474; querying temporal data G06F16/2477
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

A method for row version differentiation in a database management system employs steps of identifying a versioned table to said database; creating a logical primary key, comprising a prescribed number of columns in the versioned table, the logical primary key being created in a physical primary key of the versioned table; defining at least one column of the physical primary key as a version effective reference value; deriving version differentiation criteria information from a version differentiation predicate included in a request submitted by a database user, the version differentiation predicate including a name of the versioned table defined to a database, a target effective status, and a target value for version differentiation processing; retrieving rows of the versioned table that satisfy the version differentiation criteria derived from the version differentiation predicate by comparing the effective reference values of the versioned table with the version differentiation criteria.

Claims

1. A method for row version differentiation in a database management system comprising:

identifying a versioned table to said database management system;

creating a physical primary key of the versioned table;

defining to said database management system at least a first portion of said physical primary key as a logical primary key;

defining to said database management system at least a second portion of the physical primary key as a version effective reference value;

deriving version differentiation criteria information from a version differentiation predicate included in a request submitted by a database user, the version differentiation predicate identifying the versioned table and a target effective status; and

retrieving rows of the versioned table that satisfy the version differentiation criteria as a function of the version differentiation predicate submitted by the database user and the version effective reference value defined to said database management system, including comparing the version effective reference value of the versioned table as defined to the database management system with the version differentiation criteria submitted by the database user.

2. The method for row version differentiation of claim 1 wherein said version effective reference value is a version effective start value, the method for version differentiation further comprising:

identifying a version effective end value that does not participate in said physical primary key of said versioned table;

said retrieving of rows from the versioned table including comparing the effective end values of the versioned table with the version differentiation criteria.

3. The method for row version differentiation of claim 2 further comprising:

defining an effective window for each row of the versioned table as a function of the effective start value and the version effective end value for each row in the versioned table; and

validating the effective window for one row of the versioned table to ensure that the effective window for the one row of the versioned table does not overlap with effective windows for other rows of the versioned table having logical primary keys matching the logical primary key for the one row of the versioned table.

4. The method for row version differentiation of claim 1 further comprising:

identifying to said database management system a referential constraint specifying as a parent said versioned table; and

ensuring that rows exist in the versioned table such that the values of their logical primary keys correspond to the values of the columns of a dependent table identified in the referential constraint for an existing row of the dependent table.

5. The method for row version differentiation of claim 4 wherein said version effective reference value is a version effective start value, the method for version differentiation further including:

identifying a column of the dependent table during the definition of said referential constraint for use as a referential constraint effective start value; and

comparing said referential constraint effective start value and said versioned effective start value.

6. The method for row version differentiation of claim 5 further including:

identifying a column of the dependent table, during the definition of said referential constraint, for use as a referential constraint effective end value; and

comparing said referential constraint effective start value to said versioned effective start value and said effective end value.

7. The method for row version differentiation of claim 6 further comprising:

defining a referential constraint effective window for each row of the dependent table as a function of the referential constraint effective start value and the referential constraint effective end value for each row of the dependent table; and

validating the referential constraint effective window for one row of the dependent table to ensure that the referential constraint effective window for the one row of the dependent table does not overlap with the referential constraint effective windows for other rows of the dependent table having logical primary keys matching the logical primary key for the one row of the dependent table.

8. A method for row version differentiation in a database management system comprising:

identifying a versioned table to said database management system;

creating a physical primary key of the versioned table;

defining to said database management system at least a first portion of said physical primary key as a logical primary key;

defining to said database management system at least a second portion of the physical primary key as a version effective reference value;

deriving version differentiation criteria information from a version differentiation predicate included in a request submitted by a database user, the version differentiation predicate identifying the versioned table and a target effective status, and a target value range as defined by a target start value and a target end value that are included in said version differentiation predicate; and

retrieving rows of the versioned table that satisfy the version differentiation criteria as a function of the version differentiation predicate submitted by the user and the version effective reference value defined to said database management system, including comparing the version effective reference value of the versioned table as defined to the database management system with the version differentiation criteria submitted by the database user.

9. The method for row version differentiation of claim 8 further comprising:

validating said target value range for one row of the versioned table to ensure that the target value range for the one row of the versioned table does not overlap with the target value ranges for other rows of the versioned table having logical primary keys matching the logical primary key for the one row of the versioned table.