Conditional commit for data in a database

• US 20100228705A1
• 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,321,391 B2
• Time in Patent Office: Days
• US Class Current: 707/700
• 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:

a database interface, wherein the database interface enables a reading of a first set of information from 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 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 the reading of 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 a condition that a database entry is less than an upper limit value.

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

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

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

8. A database as in claim 1, wherein one condition of the one or more conditions comprises 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 reading of the first set of information from the database is read without a lock occurring during the read in the database.

14. A database as in claim 1, wherein the reading of the first set of information from the database is read with a latch occurring during the read in the database.

15. A database as in claim 1, wherein the reading of the first set of information from the database is read without a latch occurring during the read in the database.

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

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

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

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

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

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

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

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

24. A method for a database, comprising:

enabling a reading of a first set of information from the database; and

updating a second set of information in the database 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 the reading of the first set of information from the database.

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

enabling a reading of a first set of information from the database; and

updating a second set of information in the database 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 the reading of the first set of information from the database.