Order by primary key as second criterion #1954
Merged
Conversation
This file contains 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
|
Makes sense. Thumbs up from me. |
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.
If I enter post QSOs after SAT contacts sometimes there is a QSO with exactly the same time (with accuracy of a minute). The logbook shows contacts sorted by
COL_TIME_ON. But when this value is identical for more than one QSOs these QSOs get sorted byCOL_PRIMARY_KEYin ascending order it seems. I guess it would make more sense to have it in descending order so that if you log one QSO after another they get displayed in the same order as logged.Example: I logged M5JFS before DL2GRC but the logbook shows:
With this patch it would be sorted correctly: