Bug #10739
Nested CAN-FIND issues in FWD
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 Ovidiu Maxiniuc 9 months ago
Because the complexity of the queries which use CAN-FIND 4GL function, we encountered multiple issues while processing it. Usually, the problems start with the conversion where FWD will try to create an optimal query based on the structure of the specific query so that a single SQL statement is enough. Sometimes some client-side (FWD) processing are required, and in some case, with deeply nested functions the execution might fail.
This task is a tracker for other tasks related to nested CAN-FIND issues.
#5 Updated by Ovidiu Maxiniuc 9 months ago
- Related to Bug #7113: Problem with nested CAN-FIND conversion added
#7 Updated by Ovidiu Maxiniuc 9 months ago
- Related to Bug #3647: incorrect hql and incorrect sql generated for nested CAN-FIND added
#9 Updated by Ovidiu Maxiniuc 9 months ago
- Related to Bug #2097: FOR EACH with multiple, nested CAN-FINDs converts badly added
#10 Updated by Ovidiu Maxiniuc 9 months ago
- Related to Bug #3040: CAN-FIND issues added
#13 Updated by Ovidiu Maxiniuc 9 months ago
- Related to Bug #3315: infinite loop in mark_client_branch during annotations because of nest CAN-FINDs with temp and perm tables added