chore(docs): Encode db dump in UTF-8 for windows #11787
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
github-actions
bot
added
the
documentation
mmomjian
approved these changes
Aug 14, 2024
mmomjian
approved these changes
Aug 14, 2024
jrasm91
approved these changes
Aug 14, 2024
Yuvi-raj-P
pushed a commit
to Yuvi-raj-P/immich
that referenced
this pull request
Aug 19, 2024
* Encode db dump in UTF-8 for windows * Update backup-and-restore.md
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.
Powershell does not use UTF-8 encoding by default, which makes database dumps incompatible between Windows and Linux. This PR makes Windows save the dump in UTF-8 format.
https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_character_encoding?view=powershell-7.4
Surprisingly, no changes were required to the command to restore the dump. Dumps encoded in UTF-8 using the updated command in this PR restores using the existing command provided in the docs on Windows and Linux.
I found out about this quirk when helping a user on discord migrate their instance from Windows to Linux here: https://discord.com/channels/979116623879368755/1268076684498960444