Transaction as a change vector source
A database transaction is the main unit of work in the database system that makes the database consistent and independent of other transactions by securing a high level of parallelism. By getting any data failures or invalid operations, the transaction ensures that the changes covered by it can be removed, making the database consistent and valid again. The transaction is commonly formed of multiple data operations, which are, however, treated as atomic. Thus, all the changes are either accepted or the whole transaction is refused by rolling back the changes.
A database transaction is encapsulated by four rules – atomicity, consistency, isolation, and durability (ACID).
The atomicity of the transaction ensures that either the whole transaction is approved or it is refused completely. Consistency ensures that integrity constraints are successfully passed before transaction approval – for example, there is no character string...
