Update for #264 [TPROC-H] MySQL create FKs after table load. #274
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates after tests for Issue #264 - creating foreign keys after table load did not prove effective, however investigation showed that existing indexes were not compatible with TPC-H specification and therefore build updated for compliance. Default storage engine changed to innodb as updated configuration performed better than previous default myisam. Updates for both MySQL and MariaDB.
Test scripts attached to Issue #264 - potential to revisit configuration and build if MySQL/MariaDB supports features such as parallel index builds and/or parallel query in the future.