Conditional commit for data in a database

• US 10,140,331 B2
• Filed: 02/05/2016
• Issued: 11/27/2018
• Est. Priority Date: 03/05/2009
• Status: Active Grant

• Current Assignee: MATRIXX Software, Inc.
• Original Assignee: MATRIXX Software, Inc.
• Inventors: Labuda, David
• Primary Examiner(s): Waldron, Scott A.
• Assistant Examiner(s): Mina, Fatima P
• Application Number:
  US15/017,478
• Publication Number:
  US 20160154843A1
• Time in Patent Office: 1,026 Days
• CPC Class Codes: G06F 16/21 Design, administration or maintenance of databases
• CPC Class Codes: G06F 16/23 Updating
• CPC Class Codes: G06F 16/2315 Optimistic concurrency control
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/2379 Updates performed during online database operations; commit processing

Abstract

A database comprises a database interface and a database updater. The database interface enables a reading of a first set of information from the database. The database updater updates a second set of information in the database based at least in part on one or more conditions. The one or more conditions limit changes allowable to the first set of information from the database that occurred after the reading of the first set of information from the database.

Claims

1. A database, comprising:

an interface to receive a first set of information from the database; and

a hardware processor to;

read, via a first process, a first portion of the first set of information without a first read latch occurring during the read in the database, wherein the first portion comprises a first database initial value of a first database entry;

start a first calculation using the first portion of the first set of information;

after the reading of the first set of information is performed, read, via a second process, the first portion and a second portion of the first set of information without a second read latch occurring during the read in the database, wherein the second portion comprises a second database initial value of a second database entry;

update, via the second process, the first set of information to a second set of information in the database, wherein updating is based at least in part on the first database initial value of the first database entry and the second database initial value of the second database entry, wherein updating comprises updating the first database initial value of the first database entry to a first updated value and updating the second database initial value of the second database entry to a second updated value;

after the updating of the first set of information, read, via the first process, the second updated value of the second database entry; and

after the reading of the second updated value of the second database entry, calculate, for the first process, a second set of information update using the first database initial value and the second updated value;

update, via the first process, the second set of information in the database based at least in part on the second set of information update and based at least in part on one or more conditions, wherein the one or more conditions limit changes allowable to the first set of information from the database that occurred after receiving the first set of information from the database.

2. A database as in claim 1, wherein the first set of information from the database comprises one or more data entries in the database.

3. A database as in claim 1, wherein the second set of information from the database comprises one or more data entries in the database.

4. A database as in claim 1, wherein one condition of the one or more conditions comprises one or more of the following:

a condition that a database entry is less than an upper limit value, less than or equal to an upper limit value, more than a lower limit value, more than or equal to a lower limit value, or equal to a predetermined value.

5. A database as in claim 1, wherein one of the second set of information is updated to one or more of the following:

a first absolute value or a value relative to a current value.

6. A database as in claim 5, wherein the value relative to the current value is a value less than the current value.

7. A database as in claim 5, wherein the value relative to the current value is a value greater than the current value.

8. A database as in claim 1, wherein one condition of the one or more conditions comprises a database value having been written since a specific prior read.

9. A database as in claim 1, wherein one condition of the one or more conditions comprises a database value having been written since a specific prior time.

10. A database as in claim 1, wherein one condition of the one or more conditions comprises a database value having not been written since a specific prior read.

11. A database as in claim 1, wherein one condition of the one or more conditions comprises a database value having not been written since a specific prior time.

12. A database as in claim 1, wherein one condition of the one or more conditions comprises a database value having been read since a specific prior read.

13. A database as in claim 1, wherein one condition of the one or more conditions comprises a database value having been read since a specific prior time.

14. A database as in claim 1, wherein one condition of the one or more conditions comprises a database value having not been read since a specific prior read.

15. A database as in claim 1, wherein one condition of the one or more conditions comprises a database value having not been read since a specific prior time.

18. A database as in claim 1, wherein in the event that the one or more conditions are not met, omit updating the second set of information.

16. A method for a database, comprising:

receiving a first set of information from the database;

reading, via a first process, a first portion of the first set of information without a first read latch occurring during the read in the database, wherein the first portion comprises a first database initial value of a first database entry;

after the reading of the first set of information is performed, reading, via a second process, the first portion and a second portion of the first set of information without a second read latch occurring during the read in the database, wherein the second portion comprises a second database initial value of a second database entry;

updating, via the second process, the first set of information to a second set of information in the database, wherein updating is based at least in part on the first database initial value of the first database entry and the second database initial value of the second database entry, wherein updating comprises updating the first database initial value of the first database entry to a first updated value and updating the second database initial value of the second database entry to a second updated value;

after the updating of the first set of information, reading, via the first process, the second updated value of the second database entry; and

after the reading of the second updated value of the second database entry, calculating, for the first process, a second set of information update using the first database initial value and the second updated value;

updating, via the first process using a hardware processor, the second set of information in the database based at least in part on the second set of information update and based at least in part on one or more conditions, wherein the one or more conditions limit changes allowable to the first set of information from the database that occurred after receiving the first set of information from the database.

17. A computer program product for a database, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:

receiving a first set of information from the database;

reading, via a first process, a first portion of the first set of information without a first read latch occurring during the read in the database, wherein the first portion comprises a first database initial value of a first database entry;

after the reading of the first set of information is performed, reading, via a second process, the first portion and a second portion of the first set of information without a second read latch occurring during the read in the database, wherein the second portion comprises a second database initial value of a second database entry;

updating, via the second process, the first set of information to a second set of information in the database, wherein updating is based at least in part on the first database initial value of the first database entry and the second database initial value of the second database entry, wherein updating comprises updating the first database initial value of the first database entry to a first updated value and updating the second database initial value of the second database entry to a second updated value;

after the updating of the first set of information, reading, via the first process, the second updated value of the second database entry; and

after the reading of the second updated value of the second database entry, calculating, for the first process, a second set of information update using the first database initial value and the second updated value;

updating, via the first process, the second set of information in the database based at least in part on the second set of information update and based at least in part on one or more conditions, wherein the one or more conditions limit changes allowable to the first set of information from the database that occurred after receiving the first set of information from the database.