How is the principle of atomicity implemented in database management systems when performing operations?

The principle of atomicity in SQL databases means that an operation or transaction is completed entirely or not at all. This guarantees that data does not end up in an intermediate, inconsistent state.

Atomicity is achieved through the transaction mechanism. A transaction begins with the BEGIN command (or automatically), then operations are performed, and at the end, COMMIT is called to save the changes or ROLLBACK to cancel all changes if an error occurs.

Example in SQL:

BEGIN;
UPDATE accounts SET balance = balance - 100 WHERE id = 1;
UPDATE accounts SET balance = balance + 100 WHERE id = 2;
COMMIT;

If an error occurs during the execution of any operation, ROLLBACK; can be called, and the database will revert to its original state.

Thus, atomicity ensures data integrity by preventing partial execution of operations.