Deleting data in a versioned database
AssigneeKinaxis Inc.
InventorsMarin CREANGA, Dylan ELLICOTT
Life of this patent
Estimating the term…
Abstract
Systems and methods for deleting data in a versioned database, comprising: generating a version visibility data structure (VVDS) from a version graph and scenario structure; determining each combination of feasible scenarios that when deleted, delete memory; evaluating an amount of memory reclaimed for each combination of feasible scenarios; and deleting one or more combination of scenarios to free up a specific amount of memory.
Claims15
A computer-implemented method for deleting data in a versioned database, the method comprising:
- generating, by a processor, a version visibility data structure (VVDS) from a version graph and scenario structure;
- determining, by the processor, each combination of feasible scenarios that when deleted, delete memory;
- evaluating, by the processor, an amount of memory reclaimed for each combination of feasible scenarios;
- and
- deleting, by the processor, one or more combination of scenarios to free up a specific amount of memory.
A system for deleting data in a versioned database comprising:
- a processor;
- and
- a memory storing instructions that, when executed by the processor, configure the system to:
- generate, by the processor, a version visibility data structure (VVDS) from a version graph and scenario structure;
- determine, by the processor, each combination of feasible scenarios that when deleted, delete memory;
- evaluate, by the processor, an amount of memory reclaimed for each combination of feasible scenarios;
- and
- delete, by the processor, one or more combination of scenarios to free up a specific amount of memory.
A non-transitory computer-readable storage medium, the computer-readable storage medium including instructions that when executed by a computer, cause the computer to:
- generate, by a processor, a version visibility data structure (VVDS) from a version graph and scenario structure;
- determine, by the processor, each combination of feasible scenarios that when deleted, delete memory;
- evaluate, by the processor, an amount of memory reclaimed for each combination of feasible scenarios;
- and
- delete, by the processor, one or more combination of scenarios to free up a specific amount of memory.
Dependencies are inferred from the claim text.