keeping table export ordering indicated in "includeTables"#581
Merged
rmpestano merged 1 commit intodatabase-rider:masterfrom Mar 18, 2024
Merged
keeping table export ordering indicated in "includeTables"#581rmpestano merged 1 commit intodatabase-rider:masterfrom
rmpestano merged 1 commit intodatabase-rider:masterfrom
Conversation
Member
|
Hi @tomlux,
thanks for your contribution! |
Member
|
Seems it still has an ordering issue: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The tables exported with ExportDataSet have no ordining.
These bothe ExportDataSet instructions are generateing the same export files:
Changing the code from HashMap to LinkedHashMap is givin the developer the control of the table ordering.