Bug #10822
Lock is not acquired if the update field value is the same as the current one
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:
Related issues
History
#1 Updated by Artur Școlnic 9 months ago
If a no-lock is set on a record it cannot be modified, 4GL does not allow any assignment and raises
** <filename> record has NO-LOCK status, update to field not allowed. (396)
In FWD the assigned value is checked, if it is the same as the current one, the lock is not acquired and the error is not raised.
- Testcase:
find first itemBuf no-lock. itemBuf.itemName = itemBuf.itemName + "". //FWD will not raise the error
- Possible resolution:
InBaseRecord.setDatum,lockForUpdateshould be executed regardless of the update value.
#2 Updated by Artur Școlnic 9 months ago
- Related to Support #10664: Develop a multi session test suite in harness added