The server or client was started with an option that does not accept an argument, yet an argument was supplied.
MySQL Error 70: EE_OPTION_WITHOUT_ARGUMENT appears when you give a value to a command-line or option-file flag that must stand alone, such as --no-data. Remove the “=value” or extra token and restart the command to resolve the issue.
%s: option '--%s' cannot take an argument. EE_OPTION_WITHOUT_ARGUMENT was added in 8.0.13.
Error 70 (EE_OPTION_WITHOUT_ARGUMENT) is thrown when any MySQL program sees an option that must not receive a value but is supplied with one. The message format is “%s: option '--%s' cannot take an argument.”
The condition was introduced in MySQL 8.0.13 to fail fast on invalid syntax.
It occurs in the server, client utilities, and plugins that parse my.cnf files or command-line arguments.
MySQL emits Error 70 if an option defined as “no_argument” in the source code is passed using either the = delimiter or a following token. Examples include --help, --skip-grant-tables, --no-data, and --verbose.
Configuration files trigger the same error when they contain a space or = after a no-argument flag.
The parser treats any following characters as an argument and raises the condition.
Verify the offending option in the error text, then remove its argument. Write the flag exactly as documented: a double dash followed immediately by the option name and nothing else.
After editing the command or configuration file, rerun the program.
The utility should now start without complaining about invalid arguments.
mysqldump --no-data=true db - Remove “=true” and use “--no-data” only.
mysqlpump --add-drop-table yes db - Delete “yes” or change to “--add-drop-table” alone.
Always consult --help output or the MySQL manual before adding new flags. Copy options exactly, avoiding extra spaces or = signs.
Version-control option files and review diffs in pull requests.
Static checks in CI can catch malformed flags before they reach production.
Error 71 EE_OPTION_REQUIRES_ARGUMENT arises when an option that needs a value is missing one; supply a proper argument to fix.
Error 1231 ER_WRONG_VALUE_FOR_VAR occurs when a system variable receives an unacceptable value; ensure the value fits the allowed set.
.
No. It is triggered before the server or client starts processing SQL, during option parsing.
Versions 8.0.13 and later include this error code. Earlier releases silently ignored the extra value.
No supported flag exists to bypass argument validation. Correct the option syntax instead.
Galaxy’s connection dialog validates flags and shows inline docs, preventing misconfigured no-argument options.
.avif)
.avif){kind=logo}
