fix: unknown variable column-statistics=0 with MariaDB 10 #256
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
alexislefebvre
force-pushed
the
fix-unknown-variable-column-statistics-0
branch
11 times, most recently
from
08f80ed to
876fc8c
Compare
alexislefebvre
force-pushed
the
fix-unknown-variable-column-statistics-0
branch
from
876fc8c to
02ec63a
Compare
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.
Fixes #251
I tried to run something like
@exec(mysqldump … --column-statistics=0)but it always shownunknown variable column-statistics=0in the output so I switched to checking the provider of themysqldumpcommand. It may be less reliable but it's the safest way for now.