Description
The first Note in the No Locking subsection of Local Consistency is a bit confusing in that it suggests that under the hood MVCC hides this functionality from the end user, but continues by saying it requires "them" to coordinate concurrent changes. It is not clear to me who the end user is in this statement (i.e. is it an individual using an application which in turns uses a relational database?). And if it is truly an application end user (not an application developer), it is not clear to me how such an individual would coordinate concurrent changes.
The original text:
Note that modern relational databases avoid locks by implementing MVCC under the hood, but hide it from the end user, requiring them to coordinate concurrent changes of single rows or fields.