{"id":946,"date":"2023-11-17T06:04:55","date_gmt":"2023-11-17T06:04:55","guid":{"rendered":"https:\/\/learnlearn.uk\/ibcs\/?page_id=946"},"modified":"2023-11-17T06:05:49","modified_gmt":"2023-11-17T06:05:49","slug":"database-transaction-terminology","status":"publish","type":"page","link":"https:\/\/learnlearn.uk\/ibcs\/database-transaction-terminology\/","title":{"rendered":"Database Transaction Terminology"},"content":{"rendered":"
\n

Transaction<\/h2>\n
\n\n

Transaction<\/h3>\n

\"\"<\/p>\n

A transaction is a sequence of one or more SQL statements that are executed as a single unit of work. A transaction can either be committed (applied to the database) or rolled back (undone), ensuring data consistency and integrity.<\/p>\n

 <\/p>\n\n<\/div>

Commit<\/h2>\n
\n\n

Commit<\/h3>\n

\"\"<\/p>\n

Committing a transaction means making its changes permanent in the database. After a successful commit, the changes are visible to other transactions.<\/p>\n

 <\/p>\n\n<\/div>

Rollback<\/h2>\n
\n\n

Rollback<\/h3>\n

\"\"<\/p>\n

Rolling back a transaction means undoing its changes, reverting the database to its state before the transaction started. It is typically used in case of errors or exceptions.<\/p>\n\n<\/div>

Savepoint<\/h2>\n
\n\n

Savepoint<\/h3>\n

\"\"<\/p>\n

A savepoint is a point within a transaction to which you can later roll back. It allows you to create intermediate points in a transaction and roll back to them without affecting the entire transaction.<\/p>\n

 <\/p>\n\n<\/div>

Concurrency<\/h2>\n
\n\n

Concurrency Control<\/h3>\n

Concurrency control mechanisms ensure that transactions execute in a way that preserves the consistency of the database.<\/p>\n

Two common concurrency control protocols are\u00a0Two-Phase Locking (2PL)<\/b>\u00a0and\u00a0Optimistic Concurrency Control (OCC)<\/b>.<\/p>\n