Dependent commit queue for a database

• US 9,305,035 B2
• Filed: 07/02/2013
• Issued: 04/05/2016
• 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): VU, BAI DUC
• Application Number:
  US13/933,443
• Publication Number:
  US 20140012807A1
• Time in Patent Office: 1,008 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 16/22 Indexing; Data structures therefor; Storage structures
• CPC Class Codes: G06F 16/2315 Optimistic concurrency control
• 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 receives a first set of information and a second set of information to be updated in the database. The database updater updates a second set of information in the database based at least in part on a condition that a first set of information in the database has been previously updated.

Claims

1. A database configured for conditional updating, comprising:

a database interface, wherein the database interface;

receives a first conditional update command from a first process, wherein the first conditional update command comprises an update to a first set of information in the database and a first condition, wherein the update to the first set of information comprises an update of at least one database entry to a second value, wherein the first process calculates the update to the first set of information based at least in part on a first value of the at least one database entry, wherein the first condition comprises a first set of boundary conditions for validity of the first value of the at least one database entry; and

receives a second conditional update command from a second process, wherein the second conditional update command comprises an update to a second set of information in the database and a second condition, wherein the update to the second set of information comprises an update of the at least one database entry to a third value, wherein the second process calculates the update to the second set of information based at least in part on the first value of the at least one database entry, wherein the second condition comprises a second set of boundary conditions for validity of the second value of the at least one database entry; and

a processor configured to;

conditionally update the first set of information according to the first conditional update command, wherein conditionally updating the first set of information comprises comparing the first value of the at least one database entry in the first set of information to the first set of boundary conditions, and in the event that the first condition is passed, submitting a first update to a commit queue;

conditionally update the second set of information according to the second conditional update command, wherein conditionally updating the second set of information comprises comparing the second value of the at least one database entry in the second set of information to the second set of boundary conditions, and in the event that the second condition is passed, submitting a second update to the commit queue, and;

in the event that the first update in the commit queue has been successfully committed, commit the second update in the commit queue.

2. The database as in claim 1, wherein the first set of information comprises two or more database entries to be updated in the database.

3. The database as in claim 1, wherein the second set of information comprises two or more database entries to be updated in the database.

4. The database as in claim 1, wherein a boundary condition of one of the first set of boundary conditions or the second set of boundary conditions comprises a condition that the first or the second value of the at least one database entry is less than an upper limit value.

5. The database as in claim 1, wherein a boundary condition of one of the first set of boundary conditions or the second set of boundary conditions comprises a condition that the first or the second value of the at least one database entry is less than or equal to an upper limit value.

6. The database as in claim 1, wherein a boundary condition of one of the first set of boundary conditions or the second set of boundary conditions comprises a condition that the first or the second value of the at least one database entry is more than a lower limit value.

7. The database as in claim 1, wherein a boundary condition of one of the first set of boundary conditions or the second set of boundary conditions comprises a condition that the first or the second value of the at least one database entry is more than or equal to a lower limit value.

8. The database as in claim 1, wherein a boundary condition of one of the first set of boundary conditions or the second set of boundary conditions comprises a condition that the first or the second value of the at least one database entry is equal to a predetermined value.

9. The database as in claim 1, wherein the first conditional update command comprises the at least one database entry of the first set of information to be updated to a first absolute value.

10. The database as in claim 1, wherein the first conditional update command comprises the at least one database entry of the first set of information to be updated to a value relative to a current value.

11. The database as in claim 10, wherein the value relative to the current value is a value less than the current value.

12. The database as in claim 10, wherein the value relative to the current value is a value greater than the current value.

13. The database as in claim 1, wherein the first conditional update command is evaluated with a latch on the first set of information.

14. The database as in claim 1, wherein the first condition further comprises a condition that a database value has been written since a specific prior read.

15. The database as in claim 1, wherein the first condition further comprises a condition that a database value has been written since a specific prior time.

16. The database as in claim 1, wherein the first condition further comprises a condition that a database value has not been written since a specific prior read.

17. The database as in claim 1, wherein the first condition further comprises a condition that a database value has not been written since a specific prior time.

18. The database as in claim 1, wherein the first condition further comprises a condition that a database value has been read since a specific prior read.

19. The database as in claim 1, wherein the first condition further comprises condition that a database value has been read since a specific prior time.

20. The database as in claim 1, wherein the first condition further comprises a condition that a database value has been not read since a specific prior read.

21. The database as in claim 1, wherein the first condition further comprises a condition that a database value has not been read since a specific prior time.

22. A method for conditionally updating a database, comprising:

receiving a first conditional update command from a first process, wherein the first conditional update command comprises an update to a first set of information in the database and a first condition, wherein the update to the first set of information comprises an update of at least one database entry to a second value, wherein the first process calculates the update to the first set of information based at least in part on a first value of the at least one database entry, wherein the first condition comprises a first set of boundary conditions for validity of the first value of the at least one database entry;

receiving a second conditional update command from a second process, wherein the second conditional update command comprises an update to a second set of information in the database and a second condition, wherein the update to the second set of information comprises an update of the at least one database entry to a third value, wherein the second process calculates the update to the second set of information based at least in part on the first value of the at least one database entry, wherein the second condition comprises a second set of boundary conditions for validity of the second value of the at least one database entry;

conditionally updating, using a processor, the first set of information according to the first conditional update command, wherein conditionally updating comprises comparing the first value of the at least one database entry in the first set of information to the first set of boundary conditions, and in the event that the first condition is passed, submitting a first update to a commit queue;

conditionally updating the second set of information according to the second conditional update command, wherein conditionally updating comprises comparing the second value of the at least one database entry in the second set of information to the second set of boundary conditions, and in the event that the second condition is passed, submitting a second update to the commit queue in the event that queue; and

in the event that the first update in the commit queue has been successfully committed, committing the second conditional update in the commit queue.

23. A computer program product for conditionally updating a database, the computer program product being embodied in a tangible non-transitory computer readable storage medium and comprising computer instructions or executable instructions when executed by a computer processor to perform a steps of:

receiving a first conditional update command from a first process, wherein the first conditional update command comprises an update to a first set of information in the database and a first condition, wherein the update to the first set of information comprises an update of at least one database entry to a second value, wherein the first process calculates the update to the first set of information based at least in part on a first value of the at least one database entry, wherein the first condition comprises a first set of boundary conditions for the validity of the first value of the at least one database entry;

receiving a second conditional update command from a second process, wherein the second conditional update command comprises an update to a second set of information in the database and a second condition, wherein the update to the second set of information comprises an update of the at least one database entry to a third value, wherein the second process calculates the update to the second set of information based at least in part on the first value of the at least one database entry, wherein the second condition comprises a second set of boundary conditions for validity of the second value of the at least one database entry;

conditionally updating, using a processor, the first set of information according to the first conditional update command, wherein conditionally updating comprises comparing the first value of the at least one database entry in the first set of information to the first set of boundary conditions, and in the event that the first condition is passed, submitting a first update to a commit queue;

conditionally updating the second of information according to the second conditional update command, wherein conditionally updating comprises comparing the second value of the at least one database entry in the second set of information to the second set of boundary conditions, and in the event that the second condition is passed, submitting the second conditional a second update to the commit queue; and

in the event that the first update in the commit queue has been successfully committed, committing the second update in the commit queue.