generated from LizardByte/template-base
-
-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Labels
6+ monthsEstimated completion in 6+ monthsEstimated completion in 6+ monthsC++LizardByte/SunshineSQLeffort:LargeplannedThis work is plannedThis work is plannedpriority:Medium
Description
Is there an existing issue for this item?
- I have searched the existing issues
Repositories
LizardByte/Sunshine
Languages/Skills/Technologies
C++, SQL
Description
I believe it's a better practice to store data in a proper database instead of random json files.
Pros
- All data in one location
- Apps can have an actual ID (auto incrementing)
- No more boost json
- Can use db fixtures for unit testing different scenarios
- Can use proper migrations when the db structure changes, storing the db version in migration table... with up and down migrations. For down migrations Sunshine could download the downgrade SQL file from the git repo since it wouldn't be available in the previous versions of Sunshine.
Cons
- All data in one location
- SQL
Estimated Effort
effort:Large
Priority
priority:Medium
Target Milestone
6+ months
Dependencies
No response
Metadata
Metadata
Assignees
Labels
6+ monthsEstimated completion in 6+ monthsEstimated completion in 6+ monthsC++LizardByte/SunshineSQLeffort:LargeplannedThis work is plannedThis work is plannedpriority:Medium
Type
Projects
Status
Todo