Project

General

Profile

Bug #3040

CAN-FIND issues

Added by Greg Shah about 8 years ago. Updated about 8 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:

Related issues

Related to Database - Bug #3041: ambiguous field references are allowed in a CAN-FIND New
Related to Database - Bug #2034: correct conversion of CAN-FIND({FIRST|LAST} ... {SHARE-LOCK|EXCLUSIVE_LOCK} [NO-WAIT]) New

History

#1 Updated by Greg Shah about 8 years ago

The following are known and/or suspected issues:

1. CAN-FIND with share or exclusive lock in a WHERE clause cannot be done using a sub-select and it instead is a FindQuery whose result is substituted in. This is just a performance issue.

2. CAN-FIND nested more than 2 levels converts improperly.

3. Conversion of CAN-FIND in a client-side WHERE is mangled. See #2608.

4. Ambiguous field references in CAN-FIND are allowed (where they otherwise would not be allowed). See #3041.

Also available in: Atom PDF