Unsafe locks

Unsafe read or write locks should be avoided since they do not guarantee the integrity of the data at the time the operations on the database are performed (that is, read or write). Also referred to as "dirty reads" or "dirty writes," these actions should only be considered in rare cases when the Developer understands the trade off and performance implications using these locks.

See the following scenarios for examples on recommended locking best practices:

• Create a record
• Read a record
• Update a record