Database transaction

From Simple English Wikipedia, the free encyclopedia

Depending on the model used, making changes to the data in a database can be complex. That means that several steps are needed to perform a change. In that context, all the steps are grouped. This group is called a transaction. Many databases give guarantees about the data, and they also do checks. When something goes wrong in one step, all the steps in the group, or transaction, are undone. This is called a rollback. When all the steps have been executed, and there was no error, this state can be persisted. People will talk about committing a transaction.

A database transaction is generally atomic. That means, it is either done completely, or it is not done. The state of it being done is not visible.

Most of the time, transactions are needed to guarantee the ACID principle of databases.[1]

References[change | change source]

  1. "What are the ACID properties? | Data Basecamp". 2022-07-02. Retrieved 2022-07-07.