|
|
|
FairCom DB introduces a new feature to prevent “dirty” record reads. Commit read locks enable an implicit, high performance, low-level record lock, ensuring consistent data record reads in high volume transaction environments. This new behavior is on by default. If a record update, under transaction control, is updated or deleted without an explicit lock held, error CMLK_ERR (768, commit lock error: make sure record update performed with lock) is now returned.
Please review the section "Commit Read Locks for Guaranteed Data Reads" for complete details.
