Dependent commit queue for a database

• US 20100228706A1
• Filed: 03/05/2009
• Published: 09/09/2010
• Est. Priority Date: 03/05/2009
• Status: Active Grant

• Current Assignee: MATRIXX Software, Inc.
• Original Assignee: Buddha Software, Inc.
• Inventors: Labuda, David
• Granted Patent: US 8,504,538 B2
• Time in Patent Office: Days
• US Class Current: 707/700
• 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, wherein the database interface receives a first set of information and a second set of information to be updated in the database; and

a database updater, wherein 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.

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

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

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

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

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

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

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

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

10. A database as in claim 1, wherein one of the second set of information is updated to a value relative to a current value.

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

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

13. A database as in claim 1, wherein the updating of the second set of information from the database is updated without a lock occurring during the update of the database.

14. A database as in claim 1, wherein the updating of the second set of information from the database is updated with a latch occurring during the update of the database.

15. A database as in claim 1, wherein the 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.

16. A database as in claim 1, the 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.

17. A database as in claim 1, the 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.

18. A database as in claim 1, the 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.

19. A database as in claim 1, the 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.

20. A database as in claim 1, the 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.

21. A database as in claim 1, the 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.

22. A database as in claim 1, the 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.

23. A method for a database, comprising:

receiving a first set of information and a second set of information to be updated in the database; and

updating 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.

24. A computer program product for committing a plurality of rating events, the computer program product being embodied in a computer readable storage medium and comprising computer instructions for:

receiving a first set of information and a second set of information to be updated in the database; and

updating 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.