Database lock
A database lock coordinates concurrent access to data or database objects so incompatible operations do not proceed unchecked.
Coordinate concurrent access
A database lock governs which operations may access particular data or objects at the same time. Scope and compatibility depend on the lock type. In a fictional example, two transactions want to change the same order row; one may have to wait for the other.
A row lock does not automatically block every read query across the whole table. Long open transactions can, however, increase waiting. Mutual waiting can cause a deadlock that the system must handle. Check lock scope, duration and error handling. A database lock is not a user permission and does not replace the business decision about which change is allowed.
Sources
Related terms
- Optimistic lockingOptimistic locking detects on save whether a record has changed since the version that was read.
- Data validationData validation checks data against defined requirements such as format, required fields or permitted value ranges.
- Schema changeA schema change alters database structure, such as tables, columns, data types or constraints on permitted data.
- Legacy systemAn existing system still in use, with technical and business dependencies accumulated over time.
- Multi-tenancyMulti-tenancy supports separate customer or group scopes in one solution. A tenant is not automatically one person or one database.
- Browser cacheThe browser cache stores suitable HTTP responses for later use. Reuse and revalidation follow the applicable rules.
Articles on this topic
Software Development with ASES
Custom software, web and mobile apps