Refactor oma-history database
#324
Open
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
eatradish
force-pushed
the
oma-history-refactor
branch
5 times, most recently
from
2d98a8b to
1c276bd
Compare
eatradish
force-pushed
the
oma-history-refactor
branch
from
1c276bd to
a672eab
Compare
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.
TODO
serde-jsondependencySummaryTypeResearch
The old
oma historyoutput had titles that didn't necessarily describe what they did, e.g. changes made viaoma tuiwere attributed to “Changes”, how should we redesign the titles in the menu? This will also affect how some fields are stored in the databaseThe new
oma historywill be more flexible and have more possible ways of querying the data the user wants, do we need to categorize some of the common queries into subcommands inoma history?How should I migrate from the old table to the new one?