Skip to content
This repository has been archived by the owner on Nov 28, 2020. It is now read-only.

mysqldump needs extra setting to support newer nextcloud versions #5

Open
BoxedBrain opened this issue Nov 21, 2019 · 2 comments
Open
Assignees
Labels
enhancement New feature or request

Comments

@BoxedBrain
Copy link
Contributor

Problem:
As the newer versions of nextcloud need utf8mb4 support, the mysqldump should be run with --default-character-set=utf8mb4 to not break files/comments with emoji in it.
See also: https://docs.nextcloud.com/server/latest/admin_manual/configuration_database/mysql_4byte_support.html

Also make sure your backup strategy still work. If you use mysqldump make sure to add the --default-character-set=utf8mb4 option. Otherwise your backups are broken and restoring them will result in ? instead of the emojis, making files inaccessible.

Suggestion:
Maybe add to the sql.details file another row we could set needed parameters our self?

@BoxedBrain BoxedBrain changed the title mysqldump needs extra setting for default-character-set mysqldump needs extra setting to support newer nextcloud versions Nov 21, 2019
@asifbacchus
Copy link
Owner

I don't really use NextCloud much anymore so I appreciate you pointing stuff like this out! What would you prefer, a manual 'options' line in sql.details or should I just update the cmd in the script?

@asifbacchus asifbacchus self-assigned this Nov 21, 2019
@asifbacchus asifbacchus added the enhancement New feature or request label Nov 21, 2019
@BoxedBrain
Copy link
Contributor Author

Adding another line to the conf. file the user could add any mysqldump parameter would be more flexible I think.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants