Conditional commit for data in a database

• US 8,321,391 B2
• Filed: 03/05/2009
• Issued: 11/27/2012
• 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): GIRMA, ANTENEH B
• Application Number:
  US12/380,981
• Publication Number:
  US 20100228705A1
• Time in Patent Office: 1,363 Days
• Field of Search: None
• US Class Current: 707/703
• 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 system for conditionally updating a database, comprising:

a processor configured to;

start a first transaction that operates on an existing first set of information from a database;

start a second transaction that operates on the existing first set of information from the database;

read, for the first transaction, the first set of information, A, from the database;

read, for the second transaction, the first set of information, A, from the database;

calculate, for the first transaction, a new value A1 based on A;

calculate, for the first transaction, a first set of boundary conditions for the validity of the new value A1;

in the event that a first newly read value for A satisfies the first set of boundary conditions, update for the first transaction A to A1;

in the event that the first newly read value for A does not satisfy the first set of boundary conditions, terminate the first transaction;

calculate, for the second transaction, a new value A2 based on A;

calculate, for the second transaction, a second set of boundary conditions for the validity of the new value A2;

in the event that a second newly read value for A satisfies the second set of boundary conditions, update for the second transaction A to A2;

in the event that the second newly read value for A does not satisfy the second set of boundary conditions, terminate the second transaction,

a database interface wherein the interface receives and sends information from a database to the processor, and wherein the database stores the first set information A.

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

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

4. The system 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. The system 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. The system 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. The system 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. The system 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. The system as in claim 1, wherein one of the second set of information is updated to a first absolute value.

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

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

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

13. The system as in claim 1, wherein the reading of the set of information from the database is read without a lock occurring during the read of the database, and wherein the calculating of the update is also done without a lock on the set of information.

14. The system 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. The system 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. The system 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. The system 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. The system 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. The system 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. The system 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. The system 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. The system 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. The system 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.

26. The system as in claim 1, wherein the committing of the update is done with a lock on the second set of information only on during the committing of the update but not during the rest of the transaction.

27. The system as in claim 1, wherein the first set of information and the second set of information are the same set of information.

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

starting a first transaction that operates on an existing first set of information, A, from a database without;

starting a second transaction that operates on the existing first set of information from the database;

reading, for the first transaction a first set of information from the database;

reading, for the second transaction, the first set of information, A, from the database;

calculating, for the first transaction, a new value A1 based on A;

calculating, for the first transaction, a first set of boundary conditions for the validity of the new value A1;

in the event that a first newly read value for A satisfies the first set of boundary conditions, updating for the first transaction A to A1 by storing A1 in a database;

in the event that the first newly read value for A does not satisfy the first set of boundary conditions, terminating the first transaction;

calculating, for the second transaction, a new value A2 based on A;

calculating, for the second transaction, a second set of boundary conditions for the validity of the new value A2;

in the event that a second newly read value for A satisfies the second set of boundary conditions, updating for the second transaction A to A2 by storing A2 in the database;

in the event that the second newly read value for A does not satisfy the second set of boundary conditions, terminating the second transaction.

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

starting a first transaction that operates on an existing first set of information, A, from a database without;

starting a second transaction that operates on the existing first set of information from the database;

reading, for the first transaction a first set of information from the database;

reading, for the second transaction, the first set of information, A, from the database;

calculating, for the first transaction, a new value A1 based on A;

calculating, for the first transaction, a first set of boundary conditions for the validity of the new value A1;

in the event that a first newly read value for A satisfies the first set of boundary conditions, updating for the first transaction A to A1 by storing A1 in a database;

in the event that the first newly read value for A does not satisfy the first set of boundary conditions, terminating the first transaction;

calculating, for the second transaction, a new value A2 based on A;

calculating, for the second transaction, a second set of boundary conditions for the validity of the new value A2;

in the event that a second newly read value for A satisfies the second set of boundary conditions, updating for the second transaction A to A2 by storing A2 in the database;

in the event that the second newly read value for A does not satisfy the second set of boundary conditions, terminating the second transaction.