Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[8.x] Schema Dump: check error message with command option instead of table name #34233

Merged
merged 2 commits into from
Sep 9, 2020
Merged

Conversation

roberto-butti
Copy link
Contributor

Short version: fix typo in message error

Long version: if the first try in the command line is to use "--column-statistics=0" and you have an error because the option is not supported by your client (too old) you will have a message about the missing option (column-statistics)
Instead, if the first try is to not use "--column-statistics=0" option and you have an error because you have a new client and a old server (mysql5.7) you will have a message about the missing table ("column_statistics")
So with this implementation (where it is used with "--column-statistics=0") the error will be about "column-statistics"

Command option: column-statistics
Table name : column_statistics

Tested with mysqldump 5.7 , mysqldump 8, mysqld 5.7, mysqld8

Command option: column-statistics
Table name :  column_statistics
@roberto-butti roberto-butti changed the title Schema Dump: check error message with command option instead of table name [8.x] Schema Dump: check error message with command option instead of table name Sep 9, 2020
@taylorotwell taylorotwell merged commit 1e3a8b7 into laravel:8.x Sep 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants