System with multiple conditional commit databases
AssigneeMatrixx Software, Inc.
InventorsDavid Labuda, Keith Brefczynski
Life of this patent
Estimating the term…
Abstract
A system for processing a transaction is disclosed. The system comprises a processor and a memory. The processor is configured to check a condition using data in a first database, wherein the data is associated with a transaction, wherein the data in the first database is latched before checking the condition and is unlatched after checking the condition. The processor is further configured to indicate to a second database to check the condition using data in the second database, wherein the data is associated with the transaction. The data in the second database is latched before checking the condition and is unlatched after checking the condition. The memory is coupled to the processor and configured to provide the processor with instructions.
Claims17
A system for processing a transaction, comprising:
- a processor configured to:
- check a condition using data in a first database as part of processing a first prepare, wherein the data is associated with a transaction, wherein the data in the first database is latched before checking the condition and is unlatched after checking the condition;
- indicate to a second database to check the same condition using data in the second database as part of a second prepare, wherein the data is associated with the transaction, wherein the data in the second database is latched before checking the condition and is unlatched after checking the condition;
- determine whether the condition check in the first database and the second database has passed;
- in the event both condition checks have passed, implement a commit state associated with the transaction in the first database, wherein the data in the first database is latched before implementing the commit state in the first database and is unlatched after the implementing of the commit state in the first database;
- indicate to the second database that the commit state is to be implemented in the second database, wherein the data in the second database is latched before implementing the commit state in the second database and is unlatched after the implementing of the commit state in the second database;
- and
- a memory coupled to the processor and configured to provide the processor with instructions.
A method for processing a transaction, comprising:
- checking a condition using data in a first database as part of processing a first prepare, wherein the data is associated with a transaction, wherein the data in the first database is latched before checking the condition and is unlatched after checking the condition;
- indicating to a second database to check the same condition using data in the second database as part of a second prepare, wherein the data is associated with the transaction, wherein the data in the second database is latched before checking the condition and is unlatched after checking the condition;
- determining whether the condition check in the first database and the second database has passed;
- in the event both condition checks have passed, implementing a commit state associated with the transaction in the first database, wherein the data in the first database is latched before implementing the commit state in the first database and is unlatched after the implementing of the commit state in the first database;
- and
- indicating to the second database that the commit state is to be implemented in the second database, wherein the data in the second database is latched before implementing the commit state in the second database and is unlatched after the implementing of the commit state in the second database.
A computer program product for processing a transaction, the computer program product comprising a non-transitory computer readable storage medium storing computer instructions for:
- checking a condition using data in a first database as part of processing a first prepare, wherein the data is associated with a transaction, wherein the data in the first database is latched before checking the condition and is unlatched after checking the condition;
- indicating to a second database to check the same condition using data in the second database as part of a second prepare, wherein the data is associated with the transaction, wherein the data in the second database is latched before checking the condition and is unlatched after checking the condition;
- determining whether the condition check in the first database and the second database has passed;
- in the event both condition checks have passed, implementing a commit state associated with the transaction in the first database, wherein the data in the first database is latched before implementing the commit state in the first database and is unlatched after the implementing of the commit state in the first database;
- and
- indicating to the second database that the commit state is to be implemented in the second database, wherein the data in the second database is latched before implementing the commit state in the second database and is unlatched after the implementing of the commit state in the second database.
Dependencies are inferred from the claim text.