OpenEdge Data Management: DataServer for Microsoft SQL Server

Initial Programming Considerations
2–44
Executing the above code against the DataServer will have different results because the
DataServer does not retain any lock conditions beyond the scope of the transaction boundary.
The DataServer will release the EXCLUSIVE-LOCK on the record at the END statement of
Transaction 1. This leaves the record exposed to modification by another client during the PAUSE
statement. If another client modifies the state-name value to “Granite State” during the PAUSE,
Transaction 2 will read the updated value during the FIND statement. However, because of
OpenEdge buffering rules and record scoping, neither buffer is refreshed with the updated value
and the DISPLAY statement displays “New Hampshire New Hampshire.”
To avoid this type of problem, the following workarounds are available:
• Change the lock status in Transaction 1 to NO-LOCK if an EXCLUSIVE-LOCK is not required.
The lock upgrade in Transaction 2 will force the buffer to be updated in this transaction.
• If the lock can not be changed in Transaction 1, release the first buffer before the start of
Transaction 2 with the statement “RELEASE st_buf1.” The RELEASE statement will force a
refresh of the data when the FIND in Transaction 2 executes.