Skip to content
Discussion options

You must be logged in to vote

Fixing the current rows with the SQL might work for now, but new backups will have the same problem, so yes — you'll need to upgrade to 4.22 to solve it for good.

Replies: 4 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by miloserdoff
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants
Converted from issue

This discussion was converted from issue #13231 on May 26, 2026 15:31.