Mysql and logging fix #476
Closed
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
rjbs
approved these changes
Apr 28, 2024
This makes our newer mysql/mariadb behave like the old pause mariadb, so unicode data can be inserted/retrieved from the users.fullname column without needing to make changes to our database schema.
Otherwise, for some reason, it doesn't pick up log entries.
rjbs
force-pushed
the
mysql-and-logging-fix
branch
from
7c4043e to
535ef69
Compare
|
Applied! |
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.
Configure mysqld so utf8 data in fullname column behaves like it used to.
Also in bootstrap restart journald one last time so we actually get logs