Back up database data #48
Labels
enhancement
New feature or request
good first issue
Good for newcomers
infrastructure
May need updates outside of application code
Milestone
Comments
lunakv
added
enhancement
|
Isn't it easy to regenerate from the source data? |
|
The parsed documents, yes, those are trivial to recreate. The diffs, however, contain a lot of manual tweaks that I really wouldn't want to spend the time on re-adjusting. And once we're storing those, we might as well store it all. Not to mention, the database also contains metadata such as set names, set codes, and update bulletin links, which don't appear in the raw files. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The backups currently only contain the source files. It would be good to have some database dumps included for parsed data as well, so it doesn't get lost in case the databse is corrupted or something.
The approach that comes to mind for this is one file per table with all the metadata columns, and then a directory with JSONs for each row with data columns.
The text was updated successfully, but these errors were encountered: