Feature #6721
calculate field lists at conversion time where possible
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 1 year ago
There are use cases of buffers in which it is not possible to statically calculate the exact fields used at runtime (even using call graph). Examples:
- buffers passed as a handle
- buffers passed as a parameter (table, table-handle, buffer) to code implemented with super-procedures
- dynamic database usage of a static buffer
- dynamic temp-tables
Even the cases that can be statically calculated, might require a call graph to fully calculate them if there is parameter usage.
OK, so this is hard. So what? Lots of things we do are hard. We should measure:
- the benefit of field lists (simulate cases where we use them and don't use them and compare)
- what percentage of cases can be calculated using static techniques
- without call graph
- with call graph
Given this, we can make some kind of estimate of the impact.
#2 Updated by Greg Shah over 1 year ago
- Related to Feature #2137: runtime support for FIELDS/EXCEPT record phrase options added
#3 Updated by Alexandru Lungu about 1 year ago
- Related to Bug #7185: H2 in-memory lazy hydration added
#4 Updated by Greg Shah 6 months ago
- Related to Feature #8067: investigate adding automatically adding a FIELDS clause for simple record blocks added