Database · hard

41. Database Transactions & Locking

Ensuring data consistency.

DB::transaction(function () { ... }) wraps multiple queries so they all commit or roll back together, essential for operations like transferring balances between accounts. Pessimistic locking with ->lockForUpdate() or ->sharedLock() prevents race conditions when concurrent requests modify the same rows, such as decrementing an inventory count. Deadlocks can occur if lock ordering is inconsistent across transactions, so consistent access patterns matter.

Check your understanding

1. What does ->lockForUpdate() do in a query?
Caches the query resultAcquires a row-level lock to prevent concurrent modificationDeletes the row after readingSkips validation
2. What happens if an exception is thrown inside DB::transaction()?
Nothing, it's ignoredThe transaction is automatically rolled backThe app crashes without rollbackOnly the last query rolls back