Efficient queriability of version histories in a repository

• US 7,730,032 B2
• Filed: 01/12/2006
• Issued: 06/01/2010
• Est. Priority Date: 01/12/2006
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Sedlar, Eric, Baby, Thomas, Idicula, Sam, Agarwal, Nipun
• Primary Examiner(s): Trujillo; James
• Assistant Examiner(s): SOMERS, MARC S
• Application Number:
  US11/332,117
• Publication Number:
  US 20070162441A1
• Time in Patent Office: 1,601 Days
• Field of Search: 707/203
• US Class Current: 707/638
• CPC Class Codes: G06F 16/1873 Versioning file systems, temporal file systems, e.g. file system supporting different historic versions of files
• CPC Class Codes: G06F 40/197 Version control for software G06F8/71

Abstract

Efficient evaluation of resource version history queries is enabled by using a data container storing records corresponding to links between successive versions of a resource. The records include: (a) a record identifier, (b) a predecessor identifier, (c) a successor identifier, (d) a predecessor rowset, which comprises the record identifier of each record in which the predecessor identifier in this record is the successor identifier, and (e) a successor rowset, which comprises the record identifier of each record in which the successor identifier in this record is the predecessor identifier. Depending on the nature of a request, a record is identified in which a particular version is identified by either the predecessor identifier or the successor identifier. Either the predecessor or successor rowsets are recursively read, while the predecessor or successor identifiers corresponding to each record read are added to a result set, thereby forming the ancestor or descendant version history.

Claims

1. A computer-implemented method comprising:

determining a version history for a particular version of a resource identified by a unique identifier, including;

accessing a version history data table;

wherein the version history data table includes a plurality of rows;

wherein each particular row of the plurality of rows represents one and only one link between successive versions of said resource;

wherein each particular row of the plurality of rows does not represent a particular version of said resource;

wherein said resource is stored in a database, said database supporting versioning of resources,

wherein each row of the plurality of rows is associated with a row identifier that uniquely identifies said row, and each row represents;

a predecessor identifier, wherein the predecessor identifier is a unique identifier of a version that immediately precedes, in said version history of said resource, the link corresponding to this row, and

a successor identifier, wherein the successor identifier is a unique identifier of a version that immediately succeeds, in said version history of said resource, the link corresponding to this row,

a predecessor rowset, wherein the predecessor rowset comprises the row identifier of each of one or more corresponding rows, in said version history data table, in which the predecessor identifier in this row is the successor identifier in a corresponding row of said one or more corresponding rows, and

a successor rowset, wherein the successor rowset comprises the row identifier of each of one or more corresponding rows, in said version history data table, in which the successor identifier in this row is the predecessor identifier in a corresponding row of said one or more corresponding rows; and

based on the unique identifier of said particular version of said resource, locating in said version history data table one or more rows in which the unique identifier of said particular version of said resource is one of either the predecessor identifier or the successor identifier;

wherein the steps of accessing and locating are performed by one or more computing devices.

2. The method of claim 1, wherein said step of determining includes determining an ancestor version history for said particular version of said resource, and wherein said step of locating further comprises the steps of:

locating one or more first rows in which the unique identifier of said particular version of said resource is the predecessor identifier;

reading the predecessor rowset from each of said one or more first rows;

recursively reading one or more predecessor rowsets for the rows corresponding to one or more row identifiers in the predecessor rowset from each of said one or more first rows until reading, for each recursion, a predecessor rowset that is empty or null; and

while performing said step of recursively reading said one or more predecessor rowsets, adding to a result set the predecessor identifier corresponding to each of the rows read.

3. The method of claim 2, further comprising the steps of:

determining one or more resource identifiers corresponding to respective one or more predecessor identifiers in said result set;

accessing a resource data table that is a different data table than said version history data table, wherein resources in said resource data table are identified by corresponding resource identifiers; and

reading, from said resource data table, one or more resources corresponding to said one or more resource identifiers.

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

while performing a database operation that involves said resource data table, updating said version history data table.

5. The method of claim 1, wherein said step of determining includes determining a descendant version history for said particular version of said resource, and wherein said step of locating further comprises the steps of:

locating one or more first rows in which the unique identifier of said particular version of said resource is the successor identifier;

reading the successor rowset from each of said one or more first rows;

recursively reading one or more successor rowsets for the rows corresponding to one or more row identifiers in the successor rowset from each of said one or more first rows until reading, for each recursion, a successor rowset that is empty or null; and

while performing said step of recursively reading said one or more successor rowsets, adding to a result set the successor identifier corresponding to each of the rows read.

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

determining one or more resource identifiers corresponding to respective one or more successor identifiers in said result set;

accessing a resource data table that is a different data table than said version history data table, wherein resources in said resource data table are identified by corresponding resource identifiers; and

reading, from said resource data table, one or more resources corresponding to said one or more resource identifiers.

7. The method of claim 1, wherein each row contains the predecessor identifier, the successor identifier, the predecessor rowset, and the successor rowset.

8. The method of claim 1, further comprising the steps of:

in response to a process in which a modified version of a first resource is checked into said database,

creating one or more new rows in said version history data table by, for each of the one or more new rows,

generating a row identifier that uniquely identifies the row,

inserting in the row a predecessor identifier corresponding to a version of said first resource that immediately precedes said modified version of said first resource,

inserting in the row a successor identifier corresponding to said modified version of said first resource, and

inserting in the row a predecessor rowset comprising the row identifier of each of one or more corresponding rows, in said version history data table, in which the predecessor identifier corresponding to the version of said first resource that immediately precedes said modified version of said first resource is the successor identifier in a corresponding row of said one or more corresponding rows; and

updating each row, in said version history data table, in which the successor identifier corresponds to a version of said first resource that immediately precedes said modified version of said first resource, by,

updating the successor rowset to include the row identifier of each of said one or more new rows.

9. A computer-readable storage medium storing a data structure in which data is stored, wherein each particular row of one or more rows in said data structure represents one and only one link between successive versions of a resource stored in a database that supports versioning of resources, wherein each particular row of the one or more rows does not represent a particular version of said resource, wherein each row is associated with a row identifier that uniquely identifies the row, and wherein said data structure comprises:

a first field for storing a predecessor identifier, wherein the predecessor identifier is a unique identifier of a version that immediately precedes the link corresponding to this row;

a second field for storing a successor identifier, wherein the successor identifier is a unique identifier of a version that immediately succeeds the link corresponding to this row;

a third field for storing a predecessor rowset, wherein the predecessor rowset comprises the row identifier of each of one or more corresponding predecessor rows, in said data structure, in which the predecessor identifier in this row is the successor identifier in a corresponding row of said one or more corresponding predecessor rows; and

a fourth field for storing a successor rowset, wherein the successor rowset comprises the row identifier of each of one or more corresponding successor rows, in said data structure, in which the successor identifier in this row is the predecessor identifier in a corresponding row of said one or more corresponding successor rows.

10. A computer-readable storage medium storing instruction for including instructions for performing the steps of:

determining a version history for a particular version of a resource identified by a unique identifier, including;

accessing a version history data table;

wherein the version history data table includes a plurality of rows;

wherein each particular row of the plurality of rows represents one and only one link between successive versions of said resource;

wherein each particular row of the plurality of rows does not represent a particular version of said resource;

wherein said resource is stored in a database, said database supporting versioning of resources,

wherein each row of the plurality of rows is associated with a row identifier that uniquely identifies said row, and each row represents;

a predecessor identifier, wherein the predecessor identifier is a unique identifier of a version that immediately precedes, in said version history of said resource, the link corresponding to this row, and

a successor identifier, wherein the successor identifier is a unique identifier of a version that immediately succeeds, in said version history of said resource, the link corresponding to this row,

a predecessor rowset, wherein the predecessor rowset comprises the row identifier of each of one or more corresponding rows, in said version history data table, in which the predecessor identifier in this row is the successor identifier in a corresponding row of said one or more corresponding rows, and

a successor rowset, wherein the successor rowset comprises the row identifier of each of one or more corresponding rows, in said version history data table, in which the successor identifier in this row is the predecessor identifier in a corresponding row of said one or more corresponding rows; and

based on the unique identifier of said particular version of said resource, locating in said version history data table one or more rows in which the unique identifier of said particular version of said resource is one of either the predecessor identifier or the successor identifier.

11. The computer-readable storage medium of claim 10, wherein said step of determining includes determining an ancestor version history for said particular version of said resource, and wherein said step of locating further comprises the steps of:

locating one or more first rows in which the unique identifier of said particular version of said resource is the predecessor identifier;

reading the predecessor rowset from each of said one or more first rows;

recursively reading one or more predecessor rowsets for the rows corresponding to one or more row identifiers in the predecessor rowset from each of said one or more first rows until reading, for each recursion, a predecessor rowset that is empty or null; and

while performing said step of recursively reading said one or more predecessor rowsets, adding to a result set the predecessor identifier corresponding to each of the rows read.

12. The computer-readable storage medium of claim 11, wherein the instructions further comprise instructions for performing the steps of:

determining one or more resource identifiers corresponding to respective one or more predecessor identifiers in said result set;

accessing a resource data table that is a different data table than said version history data table, wherein resources in said resource data table are identified by corresponding resource identifiers; and

reading, from said resource data table, one or more resources corresponding to said one or more resource identifiers.

13. The computer-readable storage medium of claim 12, wherein the instructions further comprise instructions for performing the step of:

while performing a database operation that involves said resource data table, updating said version history data table.

14. The computer-readable storage medium of claim 10, wherein said step of determining includes determining a descendant version history for said particular version of said resource, and wherein said step of locating further comprises the steps of:

locating one or more first rows in which the unique identifier of said particular version of said resource is the successor identifier;

reading the successor rowset from each of said one or more first rows;

recursively reading one or more successor rowsets for the rows corresponding to one or more row identifiers in the successor rowset from each of said one or more first rows until reading, for each recursion, a successor rowset that is empty or null; and

while performing said step of recursively reading said one or more successor rowsets, adding to a result set the successor identifier corresponding to each of the rows read.

15. The computer-readable storage medium of claim 14, wherein the instructions further comprise instructions for performing the steps of:

determining one or more resource identifiers corresponding to respective one or more successor identifiers in said result set;

accessing a resource data table that is a different data table than said version history data table, wherein resources in said resource data table are identified by corresponding resource identifiers; and

reading, from said resource data table, one or more resources corresponding to said one or more resource identifiers.

16. The computer-readable storage medium of claim 10, wherein the instructions further comprise instructions for performing the steps of:

in response to a process in which a modified version of a first resource is checked into said database,

creating one or more new rows in said version history data table by, for each of the one or more new rows,

generating a row identifier that uniquely identifies the row,

inserting in the row a predecessor identifier corresponding to a version of said first resource that immediately precedes said modified version of said first resource,

inserting in the row a successor identifier corresponding to said modified version of said first resource, and

inserting in the row a predecessor rowset comprising the row identifier of each of one or more corresponding rows, in said version history data table, in which the predecessor identifier corresponding to the version of said first resource that immediately precedes said modified version of said first resource is the successor identifier in a corresponding row of said one or more corresponding rows; and

updating each row, in said version history data table, in which the successor identifier corresponds to a version of said first resource that immediately precedes said modified version of said first resource, by,

updating the successor rowset to include the row identifier of each of said one or more new rows.

17. The computer-readable storage medium of claim 10, wherein each row contains the predecessor identifier, the successor identifier, the predecessor rowset, and the successor rowset.