Bug #97954 | Using Mysqldump 8 on 5.7 server prints invalid "NO_AUTO_CREATE_USER" | ||
---|---|---|---|
Submitted: | 10 Dec 2019 20:51 | Modified: | 20 Jul 2020 8:45 |
Reporter: | Carlos Tutte | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: mysqldump Command-line Client | Severity: | S3 (Non-critical) |
Version: | 8.0.17, 8.0.18 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | regression |
[10 Dec 2019 20:51]
Carlos Tutte
[11 Dec 2019 6:23]
MySQL Verification Team
Hello Carlos Tutte, Thank you for the report. regards, Umesh
[20 Jul 2020 8:45]
Erlend Dahl
Posted by developer Bharathy X Satish ===================================== Running 8.0 mysqldump against 5.7 server is not correct. 8.0 mysqldump can internally run queries which might not be correct on 5.7 server. Thus it is not a valid test scenario. ex: When i run 8.0.20 mysqldump against 5.7.30 i get this below error: mysqldump: Couldn't execute 'SELECT COLUMN_NAME, JSON_EXTRACT(HISTOGRAM, '$."number-of-buckets-specified"') FROM information_schema.COLUMN_STATISTICS WHERE SCHEMA_NAME = 'test' AND TABLE_NAME = 't';': Unknown table 'COLUMN_STATISTICS' in information_schema (1109) Also if 8.0 mysqldump when run against 5.7 server and if we strip the sql_mode from dump file, later if this dump file is run against 5.7 server then it is not correct as 5.7 server can recognise NO_AUTO_CREATE_USER sql_mode. Thus closing this bug as not a bug.
[16 Sep 2020 1:37]
Erick Franco
You can use mysqldump 8.0 on a 5.7 database by turning off column statistics, --column-statistics=0, but even then the problem persists.