Feature #4400
add /* UUID */ in where clause comment for every 4GL query so that SQL logging can easily be mapped back to the specific 4GL query being processed
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
version:
Related issues
History
#1 Updated by Greg Shah over 4 years ago
The idea:
- In early annotations, we calculate a UUID for every 4GL query and store it as an annotation.
- In conversion, we include this as a comment in the FQL. Presumably, this would be in the where clause. By placing it in a
/* UUID */comment, it will have no effect on the result. - This should not be stripped out when we generate SQL. That way any downstream logging will include the UUID.
- Since this will be easily visible in the Java code, we can map SQL back to specific queries.
- A report can be added to analytics to provide this mapping all the way back to the 4GL code.
- We will want to make the UUID calculation as stable as possible so that the values for a given 4GL query do not change much.
#2 Updated by Greg Shah over 2 years ago
- Related to Feature #5883: use UUIDs to associate locations in the converted source code with lock operations added
#3 Updated by Greg Shah 7 months ago
- Related to Feature #7943: improvements in lock management for diagnostics and release of orphaned locks added