Feature #2035
optimize conversion of CAN-FIND([FIRST|LAST] temp-table-record ... {SHARE-LOCK|EXCLUSIVE-LOCK})
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
4.00 h
billable:
No
vendor_id:
GCD
version:
History
#1 Updated by Eric Faulhaber about 11 years ago
- Target version changed from Code Improvements to 24
Currently, we convert this construct to use a WhereExpression, which does a client-side lock test for the found record. This is unnecessarily inefficient, since a temp-table record cannot be locked (it is private to a particular session).
So, the specification of a (non-NO-LOCK) lock option with a CAN-FIND on a temp-table is essentially meaningless, since the lock is a no-op.
Probably the simplest way to implement this optimization is to hide the lock option(s) and let the function convert naturally.
#2 Updated by Greg Shah over 7 years ago
- Target version deleted (
24)