In addition to platform-specific command-line options, MySQL Workbench has the following command-line options:
On Microsoft Windows, the command-line options contain one
leading dash instead of two. For example, use
-log-level
for Microsoft Windows and
--log-level
for Linux and macOS.
-
--log-level
level
: Controls the verbosity level for logging output from Workbench.With increasingly levels of verbosity, the valid values for
level
are: error, warning, info, debug1, debug2, and debug3.The location of the generated log files, such as
wb.log
, are as follows:Table 2.1 Default location of generated MySQL Workbench log files
Platform Default location Linux ~/.mysql/workbench/log/
macOS ~/Library/Application Support/Workbench/log/
Microsoft Windows C:\Users\
user_name
\AppData\Roaming\MySQL\Workbench\log\
--admin
: Open an administration tab to the named MySQL instance.instance
--upgrade-mysql-dbs
: Open the Migration Wizard tab.--migration
: Open the Migration Wizard tab.--log-to-stderr
: Also log tostderr
.--version
: Show MySQL Workbench version number and exit.--verbose, -v
: Enable diagnostics output.-
--query
:[connection|connection_string]
Empty: Open a query tab and prompts for a connection.
Connection: Open a named connection.
Connection_string: Create a connection based on the entered connection string, which should be in the form
$USER@$HOST:$PORT
.
--model
: open the given EER model file.modelfile
--script
: Open the given SQL file in a connection, typically used with thescript
--query
parameter.--run
: Execute the given code using the default language for GRT shell.code
--run-python
: Execute the given code in Python.script
--run-script
: Execute Python code from a file.file
--open
: Open the given file at startup. Deprecated, so instead use specific types such asfile
--script
or--model
.--quit-when-done
: Quits MySQL Workbench after--script
or--run
finishes.