The procedure for launching MySQL Workbench depends on the platform. Generally, there are two ways to launch MySQL Workbench: either from the command line or from the graphical user interface of the host operating system. Using the command-line launching facility is useful when you want to customize some aspects of the way MySQL Workbench operates. The following sections describe how to launch MySQL Workbench for each of the supported platforms.
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 Mac OS X.
Controls the verbosity level for logging output from
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:
|Mac OS X|
Open an administration tab to the named MySQL instance.
--upgrade-mysql-dbs: Open the Migration
--migration: Open the Migration Wizard tab.
--log-to-stderr: Also log to
--version: Show MySQL Workbench version number
--verbose, -v: Enable diagnostics output.
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
pen the given EER model file.
Open the given SQL file in a connection, typically used with
Execute the given code using the default language for GRT
: Execute the given
code in Python.
Execute the given code in Lua.
--open : Open
the given file at startup. Deprecated, so instead use specific
types such as
--quit-when-done: Quits MySQL Workbench after
Copyright © 2006, 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices