Dependent commit queue for a database

• US 8,504,538 B2
• Filed: 03/05/2009
• Issued: 08/06/2013
• 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:
  US12/380,983
• Publication Number:
  US 20100228706A1
• Time in Patent Office: 1,615 Days
• Field of Search: None
• US Class Current: 707/703
• 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, comprising:

a database interface; and

a processor configured to;

determine a first update to a first set of information in the database, wherein the first update further comprises a first condition for submitting to a commit queue, wherein the first condition comprises limits to changes that can be made to the first set of information, wherein the first condition further comprises reading a first value of a first database entry in the database in order to be evaluated, wherein the first condition is dependent on the first value of the first database entry;

determine a second update to a second set of information in the database, wherein a first element of the first set of information comprises a second element of the second set of information, wherein the second update is dependent on the first update, wherein the second update further comprises a second condition for submitting to the commit queue, wherein the second condition comprises limits to changes that can be made to the second set of information, wherein the second condition comprises reading a second value of a second database entry in the database in order to be evaluated, wherein the second condition is dependent on the second value of the second database entry;

submit a first update request for the first update to the first set of information to the commit queue in the event that the first condition is passed;

submit a second update request for the second update to the second set of information to the commit queue in the event that the second condition is passed;

determine whether the first update has been committed;

in the event that the first update has been successfully committed, commit the second update to the second set of information;

in the event that the first update has not been successfully committed, remove dependent update requests from the commit queue, wherein the dependent update requests include the second update request, and indicate an error in updating.

2. The database as in claim 1, wherein the first condition is one of a plurality of conditions, and wherein the plurality of conditions include a condition that the database entry is less than an upper limit value.

3. The database as in claim 1, wherein the first condition is one of a plurality of conditions, and wherein the plurality of conditions include a condition that the database entry is less than or equal to an upper limit value.

4. The database as in claim 1, wherein the first condition is one of a plurality of conditions, and wherein the plurality of conditions include a condition that the database entry is more than a lower limit value.

5. The database as in claim 1, wherein the first condition is one of a plurality of conditions, and wherein the plurality of conditions include a condition that the database entry is more than or equal to a lower limit value.

6. The database as in claim 1, wherein the first condition is one of a plurality of conditions, and wherein the plurality of conditions include a condition that the database entry is equal to a predetermined value.

7. The database as in claim 1, wherein one of the first or second set of information is updated to a first absolute value.

8. The database as in claim 1, wherein one of the first or second set of information is updated to a value relative to a current value.

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

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

11. The database as in claim 1, wherein the committing of the first update or second update to the first set of information or the second set of information is done without a lock occurring while changes are made to the database.

12. The database as in claim 1, wherein the committing of the first update or second update to the first set of information or the second set of information is done with a latch on the value of the database entry in the database involved in evaluating the condition.

13. The database as in claim 1, wherein the first condition is one of a plurality of conditions, and wherein the plurality of conditions include a condition that a database value has been written since a specific prior read.

14. The database as in claim 1, wherein the first condition is one of a plurality of conditions, and wherein the plurality of conditions include a condition that a database value has been written since a specific prior time.

15. The database as in claim 1, wherein the first condition is one of a plurality of conditions, and wherein the plurality of conditions include a condition that a database value has not been written since a specific prior read.

16. The database as in claim 1, wherein the first condition is one of a plurality of conditions, and wherein the plurality of conditions include a condition that a database value has not been written since a specific prior time.

17. The database as in claim 1, wherein the first condition is one of a plurality of conditions, and wherein the plurality of conditions include a condition that a database value has been read since a specific prior read.

18. The database as in claim 1, wherein the first condition is one of a plurality of conditions, and wherein the plurality of conditions include a condition that a database value has been read since a specific prior time.

19. The database as in claim 1, wherein the first condition is one of a plurality of conditions, and wherein the plurality of conditions include a condition that a database value has been not read since a specific prior read.

20. The database as in claim 1, wherein the first condition is one of a plurality of conditions, and wherein the plurality of conditions include a condition that a database value has not been read since a specific prior time.

21. A method for a database, comprising:

determining a first update to a first set of information in the database, wherein the first update further comprises a first condition for submitting to a commit queue, wherein the first condition comprises limits to changes that can be made to the first set of information, wherein the first condition further comprises reading a first value of a first database entry in the database in order to be evaluated, wherein the first condition is dependent on the first value of the first database entry;

determining a second update to a second set of information in the database, wherein a first element of the first set of information comprises a second element of the second set of information, wherein the second update is dependent on the first update, wherein the second update further comprises a second condition for submitting to the commit queue, wherein the second condition comprises limits to changes that can be made to the second set of information, wherein the second condition comprises reading a second value of a second database entry in the database in order to be evaluated, wherein the second condition is dependent on the second value of the second database entry;

submitting a first update request for the first update to the first set of information to the commit queue in the event that the first condition is passed;

submitting a second update request for the second update to the second set of information to the commit queue in the event that the second condition is passed;

determining whether the first update has been committed;

in the event that the first update has been successfully committed, committing the second update to the second set of information;

in the event that the first update has not been successfully committed, removing dependent update requests from the commit queue, wherein the dependent update requests include the second update request, and indicating an error in updating.

23. The method as in claim 21, wherein the first condition is one of a plurality of conditions, and wherein the plurality of conditions include a condition that the database entry is less than an upper limit value.

24. The method as in claim 21, wherein the first condition is one of a plurality of conditions, and wherein the plurality of conditions include a condition that the database entry is less than or equal to an upper limit value.

25. The method as in claim 21, wherein the first condition is one of a plurality of conditions, and wherein the plurality of conditions include a condition that the database entry is more than a lower limit value.

26. The method as in claim 21, wherein the first condition is one of a plurality of conditions, and wherein the plurality of conditions include a condition that the database entry is more than or equal to a lower limit value.

27. The method as in claim 21, wherein the first condition is one of a plurality of conditions, and wherein the plurality of conditions include a condition that the database entry is equal to a predetermined value.

28. The method as in claim 21, wherein one of the first or second set of information is updated to a first absolute value.

29. The method as in claim 21, wherein one of the first or second set of information is updated to a value relative to a current value.

30. The method as in claim 29, wherein the value relative to the current value is a value less than the current value.

31. The method as in claim 29, wherein the value relative to the current value is a value greater than the current value.

32. The method as in claim 21, wherein the committing of the first update or second update to the first set of information or the second set of information is done without a lock occurring while changes are made to the database.

33. The method as in claim 21, wherein the committing of the first update or second update to the first set of information or the second set of information is done with a latch on the value of the database entry in the database involved in evaluating the condition.

34. The method as in claim 21, wherein the first condition is one of a plurality of conditions, and wherein the plurality of conditions include a condition that a database value has been written since a specific prior read.

35. The method as in claim 21, wherein the first condition is one of a plurality of conditions, and wherein the plurality of conditions include a condition that a database value has been written since a specific prior time.

36. The method as in claim 21, wherein the first condition is one of a plurality of conditions, and wherein the plurality of conditions include a condition that a database value has not been written since a specific prior read.

37. The method as in claim 21, wherein the first condition is one of a plurality of conditions, and wherein the plurality of conditions include a condition that a database value has not been written since a specific prior time.

38. The method as in claim 21, wherein the first condition is one of a plurality of conditions, and wherein the plurality of conditions include a condition that a database value has been read since a specific prior read.

39. The method as in claim 21, wherein the first condition is one of a plurality of conditions, and wherein the plurality of conditions include a condition that a database value has been read since a specific prior time.

40. The method as in claim 21, wherein the first condition is one of a plurality of conditions, and wherein the plurality of conditions include a condition that a database value has been not read since a specific prior read.

41. The method as in claim 21, wherein the first condition is one of a plurality of conditions, and wherein the plurality of conditions include a condition that a database value has not been read since a specific prior time.

22. A computer program product for committing a plurality of updates, the computer program product being embodied in a non-transitory computer readable storage medium and comprising executable computer instructions when executed by a computer processor to perform the steps of:

determining a first update to a first set of information in the database, wherein the first update further comprises a first condition for submitting to a commit queue, wherein the first condition comprises limits to changes that can be made to the first set of information, wherein the first condition further comprises reading a first value of a first database entry in the database in order to be evaluated, wherein the first condition is dependent on the first value of the first database entry;

determining a second update to a second set of information in the database, wherein a first element of the first set of information comprises a second element of the second set of information, wherein the second update is dependent on the first update, wherein the second update further comprises a second condition for submitting to the commit queue, wherein the second condition comprises limits to changes that can be made to the second set of information, wherein the second condition comprises reading a second value of a second database entry in the database in order to be evaluated, wherein the second condition is dependent on the second value of the second database entry;

submit a first update request for the first update to the first set of information to the commit queue in the event that the first condition is passed;

submit a second update request for second update to the second set of information to the commit queue in the event that the second condition is passed;

determine whether the first update has been committed;

in the event that the first update has been successfully committed, committing the second update to the second set of information;

in the event that the first update has not been successfully committed, removing dependent update requests from the commit queue, wherein the dependent update requests include the second update request, and indicating an error in updating.