Feature #1846
add option to de-normalize extent fields
Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
Start date:
Due date:
% Done:
100%
Estimated time:
32.00 h
billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:
History
#1 Updated by Eric Faulhaber over 13 years ago
Today, extent fields are automatically normalized into separate tables. For cases where a customer used "packed" extent fields in a way that perhaps would be better represented by separate fields, provide an option to split these out with custom hints. Note that this can only work if all references to extent fields in business logic use constant index references (so they can be calculated at conversion time).
#2 Updated by Greg Shah over 13 years ago
- Target version set to Code Improvements
#3 Updated by Eric Faulhaber over 10 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
#4 Updated by Greg Shah over 9 years ago
- Target version changed from Code Improvements to Converted Code Improvements - Deduplication