In the context of GRADE business modeling, a transaction describes a chain of activities, from the moment an external event arrives and initiates the transaction, until the end, when further events and activities are beyond our scope of interest For example, a transaction might be the processing of a customer query, from the moment the query arrives until the moment an answer is sent to the customer
An atomic operation; a message, data modification, or other procedure that is guaranteed to perform completely or not at all (e.g. a database transaction)
means the transmission of information between two parties to carry out financial or administrative activities related to health care It includes the following types of information transmissions
A mechanism to group a series of service invocations into a single operation Transactions are used to make sure that either the entire series of service invocations take effect, or that none of them do An LNS host application can explicitly manage transactions or it can let the NSS implicitly start and commit transactions as needed
A transaction is a unit of work that an Objectivity/DB application can apply to a database It contains one or more logically related operations that create, access, or modify persistent objects Every interaction with persistent objects must occur within a transaction
An atomic unit of work The work in a transaction must be completed as a whole; if any part of the transaction fails, the entire transaction fails
A record of each action that is taken on an order An order may have multiple transactions, e g , a Sale and a Credit
There are several types of transactions but the most common transaction is the process that takes place when a cardholder makes a purchase with a credit card
A group of statements whose changes can be made permanent or undone only as a unit A transaction ends with a COMMIT or ROLLBACK statement If it ends with a COMMIT statement, all the changes made to the database by the statements are made permanent If the transaction fails or ends with ROLLBACK, none of the statements takes effect
A transaction is initiated as soon as the first SQL statement is executed, provided that no other transaction is currently active A COMMIT or ROLLBACK statement is required to terminate a transaction A transaction exhibits the following properties (also called ACID properties): Atomicity: In a transaction involving two or more discrete pieces of information, either all of the pieces are committed or none are Consistency: A transaction either creates a new and valid state of data, or, if any failure occurs, returns all data to its state before the transaction was started Isolation: A transaction in process and not yet committed must remain isolated from any other transaction Durability: Committed data is saved by the system such that, even in the event of a failure and system restart, the data is available in its correct state
An agreement between a buyer and a seller to exchange an asset for payment Or in accounting, any event or condition recorded in the books of account
the act of transacting within or between groups (as carrying on commercial activities); "no transactions are possible without him"; "he has always been honest is his dealings with me"