US 7,627,615 B2Granted

Copy-on-write versioning of documents

AssigneeOracle International Corporation

InventorDouglas James McMahon

Life of this patent

Estimating the term…

Loading patent…

Abstract

Approach for versioning of documents is described. A version accumulator structure stores one or more version values indicating different versions of a data object. The data object is decomposable into a plurality of nodes. One or more copies of each node of the plurality of nodes are stored, where the one or more copies are associated with non-overlapping version ranges. A first request to perform a change to the data object is received. The first request specifies an effective version value for the change, which involves a particular node. The change is performed based on the effective version value and without making a deep copy of the data object. A second request to retrieve a certain version of the data object is received. The certain version is retrieved based on the version ranges associated with the one or more copies of each node of the plurality of nodes.

Claims32

Dependent claims

A computer-implemented method for versioning of data objects comprising:

storing one or more version values in a version accumulator structure, wherein each of the one or more version values indicates a different version of a data object;
wherein the data object includes, and is decomposable into, a plurality of nodes;
storing one or more copies of each node of the plurality of nodes, wherein each copy of the one or more copies is associated with a version range which does not overlap with any other version range that is associated with any other copy of the one or more copies;
receiving a first request to perform a change to the data object, wherein the change involves a particular node of the plurality of nodes, and wherein the first request specifies an effective version value for the change;
performing the change to the data object, wherein performing the change does not include making a complete copy of the data object that reflects the change, and wherein performing the change comprises:
inspecting the version accumulator structure to determine a terminal version value, wherein the terminal version value is the smallest version value stored in the version accumulator structure that is greater than the effective version value specified in the first request;
and
performing the change based at least on the effective version value and the terminal version value;
wherein performing the change to the data object further comprises adding the particular node to the plurality of nodes included in the data object, wherein adding the particular node to the plurality of nodes comprises:
storing a copy of the particular node, wherein the copy of the particular node is associated with a particular version range, wherein a minimum version value included in the particular version range is set to the effective version value, and wherein a maximum version value included the particular version range is set to the terminal version value;
and
if the effective version value is not already stored in the version accumulator structure, then storing the effective version value in the version accumulator structure:
receiving a second request to retrieve a certain version of the data object;
and
retrieving the certain version of the data object based on version ranges associated with the one or more copies of each node of the plurality of nodes;
wherein the method is performed by one or more computing devices.

13 more elements

A machine-readable volatile or non-volatile medium storing one or more sequences of instructions which, when executed by one or more processors, cause:

storing one or more version values in a version accumulator structure, wherein each of the one or more version values indicates a different version of a data object;
wherein the data object includes, and is decomposable into, a plurality of nodes;
storing one or more copies of each node of the plurality of nodes, wherein each copy of the one or more copies is associated with a version range which does not overlap with any other version range that is associated with any other copy of the one or more copies;
receiving a first request to perform a change to the data object, wherein the change involves a particular node of the plurality of nodes, and wherein the first request specifies an effective version value for the change;
performing the change to the data object, wherein performing the change does not include making a complete copy of the data object that reflects the change, and wherein performing the change comprises:
inspecting the version accumulator structure to determine a terminal version value, wherein the terminal version value is the smallest version value stored in the version accumulator structure that is greater than the effective version value specified in the first request;
and
performing the change based at least on the effective version value and the terminal version value;
wherein performing the change to the data object further comprises adding the particular node to the plurality of nodes included in the data object, wherein adding the particular node to the plurality of nodes comprises:
storing a copy of the particular node, wherein the copy of the particular node is associated with a particular version range, wherein a minimum version value included in the particular version range is set to the effective version value, and wherein a maximum version value included the particular version range is set to the terminal version value;
and
if the effective version value is not already stored in the version accumulator structure, then storing the effective version value in the version accumulator structure;
receiving a second request to retrieve a certain version of the data object;
and
retrieving the certain version of the data object based on version ranges associated with the one or more copies of each node of the plurality of nodes.

12 more elements

Dependencies are inferred from the claim text.