Bug #101239 | mysqlcheck lacks documentation on output format or return codes | ||
---|---|---|---|
Submitted: | 20 Oct 2020 10:28 | Modified: | 14 Dec 2020 17:28 |
Reporter: | Jaime Crespo (OCA) | Email Updates: | |
Status: | Won't fix | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | 8.0 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | check tables, documentation, mysqlcheck, Output, return |
[20 Oct 2020 10:28]
Jaime Crespo
[20 Oct 2020 10:59]
MySQL Verification Team
Hello Jaime, Thank you for the report! Thanks, Umesh
[14 Dec 2020 17:28]
Paul DuBois
Posted by developer: mysqlcheck has the usual command-line exit status of 0 = success, nonzero = failure. Nonzero can be the exit status for reasons unrelated to query execution (for example, a misspelled option), so it's not a great way to tell some check has failed; no check may have even been run. If you're interested in structured query output to parse, you're probably better off using mysql to execute a CHECK TABLE statement. It has output-format options to suit application requirements.