Support #4693
check whether our index consolidation adversely affects flushing behavior
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
version:
History
#1 Updated by Eric Faulhaber almost 4 years ago
During schema conversion, we do some consolidation of the original 4GL indices to eliminate redundant indices. I am wondering whether this could have an impact on our logic regarding the timing of flushing records (and dirty database changes). The indices we eliminate are the less precise ones; we preserve the more precise ones. Could this be changing the timing with which we validate, flush inserts/updates, and share dirty updates?
We need to write test cases and investigate.