# web_object

path: /wb-html-guitools/wb-data-modeling-create-model-from-sql-script.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.4. Create EER Model from SQL Script</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-data-modeling.html" title="Chapter 7. Data Modeling"><link rel="prev" href="wb-data-modeling-create-model-from-existing-database.html" title="7.3. Create EER Model from Existing Database"><link rel="next" href="wb-model-editor.html" title="7.5. Model Editor"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="wb-data-modeling-create-model-from-sql-script"></a>7.4. Create EER Model from SQL Script</h2></div></div></div><p>
      This action item enables you to create a model from an SQL Create
      script. Such a script may have been created by hand or as a result
      of reverse engineering an existing database. The script may then
      be modified according to requirements. Clicking this action item
      launches the Reverse Engineer SQL Script wizard. This is a
      multi-stage wizard that enables you to select the script you want
      to create your model from.
    </p><p>
      For further information, see
      <a href="wb-reverse-engineer-create-script.html" title="7.7.9.1. Reverse Engineering Using a Create Script">Section 7.7.9.1, “Reverse Engineering Using a Create Script”</a>.
    </p></div></body></html>


path: /wb-html-guitools/wb-manage-server-logs-tab.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>8.7.7. The Logs Tab</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-server-administration-configuration.html" title="8.7. Server Administration and Configuration"><link rel="prev" href="wb-manage-server-advanced-options.html" title="8.7.6.3. Advanced Export Options"><link rel="next" href="wb-extending.html" title="Chapter 9. Extending Workbench"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-manage-server-logs-tab"></a>8.7.7. The Logs Tab</h3></div></div></div><p>
        The Logs tab features two subtabs:
      </p><div class="itemizedlist"><ul type="disc"><li><p>
            General
          </p></li><li><p>
            Slow Query Log
          </p></li></ul></div><p>
        The <span class="guilabel">General</span> tab shows entries from the
        server's general log file.
      </p><p>
        The <span class="guilabel">Slow Query Log</span> tab displays entries
        from the server's slow query log file.
      </p><div class="figure"><a name="wb-manage-server-logs-tab-screenshot"></a><p class="title"><b>Figure 8.12. Administrator - Logs Tab</b></p><div class="mediaobject"><img src="images/wb-manage-server-logs-tab.png" width="1024" height="707" alt="Administrator - Logs Tab"></div></div></div></body></html>


path: /wb-html-guitools/wb-sql-editor-sidebar.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>6.7.5. Sidebar</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-sql-editor.html" title="6.7. SQL Editor"><link rel="prev" href="wb-sql-editor-live-editing-tabsheets.html" title="6.7.4.6. Live Editing Tabsheets"><link rel="next" href="wb-sql-editor-connection-information-panel.html" title="6.7.5.1. Connection Information Panel"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-sql-editor-sidebar"></a>6.7.5. Sidebar</h3></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-sql-editor-connection-information-panel.html">6.7.5.1. Connection Information Panel</a></span></dt><dt><span class="section"><a href="wb-sql-editor-object-browser.html">6.7.5.2. Object Browser</a></span></dt></dl></div><p>
        The Sidebar contains these panels:
      </p><div class="itemizedlist"><ul type="disc"><li><p>
            Connection Information Panel
          </p></li><li><p>
            Object Browser
          </p></li></ul></div><p>
        The following sections describe each panel in more detail.
      </p></div></body></html>


path: /wb-html-guitools/wb-mforms.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>9.4. Adding a GUI to a Plugin Using MForms</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-extending.html" title="Chapter 9. Extending Workbench"><link rel="prev" href="wb-plugins.html" title="9.3. Plugins"><link rel="next" href="wb-scripting-shell.html" title="9.5. The Workbench Scripting Shell"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="wb-mforms"></a>9.4. Adding a GUI to a Plugin Using MForms</h2></div></div></div><p>
      MySQL Workbench is implemented with a C++ core back-end, and a native
      front-end for each supported platform. Currently the front-end is
      implemented with Windows Forms on Microsoft Windows, GTK+ on
      Linux, and Cocoa on Mac OS X. This approach permits the
      application to have a native look and feel, while reducing the
      amount of work required to maintain the project. However, the GUI
      functionality required by MySQL Workbench can be met by a subset of
      graphical operations. These are implemented in a cross-platform
      GUI library, MForms. This further reduces the development effort
      because plugin developers can use MForms rather than writing
      front-end specific code for each supported platform. This also
      helps consistency of operation across all platforms. MForms is
      coded in C++, but provides a Python interface. To use it, the
      Python code must import the <code class="literal">mforms</code> module.
    </p><p>
      <span class="bold"><strong>MForms Containers</strong></span>
    </p><p>
      Given the problems of using an absolute coordinate system across
      different platforms, MForms employs containers that perform
      automatic layout. The basic containers that MForms provides
      include:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <span class="bold"><strong>Form</strong></span>: A top-level window
          which can contain a single control, usually another container.
          The window will be sized automatically to fit its contents,
          but can also be sized statically.
        </p></li><li><p>
          <span class="bold"><strong>Box</strong></span>: This is a container that
          can be filled with one or more controls in a vertical or
          horizontal layout. Each child control can be set to use either
          the minimum of required space, or fill the box in the
          direction of the layout. In the direction perpendicular to the
          layout, for example vertical in a horizontal layout, the
          smallest possible size that can accommodate all child controls
          will be employed. So, in this example, the smallest height
          possible to accommodate the controls would be used.
        </p></li><li><p>
          <span class="bold"><strong>Table</strong></span>: This is a container
          that can organize one or more controls in a grid. The number
          of rows and columns in the table, and the location of controls
          within the grid, can be set by the developer.
        </p></li><li><p>
          <span class="bold"><strong>ScrollView</strong></span>: This is a
          container that can contain a single child control, and will
          add scrollbars if the contents do not fit the available space.
        </p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-news-5-2-13.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.27. Changes in MySQL Workbench 5.2.13 (Not released)</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="changes-5.2.x.html" title="A.1. Changes in Release 5.2"><link rel="prev" href="wb-news-5-2-14.html" title="A.1.26. Changes in MySQL Workbench 5.2.14 (21 January 2010)"><link rel="next" href="wb-news-5-2-12.html" title="A.1.28. Changes in MySQL Workbench 5.2.12 (Not released)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-news-5-2-13"></a>A.1.27. Changes in MySQL Workbench 5.2.13 (Not released)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.2.12.
      </p><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        Selecting the <span class="guimenu">Help</span>, <span class="guimenu">Check for
        Updates</span> menu item opened the web browser and displayed
        an error:
      </p><pre class="programlisting">Not Found

The requested URL /version-check.php was not found on this server.
Apache Server at wb.mysql.com Port 80</pre><p>(Bug #50415)</p></li><li><p>
        When building MySQL Workbench 5.2.11 from source on CentOS 5.4, this
        error occurred:
      </p><pre class="programlisting">python_context.cpp:388: error: invalid conversion from 'const char*' to 'char*'
python_context.cpp:388: error:   initializing argument 1 of 'PyObject*
PyImport_ImportModule(char*)'
make[4]: *** [python_context.lo] Error 1
make[4]: Leaving directory `/home/install/mysql-workbench-oss-5.2.11/library/grt/src'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home/install/mysql-workbench-oss-5.2.11/library/grt'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/install/mysql-workbench-oss-5.2.11/library'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/install/mysql-workbench-oss-5.2.11'
make: *** [all] Error 2</pre><p>
        Note, from MySQL Workbench 5.2.13, binary and source packages for
        CentOS 5.4 will be available. Due to the dependence of
        MySQL Workbench on certain packages that are older in CentOS 5.4
        than in other operating systems, MySQL Workbench has some minor
        features, such as tooltips, disabled.
       (Bug #50360)</p></li><li><p>
        In the SQL Editor, if a routine was edited, and the changes
        applied, the changes were automatically reverted if the apply
        failed. This meant that any changes the user had made had to be
        entered again.
       (Bug #49790)</p></li><li><p>
        In the SQL Editor, if an object was created or renamed, that
        change was not reflected in the user interface. This change
        fixes the problem for Linux and Mac OS X.
       (Bug #49454)</p><p>See also Bug #50424.</p></li><li><p>
        Invalid values were written to the MySQL server configuration
        file by the configuration editor. MySQL Workbench also added new
        entries to the configuration file, rather than update the
        existing entries. As a result of the this the server failed to
        start.
       (Bug #49420)</p></li><li><p>
        If the server configuration file contained more than one entry
        for <code class="literal">replicate-do-db</code>, the configuration editor
        on the <span class="guilabel">Admin</span> tab displayed only the second
        entry, rather than both.
       (Bug #49299)</p></li><li><p>
        In the configuration editor in the Admin tab, the lists for
        displaying units, such as for the <span class="guilabel">Sort buffer
        size</span> option, did not show 'G', which represents
        Gigabytes. This bug was fixed in 5.2.10.
      </p><p>
        It was subsequently decided to standardize all units around
        uppercase characters. In particular the 'k' was changed to 'K'.
        This change was made in version 5.2.13.
       (Bug #49013)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-create-new-table.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.8.2.1. Creating a New Table</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-default-schema.html" title="7.8.2. Using the Default Schema"><link rel="prev" href="wb-default-schema.html" title="7.8.2. Using the Default Schema"><link rel="next" href="wb-create-schema-objects.html" title="7.8.2.2. Creating Other Schema Objects"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-create-new-table"></a>7.8.2.1. Creating a New Table</h4></div></div></div><p>
        Create a new table by double-clicking the <span class="guilabel">Add
        Table</span> icon in the <code class="literal">Physical
        Schemata</code> panel. This opens the table editor docked at
        the bottom of the application. If you wish, you can undock or
        dock this editor in exactly the same way as the schema editor
        window.
      </p><p>
        Use the first tab of the table editor to change the name,
        collation, and engine. You may also add a comment.
      </p><p>
        Add columns to the new table by selecting the
        <span class="guilabel">Columns</span> tab. Use the default column name or
        enter a new name of your choosing. Use the <span><strong class="keycap">Tab</strong></span>
        key to move to the next column and set the column's data type.
      </p><p>
        Altering the table by adding indexes or other features is also
        easily done using the table editor.
      </p></div></body></html>


path: /wb-html-guitools/wb-layers-palette.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.5.11. The Layers Palette</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-model-editor.html" title="7.5. Model Editor"><link rel="prev" href="wb-catalog-palette.html" title="7.5.10. The Catalog Tree Palette"><link rel="next" href="wb-invisible-objects-layers.html" title="7.5.11.1. Finding Invisible Objects Using the Layers Palette"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-layers-palette"></a>7.5.11. The Layers Palette</h3></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-invisible-objects-layers.html">7.5.11.1. Finding Invisible Objects Using the Layers Palette</a></span></dt></dl></div><p>
      This palette shows all the layers and figures that have been
      placed on an EER diagram. If a layer or figure is currently
      selected, an <code class="literal">X</code> appears beside the name of the
      object and its properties are displayed in the
      <code class="literal">Properties</code> palette. This can be especially
      useful in determining which objects are selected when you have
      selected multiple objects using the various options under the
      <span class="guimenuitem">Select</span> menu item. For more information
      on this topic, see <a href="wb-edit-menu.html" title="7.5.1.2. The Edit Menu">Section 7.5.1.2, “The Edit Menu”</a>.
    </p><p>
      Selecting an object in the <code class="literal">Layers</code> palette also
      adjusts the view port to the area of the canvas where the object
      is located.
    </p></div></body></html>


path: /wb-html-guitools/wb-news-5-0-15.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.3.16. Changes in MySQL Workbench 5.0.15rc (17 March 2008)</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="changes-5.0.x.html" title="A.3. Changes in Release 5.0"><link rel="prev" href="wb-news-5-0-16.html" title="A.3.15. Changes in MySQL Workbench 5.0.16rc (26 March 2008)"><link rel="next" href="wb-news-5-0-14a.html" title="A.3.17. Changes in MySQL Workbench 5.0.14abeta (28 February 2008)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-news-5-0-15"></a>A.3.16. Changes in MySQL Workbench 5.0.15rc (17 March 2008)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.0.14abeta.
      </p><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        Using <span class="guilabel">Undo</span> on a relationship within a model
        would cause an exception.
       (Bug #35243)</p></li><li><p>
        A foreign key relationship to the source table (a reflexive
        relationship) gives a bad representation in the entity model
        diagram.
       (Bug #35237, Bug #34810)</p></li><li><p>
        Generating an <code class="literal">ALTER SCRIPT</code> or using the
        synchronize functionality on a model with entity relationships,
        the relationship lines within the diagram would be generated
        twice.
       (Bug #35213)</p></li><li><p>
        Boolean values were unsupported when trying to insert values
        into a table, the <code class="literal">TRUE</code> would instead be
        replaced by a textual, quoted version <code class="literal">'TRUE'</code>.
       (Bug #35205)</p></li><li><p>
        Printing a model diagram to PDF or Postscript, results in a
        corrupt file PDF or Postscript file that does not match the
        model.
       (Bug #35197)</p></li><li><p>
        Deleting objects within the overview pane when the corresponding
        editor pane for those objects is open would cause a crash.
       (Bug #35186)</p></li><li><p>
        When entering data into the <span class="guilabel">Default</span> column
        of the table editor, the use of the <span><strong class="keycap">Return</strong></span> key
        for saving the information about the default value was not
        supported.
       (Bug #35127)</p></li><li><p>
        There was a typographical error in the help message for the GRT
        command <code class="literal">cd</code>. The word
        <code class="literal">Absolute</code> was missing the final
        <code class="literal">e</code>. This has been corrected.
       (Bug #35119)</p></li><li><p>
        When changing the name within a foreign key relationship, the
        modified name is not reflected in the tables to which the
        foreign key is related.
       (Bug #35093)</p></li><li><p>
        Scrollbar navigation did not work after importing a DB Designer
        schema with a large canvas size. However, you could still
        navigate using the <code class="literal">Model Navigator</code> palette.
       (Bug #34988)</p></li><li><p>
        After importing a DB Designer schema, the following error
        occurred: "Cairo error: input string not valid UTF-8."
       (Bug #34987)</p></li><li><p>
        Creating a new file after changing an existing file with
        modifications could lead to the original being deleted without
        prompting to save the changes.
       (Bug #34976)</p></li><li><p>
        When saving an existing model, the <span class="guilabel">MySQL
        Model</span> overview panel would scroll to the top of the
        model definition.
       (Bug #34975)</p></li><li><p>
        Changing the <code class="literal">drawSplit</code> property of a
        connection from the <code class="literal">Properties</code> palette did
        not updated the <code class="literal">Visibility</code> section of the
        connection editor.
       (Bug #34934)</p></li><li><p>
        Editing a primary key column within a model on Microsoft Vista
        could cause a crash.
       (Bug #34922)</p></li><li><p>
        On the <code class="literal">MySQL Model</code> page, when the large icons
        view was selected, the <code class="literal">Add Table</code> icon
        disappeared.
       (Bug #34904)</p></li><li><p>
        Incorrect <code class="literal">ALTER</code> statements are created during
        the synchronization process if you add foreign keys to an
        existing or imported model.
       (Bug #34897)</p></li><li><p>
        A new <span class="guilabel">GRT Inspector</span> tab would be created
        every time the <span class="guilabel">GRT Shell</span> was opened. In
        addition, manually closing the <span class="guilabel">GRT
        Inspector</span> and <span class="guilabel">GRT Shell</span>
        components would cause an exception.
       (Bug #34857)</p></li><li><p>
        Opening an existing MySQL Workbench file after associating the
        <code class="filename">.mwb</code> extension with the application leads
        to a crash when you open a MySQL Workbench file.
       (Bug #34849)</p></li><li><p>
        When editing a model, the windows and toolbars would realign
        themselves during selection. This was related to the configured
        font sizer the DPI setting of the monitor, causing the
        application to redraw the windows to account for the
        configuration combination.
       (Bug #34822)</p></li><li><p>
        Attempting to move a table on an EER diagram after deleting a
        relationship, caused the application to crash.
       (Bug #34816)</p></li><li><p>
        The <span class="guilabel">New File</span> dialog is nonmodal, and could
        be hidden by other windows. The dialog is now always drawn on
        top of other windows.
       (Bug #34784)</p></li><li><p>
        Changing the column name of a table when you have pending
        inserts to the table did not change the column name in the
        corresponding <code class="literal">INSERT</code> statements.
       (Bug #34500)</p></li><li><p>
        The <code class="literal">Properties</code> palette was not cleared when a
        new project was started. It retained the properties of the last
        selected object.
       (Bug #34433)</p></li><li><p>
        Deleting an existing schema with an open table editor would not
        close the table editor window. The window is now closed when the
        schema is deleted.
       (Bug #34345)</p></li><li><p>
        Searching a project specifying <code class="literal">Entire Model</code>
        in the <code class="literal">In Location:</code> list did not return any
        results. This applied to the Standard Edition only.
       (Bug #34170)</p></li><li><p>
        When the page size was changed from A4 to B4 it was not possible
        to move objects on an EER diagram beyond the old page
        boundaries.
       (Bug #34148)</p></li><li><p>
        When editing comments, the <span><strong class="keycap">Return</strong></span> key would
        move to the next column, which prevented the use of newlines
        within the comment information. Workbench now permits use of the
        <span><strong class="keycap">Return</strong></span> key within the comment field.
       (Bug #33980)</p></li><li><p>
        Where relationship lines crossed, and one of the connectors was
        changed to <code class="literal">Hidden</code> or <code class="literal">Draw
        Split</code>, the semi circle that indicated the previous
        intersection was still shown on the remaining connector.
       (Bug #33818)</p></li><li><p>
        Editing an existing diagram could cause an unhandled exception
        on Windows Vista.
       (Bug #33477)</p></li><li><p>
        Identifiers (tables, column, index, triggers and other data
        types) could be created with names longer than the maximum
        support by MySQL Server.
       (Bug #33265)</p></li><li><p>
        The application crashed when attempting to export an SQL CREATE
        script.
       (Bug #33263)</p></li><li><p>
        Placing an object on the canvas of an EER diagram where you have
        reverse engineered an existing database, would lead to multiple
        copies of the object appearing on the diagram.
       (Bug #32891)</p></li><li><p>
        When scrolling through a schema, the tables in the schema were
        not redrawn correctly.
       (Bug #32835)</p></li><li><p>
        On an EER digram you could not select a relationship if the
        connection line wasn't stepped. You can now select a connector
        even if it is not stepped.
       (Bug #32734)</p></li><li><p>
        Printing a model when there is no printer connected could result
        in an application exception.
       (Bug #32320)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-note-tool.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.6.1.5. The Text Tool</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-vertical-toolbar.html" title="7.6.1. The Vertical Toolbar"><link rel="prev" href="wb-layer-tool.html" title="7.6.1.4. The Layer Tool"><link rel="next" href="wb-image-tool.html" title="7.6.1.6. The Image Tool"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-note-tool"></a>7.6.1.5. The Text Tool</h4></div></div></div><p>
        The text tool is the square icon with a capital
        <code class="literal">N</code> in the top left corner. Use this tool to
        place text objects on the EER diagram canvas. Click the tool,
        then click the desired location on the canvas. After a text
        object has been dropped on the canvas, the mouse pointer reverts
        to its default.
      </p><p>
        To add text to a text object, right-click the text object and
        choose <span class="guimenuitem">Edit Note...</span> or
        <span class="guimenuitem">Edit in New Window...</span> from the pop-up
        menu.
      </p><p>
        You can manipulate the properties of a text object by selecting
        it and then changing its properties in the
        <code class="literal">Properties</code> panel.
      </p><p>
        To activate the text tool from the keyboard, use the
        <span><strong class="keycap">N</strong></span> key. For more information about text objects,
        see <a href="wb-text-objects.html" title="7.7.7. Creating Text Objects">Section 7.7.7, “Creating Text Objects”</a>.
      </p></div></body></html>


path: /wb-html-guitools/wb-news-5-2-17.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.23. Changes in MySQL Workbench 5.2.17 (02 April 2010)</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="changes-5.2.x.html" title="A.1. Changes in Release 5.2"><link rel="prev" href="wb-news-5-2-18.html" title="A.1.22. Changes in MySQL Workbench 5.2.18 (13 April 2010)"><link rel="next" href="wb-news-5-2-16.html" title="A.1.24. Changes in MySQL Workbench 5.2.16 (17 February 2010)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-news-5-2-17"></a>A.1.23. Changes in MySQL Workbench 5.2.17 (02 April 2010)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.2.16.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        The Execute Current Statement command in the SQL Editor has been
        improved. The statement that contains the cursor will be
        executed. Further, if the cursor is outside of a statement, the
        last statement before the cursor is executed.
       (Bug #52302)</p></li><li><p>
        If MySQL Workbench attempts to connect to MySQL Server version 4.x,
        an error message is generated to indicate this version is not
        supported.
       (Bug #51455, Bug #51844)</p></li><li><p>
        MySQL Workbench has been changed so that it is possible to run the
        start, stop, and check status scripts executed from the
        Administrator, with administrator privileges. A check box has
        been provided to enable you the option of acquiring the
        administrator rights to execute the commands. This option is
        switched off by default for the check status command.
       (Bug #51276)</p></li><li><p>
        A description column has been added to the snippets table.
       (Bug #51010)</p></li><li><p>
        The WeifenLuo library was removed. This was the cause of
        difficult to trace application crashes.
       (Bug #50706)</p></li><li><p>
        Various improvements to the SQL Editor user interface, including
        additional context-sensitive menu items in the Object Explorer,
        additional buttons in the <span class="guilabel">Create Table</span> and
        <span class="guilabel">Alter Table</span> dialogs, and more clearly
        displayed error messages.
       (Bug #50637, Bug #49918)</p></li><li><p>
        The MySQL Workbench installer now includes a <span class="guilabel">Launch
        Now</span> check box. By default, this is selected, so
        MySQL Workbench will be launched when the installer exits.
       (Bug #50387)</p></li><li><p>
        In the SQL Editor, the <span class="guilabel">Comments</span> tab in the
        <span class="guilabel">Create View</span> dialog has been removed.
       (Bug #49270)</p></li><li><p>
        The Output window only appeared in the Model context.
        MySQL Workbench has been changed so that the Output window now has
        its own tab on the main screen.
       (Bug #48988)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        In the SQL Editor, the wrong table was displayed when using
        <code class="literal">EDIT</code>. This happened if two schemata contained
        tables with the same name. For example, if two schemata,
        <code class="literal">schema1</code> and <code class="literal">schema2</code> both
        contained a table <code class="literal">t1</code>, then if the following
        SQL was entered and executed, <code class="literal">schema2.t1</code>
        would be displayed instead of <code class="literal">schema1.t1</code>:
      </p><pre class="programlisting">use schema1;
edit t1;</pre><p>(Bug #52401, Bug #52692)</p></li><li><p>
        If, in the EER Diagram view, an attempt was made to edit two
        tables, MySQL Workbench crashed.
       (Bug #52158)</p></li><li><p>
        In the EER Diagram view, when the menu item
        <span class="guimenu">Model</span>, <span class="guimenu">Diagram Properties and
        Size</span> was selected from the main menu, MySQL Workbench
        crashed.
       (Bug #52065, Bug #52375)</p></li><li><p>
        The <span class="guilabel">Alter Table</span> dialog in the SQL Editor
        displayed comments with a single quote character prepending it,
        and with the last character of the comment truncated.
       (Bug #51972, Bug #52297)</p></li><li><p>
        MySQL Workbench crashed when synchronizing a model to a live server.
       (Bug #51892)</p></li><li><p>
        MySQL Workbench crashed while attempting to edit code in the SQL
        Editor.
       (Bug #51815)</p></li><li><p>
        The <span class="guilabel">New Server Instance</span> wizard did not set
        the correct name for the startup script, when the installation
        type was set to Fedora Linux (Vendor Package). Testing the
        connection resulted in the error “<span class="quote">Operation failed:
        /etc/init.d/mysql start is invalid</span>”.
       (Bug #51802)</p></li><li><p>
        In the Object Explorer of the SQL Editor, right-clicking a table
        displayed the menu option <span class="guilabel">Send to SQL
        Edtor</span>. Editor was spelled incorrectly.
       (Bug #51790)</p></li><li><p>
        When synchronizing a model containing a large number of Stored
        Routines, not all routines were synchronized with the live
        server.
       (Bug #51731)</p></li><li><p>
        When synchronizing between two triggers, unexpected
        <code class="literal">USE</code> statements and the comment “<span class="quote">--
        Trigger DDL Statements</span>” appeared intermittently. This
        caused a syntax error in the script.
       (Bug #51728)</p></li><li><p>
        If a connection was opened for querying and then
        <span><strong class="keycap">Control+W</strong></span> quickly pressed to close the
        connection, MySQL Workbench would crash.
       (Bug #51685)</p></li><li><p>
        When opening the <code class="filename">ip2nation.sql</code> file
        MySQL Workbench crashed.
       (Bug #51606, Bug #51531)</p></li><li><p>
        Exporting a result set to a CSV file resulted in a file with a
        trailing comma appended to each line including the heading.
       (Bug #51594)</p></li><li><p>
        In the <span class="guilabel">Inserts</span> tab of the Table Editor, if
        a row was right-clicked and <span class="guilabel">Delete selected
        rows</span> selected, MySQL Workbench crashed.
       (Bug #51584)</p></li><li><p>
        MySQL Workbench crashed if objects were sequentially selected in the
        EER Diagram view.
       (Bug #51573)</p></li><li><p>
        In the SQL Editor, when an SQL query was entered that contained
        a large number of characters, it appeared full width in the
        action column of the Ouput tab, causing the Response column to
        be unacceptably narrow.
       (Bug #51550)</p></li><li><p>
        In the <span class="guilabel">Alter Table</span> dialog of the SQL
        Editor, if a column was added to a table, and then an attempt
        made to alter that column's data type, the wizard generated
        <code class="literal">ADD COLUMN</code> code, rather than <code class="literal">CHANGE
        COLUMN</code>. That resulted in this error when an attempt
        was made to apply the changes:
      </p><pre class="programlisting">ERROR 1060: Duplicate column name 'test_column'</pre><p>(Bug #51516, Bug #51719)</p></li><li><p>
        In the <span class="guilabel">Alter Table</span> dialog of the SQL
        Editor, when a table was edited and changes applied, if
        subsequent changes were made and applied an error would result,
        as MySQL Workbench attempted to use <code class="literal">ADD COLUMN</code>
        rather than <code class="literal">CHANGE COLUMN</code>.
       (Bug #51481)</p></li><li><p>
        When <span class="guilabel">Manage Import / Export</span> was clicked on
        the Home screen, a server instance selected, and then
        <span class="guibutton">OK</span> clicked, MySQL Workbench displayed an
        error dialog with this message:
      </p><pre class="programlisting">MySQL Workbench has encountered a problem, External component has thrown an
exception.</pre><p>(Bug #51477, Bug #51665, Bug #51703, Bug #51733, Bug #51800, Bug #51870, Bug #51895, Bug #51963, Bug #51944, Bug #51999, Bug #52052, Bug #52262)</p></li><li><p>
        Building MySQL Workbench from source failed if
        <code class="literal">LDFLAGS="-Wl,--as-needed"</code> option was
        specified.
       (Bug #51469)</p></li><li><p>
        If a long running SQL query was executed in the SQL Editor, and
        then the <span class="guilabel">SQL Editor</span> tab closed, MySQL Workbench
        crashed if a new connection was started from the Home screen.
        This exception was generated:
      </p><pre class="programlisting">Unknown Exception: caught in c:\documents and
settings\mysqldev\build\mysql-workbench-oss-5.2.16\backend\windows\wbprivate.wr\src\Wb.h
at line 1087</pre><p>(Bug #51467)</p></li><li><p>
        It was not possible to connect to the MySQL server with
        MySQL Workbench if using sockets.
       (Bug #51419, Bug #51460)</p></li><li><p>
        When a model with a view was exported using
        <span class="guimenu">File</span>, <span class="guimenu">Export</span>,
        <span class="guimenu">Forward Engineer SQL CREATE Script</span>, a
        semicolon was added to the end of the <code class="literal">CREATE
        VIEW</code> statement, even if one was already present from
        the view code entered.
       (Bug #51416)</p></li><li><p>
        On the MySQL Model tab, if a table was clicked on and edited
        using the context menu option <span class="guimenu">Edit Table</span>,
        MySQL Workbench crashed.
       (Bug #51410, Bug #50936)</p></li><li><p>
        If all screens and tabs were closed in MySQL Workbench and then
        <span class="guimenu">Data</span>, <span class="guimenu">Manage Connections</span>
        selected, then when the <span class="guilabel">Manage DB
        Connections</span> dialog was closed an unknown exception
        occurred.
       (Bug #51403)</p></li><li><p>
        If a server instance was created with the <span class="guilabel">New
        Instance</span> wizard with SSH disabled, this exception
        occurred when attempting to administer the server instance:
      </p><pre class="programlisting">
Exception = System.Runtime.InteropServices.SEHException
Message = External component has thrown an exception.
FullText = System.Runtime.InteropServices.SEHException: External component has thrown an
exception.
   at MySQL.Forms.DrawBoxImpl.drawbox_mouse_click(Object sender, MouseEventArgs e)
   at System.Windows.Forms.Control.OnMouseClick(MouseEventArgs e)
   at System.Windows.Forms.Control.WmMouseUp(Message&amp; m, MouseButtons button, Int32
clicks)
   at System.Windows.Forms.Control.WndProc(Message&amp; m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message&amp; m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message&amp; m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam,
IntPtr lparam)
</pre><p>(Bug #51368, Bug #51476, Bug #51522, Bug #51483, Bug #51978, Bug #51810, Bug #51883, Bug #51803, Bug #52115, Bug #52163, Bug #51292, Bug #51668, Bug #51784, Bug #51789, Bug #51940, Bug #51947, Bug #52021, Bug #52028, Bug #52108, Bug #52240)</p></li><li><p>
        After exporting a schema to disk, importing the schema did not
        restore the tables.
       (Bug #51261)</p></li><li><p>
        In the Routine Editor, the editor added “<span class="quote">//</span>” as the
        last delimiter, even though “<span class="quote">DELIMITER $$</span>” was used
        at the beginning of the code.
       (Bug #51247)</p></li><li><p>
        In the SQL Editor, if a foreign key name was changed using the
        <span class="guilabel">Foreign Key</span> tab or
        <span class="guilabel">Indexes</span> tab of the <span class="guilabel">Alter
        Table</span> dialog, this error was generated:
      </p><pre class="programlisting">Type mismatch: expected type string, but got list</pre><p>(Bug #51192)</p></li><li><p>
        When the MySQL Workbench source was configured, the package
        <code class="literal">gnome-keyring-1</code> was not found.
       (Bug #51090)</p></li><li><p>
        There were discrepancies between the list of pre-requisite
        packages given on the MySQL Workbench website and those listed in
        the <code class="filename">README</code> file in the MySQL Workbench
        distribution.
       (Bug #51085)</p></li><li><p>
        On the <span class="guilabel">Output</span> tab of the SQL Editor, it was
        not possible to properly view the contents of the Action and
        Message columns, if the text exceeded the standard column width.
      </p><p>
        MySQL Workbench has now added a detail panel, so that long messages
        can be easily viewed.
       (Bug #51040)</p></li><li><p>
        In the Administrator section of MySQL Workbench, if a new user was
        created, the password was not correctly applied for the account,
        resulting in the new user being denied access when an attempt
        was made to connect to a server with that user account.
       (Bug #50983, Bug #51464)</p></li><li><p>
        An Out of Range exception occurred when switching from the Table
        Editor to the Home screen.
       (Bug #50980, Bug #51030)</p></li><li><p>
        In the <span class="guilabel">Output</span> tab of the SQL Editor, if a
        query produced an error response, it was difficult to read the
        returned error message. The message could only be read using
        mouse-over in the <span class="guilabel">Response</span> column, and the
        error message text could not be copied. The
        <span class="guilabel">Response</span> column is now renamed to
        <span class="guilabel">Message</span>. Further, the
        <span class="guilabel">Message</span> column has been widened, and new
        <span class="guilabel">Action</span> and <span class="guilabel">Message</span>
        detail panels have been added, making it easier to read error
        messages.
       (Bug #50629, Bug #50860)</p></li><li><p>
        When using the main menu item <span class="guimenu">Scripting</span>,
        <span class="guimenu">Run Workbench Script File</span>, the dialog
        appended “<span class="quote">.lua</span>” to the selected file name. This
        resulted in a failure to load the desired file.
       (Bug #50501)</p></li><li><p>
        In the SQL Editor, field names containing an underscore were
        displayed incorrectly on the Results tab. Instead of the
        underscore being displayed in the correct location the following
        character appeared underlined.
       (Bug #50132)</p></li><li><p>
        When a schema with Foreign keys and associated automatically
        generated foreign indexes was exported with the <span class="guilabel">Skip
        Creation of FOREIGN KEYS</span> check box selected, the
        generated script still contained the indexes.
       (Bug #49987)</p></li><li><p>
        In the SQL Editor, in a result set tab it was not possible to
        copy values from the result set. MySQL Workbench now includes the
        context sensitive menu items <span class="guimenu">Copy row values</span>
        and <span class="guimenu">Copy field content</span>.
       (Bug #49683, Bug #50170)</p></li><li><p>
        The Table Editor, Routine Editor, and other object editors
        stayed open, even if the user switched from the MySQL Model page
        to the SQL Editor page, Home screen, or Administrator page,
        thereby causing confusion.
       (Bug #49367)</p></li><li><p>
        In the live editing tab of the SQL Editor, if the
        <span><strong class="keycap">Alt+Tab</strong></span> key combination was used, the ascending
        and descending sort order of the columns could no longer be
        changed.
       (Bug #49366)</p></li><li><p>
        The live data editor in SQL Editor did not permit the columns to
        be sorted in descending order by clicking the column heading. It
        only permitted column sorting in ascending order through
        clicking the column heading.
       (Bug #49302)</p></li><li><p>
        In the <span class="guilabel">Overview</span> tab of the SQL Editor there
        was no scrolling facility available. This meant that if the
        model contained a large number of schema objects the panel area
        was quickly filled, and it was not possible to view all of the
        objects without the ability to scroll.
       (Bug #49290, Bug #51634)</p></li><li><p>
        In the <span class="guilabel">Alter Routine</span> dialog of the SQL
        Editor, when a routine was changed, and the changes successfully
        applied using the <span class="guilabel">Apply SQL Script to
        Database</span> dialog, the <span class="guilabel">Alter
        Routine</span> dialog still prompted the user to apply
        changes, even though the changes had already been successfully
        applied.
       (Bug #49273)</p></li><li><p>
        When switching from a tab such as the <span class="guilabel">SQL
        Editor</span> tab to the Home screen, the toolbar did not
        change accordingly. However, the buttons on the toolbar were
        still active, leading to the possibility of unintentional
        actions.
       (Bug #49147)</p></li><li><p>
        In the SQL editor, if Alter Table was invoked for a table, and
        then the partitioning tab selected and partitioning enabled, it
        was possible to select a partition count of 0, which then
        generated an error if an attempt was made to apply changes.
       (Bug #49050)</p></li><li><p>
        This bug occurred when using the MySQL Workbench Administrator with
        MySQL Server version 5.0. When selecting Enable General Log in
        the Administrator's configuration page, MySQL Workbench attempted to
        add the option <code class="literal">general-log</code> to the
        configuration file, even thought this is not supported by MySQL
        Server 5.0.
       (Bug #49011)</p></li><li><p>
        In the <span class="guilabel">Overview</span> tab of the SQL Editor, if
        there were a large number of schemata, it was not possible to
        access certain schemata because they did not all fit on the
        schema tab control.
      </p><p>
        MySQL Workbench has been changed so that there is now a small drop
        down control that enables you to select the required schema,
        even if it is not currently visible on the schema tab control.
       (Bug #48898, Bug #50169)</p></li><li><p>
        In the EER Diagram view, when zooming in or out of the diagram
        the screen was not redrawn correctly.
       (Bug #48020, Bug #48032, Bug #34505)</p></li><li><p>
        When using the option <span class="guilabel">Omit Schemata Qualifier in
        Object Names</span> in the <span class="guilabel">Forward
        Engineer</span> dialog, the schema name still appeared in
        <code class="literal">DROP</code>, <code class="literal">CREATE SCHEMA</code>,
        <code class="literal">INSERT</code> and <code class="literal">USE</code> statements.
        The schema name also appeared in the table comments.
       (Bug #46837, Bug #51411)</p></li><li><p>
        In the configuration settings panel of the Administrator, the
        ',' character was treated as part of the database name, and so
        it was not possible to specify multiple databases for certain
        configuration options.
      </p><p>
        MySQL Workbench has been changed as follows:
      </p><p>
        Several configuration options permit multiple databases to be
        specified. For example, binlog-do-db and binlog-ignore-db.
        However, if a comma is used to delimit these databases, the
        comma is correctly treated as part of the database name. This
        means that to specify multiple databases you must use multiple
        instances of the option.
      </p><p>
        To specify multiple instances of the option, the “;”
        character can be used in MySQL Workbench. When text is entered into
        the option entry field and the “;” symbol detected,
        MySQL Workbench prompts you to select multiple instances, or leave
        the option entry unchanged. If selected the option will be
        written to the configuration file as multiple instances.
        Further, when a multiple instance option is detected in a
        configuration file it is parsed into &lt;value1&gt; ;
        &lt;value2&gt; ; ... ; &lt;valueN&gt;.
       (Bug #15245, Bug #11745436)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-manage-server-advanced-options.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>8.7.6.3. Advanced Export Options</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-manage-server-data-dump-tab.html" title="8.7.6. The Data Dump Tab"><link rel="prev" href="wb-manage-server-import-from-disk.html" title="8.7.6.2. Import from Disk"><link rel="next" href="wb-manage-server-logs-tab.html" title="8.7.7. The Logs Tab"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-manage-server-advanced-options"></a>8.7.6.3. Advanced Export Options</h4></div></div></div><p>
          The Advanced Export Options tab contains a number of options
          to enable you to control the export operation. These options
          control the SQL generated during the operation.
        </p><div class="figure"><a name="wb-manage-server-data-options-screenshot"></a><p class="title"><b>Figure 8.11. Administrator - Advanced Options</b></p><div class="mediaobject"><img src="images/wb-manage-server-data-options.png" width="1024" height="707" alt="Administrator - Advanced
              Options"></div></div></div></body></html>


path: /wb-html-guitools/wb-sql-editor-object-browser.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>6.7.5.2. Object Browser</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-sql-editor-sidebar.html" title="6.7.5. Sidebar"><link rel="prev" href="wb-sql-editor-connection-information-panel.html" title="6.7.5.1. Connection Information Panel"><link rel="next" href="wb-data-modeling.html" title="Chapter 7. Data Modeling"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-sql-editor-object-browser"></a>6.7.5.2. Object Browser</h4></div></div></div><p>
          The Object Browser contains an Actions list and a Schemata
          list, as seen in the following screenshot.
        </p><div class="figure"><a name="wb-sql-editor-object-browser-screenshot"></a><p class="title"><b>Figure 6.14. SQL Editor - Object Browser</b></p><div class="mediaobject"><img src="images/wb-sql-editor-actions-screenshot.png" width="208" height="238" alt="SQL Editor - Object Browser"></div></div><p>
          <span class="bold"><strong>Object Browser Actions List</strong></span>
        </p><p>
          The Object Browser contains an Actions list. The actions are:
        </p><div class="itemizedlist"><ul type="disc"><li><p>
              <span class="guilabel">Execute SQL File</span>: Opens a file
              chooser dialog that enables you to select an SQL script to
              execute.
            </p></li><li><p>
              <span class="guilabel">Add Schema</span>: Enables you to add a new
              schema to your server.
            </p></li><li><p>
              <span class="guilabel">Add Table</span>: Enables you to create a
              new table via the <span class="guilabel">new_table</span> dialog.
            </p></li><li><p>
              <span class="guilabel">Add View</span>: Enables you to create a new
              view via the <span class="guilabel">new_view</span> dialog.
            </p></li><li><p>
              <span class="guilabel">Add Routine</span>: Enables you to create a
              new routine via the <span class="guilabel">new_routine</span>
              dialog.
            </p></li></ul></div><p>
          <span class="bold"><strong>Schemata List</strong></span>
        </p><p>
          The Schemata list shows available schemata on the currently
          connected server. These can be explored to show tables, views,
          and routines within the schema.
        </p><div class="figure"><a name="wb-sql-editor-schemata-explorer-screenshot"></a><p class="title"><b>Figure 6.15. SQL Editor - Schemata Explorer</b></p><div class="mediaobject"><img src="images/wb-sql-editor-schemata-explorer-screenshot.png" width="204" height="306" alt="SQL Editor - Schemata Explorer"></div></div><p>
          It is possible to set a schema as the default schema by
          right-clicking the schema and selecting the <span class="guimenuitem">Set
          As Default Schema</span> menu item. This executes a
          <code class="literal">USE <em class="replaceable"><code>schema_name</code></em></code>
          statement so that subsequent statements without schema
          qualifiers are executed against this schema. This setting
          applies only to the query session. To set a default schema for
          multiple MySQL Workbench sessions, you must set the default schema
          for the stored connection. From the Home screen, click
          <span class="guilabel">Manage Connections</span>, then in the
          <span class="guilabel">Manage DB Connection</span> dialog, set the
          desired default schema on the <span class="guilabel">Parameters</span>
          tab.
        </p><p>
          A useful feature that was introduced in MySQL Workbench 5.2.9 is
          the ability to rapidly enter table, view, or column names into
          the SQL Statement area. Double-clicking a table, view, or
          column name in the schemata explorer inserts the name into the
          SQL Query area. This reduces typing significantly when
          entering SQL statements containing references to several
          tables, views, or columns.
        </p><p>
          The Object Browser also features a context menu which can be
          displayed by right-clicking an object. For example,
          right-clicking a table displays the following menu items:
        </p><div class="itemizedlist"><ul type="disc"><li><p>
              <span class="guimenuitem">Select Rows - Limit 1000</span>: Pulls
              up to 1000 rows of table data from the live server into a
              Results tabsheet.
            </p></li><li><p>
              <span class="guimenuitem">Edit Table Data</span>: Pulls table
              data from the live server into a named tabsheet, and
              enables editing. Data can be saved directly to the live
              server.
            </p></li><li><p>
              <span class="guimenuitem">Copy to Clipboard</span>: There are
              various submenus, each of which copies information to the
              clipboard:
            </p><div class="itemizedlist"><ul type="circle"><li><p>
                  Name (short): Copies the table name.
                </p></li><li><p>
                  Name (long): Copies the qualified table name in the
                  form <code class="literal">`schema`.`table`</code>.
                </p></li><li><p>
                  Column Names: Copies qualified column names the form
                  <code class="literal">`table`.`column1`,
                  `table`.`column2`,...</code>.
                </p></li><li><p>
                  Select All Statement: Copies a statement to select all
                  columns in this form:
                </p><pre class="programlisting">SELECT
`table`.`column1`,
`table`.`column2`,
...
FROM `schema`.`table`;</pre></li><li><p>
                  Insert Statement: Copies an <code class="literal">INSERT</code>
                  statement to insert all columns.
                </p></li><li><p>
                  Update Statement: Copies an <code class="literal">UPDATE</code>
                  statement to update all columns.
                </p></li><li><p>
                  Delete Statement: Copies a <code class="literal">DELETE</code>
                  statement in the form <code class="literal">DELETE FROM
                  `world`.`country` WHERE
                  &lt;where_condition&gt;;</code>.
                </p></li></ul></div></li><li><p>
              <span class="guimenuitem">Send to SQL Editor</span>: Provides
              functionality similar to Copy to Clipboard. However, this
              item inserts the SQL code directly into the SQL Query
              panel, where it can be edited further as required.
            </p></li><li><p>
              <span class="guimenuitem">Alter Table</span>: Displays the table
              editor loaded with the details of the table.
            </p></li><li><p>
              <span class="guimenuitem">Create Table</span>: Launches a dialog
              to enable you to create a new table.
            </p></li><li><p>
              <span class="guimenuitem">Drop Table</span>: Drops the table.
              All data in the table will be lost if this operation is
              carried out.
            </p></li><li><p>
              <span class="guimenuitem">Refresh All</span>: Refreshes all
              schemata in the explorer by resynchronizing with the
              server.
            </p></li></ul></div><p>
          Right-clicking an empty area inside the object browser
          displays the following menu items:
        </p><div class="itemizedlist"><ul type="disc"><li><p>
              <span class="guimenuitem">Create Schema</span>: Enables you to
              create a new schema on the connected server. You can apply
              your changes to synchronize with the live server by
              clicking the <span class="guibutton">Apply</span> button.
            </p></li><li><p>
              <span class="guimenuitem">Refresh All</span>: Synchronizes with
              the live server to update the information displayed by the
              schemata explorer.
            </p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-data-modeling.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Chapter 7. Data Modeling</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="index.html" title="MySQL Workbench"><link rel="prev" href="wb-sql-editor-object-browser.html" title="6.7.5.2. Object Browser"><link rel="next" href="wb-data-modeling-open-existing-model.html" title="7.1. Open an Existing EER Model"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="wb-data-modeling"></a>Chapter 7. Data Modeling</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="wb-data-modeling-open-existing-model.html">7.1. Open an Existing EER Model</a></span></dt><dt><span class="section"><a href="wb-data-modeling-create-new-model.html">7.2. Create New EER Model</a></span></dt><dt><span class="section"><a href="wb-data-modeling-create-model-from-existing-database.html">7.3. Create EER Model from Existing Database</a></span></dt><dt><span class="section"><a href="wb-data-modeling-create-model-from-sql-script.html">7.4. Create EER Model from SQL Script</a></span></dt><dt><span class="section"><a href="wb-model-editor.html">7.5. Model Editor</a></span></dt><dd><dl><dt><span class="section"><a href="wb-data-modeling-menus.html">7.5.1. Modeling Menus</a></span></dt><dt><span class="section"><a href="wb-toolbar.html">7.5.2. The Toolbar</a></span></dt><dt><span class="section"><a href="wb-eer-diagrams-section.html">7.5.3. EER Diagrams</a></span></dt><dt><span class="section"><a href="wb-view-overview-physical-schemata.html">7.5.4. The Physical Schemata Panel</a></span></dt><dt><span class="section"><a href="wb-model-overview-privileges.html">7.5.5. The Schema Privileges Panel</a></span></dt><dt><span class="section"><a href="wb-views-overview-scripts.html">7.5.6. The SQL Scripts Panel</a></span></dt><dt><span class="section"><a href="wb-views-overview-notes.html">7.5.7. The Model Notes Panel</a></span></dt><dt><span class="section"><a href="wb-history-palette.html">7.5.8. The History Palette</a></span></dt><dt><span class="section"><a href="wb-navigator-panel.html">7.5.9. The Model Navigator Panel</a></span></dt><dt><span class="section"><a href="wb-catalog-palette.html">7.5.10. The Catalog Tree Palette</a></span></dt><dt><span class="section"><a href="wb-layers-palette.html">7.5.11. The Layers Palette</a></span></dt><dt><span class="section"><a href="wb-properties-palette.html">7.5.12. The Properties Palette</a></span></dt></dl></dd><dt><span class="section"><a href="wb-eer-diagram-editor.html">7.6. EER Diagram Editor</a></span></dt><dd><dl><dt><span class="section"><a href="wb-vertical-toolbar.html">7.6.1. The Vertical Toolbar</a></span></dt></dl></dd><dt><span class="section"><a href="wb-working-with-models.html">7.7. Working with Models</a></span></dt><dd><dl><dt><span class="section"><a href="wb-tables.html">7.7.1. Creating Tables</a></span></dt><dt><span class="section"><a href="wb-foreign-key-relationships.html">7.7.2. Creating Foreign Key Relationships</a></span></dt><dt><span class="section"><a href="wb-creating-views.html">7.7.3. Creating Views</a></span></dt><dt><span class="section"><a href="wb-routines-routine-groups.html">7.7.4. Creating Routines and Routine Groups</a></span></dt><dt><span class="section"><a href="wb-layers.html">7.7.5. Creating Layers</a></span></dt><dt><span class="section"><a href="wb-notes.html">7.7.6. Creating Notes</a></span></dt><dt><span class="section"><a href="wb-text-objects.html">7.7.7. Creating Text Objects</a></span></dt><dt><span class="section"><a href="wb-images.html">7.7.8. Creating Images</a></span></dt><dt><span class="section"><a href="wb-reverse-engineering.html">7.7.9. Reverse Engineering</a></span></dt><dt><span class="section"><a href="wb-forward-engineering.html">7.7.10. Forward Engineering</a></span></dt></dl></dd><dt><span class="section"><a href="wb-tutorials.html">7.8. Modeling Tutorials</a></span></dt><dd><dl><dt><span class="section"><a href="wb-importing-sql-script.html">7.8.1. Importing a Data Definition SQL Script</a></span></dt><dt><span class="section"><a href="wb-default-schema.html">7.8.2. Using the Default Schema</a></span></dt><dt><span class="section"><a href="wb-basic-modeling.html">7.8.3. Basic Modeling</a></span></dt><dt><span class="section"><a href="wb-documenting-sakila.html">7.8.4. Documenting the <code class="literal">sakila</code> Database</a></span></dt></dl></dd><dt><span class="section"><a href="wb-printing.html">7.9. Printing</a></span></dt><dd><dl><dt><span class="section"><a href="wb-printing-options.html">7.9.1. Printing Options</a></span></dt></dl></dd><dt><span class="section"><a href="wb-validation-plugins.html">7.10. MySQL Workbench Schema Validation Plugins (Commercial Version)</a></span></dt><dd><dl><dt><span class="section"><a href="wb-general-validation.html">7.10.1. General Validation</a></span></dt><dt><span class="section"><a href="wb-mysql-validation.html">7.10.2. MySQL-Specific Validation</a></span></dt></dl></dd><dt><span class="section"><a href="wb-model-reporting.html">7.11. The DBDoc Model Reporting Dialog Window (Commercial Version)</a></span></dt><dt><span class="section"><a href="dbdoc-templates.html">7.12. Customizing DBDoc Model Reporting Templates</a></span></dt><dd><dl><dt><span class="section"><a href="dbdoc-templates-markers.html">7.12.1. Supported Template Markers</a></span></dt><dt><span class="section"><a href="dbdoc-templates-custom.html">7.12.2. Creating a Custom Template</a></span></dt></dl></dd></dl></div><p>
    MySQL Workbench provides extensive capabilities for creating and
    manipulating database models, including these:
  </p><div class="itemizedlist"><ul type="disc"><li><p>
        Create and manipulate a model graphically
      </p></li><li><p>
        Reverse engineer a live database to a model
      </p></li><li><p>
        Forward engineer a model to a script or live database
      </p></li><li><p>
        Create and edit tables and insert data
      </p></li></ul></div><p>
    This is not an exhaustive list. The following sections discuss these
    and additional data-modeling capablities.
  </p><p>
    The Home window is the typical starting point for work with data
    modeling. In the Data Modeling section of the Workspace, you can use
    the action items there to create and manage models, forward and
    reverse engineer, and compare and synchronize schemata:
  </p><div class="itemizedlist"><ul type="disc"><li><p>
        Open an Existing EER Model
      </p></li><li><p>
        Create new EER Model
      </p></li><li><p>
        Create EER Model from Existing Database
      </p></li><li><p>
        Create EER Model from SQL Script
      </p></li></ul></div><p>
    The following sections describe these action items.
  </p></div></body></html>


path: /wb-html-guitools/wb-plugins-menu.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.5.1.7. The Plugins Menu</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-data-modeling-menus.html" title="7.5.1. Modeling Menus"><link rel="prev" href="wb-database-menu.html" title="7.5.1.6. The Database Menu"><link rel="next" href="wb-scripting-menu.html" title="7.5.1.8. The Scripting Menu"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-plugins-menu"></a>7.5.1.7. The Plugins Menu</h4></div></div></div><p>
      The <span class="guimenu">Plugins</span> menu lists any plugins that you may
      have installed. For more information about this menu, see
      <a href="wb-plugins.html" title="9.3. Plugins">Section 9.3, “Plugins”</a>.
    </p></div></body></html>


path: /wb-html-guitools/wb-hand-tool.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.6.1.2. The Hand Tool</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-vertical-toolbar.html" title="7.6.1. The Vertical Toolbar"><link rel="prev" href="wb-standard-mouse-pointer.html" title="7.6.1.1. The Standard Mouse Pointer"><link rel="next" href="wb-eraser-tool.html" title="7.6.1.3. The Eraser Tool"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-hand-tool"></a>7.6.1.2. The Hand Tool</h4></div></div></div><p>
        The hand tool is used to move the entire EER diagram. Left-click
        on this tool and then left-click anywhere on the EER diagram
        canvas. Moving the mouse while holding down the mouse button
        changes the view port of the canvas.
      </p><p>
        To determine your position on the canvas, look at the
        <code class="literal">Model Navigator</code> panel on the upper right. If
        the <code class="literal">Model Navigator</code> panel is not open, use
        <span class="guimenu">View</span>, <span class="guisubmenu">Windows</span>,
        <span class="guimenuitem">Model Navigator</span> to open it.
      </p><p>
        To activate the hand tool from the keyboard, use the
        <span><strong class="keycap">H</strong></span> key.
      </p><p>
        You can also change the view port of an EER diagram using the
        <code class="literal">Model Navigator</code> panel. See
        <a href="wb-navigator-panel.html" title="7.5.9. The Model Navigator Panel">Section 7.5.9, “The Model Navigator Panel”</a>.
      </p></div></body></html>


path: /wb-html-guitools/wb-validation-plugins.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.10. MySQL Workbench Schema Validation Plugins (Commercial Version)</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-data-modeling.html" title="Chapter 7. Data Modeling"><link rel="prev" href="wb-printing-options.html" title="7.9.1. Printing Options"><link rel="next" href="wb-general-validation.html" title="7.10.1. General Validation"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="wb-validation-plugins"></a>7.10. MySQL Workbench Schema Validation Plugins (Commercial Version)</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-general-validation.html">7.10.1. General Validation</a></span></dt><dt><span class="section"><a href="wb-mysql-validation.html">7.10.2. MySQL-Specific Validation</a></span></dt></dl></div><p>
    MySQL Workbench provides validation modules so that you can test your
    models before implementing them.
  </p><p>
    The validation plugins are accessed from the
    <span class="guimenu">Model</span> menu. One plugin performs general
    validation for any Relational Database Management System (RDMS) and
    the other is MySQL specific. Beneath these menu items are a number
    of specific validation tests. Running any one of these tests opens
    an output window docked at the bottom of the application. Warning
    messages are displayed on the left side of this window and the tests
    performed are displayed on the right.
  </p><p>
    The following sections outline the tasks performed by the validation
    modules.
  </p></div></body></html>


path: /wb-html-guitools/wb-model-menu.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.5.1.5. The Model Menu</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-data-modeling-menus.html" title="7.5.1. Modeling Menus"><link rel="prev" href="wb-arrange-menu.html" title="7.5.1.4. The Arrange Menu"><link rel="next" href="wb-database-menu.html" title="7.5.1.6. The Database Menu"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-model-menu"></a>7.5.1.5. The Model Menu</h4></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-model-menu.html#wb-reporting">7.5.1.5.1. The DBDoc Model Reporting Dialog Window (Commercial Version)</a></span></dt><dt><span class="section"><a href="wb-model-menu.html#wb-validation-menus">7.5.1.5.2. The Validation Submenus (Commercial Version)</a></span></dt><dt><span class="section"><a href="wb-model-menu.html#wb-object-notation-menu">7.5.1.5.3. The Object Notation Submenu</a></span></dt><dt><span class="section"><a href="wb-model-menu.html#wb-relationship-notation-menu">7.5.1.5.4. The Relationship Notation Submenu</a></span></dt></dl></div><p>
      The <span class="guimenu">Model</span> menu has these items:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <span class="guimenuitem">Add Diagram</span>: Creates a new EER
          Diagram. The keyboard shortcut is <span><strong class="keycap">Control+T</strong></span>.
        </p></li><li><p>
          <span class="guimenuitem">Create Diagram From Catalog
          Objects</span>: Creates an EER diagram from all the
          objects in the catalog.
        </p></li><li><p>
          <span class="guimenuitem">DBDoc – Model Reporting...</span>:
          For information about this menu item, see
          <a href="wb-model-menu.html#wb-reporting" title="7.5.1.5.1. The DBDoc Model Reporting Dialog Window (Commercial Version)">Section 7.5.1.5.1, “The DBDoc Model Reporting Dialog Window (Commercial Version)”</a>. Commercial version only.
        </p></li><li><p>
          <span class="guimenuitem">User Defined Types</span>: Presents a
          dialog box that enables you to add and delete user defined
          data types.
        </p></li><li><p>
          <span class="guimenuitem">Object Notation</span>: For information
          about this menu item, see
          <a href="wb-model-menu.html#wb-object-notation-menu" title="7.5.1.5.3. The Object Notation Submenu">Section 7.5.1.5.3, “The Object Notation Submenu”</a>.
        </p></li><li><p>
          <span class="guimenuitem">Relationship Notation</span>: For
          information about this menu item, see
          <a href="wb-model-menu.html#wb-relationship-notation-menu" title="7.5.1.5.4. The Relationship Notation Submenu">Section 7.5.1.5.4, “The Relationship Notation Submenu”</a>.
        </p></li><li><p>
          <span class="guimenuitem">Diagram Properties and Size</span>: Opens
          a diagram size dialog box that enables you to adjust the width
          or height of the canvas. The unit of measure is pages; the
          default value is two.
        </p><p>
          When you have tables with numerous columns, use this menu item
          to increase the size of the EER.
        </p></li><li><p>
          <span class="guimenuitem">Validation</span>: For information about
          this menu item, see <a href="wb-model-menu.html#wb-validation-menus" title="7.5.1.5.2. The Validation Submenus (Commercial Version)">Section 7.5.1.5.2, “The Validation Submenus (Commercial Version)”</a>.
          Commercial version only.
        </p></li><li><p>
          <span class="guimenuitem">Model Options</span>: Sets options at the
          model level. These options should not be confused with the
          options that are set globally for the Workbench application,
          and which are referred to as Workbench Preferences. The
          available model options are a subset of the Workbench
          Preferences options.
        </p><p>
          For more information about Workbench Preferences, see
          <a href="wb-preferences-model.html" title="5.4.4. The Model Tab">Section 5.4.4, “The Model Tab”</a>.
        </p></li></ul></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="wb-reporting"></a>7.5.1.5.1. The DBDoc Model Reporting Dialog Window (Commercial Version)</h5></div></div></div><p>
        This dialog window is found by navigating to the
        <span class="guimenu">Model</span> menu and choosing the
        <span class="guimenuitem">DBDoc - Model Reporting...</span> item.
      </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
          The <span class="guimenuitem">DBDoc - Model Reporting...</span> item
          is not available in the MySQL Workbench OSS version.
        </p></div><p>
        Use this dialog window to set the options for creating
        documentation of your database models. For more information, see
        <a href="wb-model-reporting.html" title="7.11. The DBDoc Model Reporting Dialog Window (Commercial Version)">Section 7.11, “The DBDoc Model Reporting Dialog Window (Commercial Version)”</a>.
      </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="wb-validation-menus"></a>7.5.1.5.2. The Validation Submenus (Commercial Version)</h5></div></div></div><p>
        The <span class="guimenu">Model</span> menu has two validation submenus,
        <span class="guisubmenu">Validation</span> and <span class="guisubmenu">Validation
        (MySQL)</span>. Use these submenus for general validation
        and MySQL-specific validation of the objects and relationships
        defined in your model.
      </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
          These items are not available in the MySQL Workbench OSS version.
        </p></div><p>
        The <span class="guisubmenu">Validation</span> submenu has these items:
      </p><div class="itemizedlist"><ul type="disc"><li><p>
            <span class="guimenuitem">Validate All</span>: Performs all
            available validation checks
          </p></li><li><p>
            <span class="guimenuitem">Empty Content Validation</span>: Checks
            for objects with no content, such as a table with no columns
          </p></li><li><p>
            <span class="guimenuitem">Table Efficiency Validation</span>:
            Checks the efficiency of tables, such as a table with no
            primary key defined
          </p></li><li><p>
            <span class="guimenuitem">Duplicate Identifiers Validation</span>:
            Checks for duplicate identifiers, such as two tables with
            the same name
          </p></li><li><p>
            <span class="guimenuitem">Consistency Validation</span>: Checks
            for consistent naming conventions
          </p></li><li><p>
            <span class="guimenuitem">Logic Validation</span>: Checks, for
            example, that a foreign key does not reference a nonprimary
            key column in the source table
          </p></li></ul></div><p>
        The <span class="guisubmenu">Validation (MySQL)</span> submenu has
        these items:
      </p><div class="itemizedlist"><ul type="disc"><li><p>
            <span class="guimenuitem">Validate All</span>: Performs all
            available validation checks
          </p></li><li><p>
            <span class="guimenuitem">Integrity Validation</span>: Checks for
            invalid references, such as a table name longer than the
            maximum permitted
          </p></li><li><p>
            <span class="guimenuitem">Syntax validation</span>: Checks for
            correct SQL syntax
          </p></li><li><p>
            <span class="guimenuitem">Duplicate Identifiers Validation
            (Additions)</span>: Checks for objects with the same
            name
          </p></li></ul></div><p>
        For detailed information about validation, see
        <a href="wb-validation-plugins.html" title="7.10. MySQL Workbench Schema Validation Plugins (Commercial Version)">Section 7.10, “MySQL Workbench Schema Validation Plugins (Commercial Version)”</a>.
      </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="wb-object-notation-menu"></a>7.5.1.5.3. The Object Notation Submenu</h5></div></div></div><p>
        The items under the <span class="guisubmenu">Object Notation</span>
        submenu apply exclusively to an EER diagram. They are not
        enabled unless an EER diagram tab is selected.
      </p><p>
        The <span class="guisubmenu">Object Notation</span> submenu has these
        items:
      </p><div class="itemizedlist"><ul type="disc"><li><p>
            <span class="guimenuitem">Workbench (Default)</span>: Displays
            table columns, indexes, and triggers
          </p></li><li><p>
            <span class="guimenuitem">Workbench (Simplified)</span>: Shows
            only a table's columns
          </p></li><li><p>
            <span class="guimenuitem">Workbench (PKs and FKs only)</span>:
            Shows only columns that are primary and foreign keys
          </p></li><li><p>
            <span class="guimenuitem">Classic</span>: Similar to the
            <code class="literal">Workbench (Simplified)</code> style showing only
            the table's columns
          </p></li><li><p>
            <span class="guimenuitem">IDEF1X</span>: The ICAM DEFinition
            language information modeling style
          </p></li></ul></div><p>
        The object notation style that you choose persists for the
        duration of your MySQL Workbench session and is saved along with
        your model. When MySQL Workbench is restarted, the object notation
        reverts to the default.
      </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
          If you plan to export or print an EER diagram be sure to
          decide on a notation style first. Changing notation styles
          after objects have been placed on a diagram can significantly
          change the appearance of the diagram.
        </p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="wb-relationship-notation-menu"></a>7.5.1.5.4. The Relationship Notation Submenu</h5></div></div></div><p>
        The items under the <span class="guisubmenu">Relationship
        Notation</span> submenu apply exclusively to an EER
        diagram. They are not enabled unless an EER diagram tab is
        selected.
      </p><p>
        The <span class="guisubmenu">Relationship Notation</span> submenu has
        these items:
      </p><div class="itemizedlist"><ul type="disc"><li><p>
            <span class="guimenuitem">Crow's Foot (IE)</span>: The default
            modeling style. For an example, see
            <a href="wb-creating-eer-diagram.html#wb-sakila-tutorial-image" title="Figure 7.42. Adding Tables to the Canvas">Figure 7.42, “Adding Tables to the Canvas”</a>.
          </p></li><li><p>
            <span class="guimenuitem">Classic</span>: Uses a diamond shape to
            indicate cardinality.
          </p></li><li><p>
            <span class="guimenuitem">Connect to Columns</span>
          </p></li><li><p>
            <span class="guimenuitem">UML</span>: Universal Modeling Language
            style.
          </p></li><li><p>
            <span class="guimenuitem">IDEF1X</span>: The ICAM DEFinition
            language information modeling method
          </p></li></ul></div><p>
        To view the different styles, set up a relationship between two
        or more tables and choose the different menu items.
      </p><p>
        The relationship notation style that you choose persists for the
        duration of your MySQL Workbench session and is saved along with
        your model. When MySQL Workbench is restarted, the relationship
        notation reverts to the default, the <code class="literal">Crow's
        Foot</code> style.
      </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
          If you plan to export or print an EER diagram, be sure to
          decide on a notation style first. Changing notation styles
          after objects have been placed on a diagram can significantly
          change the appearance of the diagram.
        </p></div></div></div></body></html>


path: /wb-html-guitools/wb-routine-groups.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.7.4.2. Routine Groups</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-routines-routine-groups.html" title="7.7.4. Creating Routines and Routine Groups"><link rel="prev" href="wb-routines.html" title="7.7.4.1. Routines"><link rel="next" href="wb-layers.html" title="7.7.5. Creating Layers"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-routine-groups"></a>7.7.4.2. Routine Groups</h4></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-routine-groups.html#wb-routine-groups-physical-schemata">7.7.4.2.1. Adding Routine Groups to the Physical Schemata</a></span></dt><dt><span class="section"><a href="wb-routine-groups.html#wb-using-routine-groups-tool">7.7.4.2.2. Adding Routine Groups to an EER Diagram</a></span></dt><dt><span class="section"><a href="wb-routine-groups.html#wb-routine-groups-editor">7.7.4.2.3. The Routine Group Editor</a></span></dt></dl></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="wb-routine-groups-physical-schemata"></a>7.7.4.2.1. Adding Routine Groups to the Physical Schemata</h5></div></div></div><p>
        Double-clicking the <code class="literal">Add Routine Group</code> icon in
        the <code class="literal">Physical Schemata</code> section of the
        <code class="literal">MySQL Model</code> page adds a routine group with
        the default name of <code class="literal">routines1</code>. If a routine
        group with this name already exists, the new routine group is
        named <code class="literal">routines2</code>.
      </p><p>
        Adding a new routine group automatically opens the routine
        groups editor docked at the bottom of the application. For
        information about using the routine groups editor, see
        <a href="wb-routine-groups.html#wb-routine-groups-editor" title="7.7.4.2.3. The Routine Group Editor">Section 7.7.4.2.3, “The Routine Group Editor”</a>.
      </p><p>
        Right-clicking a routine group opens a pop-up menu with the
        following items:
      </p><div class="itemizedlist"><ul type="disc"><li><p>
            <span class="guimenuitem">Rename</span>
          </p></li><li><p>
            <span class="guimenuitem">Cut
            '<em class="replaceable"><code>routine_group_name</code></em>'</span>
          </p></li><li><p>
            <span class="guimenuitem">Copy
            '<em class="replaceable"><code>routine_group_name</code></em>'</span>
          </p></li><li><p>
            <span class="guimenuitem">Edit Routine...</span>
          </p></li><li><p>
            <span class="guimenuitem">Edit in New Window...</span>
          </p></li><li><p>
            <span class="guimenuitem">Copy SQL to Clipboard</span>
          </p></li><li><p>
            <span class="guimenuitem">Delete
            '<em class="replaceable"><code>routine_group_name</code></em>'</span>
          </p></li></ul></div><p>
        The <span class="guimenuitem">Edit Routine Group...</span> item opens
        the routine group editor, which is described in
        <a href="wb-routine-groups.html#wb-routine-groups-editor" title="7.7.4.2.3. The Routine Group Editor">Section 7.7.4.2.3, “The Routine Group Editor”</a>.
      </p><p>
        The cut and paste items are useful for copying routine groups
        between different schemata.
      </p><p>
        Deleting a routine group from the <code class="literal">MySQL Model</code>
        page removes the group but does not remove any routines
        contained in that group.
      </p><p>
        Any routine groups added to the <code class="literal">Physical
        Schemata</code> also show up in the
        <code class="literal">Catalog</code> palette on the right side of the
        application. They may be added to an EER Digram by dragging and
        dropping them from this palette.
      </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="wb-using-routine-groups-tool"></a>7.7.4.2.2. Adding Routine Groups to an EER Diagram</h5></div></div></div><p>
        To add routine groups to an EER Diagram, use the
        <code class="literal">Routine Groups</code> tool on the vertical toolbar.
        Make sure that the <span class="guilabel">EER Diagram</span> tab is
        selected, then right-click the routine groups icon on the
        vertical toolbar. The routine groups icon is immediately above
        the lowest toolbar separator.
      </p><p>
        Clicking the mouse on this icon changes the mouse pointer to a
        routine group pointer. You can also change the mouse pointer to
        a routine pointer by pressing the <span><strong class="keycap">G</strong></span> key.
      </p><p>
        Choosing the <code class="literal">Routine Group</code> tool changes the
        contents of the toolbar that appears immediately below the menu
        bar. When the <code class="literal">Routine Groups</code> pointer is
        active, this toolbar contains a schemata list and a color chart
        list. Use these lists to select the appropriate schema and color
        accent for the new routine group. Make sure that you associate
        the new routine group with a database. The color of your routine
        group can be changed later using the
        <code class="literal">Properties</code> palette.
      </p><p>
        Create a routine group by clicking anywhere on the EER Diagram
        canvas. This creates a new routine group with the default name
        <code class="literal">routines1</code>. To revert to the default mouse
        pointer, click the arrow icon at the top of the vertical
        toolbar.
      </p><p>
        Right-clicking a routine group opens a pop-up menu. With the
        exception of the delete option and rename options, these menu
        options function as described in
        <a href="wb-routine-groups.html#wb-routine-groups-physical-schemata" title="7.7.4.2.1. Adding Routine Groups to the Physical Schemata">Section 7.7.4.2.1, “Adding Routine Groups to the Physical Schemata”</a>. There is
        no rename option, and the behavior of the delete option is
        determined by your MySQL Workbench options settings. For more
        information, see <a href="wb-preferences-model.html" title="5.4.4. The Model Tab">Section 5.4.4, “The Model Tab”</a>.
      </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="wb-routine-groups-editor"></a>7.7.4.2.3. The Routine Group Editor</h5></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-routine-groups.html#wb-routine-groups-tab">7.7.4.2.3.1. The Routine Groups Tab</a></span></dt><dt><span class="section"><a href="wb-routine-groups.html#wb-routine-groups-editor-privileges">7.7.4.2.3.2. The Privileges Tab</a></span></dt><dt><span class="section"><a href="wb-routine-groups.html#wb-modifying-routine">7.7.4.2.3.3. Modifying a Routine Group Using the Properties Palette</a></span></dt></dl></div><p>
        To invoke the routine group editor, double-click a routine group
        object on the EER Diagram canvas or double-click a routine group
        in the <code class="literal">Physical Schemata</code> section on the
        <code class="literal">MySQL Model</code> page. This opens the routine
        group editor docked at the bottom of the application.
        Double-clicking the title bar undocks the editor. Do the same to
        redock it. Any number of routine groups may be open at the same
        time. Each additional routine group appears as a tab at the top
        of the routine editor,
      </p><p>
        <span class="guilabel">Routine group</span> and
        <span class="guilabel">Privileges</span> tabs appear at the bottom of the
        routine editor. Navigate between different tabs using the mouse
        or from the keyboard by pressing
        <span><strong class="keycap">Control+Alt+Tab</strong></span>.
      </p><div class="section" lang="en"><div class="titlepage"><div><div><h6 class="title"><a name="wb-routine-groups-tab"></a>7.7.4.2.3.1. The Routine Groups Tab</h6></div></div></div><p>
          Use the <span class="guilabel">Routine Groups</span> tab of the routine
          groups editor to perform the following tasks:
        </p><div class="itemizedlist"><ul type="disc"><li><p>
              Rename the routine group using the
              <span class="guilabel">Name</span> field.
            </p></li><li><p>
              Add routines to the group by dragging and dropping them.
            </p></li><li><p>
              Add comments to the routine group.
            </p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h6 class="title"><a name="wb-routine-groups-editor-privileges"></a>7.7.4.2.3.2. The Privileges Tab</h6></div></div></div><p>
          The <span class="guilabel">Privileges</span> tab of the routine group
          editor functions in exactly the same way as the
          <span class="guilabel">Privileges</span> tab of the table editor. For
          more information, see
          <a href="wb-table-editor.html#wb-table-editor-privileges-tab" title="7.7.1.3.10. The Privileges Tab">Section 7.7.1.3.10, “The Privileges Tab”</a>.

          </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
              Privileges are available only in the Standard Edition of
              MySQL Workbench.
            </p></div><p>
        </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h6 class="title"><a name="wb-modifying-routine"></a>7.7.4.2.3.3. Modifying a Routine Group Using the Properties Palette</h6></div></div></div><p>
          When you select a routine group on the EER Diagram canvas, its
          properties are displayed in the <code class="literal">Properties</code>
          palette. All of the properties accessible from the
          <code class="literal">Properties</code> palette apply to the appearance
          of a routine group on the EER Diagram canvas.
        </p><p>
          For a list of properties accessible through the
          <code class="literal">Properties</code> palette, see
          <a href="wb-properties-palette.html" title="7.5.12. The Properties Palette">Section 7.5.12, “The Properties Palette”</a>.
        </p></div></div></div></body></html>


path: /wb-html-guitools/changes-5.2.x.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1. Changes in Release 5.2</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-change-history.html" title="Appendix A. MySQL Workbench Change History"><link rel="prev" href="wb-change-history.html" title="Appendix A. MySQL Workbench Change History"><link rel="next" href="wb-news-5-2-37.html" title="A.1.1. Changes in MySQL Workbench 5.2.37 (Not yet released)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="changes-5.2.x"></a>A.1. Changes in Release 5.2</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-news-5-2-37.html">A.1.1. Changes in MySQL Workbench 5.2.37 (Not yet released)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-36.html">A.1.2. Changes in MySQL Workbench 5.2.36 (Not yet released)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-35.html">A.1.3. Changes in MySQL Workbench 5.2.35 (23 September 2011)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-34.html">A.1.4. Changes in MySQL Workbench 5.2.34 (26 May 2011)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-33b.html">A.1.5. Changes in MySQL Workbench 5.2.33b (21 March 2011)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-33.html">A.1.6. Changes in MySQL Workbench 5.2.33 (11 March 2011)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-32.html">A.1.7. Changes in MySQL Workbench 5.2.32 (05 March 2011)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-31a.html">A.1.8. Changes in MySQL Workbench 5.2.31a (13 December 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-31.html">A.1.9. Changes in MySQL Workbench 5.2.31 (08 December 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-30.html">A.1.10. Changes in MySQL Workbench 5.2.30 (20 November 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-29.html">A.1.11. Changes in MySQL Workbench 5.2.29 (12 October 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-28.html">A.1.12. Changes in MySQL Workbench 5.2.28 (19 September 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-27.html">A.1.13. Changes in MySQL Workbench 5.2.27 (01 September 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-26.html">A.1.14. Changes in MySQL Workbench 5.2.26 (06 August 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-25.html">A.1.15. Changes in MySQL Workbench 5.2.25 (30 June 2010 General Availability)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-24.html">A.1.16. Changes in MySQL Workbench 5.2.24 (21 June 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-23.html">A.1.17. Changes in MySQL Workbench 5.2.23 (Internal release only)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-22.html">A.1.18. Changes in MySQL Workbench 5.2.22 (02 June 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-21.html">A.1.19. Changes in MySQL Workbench 5.2.21 (12 May 2010 Release Candidate)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-20.html">A.1.20. Changes in MySQL Workbench 5.2.20 (27 April 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-19.html">A.1.21. Changes in MySQL Workbench 5.2.19 (16 April 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-18.html">A.1.22. Changes in MySQL Workbench 5.2.18 (13 April 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-17.html">A.1.23. Changes in MySQL Workbench 5.2.17 (02 April 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-16.html">A.1.24. Changes in MySQL Workbench 5.2.16 (17 February 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-15.html">A.1.25. Changes in MySQL Workbench 5.2.15 (28 January 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-14.html">A.1.26. Changes in MySQL Workbench 5.2.14 (21 January 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-13.html">A.1.27. Changes in MySQL Workbench 5.2.13 (Not released)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-12.html">A.1.28. Changes in MySQL Workbench 5.2.12 (Not released)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-11.html">A.1.29. Changes in MySQL Workbench 5.2.11 (18 December 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-10.html">A.1.30. Changes in MySQL Workbench 5.2.10 (01 December 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-9.html">A.1.31. Changes in MySQL Workbench 5.2.9 (Internal release only)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-8.html">A.1.32. Changes in MySQL Workbench 5.2.8 (18 November 2009 Beta)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-7.html">A.1.33. Changes in MySQL Workbench 5.2.7 (Internal release only)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-6.html">A.1.34. Changes in MySQL Workbench 5.2.6 (21 October 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-5.html">A.1.35. Changes in MySQL Workbench 5.2.5 (Internal Release Only)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-4.html">A.1.36. Changes in MySQL Workbench 5.2.4 (07 October 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-3.html">A.1.37. Changes in MySQL Workbench 5.2.3 (15 September 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-2.html">A.1.38. Changes in MySQL Workbench 5.2.2 (27 July 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-1.html">A.1.39. Changes in MySQL Workbench 5.2.1 (22 May 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-0.html">A.1.40. Changes in MySQL Workbench 5.2.0 (30 April 2009 Alpha)</a></span></dt></dl></div></div></body></html>


path: /wb-html-guitools/license-bitstream-vera.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>B.2. Bitstream Vera License</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-third-party-licenses.html" title="Appendix B. Third Party Licenses"><link rel="prev" href="license-flat-tab-control.html" title="B.1. .NET Flat TabControl License"><link rel="next" href="license-boost.html" title="B.3. Boost Library License"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="license-bitstream-vera"></a>B.2. Bitstream Vera License</h2></div></div></div><p>
    The following software may be included in this product:
  </p><pre class="programlisting">Bitstream Vera

Copyright (c) 2003 by Bitstream, Inc. All Rights Reserved. Bitstream Vera is a trademark
of Bitstream, Inc. 

Permission is hereby granted, free of charge, to any 
person obtaining a copy of the fonts accompanying this 
license ("Fonts") and associated documentation files 
(the "Font Software"), to reproduce and distribute the 
Font Software, including without limitation the rights 
to use, copy, merge, publish, distribute, and/or sell 
copies of the Font Software, and to permit persons to 
whom the Font Software is furnished to do so, subject 
to the following conditions: 

The above copyright and trademark notices and this 
permission notice shall be included in all copies of 
one or more of the Font Software typefaces.

The Font Software may be modified, altered, or added 
to, and in particular the designs of glyphs or characters 
in the Fonts may be modified and additional glyphs or 
characters may be added to the Fonts, only if the fonts 
are renamed to names not containing either the words 
"Bitstream" or the word "Vera".

This License becomes null and void to the extent 
applicable to Fonts or Font Software that has been 
modified and is distributed under the "Bitstream 
Vera" names. 

The Font Software may be sold as part of a larger 
software package but no copy of one or more of the 
Font Software typefaces may be sold by itself. 

THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT 
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING 
BUT NOT LIMITED TO ANY WARRANTIES OF MERCHANTABILITY, 
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT 
OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN 
NO EVENT SHALL BITSTREAM OR THE GNOME FOUNDATION BE 
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, 
INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, 
OR CONSEQUENTIAL DAMAGES, WHETHER IN AN ACTION OF 
CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF 
THE USE OR INABILITY TO USE THE FONT SOFTWARE OR 
FROM OTHER DEALINGS IN THE FONT SOFTWARE. 

Except as contained in this notice, the names of Gnome, 
the Gnome Foundation, and Bitstream Inc., shall not 
be used in advertising or otherwise to promote the 
sale, use or other dealings in this Font Software 
without prior written authorization from the Gnome 
Foundation or Bitstream Inc., respectively. For 
further information, contact: fonts at gnome dot org.</pre></div></body></html>


path: /wb-html-guitools/license-scintilla-net.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>B.21. ScintillaNET License</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-third-party-licenses.html" title="Appendix B. Third Party Licenses"><link rel="prev" href="license-scintilla.html" title="B.20. Scintilla License"><link rel="next" href="license-tinyxml.html" title="B.22. TinyXML License"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="license-scintilla-net"></a>B.21. ScintillaNET License</h2></div></div></div><p>
    The following software may be included in this product:
  </p><pre class="programlisting">ScintillaNET

ScintillaNET is based on the Scintilla component by Neil Hodgson. 
ScintillaNET is released on this same license. 

The ScintillaNET bindings are Copyright 2002-2006 by Garrett Serack 

All Rights Reserved 

Permission to use, copy, modify, and distribute this 
software and its documentation for any purpose and 
without fee is hereby granted, provided that the above 
copyright notice appear in all copies and that both 
that copyright notice and this permission notice appear 
in supporting documentation. 

GARRETT SERACK AND ALL EMPLOYERS PAST AND PRESENT DISCLAIM 
ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL 
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO 
EVENT SHALL GARRETT SERACK AND ALL EMPLOYERS PAST AND PRESENT 
BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR 
ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR 
PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER 
TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE 
OR PERFORMANCE OF THIS SOFTWARE. 

The license for Scintilla is as follows:
----------------------------------------------------------- 
Copyright 1998-2006 by Neil Hodgson 

All Rights Reserved 

Permission to use, copy, modify, and distribute this 
software and its documentation for any purpose and 
without fee is hereby granted, provided that the above 
copyright notice appear in all copies and that both that 
copyright notice and this permission notice appear in 
supporting documentation. 

NEIL HODGSON DISCLAIMS ALL WARRANTIES WITH REGARD TO 
THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF 
MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL NEIL 
HODGSON BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL 
DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF 
USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, 
NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR 
IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.</pre></div></body></html>


path: /wb-html-guitools/wb-relationship-tools.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.7.2.1. Adding Foreign Key Relationships Using an EER Diagram</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-foreign-key-relationships.html" title="7.7.2. Creating Foreign Key Relationships"><link rel="prev" href="wb-foreign-key-relationships.html" title="7.7.2. Creating Foreign Key Relationships"><link rel="next" href="wb-relationship-editor.html" title="7.7.2.2. The Relationship Editor"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-relationship-tools"></a>7.7.2.1. Adding Foreign Key Relationships Using an EER Diagram</h4></div></div></div><p>
      The vertical toolbar on the left side of an EER Diagram has six
      foreign key tools:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <code class="literal">one-to-one non-identifying relationship</code>
        </p></li><li><p>
          <code class="literal">one-to-many non-identifying relationship</code>
        </p></li><li><p>
          <code class="literal">one-to-one identifying relationship</code>
        </p></li><li><p>
          <code class="literal">one-to-many identifying relationship</code>
        </p></li><li><p>
          <code class="literal">many-to-many identifying relationship</code>
        </p></li><li><p>
          <code class="literal">Place a Relationship Using Existing Columns</code>
        </p></li></ul></div><p>
      An identifying relationship is one where the child table cannot be
      uniquely identified without its parent. Typically this occurs
      where an intermediary table is created to resolve a many-to-many
      relationship. In such cases, the primary key is usually a
      composite key made up of the primary keys from the two original
      tables. An identifying relationship is indicated by a solid line
      between the tables and a nonidentifying relationship is indicated
      by a broken line.
    </p><p>
      Create or drag and drop the tables that you wish to connect.
      Ensure that there is a primary key in the table that will be on
      the “<span class="quote">one</span>” side of the relationship. Click on the
      appropriate tool for the type of relationship you wish to create.
      If you are creating a one-to-many relationship, first click the
      table that is on the “<span class="quote">many</span>” side of the relationship,
      then on the table containing the referenced key. This creates a
      column in the table on the many side of the relationship. The
      default name of this column is
      <em class="replaceable"><code>table_name_key_name</code></em> where the table
      name and the key name both refer to the table containing the
      referenced key.
    </p><p>
      When the many-to-many tool is active, double-clicking a table
      creates an associative table with a many-to-many relationship. For
      this tool to function there must be a primary key defined in the
      initial table.
    </p><p>
      Use the <span class="guimenu">Model</span> menu, <span class="guimenuitem">Menu
      Options</span> menu item to set a project-specific default
      name for the foreign key column (see
      <a href="wb-model-menu.html#wb-relationship-notation-menu" title="7.5.1.5.4. The Relationship Notation Submenu">Section 7.5.1.5.4, “The Relationship Notation Submenu”</a>). To change the
      global default, see <a href="wb-preferences-model.html" title="5.4.4. The Model Tab">Section 5.4.4, “The Model Tab”</a>.
    </p><p>
      To edit the properties of a foreign key, double-click anywhere on
      the connection line that joins the two tables. This opens the
      relationship editor.
    </p><p>
      Mousing over a relationship connector highlights the connector and
      the related keys as shown in the following figure. The
      <code class="literal">film</code> and the <code class="literal">film_actor</code>
      tables are related on the <code class="literal">film_id</code> field and
      these fields are highlighted in both tables. Since the
      <code class="literal">film_id</code> field is part of the primary key in the
      <code class="literal">film_actor</code> table, a solid line is used for the
      connector between the two tables.
    </p><div class="figure"><a name="wb-foreign-key-image"></a><p class="title"><b>Figure 7.11. The Relationship Connector</b></p><div class="mediaobject"><img src="images/wb-foreign-key.png" width="487" height="357" alt="The relationship connector"></div></div><p>
      If the placement of a connection's caption is not suitable, you
      can change its position by dragging it to a different location. If
      you have set a secondary caption, its position can also be
      changed. For more information about secondary captions, see
      <a href="wb-connection-properties.html" title="7.7.2.3. Connection Properties">Section 7.7.2.3, “Connection Properties”</a>. Where the notation
      style permits, <code class="literal">Classic</code> for example, the
      cardinality indicators can also be repositioned.
    </p><p>
      The relationship notation style in
      <a href="wb-relationship-tools.html#wb-foreign-key-image" title="Figure 7.11. The Relationship Connector">Figure 7.11, “The Relationship Connector”</a> is the default, crow's
      foot. You can change this if you are using a commercial version of
      MySQL Workbench. For more information, see
      <a href="wb-model-menu.html#wb-relationship-notation-menu" title="7.5.1.5.4. The Relationship Notation Submenu">Section 7.5.1.5.4, “The Relationship Notation Submenu”</a>.
    </p><p>
      You can select multiple connections by holding down the
      <span><strong class="keycap">Control</strong></span> key as you click a connection. This can
      be useful for highlighting specific relationships on an EER
      diagram.
    </p></div></body></html>


path: /wb-html-guitools/wb-reference-relationship-tools.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.6.1.10. The Relationship Tools</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-vertical-toolbar.html" title="7.6.1. The Vertical Toolbar"><link rel="prev" href="wb-routine-group-tool.html" title="7.6.1.9. The Routine Group Tool"><link rel="next" href="wb-working-with-models.html" title="7.7. Working with Models"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-reference-relationship-tools"></a>7.6.1.10. The Relationship Tools</h4></div></div></div><p>
        The five relationship tools are used to represent the following
        relationships:
      </p><div class="itemizedlist"><ul type="disc"><li><p>
            One-to-many nonidentifying relationships
          </p></li><li><p>
            One-to-one nonidentifying relationships
          </p></li><li><p>
            One-to-many identifying relationships
          </p></li><li><p>
            One-to-one identifying relationships
          </p></li><li><p>
            Many-to-many identifying relationships
          </p></li></ul></div><p>
        These tools appear at the bottom of the vertical tool bar. Hover
        the mouse pointer over each tool to see a text hint that
        describes its function.
      </p><p>
        For more information about relationships, see
        <a href="wb-foreign-key-relationships.html" title="7.7.2. Creating Foreign Key Relationships">Section 7.7.2, “Creating Foreign Key Relationships”</a>.
      </p></div></body></html>


path: /wb-html-guitools/wb-news-5-2-5.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.35. Changes in MySQL Workbench 5.2.5 (Internal Release Only)</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="changes-5.2.x.html" title="A.1. Changes in Release 5.2"><link rel="prev" href="wb-news-5-2-6.html" title="A.1.34. Changes in MySQL Workbench 5.2.6 (21 October 2009)"><link rel="next" href="wb-news-5-2-4.html" title="A.1.36. Changes in MySQL Workbench 5.2.4 (07 October 2009)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-news-5-2-5"></a>A.1.35. Changes in MySQL Workbench 5.2.5 (Internal Release Only)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.2.4.
      </p><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        The following exception was generated when closing the
        <span class="guilabel">Relationship</span> tab for an EER Diagram:
      </p><pre class="programlisting">
System.NullReferenceException: Referência de objeto não definida para uma instância de
um objeto.
   em MySQL.GUI.Workbench.MainForm.mainDockPanel_ActiveDocumentClosing(Object sender,
ActiveDocumentClosingEventArgs e)
   em
WeifenLuo.WinFormsUI.Docking.DockPanel.OnActiveDocumentClosing(ActiveDocumentClosingEventA
rgs e)
   em WeifenLuo.WinFormsUI.Docking.DockPane.CloseContent(IDockContent content)
   em WeifenLuo.WinFormsUI.Docking.DockPane.CloseActiveContent()
   em WeifenLuo.WinFormsUI.Docking.VS2005DockPaneStrip.Close_Click(Object sender,
EventArgs e)
   em System.Windows.Forms.Control.OnClick(EventArgs e)
   em System.Windows.Forms.Control.WmMouseUp(Message&amp; m, MouseButtons button, Int32
clicks)
   em System.Windows.Forms.Control.WndProc(Message&amp; m)
   em System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message&amp; m)
   em System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message&amp; m)
   em System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam,
IntPtr lparam)
</pre><p>(Bug #47958)</p></li><li><p>
        When attempting to run MySQL Workbench, the splash screen appeared
        and then the application immediately crashed, generating the
        “<span class="quote">Send error report to Microsoft</span>” dialog. On
        debugging it was found that MySQL Workbench was throwing a
        <code class="literal">TypeLoadException</code>:
      </p><pre class="programlisting">Could not load type 'WeifenLuo.WinFormsUI.Docking.ActiveDocumentClosingEventArgs' from
assembly 'WeifenLuo.WinFormsUI.Docking, Version=2.2.3428.40956, Culture=neutral,
PublicKeyToken=null'.</pre><p>
        On inspection of the referenced assembly it was confirmed that
        there was no type
        <code class="literal">ActiveDocumentClosingEventArgs</code> defined.
       (Bug #47534, Bug #47480)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-model-reporting.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.11. The DBDoc Model Reporting Dialog Window (Commercial Version)</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-data-modeling.html" title="Chapter 7. Data Modeling"><link rel="prev" href="wb-mysql-validation.html" title="7.10.2. MySQL-Specific Validation"><link rel="next" href="dbdoc-templates.html" title="7.12. Customizing DBDoc Model Reporting Templates"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="wb-model-reporting"></a>7.11. The DBDoc Model Reporting Dialog Window (Commercial Version)</h2></div></div></div><p>
    This dialog window is found by navigating to the
    <span class="guimenu">Model</span> menu and choosing the <span class="guimenu">DBDoc -
    Model Reporting...</span> item.
  </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
      The <span class="guimenuitem">DBDoc - Model Reporting...</span> item is
      not available in the MySQL Workbench OSS version.
    </p></div><p>
    Use this dialog window to set the options for creating documentation
    of your database models.
  </p><div class="figure"><a name="wb-dbdoc-wizard-main-detailed-frames"></a><p class="title"><b>Figure 7.46. The DBDoc Model Reporting Main Wizard</b></p><div class="mediaobject"><img src="images/wb-dbdoc-wizard-main-detailed-frames.png" width="680" height="650" alt="The DBDoc Model Reporting main wizard"></div></div><p>
    You can choose from four available templates:
  </p><div class="itemizedlist"><ul type="disc"><li><p>
        <code class="literal">HTML Basic Frames</code>: Model documentation in
        HTML format that makes use of frames
      </p></li><li><p>
        <code class="literal">HTML Basic Single Page</code>: Single Page HTML
        documentation, not using frames
      </p></li><li><p>
        <code class="literal">HTML Detailed Frames</code>: Detailed HTML
        documentation, using frames
      </p></li><li><p>
        <code class="literal">Text Basic</code>: Text file documentation
      </p></li></ul></div><p>
    When you click a template, a preview image displays on the right
    side of the page. For the <code class="literal">HTML Basic Frames</code>
    template, you can select either the <code class="literal">Colorful</code> or
    the <code class="literal">Restrained Colors</code> option from the
    <span class="guilabel">Style</span> list. The <code class="literal">HTML Basic Single
    Page</code> template offers only the <code class="literal">Colorful</code>
    style. The <code class="literal">HTML Detailed Frames</code> template offers
    the <code class="literal">Vibrant</code> style, and also the more subdued
    <code class="literal">Coated</code> style. The <code class="literal">Text Basic</code>
    template offers only the <code class="literal">Fixed Size Font</code> style.
  </p><p>
    From the <span class="guilabel">Base Options</span> frame choose the report
    title and the output directory for the report files.
  </p><p>
    As of MySQL Workbench 5.1.17, it is possible to specify variables in the
    output path:
  </p><div class="itemizedlist"><ul type="disc"><li><p>
        <span class="bold"><strong>~</strong></span>: The user's home directory.
        Available on Linux and Mac OS X versions only.
      </p></li><li><p>
        <span class="bold"><strong>%desktopfolder%</strong></span>: The user's
        desktop.
      </p></li><li><p>
        <span class="bold"><strong>%documentsfolder%</strong></span>: The user's
        Documents folders. The following table shows typical values for
        various platforms.
      </p><div class="informaltable"><table border="1"><colgroup><col><col></colgroup><thead><tr><th>Platform</th><th>Typical Default Documents Folder</th></tr></thead><tbody><tr><td>Windows</td><td><code class="filename">C:\Documents and
                Settings\<em class="replaceable"><code>user_name</code></em>\My
                Documents</code></td></tr><tr><td>Linux</td><td><code class="filename">~/Documents</code></td></tr><tr><td>Mac OS X</td><td><code class="filename">Users/<em class="replaceable"><code>user_name</code></em>/Documents</code></td></tr></tbody></table></div></li><li><p>
        <span class="bold"><strong>%date%</strong></span>: The date in the format
        YYYY-MM-DD.
      </p></li><li><p>
        <span class="bold"><strong>%time%</strong></span>: The time in the format
        HHMM.
      </p></li><li><p>
        <span class="bold"><strong>%year%</strong></span>: The year in the format
        YYYY.
      </p></li><li><p>
        <span class="bold"><strong>%month%</strong></span>: The month in the
        format MM. January is 01 and December is 12.
      </p></li><li><p>
        <span class="bold"><strong>%monthname%</strong></span>: The name of the
        month, rather than the number.
      </p></li><li><p>
        <span class="bold"><strong>%day%</strong></span>: The day number in the
        format DD. For example, the 12th would be 12.
      </p></li></ul></div><p>
    Content options can also be set:
  </p><div class="itemizedlist"><ul type="disc"><li><p>
        <code class="literal">Render Table Columns</code>: Display all the
        columns.
      </p></li><li><p>
        <code class="literal">Render Table Indices</code>: Display all the
        indexes.
      </p></li><li><p>
        <code class="literal">Render Foreign Keys</code>: Display all the foreign
        keys.
      </p></li><li><p>
        <code class="literal">List Foreign Keys that refer to that table</code>:
        Display the tables that foreign keys reference.
      </p></li></ul></div><p>
    Clicking the <span class="guibutton">Finish</span> button creates the
    directory defined in the <span class="guilabel">Output directory</span> text
    box. If you chose to create <code class="literal">HTML Basic Frames</code>,
    you will find the following files in this directory:
  </p><div class="itemizedlist"><ul type="disc"><li><p>
        <code class="filename">basic.css</code>: The style sheet for the
        <code class="filename">overview.html</code> page.
      </p></li><li><p>
        <code class="filename">index.html</code>: The main page.
      </p></li><li><p>
        <code class="filename">overview.html</code>: The model overview, the
        navigation links shown in the sidebar.
      </p></li><li><p>
        <code class="filename">restrained.css</code>: The CSS file used if the
        <code class="literal">Restrained Colors</code> style option was chosen.
      </p></li><li><p>
        <code class="filename">table_details.html</code>: The main frame of the
        model report.
      </p></li></ul></div><p>
    Choosing the <code class="literal">HTML Basic Single Page</code> option
    creates a style sheet and an <code class="filename">index.html</code> file.
  </p><p>
    Choosing the <code class="literal">HTML Detailed Frames</code> option creates
    the following files:
  </p><div class="itemizedlist"><ul type="disc"><li><p>
        <code class="filename">basic.css</code>: The style sheet for the
        <code class="filename">overview.html</code> page. This is used if the
        <code class="literal">vibrant</code> style is chosen.
      </p></li><li><p>
        <code class="filename">coated.css</code>: The CSS file used if the
        <code class="literal">Coated</code> style option was chosen.
      </p></li><li><p>
        <code class="filename">details_list.html</code>: A Schema overview along
        with details of columns, indexes and foreign keys for each
        schema.
      </p></li><li><p>
        <code class="filename">full_list.html</code>: List of all columns and
        indexes for the schema.
      </p></li><li><p>
        <code class="filename">index.html</code>: The main page.
      </p></li><li><p>
        <code class="filename">overview.html</code>: Overview information for the
        report such as report title, project name and author.
      </p></li><li><p>
        <code class="filename">overview_list.html</code>: A summary of schema in
        the model along with a list of tables contained in each schema.
      </p></li><li><p>
        <code class="filename">table_details.html</code>: The main report
        details.
      </p></li><li><p>
        <code class="filename">top.html</code>: The top frame of the report.
      </p></li></ul></div><p>
    Choosing the <code class="literal">Text Basic</code> option creates a
    directory containing one text file.
  </p><p>
    You can click <code class="filename">index.html</code> to view a report. The
    following screenshot shows the <code class="literal">HTML Detailed
    Frames</code> report being displayed:
  </p><div class="figure"><a name="wb-dbdoc-detailed-report-schema"></a><p class="title"><b>Figure 7.47. The DBDoc Model Report</b></p><div class="mediaobject"><img src="images/wb-dbdoc-detailed-report-schema.png" width="1152" height="862" alt="The DBDoc Model Report"></div></div><p>
    If you wish to create custom templates please refer to
    <a href="dbdoc-templates.html" title="7.12. Customizing DBDoc Model Reporting Templates">Section 7.12, “Customizing DBDoc Model Reporting Templates”</a>.
  </p></div></body></html>


path: /wb-html-guitools/wb-exploring-scripting-shell.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>9.5.1. Exploring the Workbench Scripting Shell</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-scripting-shell.html" title="9.5. The Workbench Scripting Shell"><link rel="prev" href="wb-scripting-shell.html" title="9.5. The Workbench Scripting Shell"><link rel="next" href="wb-scripting-shell-window.html" title="9.5.2. The Shell Window"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-exploring-scripting-shell"></a>9.5.1. Exploring the Workbench Scripting Shell</h3></div></div></div><p>
        To open the Workbench Scripting Shell, select <span class="guimenu">Scripting</span>,
        <span class="guimenuitem">Scripting Shell</span> from the main menu.
        You can also open the Workbench Scripting Shell using the
        <span><strong class="keycap">Control+F3</strong></span> key combination on Windows and
        Linux, <span><strong class="keycap">Command+F3</strong></span> on Mac OS X, or by clicking
        the shell button above the EER diagram navigator. The Workbench Scripting Shell
        will then open in a new dialog.
      </p><p>
        The following screenshot shows the Workbench Scripting Shell dialog.
      </p><div class="figure"><a name="wb-scripting-shell-console"></a><p class="title"><b>Figure 9.1. The Workbench Scripting Shell</b></p><div class="mediaobject"><img src="images/wb-scripting-shell.png" width="798" height="598" alt="The Workbench Scripting Shell"></div></div></div></body></html>


path: /wb-html-guitools/wb-news-5-2-0.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.40. Changes in MySQL Workbench 5.2.0 (30 April 2009 Alpha)</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="changes-5.2.x.html" title="A.1. Changes in Release 5.2"><link rel="prev" href="wb-news-5-2-1.html" title="A.1.39. Changes in MySQL Workbench 5.2.1 (22 May 2009)"><link rel="next" href="changes-5.1.x.html" title="A.2. Changes in Release 5.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-news-5-2-0"></a>A.1.40. Changes in MySQL Workbench 5.2.0 (30 April 2009 Alpha)</h3></div></div></div><p>
        This is the first alpha release of 5.2.0.
      </p><p>This section has no changelog entries.</p></div></body></html>


path: /wb-html-guitools/wb-manage-server-variables-tab.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>8.7.5. The Variables Tab</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-server-administration-configuration.html" title="8.7. Server Administration and Configuration"><link rel="prev" href="wb-manage-server-connections-tab.html" title="8.7.4. The Connections Tab"><link rel="next" href="wb-manage-server-data-dump-tab.html" title="8.7.6. The Data Dump Tab"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-manage-server-variables-tab"></a>8.7.5. The Variables Tab</h3></div></div></div><p>
        The Variables tab displays a list of all server and status
        variables.
      </p><div class="figure"><a name="wb-manage-server-variables-tab-screenshot"></a><p class="title"><b>Figure 8.8. Administrator - Variables Tab</b></p><div class="mediaobject"><img src="images/wb-manage-server-variables-tab.png" width="1024" height="707" alt="Administrator - Variables Tab"></div></div></div></body></html>


path: /wb-html-guitools/wb-change-history.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Appendix A. MySQL Workbench Change History</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="index.html" title="MySQL Workbench"><link rel="prev" href="workbench-faq.html" title="Chapter 11. MySQL Workbench FAQ"><link rel="next" href="changes-5.2.x.html" title="A.1. Changes in Release 5.2"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="appendix" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="wb-change-history"></a>Appendix A. MySQL Workbench Change History</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="changes-5.2.x.html">A.1. Changes in Release 5.2</a></span></dt><dd><dl><dt><span class="section"><a href="wb-news-5-2-37.html">A.1.1. Changes in MySQL Workbench 5.2.37 (Not yet released)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-36.html">A.1.2. Changes in MySQL Workbench 5.2.36 (Not yet released)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-35.html">A.1.3. Changes in MySQL Workbench 5.2.35 (23 September 2011)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-34.html">A.1.4. Changes in MySQL Workbench 5.2.34 (26 May 2011)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-33b.html">A.1.5. Changes in MySQL Workbench 5.2.33b (21 March 2011)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-33.html">A.1.6. Changes in MySQL Workbench 5.2.33 (11 March 2011)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-32.html">A.1.7. Changes in MySQL Workbench 5.2.32 (05 March 2011)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-31a.html">A.1.8. Changes in MySQL Workbench 5.2.31a (13 December 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-31.html">A.1.9. Changes in MySQL Workbench 5.2.31 (08 December 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-30.html">A.1.10. Changes in MySQL Workbench 5.2.30 (20 November 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-29.html">A.1.11. Changes in MySQL Workbench 5.2.29 (12 October 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-28.html">A.1.12. Changes in MySQL Workbench 5.2.28 (19 September 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-27.html">A.1.13. Changes in MySQL Workbench 5.2.27 (01 September 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-26.html">A.1.14. Changes in MySQL Workbench 5.2.26 (06 August 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-25.html">A.1.15. Changes in MySQL Workbench 5.2.25 (30 June 2010 General Availability)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-24.html">A.1.16. Changes in MySQL Workbench 5.2.24 (21 June 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-23.html">A.1.17. Changes in MySQL Workbench 5.2.23 (Internal release only)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-22.html">A.1.18. Changes in MySQL Workbench 5.2.22 (02 June 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-21.html">A.1.19. Changes in MySQL Workbench 5.2.21 (12 May 2010 Release Candidate)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-20.html">A.1.20. Changes in MySQL Workbench 5.2.20 (27 April 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-19.html">A.1.21. Changes in MySQL Workbench 5.2.19 (16 April 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-18.html">A.1.22. Changes in MySQL Workbench 5.2.18 (13 April 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-17.html">A.1.23. Changes in MySQL Workbench 5.2.17 (02 April 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-16.html">A.1.24. Changes in MySQL Workbench 5.2.16 (17 February 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-15.html">A.1.25. Changes in MySQL Workbench 5.2.15 (28 January 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-14.html">A.1.26. Changes in MySQL Workbench 5.2.14 (21 January 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-13.html">A.1.27. Changes in MySQL Workbench 5.2.13 (Not released)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-12.html">A.1.28. Changes in MySQL Workbench 5.2.12 (Not released)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-11.html">A.1.29. Changes in MySQL Workbench 5.2.11 (18 December 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-10.html">A.1.30. Changes in MySQL Workbench 5.2.10 (01 December 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-9.html">A.1.31. Changes in MySQL Workbench 5.2.9 (Internal release only)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-8.html">A.1.32. Changes in MySQL Workbench 5.2.8 (18 November 2009 Beta)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-7.html">A.1.33. Changes in MySQL Workbench 5.2.7 (Internal release only)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-6.html">A.1.34. Changes in MySQL Workbench 5.2.6 (21 October 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-5.html">A.1.35. Changes in MySQL Workbench 5.2.5 (Internal Release Only)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-4.html">A.1.36. Changes in MySQL Workbench 5.2.4 (07 October 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-3.html">A.1.37. Changes in MySQL Workbench 5.2.3 (15 September 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-2.html">A.1.38. Changes in MySQL Workbench 5.2.2 (27 July 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-1.html">A.1.39. Changes in MySQL Workbench 5.2.1 (22 May 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-0.html">A.1.40. Changes in MySQL Workbench 5.2.0 (30 April 2009 Alpha)</a></span></dt></dl></dd><dt><span class="section"><a href="changes-5.1.x.html">A.2. Changes in Release 5.1</a></span></dt><dd><dl><dt><span class="section"><a href="wb-news-5-1-19.html">A.2.1. Changes in MySQL Workbench 5.1.19 (06 September 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-18.html">A.2.2. Changes in MySQL Workbench 5.1.18 (03 September 2009 General Availability)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-17.html">A.2.3. Changes in MySQL Workbench 5.1.17 (14 August 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-16.html">A.2.4. Changes in MySQL Workbench 5.1.16 (30 June 2009 General Availability)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-15.html">A.2.5. Changes in MySQL Workbench 5.1.15 (26 June 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-14.html">A.2.6. Changes in MySQL Workbench 5.1.14 (19 June 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-13.html">A.2.7. Changes in MySQL Workbench 5.1.13 (12 June 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-12.html">A.2.8. Changes in MySQL Workbench 5.1.12 (27 April 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-11.html">A.2.9. Changes in MySQL Workbench 5.1.11 (Not yet released)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-10.html">A.2.10. Changes in MySQL Workbench 5.1.10 (10 April 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-9.html">A.2.11. Changes in MySQL Workbench 5.1.9 (Not yet released Beta)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-8.html">A.2.12. Changes in MySQL Workbench 5.1.8 (Not yet released)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-7.html">A.2.13. Changes in MySQL Workbench 5.1.7 (Not yet released)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-6.html">A.2.14. Changes in MySQL Workbench 5.1.6 (Not yet released)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-4.html">A.2.15. Changes in MySQL Workbench 5.1.4 (Not yet released)</a></span></dt></dl></dd><dt><span class="section"><a href="changes-5.0.x.html">A.3. Changes in Release 5.0</a></span></dt><dd><dl><dt><span class="section"><a href="wb-news-5-0-30.html">A.3.1. Changes in MySQL Workbench 5.0.30 (18 February 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-29.html">A.3.2. Changes in MySQL Workbench 5.0.29 (12 December 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-28.html">A.3.3. Changes in MySQL Workbench 5.0.28 (06 December 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-27.html">A.3.4. Changes in MySQL Workbench 5.0.27 (07 November 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-26.html">A.3.5. Changes in MySQL Workbench 5.0.26 (16 October 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-25.html">A.3.6. Changes in MySQL Workbench 5.0.25 (12 September 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-24.html">A.3.7. Changes in MySQL Workbench 5.0.24 (12 August 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-23.html">A.3.8. Changes in MySQL Workbench 5.0.23 (25 June 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-22.html">A.3.9. Changes in MySQL Workbench 5.0.22 (27 May 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-21.html">A.3.10. Changes in MySQL Workbench 5.0.21 (27 April 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-20.html">A.3.11. Changes in MySQL Workbench 5.0.20 (26 April 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-19.html">A.3.12. Changes in MySQL Workbench 5.0.19 (15 April 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-18.html">A.3.13. Changes in MySQL Workbench 5.0.18rc (not released)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-17.html">A.3.14. Changes in MySQL Workbench 5.0.17rc (07 April 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-16.html">A.3.15. Changes in MySQL Workbench 5.0.16rc (26 March 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-15.html">A.3.16. Changes in MySQL Workbench 5.0.15rc (17 March 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-14a.html">A.3.17. Changes in MySQL Workbench 5.0.14abeta (28 February 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-14.html">A.3.18. Changes in MySQL Workbench 5.0.14beta (25 February 2008)</a></span></dt></dl></dd></dl></div><p>
    The following sections outline the changes between versions for
    MySQL Workbench.
  </p></div></body></html>


path: /wb-html-guitools/license-gnu-lgpl-2-1.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>B.11. GNU Lesser General Public License Version 2.1, February 1999</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-third-party-licenses.html" title="Appendix B. Third Party Licenses"><link rel="prev" href="license-glitz.html" title="B.10. Glitz License"><link rel="next" href="license-html-renderer.html" title="B.12. HtmlRenderer (System.Drawing.Html)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="license-gnu-lgpl-2-1"></a>B.11. GNU Lesser General Public License Version 2.1, February 1999</h2></div></div></div><pre class="programlisting">The following applies to all products licensed under the 
GNU Lesser General Public License, Version 2.1: You may 
not use the identified files except in compliance with 
the GNU Lesser General Public License, Version 2.1 (the 
"License"). You may obtain a copy of the License at
http://www.gnu.org/licenses/lgpl-2.1.html. A copy of the 
license is also reproduced below. Unless required by 
applicable law or agreed to in writing, software distributed 
under the License is distributed on an "AS IS" BASIS, 
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express 
or implied. See the License for the specific language governing
permissions and limitations under the License.

                  GNU LESSER GENERAL PUBLIC LICENSE
                       Version 2.1, February 1999

 Copyright (C) 1991, 1999 Free Software Foundation, Inc.
 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA
 Everyone is permitted to copy and distribute verbatim copies
 of this license document, but changing it is not allowed.

[This is the first released version of the Lesser GPL.  It also counts
 as the successor of the GNU Library Public License, version 2, hence
 the version number 2.1.]

                            Preamble

  The licenses for most software are designed to take away your
freedom to share and change it.  By contrast, the GNU General Public
Licenses are intended to guarantee your freedom to share and change
free software--to make sure the software is free for all its users.

  This license, the Lesser General Public License, applies to some
specially designated software packages--typically libraries--of the
Free Software Foundation and other authors who decide to use it.  You
can use it too, but we suggest you first think carefully about whether
this license or the ordinary General Public License is the better
strategy to use in any particular case, based on the explanations below.

  When we speak of free software, we are referring to freedom of use,
not price.  Our General Public Licenses are designed to make sure that
you have the freedom to distribute copies of free software (and charge
for this service if you wish); that you receive source code or can get
it if you want it; that you can change the software and use pieces of
it in new free programs; and that you are informed that you can do
these things.

  To protect your rights, we need to make restrictions that forbid
distributors to deny you these rights or to ask you to surrender these
rights.  These restrictions translate to certain responsibilities for
you if you distribute copies of the library or if you modify it.

  For example, if you distribute copies of the library, whether gratis
or for a fee, you must give the recipients all the rights that we gave
you.  You must make sure that they, too, receive or can get the source
code.  If you link other code with the library, you must provide
complete object files to the recipients, so that they can relink them
with the library after making changes to the library and recompiling
it.  And you must show them these terms so they know their rights.

  We protect your rights with a two-step method: (1) we copyright the
library, and (2) we offer you this license, which gives you legal
permission to copy, distribute and/or modify the library.

  To protect each distributor, we want to make it very clear that
there is no warranty for the free library.  Also, if the library is
modified by someone else and passed on, the recipients should know
that what they have is not the original version, so that the original
author's reputation will not be affected by problems that might be
introduced by others.

  Finally, software patents pose a constant threat to the existence of
any free program.  We wish to make sure that a company cannot
effectively restrict the users of a free program by obtaining a
restrictive license from a patent holder.  Therefore, we insist that
any patent license obtained for a version of the library must be
consistent with the full freedom of use specified in this license.

  Most GNU software, including some libraries, is covered by the
ordinary GNU General Public License.  This license, the GNU Lesser
General Public License, applies to certain designated libraries, and
is quite different from the ordinary General Public License.  We use
this license for certain libraries in order to permit linking those
libraries into non-free programs.

  When a program is linked with a library, whether statically or using
a shared library, the combination of the two is legally speaking a
combined work, a derivative of the original library.  The ordinary
General Public License therefore permits such linking only if the
entire combination fits its criteria of freedom.  The Lesser General
Public License permits more lax criteria for linking other code with
the library.

  We call this license the "Lesser" General Public License because it
does Less to protect the user's freedom than the ordinary General
Public License.  It also provides other free software developers Less
of an advantage over competing non-free programs.  These disadvantages
are the reason we use the ordinary General Public License for many
libraries.  However, the Lesser license provides advantages in certain
special circumstances.

  For example, on rare occasions, there may be a special need to
encourage the widest possible use of a certain library, so that it
becomes a de-facto standard.  To achieve this, non-free programs 
must be allowed to use the library.  A more frequent case is that 
a free library does the same job as widely used non-free libraries.  
In this case, there is little to gain by limiting the free library 
to free software only, so we use the Lesser General Public License.

  In other cases, permission to use a particular library in non-free
programs enables a greater number of people to use a large body of
free software.  For example, permission to use the GNU C Library in
non-free programs enables many more people to use the whole GNU
operating system, as well as its variant, the GNU/Linux operating
system.

  Although the Lesser General Public License is Less protective of the
users' freedom, it does ensure that the user of a program that is
linked with the Library has the freedom and the wherewithal to run
that program using a modified version of the Library.

  The precise terms and conditions for copying, distribution and
modification follow.  Pay close attention to the difference between a
"work based on the library" and a "work that uses the library".  The
former contains code derived from the library, whereas the latter must
be combined with the library in order to run.

                  GNU LESSER GENERAL PUBLIC LICENSE
   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

  0. This License Agreement applies to any software library or other
program which contains a notice placed by the copyright holder or
other authorized party saying it may be distributed under the terms of
this Lesser General Public License (also called "this License").
Each licensee is addressed as "you".

  A "library" means a collection of software functions and/or data
prepared so as to be conveniently linked with application programs
(which use some of those functions and data) to form executables.

  The "Library", below, refers to any such software library or work
which has been distributed under these terms.  A "work based on the
Library" means either the Library or any derivative work under
copyright law: that is to say, a work containing the Library or a
portion of it, either verbatim or with modifications and/or translated
straightforwardly into another language.  (Hereinafter, translation is
included without limitation in the term "modification".)

  "Source code" for a work means the preferred form of the work for
making modifications to it.  For a library, complete source code means
all the source code for all modules it contains, plus any associated
interface definition files, plus the scripts used to control
compilation and installation of the library.

  Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope.  The act of
running a program using the Library is not restricted, and output from
such a program is covered only if its contents constitute a work based
on the Library (independent of the use of the Library in a tool for
writing it).  Whether that is true depends on what the Library does
and what the program that uses the Library does.

  1. You may copy and distribute verbatim copies of the Library's
complete source code as you receive it, in any medium, provided that
you conspicuously and appropriately publish on each copy an
appropriate copyright notice and disclaimer of warranty; keep intact
all the notices that refer to this License and to the absence of any
warranty; and distribute a copy of this License along with the
Library.

  You may charge a fee for the physical act of transferring a copy,
and you may at your option offer warranty protection in exchange for a
fee.

  2. You may modify your copy or copies of the Library or any portion
of it, thus forming a work based on the Library, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:

    a) The modified work must itself be a software library.

    b) You must cause the files modified to carry prominent notices
    stating that you changed the files and the date of any change.

    c) You must cause the whole of the work to be licensed at no
    charge to all third parties under the terms of this License.

    d) If a facility in the modified Library refers to a function or a
    table of data to be supplied by an application program that uses
    the facility, other than as an argument passed when the facility
    is invoked, then you must make a good faith effort to ensure that,
    in the event an application does not supply such function or
    table, the facility still operates, and performs whatever part of
    its purpose remains meaningful.

    (For example, a function in a library to compute square roots has
    a purpose that is entirely well-defined independent of the
    application.  Therefore, Subsection 2d requires that any
    application-supplied function or table used by this function must
    be optional: if the application does not supply it, the square
    root function must still compute square roots.)

These requirements apply to the modified work as a whole.  If
identifiable sections of that work are not derived from the Library,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works.  But when you
distribute the same sections as part of a whole which is a work based
on the Library, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote
it.

Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Library.

In addition, mere aggregation of another work not based on the Library
with the Library (or with a work based on the Library) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.

  3. You may opt to apply the terms of the ordinary GNU General Public
License instead of this License to a given copy of the Library.  To do
this, you must alter all the notices that refer to this License, so
that they refer to the ordinary GNU General Public License, version 2,
instead of to this License.  (If a newer version than version 2 of the
ordinary GNU General Public License has appeared, then you can specify
that version instead if you wish.)  Do not make any other change in
these notices.

  Once this change is made in a given copy, it is irreversible for
that copy, so the ordinary GNU General Public License applies to all
subsequent copies and derivative works made from that copy.

  This option is useful when you wish to copy part of the code of
the Library into a program that is not a library.

  4. You may copy and distribute the Library (or a portion or
derivative of it, under Section 2) in object code or executable form
under the terms of Sections 1 and 2 above provided that you accompany
it with the complete corresponding machine-readable source code, which
must be distributed under the terms of Sections 1 and 2 above on a
medium customarily used for software interchange.

  If distribution of object code is made by offering access to copy
from a designated place, then offering equivalent access to copy the
source code from the same place satisfies the requirement to
distribute the source code, even though third parties are not
compelled to copy the source along with the object code.

  5. A program that contains no derivative of any portion of the
Library, but is designed to work with the Library by being compiled or
linked with it, is called a "work that uses the Library".  Such a
work, in isolation, is not a derivative work of the Library, and
therefore falls outside the scope of this License.

  However, linking a "work that uses the Library" with the Library
creates an executable that is a derivative of the Library (because it
contains portions of the Library), rather than a "work that uses the
library".  The executable is therefore covered by this License.
Section 6 states terms for distribution of such executables.

  When a "work that uses the Library" uses material from a header file
that is part of the Library, the object code for the work may be a
derivative work of the Library even though the source code is not.
Whether this is true is especially significant if the work can be
linked without the Library, or if the work is itself a library.  The
threshold for this to be true is not precisely defined by law.

  If such an object file uses only numerical parameters, data
structure layouts and accessors, and small macros and small inline
functions (ten lines or less in length), then the use of the object
file is unrestricted, regardless of whether it is legally a derivative
work.  (Executables containing this object code plus portions of the
Library will still fall under Section 6.)

  Otherwise, if the work is a derivative of the Library, you may
distribute the object code for the work under the terms of Section 6.
Any executables containing that work also fall under Section 6,
whether or not they are linked directly with the Library itself.

  6. As an exception to the Sections above, you may also combine or
link a "work that uses the Library" with the Library to produce a
work containing portions of the Library, and distribute that work
under terms of your choice, provided that the terms permit
modification of the work for the customer's own use and reverse
engineering for debugging such modifications.

  You must give prominent notice with each copy of the work that the
Library is used in it and that the Library and its use are covered by
this License.  You must supply a copy of this License.  If the work
during execution displays copyright notices, you must include the
copyright notice for the Library among them, as well as a reference
directing the user to the copy of this License.  Also, you must do one
of these things:

    a) Accompany the work with the complete corresponding
    machine-readable source code for the Library including whatever
    changes were used in the work (which must be distributed under
    Sections 1 and 2 above); and, if the work is an executable linked
    with the Library, with the complete machine-readable "work that
    uses the Library", as object code and/or source code, so that the
    user can modify the Library and then relink to produce a modified
    executable containing the modified Library.  (It is understood
    that the user who changes the contents of definitions files in the
    Library will not necessarily be able to recompile the application
    to use the modified definitions.)

    b) Use a suitable shared library mechanism for linking with the
    Library.  A suitable mechanism is one that (1) uses at run time a
    copy of the library already present on the user's computer system,
    rather than copying library functions into the executable, and (2)
    will operate properly with a modified version of the library, if
    the user installs one, as long as the modified version is
    interface-compatible with the version that the work was made with.

    c) Accompany the work with a written offer, valid for at
    least three years, to give the same user the materials
    specified in Subsection 6a, above, for a charge no more
    than the cost of performing this distribution.

    d) If distribution of the work is made by offering access to copy
    from a designated place, offer equivalent access to copy the above
    specified materials from the same place.

    e) Verify that the user has already received a copy of these
    materials or that you have already sent this user a copy.

  For an executable, the required form of the "work that uses the
Library" must include any data and utility programs needed for
reproducing the executable from it.  However, as a special exception,
the materials to be distributed need not include anything that is
normally distributed (in either source or binary form) with the major
components (compiler, kernel, and so on) of the operating system on
which the executable runs, unless that component itself accompanies
the executable.

  It may happen that this requirement contradicts the license
restrictions of other proprietary libraries that do not normally
accompany the operating system.  Such a contradiction means you cannot
use both them and the Library together in an executable that you
distribute.

  7. You may place library facilities that are a work based on the
Library side-by-side in a single library together with other library
facilities not covered by this License, and distribute such a combined
library, provided that the separate distribution of the work based on
the Library and of the other library facilities is otherwise
permitted, and provided that you do these two things:

    a) Accompany the combined library with a copy of the same work
    based on the Library, uncombined with any other library
    facilities.  This must be distributed under the terms of the
    Sections above.

    b) Give prominent notice with the combined library of the fact
    that part of it is a work based on the Library, and explaining
    where to find the accompanying uncombined form of the same work.

  8. You may not copy, modify, sublicense, link with, or distribute
the Library except as expressly provided under this License.  Any
attempt otherwise to copy, modify, sublicense, link with, or
distribute the Library is void, and will automatically terminate your
rights under this License.  However, parties who have received copies,
or rights, from you under this License will not have their licenses
terminated so long as such parties remain in full compliance.

  9. You are not required to accept this License, since you have not
signed it.  However, nothing else grants you permission to modify or
distribute the Library or its derivative works.  These actions are
prohibited by law if you do not accept this License.  Therefore, by
modifying or distributing the Library (or any work based on the
Library), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Library or works based on it.

  10. Each time you redistribute the Library (or any work based on the
Library), the recipient automatically receives a license from the
original licensor to copy, distribute, link with or modify the Library
subject to these terms and conditions.  You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties with
this License.

  11. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License.  If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Library at all.  For example, if a patent
license would not permit royalty-free redistribution of the Library by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Library.

If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended 
to apply, and the section as a whole is intended to apply in other
circumstances.

It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system which is
implemented by public license practices.  Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.

This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.

  12. If the distribution and/or use of the Library is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Library under this License 
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded.  In such case, this License incorporates
the limitation as if written in the body of this License.

  13. The Free Software Foundation may publish revised and/or new
versions of the Lesser General Public License from time to time.
Such new versions will be similar in spirit to the present version,
but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number.  If the Library
specifies a version number of this License which applies to it and
"any later version", you have the option of following the terms and
conditions either of that version or of any later version published by
the Free Software Foundation.  If the Library does not specify a
license version number, you may choose any version ever published by
the Free Software Foundation.

  14. If you wish to incorporate parts of the Library into other free
programs whose distribution conditions are incompatible with these,
write to the author to ask for permission.  For software which is
copyrighted by the Free Software Foundation, write to the Free
Software Foundation; we sometimes make exceptions for this.  Our
decision will be guided by the two goals of preserving the free status
of all derivatives of our free software and of promoting the sharing
and reuse of software generally.

                            NO WARRANTY

  15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
LIBRARY IS WITH YOU.  SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

  16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.

                     END OF TERMS AND CONDITIONS

           How to Apply These Terms to Your New Libraries

  If you develop a new library, and you want it to be of the greatest
possible use to the public, we recommend making it free software that
everyone can redistribute and change.  You can do so by permitting
redistribution under these terms (or, alternatively, under the terms 
of the ordinary General Public License).

  To apply these terms, attach the following notices to the library.
It is safest to attach them to the start of each source file to most
effectively convey the exclusion of warranty; and each file should 
have at least the "copyright" line and a pointer to where the full
notice is found.

    &lt;one line to give the library's name and a brief idea of what it does.&gt;
    Copyright (C) &lt;year&gt;  &lt;name of author&gt;

    This library is free software; you can redistribute it and/or
    modify it under the terms of the GNU Lesser General Public
    License as published by the Free Software Foundation; either
    version 2.1 of the License, or (at your option) any later version.

    This library is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
    Lesser General Public License for more details.

    You should have received a copy of the GNU Lesser General Public
    License along with this library; if not, write to the Free Software
    Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
    02110-1301  USA

Also add information on how to contact you by electronic and paper mail.

You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the library, if
necessary.  Here is a sample; alter the names:

  Yoyodyne, Inc., hereby disclaims all copyright interest in the
  library `Frob' (a library for tweaking knobs) written by James 
  Random Hacker.

  &lt;signature of Ty Coon&gt;, 1 April 1990
  Ty Coon, President of Vice

That's all there is to it!</pre></div></body></html>


path: /wb-html-guitools/wb-news-5-1-15.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.2.5. Changes in MySQL Workbench 5.1.15 (26 June 2009)</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="changes-5.1.x.html" title="A.2. Changes in Release 5.1"><link rel="prev" href="wb-news-5-1-16.html" title="A.2.4. Changes in MySQL Workbench 5.1.16 (30 June 2009 General Availability)"><link rel="next" href="wb-news-5-1-14.html" title="A.2.6. Changes in MySQL Workbench 5.1.14 (19 June 2009)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-news-5-1-15"></a>A.2.5. Changes in MySQL Workbench 5.1.15 (26 June 2009)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.1.14.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        A routine object was deleted if its code was removed from the
        routine group. This behavior has now been noted in the main
        documentation.
       (Bug #45738)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        Selecting <span class="guilabel">Database</span>, <span class="guilabel">Generate
        Catalog Diff Report</span> from the main menu caused
        MySQL Workbench to crash.
       (Bug #45652)</p></li><li><p>
        Generated INSERT statements did not have a database name.
      </p><p>
        The generated <code class="literal">INSERT</code> statements were at the
        end of the SQL output. However, there was no <code class="literal">USE
        database</code> statement before the group of inserts. The
        comment before the group of <code class="literal">INSERTS</code> did refer
        to the database table.
      </p><p>
        If you had multiple databases, this generated errors on import.
       (Bug #45642)</p></li><li><p>
        In the <span class="guilabel">Forward Engineer SQL Script</span> wizard,
        when the <span class="guibutton">Show Filter</span> button was clicked,
        the left hand panel containing database and table names was too
        narrow, especially if a long database name or table name was
        used. This made it hard to determine which tables to select.
       (Bug #45623)</p></li><li><p>
        The <span class="guimenu">File</span>, <span class="guimenu">Export</span>,
        <span class="guimenu">Forward Engineer SQL CREATE Script</span> wizard
        contained malfunctioning buttons. When prompted with the message
        “<span class="quote">Do you want to overwrite an existing .sql file?</span>”,
        the <span class="guibutton">Replace</span> and
        <span class="guibutton">Cancel</span> buttons had the reverse effect.
        Clicking <span class="guibutton">Replace</span> cancelled the action,
        whereas clicking <span class="guibutton">Cancel</span> proceeded to the
        next step.
       (Bug #45619)</p></li><li><p>
        In Ubuntu Linux, right-clicking any item in the
        <span class="guilabel">Catalog</span>, <span class="guilabel">Layers</span>,
        <span class="guilabel">User Types</span>, or <span class="guilabel">History</span>
        tabs, or other tabs typically docked in the right hand side of
        MySQL Workbench, did not display a context-sensitive menu.
       (Bug #44298)</p></li><li><p>
        MySQL Workbench <span class="guimenu">Syncronize Model</span> feature had
        unexpected behavior. For example, synchronizing the model with
        the live database would cause changes to the database, even if
        this was not desired. Also, if tables were dropped in the live
        database, and the model synchronized, the changes to the live
        database were not reflected in the model. Further, if a model
        was created and synchronized to an empty schema in the live
        database, when synchronization took place again, MySQL Workbench
        would indicate many changes were required, even if no changes
        had been made to the model or database.
       (Bug #42149)</p></li><li><p>
        Double-clicking a layer in the <span class="guilabel">Layers</span> tab
        did not select it in the EER Diagram canvas. However, other
        objects in the <span class="guilabel">Layers</span> tab could be selected
        on the EER Diagram canvas in this manner.
       (Bug #34938)</p></li><li><p>
        Right-clicking a relationship in the <span class="guilabel">EER
        Diagram</span> canvas, and selecting <span class="guimenu">Edit in New
        Window...</span> from the context-sensitive menu, had no
        effect.
       (Bug #34069)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-text-object-editor.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.7.7.2. The Text Object Editor</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-text-objects.html" title="7.7.7. Creating Text Objects"><link rel="prev" href="wb-using-text-object-tool.html" title="7.7.7.1. Adding Text Objects to an EER Diagram"><link rel="next" href="wb-images.html" title="7.7.8. Creating Images"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-text-object-editor"></a>7.7.7.2. The Text Object Editor</h4></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-text-object-editor.html#wb-modifying-text-object">7.7.7.2.1. Modifying a Text Object Using the <code class="literal">Properties</code> Palette</a></span></dt></dl></div><p>
      To invoke the text object editor, double-click a text object on
      the EER Diagram canvas. This opens the editor docked at the bottom
      of the application. Double-clicking the text object table undocks
      the editor. Double-click the title bar to redock it. Any number of
      text objects may be open at the same time. Each additional text
      objects appears as a tab at the top of the text editor.
    </p><p>
      Use the editor to change the name of a text object or its
      contents.
    </p><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="wb-modifying-text-object"></a>7.7.7.2.1. Modifying a Text Object Using the <code class="literal">Properties</code> Palette</h5></div></div></div><p>
        When you select a text object on the EER Diagram canvas, its
        properties are displayed in the <code class="literal">Properties</code>
        palette. Most of the properties accessible from the
        <code class="literal">Properties</code> palette apply to the appearance of
        a view on the EER Diagram canvas.
      </p><p>
        For a list of properties accessible through the
        <code class="literal">Properties</code> palette, see
        <a href="wb-properties-palette.html" title="7.5.12. The Properties Palette">Section 7.5.12, “The Properties Palette”</a>.
      </p><p>
        There is no property in the <code class="literal">Properties</code>
        palette for changing the font used by a text object. To do so,
        choose the <span class="guilabel">Appearance</span> tab of the Workbench
        Preferences dialog. For more information, see
        <a href="wb-preferences-appearance.html" title="5.4.7. The Appearance Tab">Section 5.4.7, “The Appearance Tab”</a>.
      </p></div></div></body></html>


path: /wb-html-guitools/wb-sql-editor-connection-information-panel.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>6.7.5.1. Connection Information Panel</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-sql-editor-sidebar.html" title="6.7.5. Sidebar"><link rel="prev" href="wb-sql-editor-sidebar.html" title="6.7.5. Sidebar"><link rel="next" href="wb-sql-editor-object-browser.html" title="6.7.5.2. Object Browser"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-sql-editor-connection-information-panel"></a>6.7.5.1. Connection Information Panel</h4></div></div></div><p>
          This panel summarizes the current connection to the server.
        </p><div class="figure"><a name="wb-sql-editor-connection-information-palette-screenshot"></a><p class="title"><b>Figure 6.13. SQL Editor - Connection Information Palette</b></p><div class="mediaobject"><img src="images/wb-sql-editor-connection-information-palette-screenshot.png" width="202" height="110" alt="SQL Editor - Connection Information
              Palette"></div></div></div></body></html>


path: /wb-html-guitools/wb-news-5-2-16.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.24. Changes in MySQL Workbench 5.2.16 (17 February 2010)</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="changes-5.2.x.html" title="A.1. Changes in Release 5.2"><link rel="prev" href="wb-news-5-2-17.html" title="A.1.23. Changes in MySQL Workbench 5.2.17 (02 April 2010)"><link rel="next" href="wb-news-5-2-15.html" title="A.1.25. Changes in MySQL Workbench 5.2.15 (28 January 2010)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-news-5-2-16"></a>A.1.24. Changes in MySQL Workbench 5.2.16 (17 February 2010)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.2.15.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        In the SQL editor, the keyboard shortcut to run a single query
        has been changed to <span><strong class="keycap">Control+Enter</strong></span>. To run all
        queries the keyboard shortcut has been changed to
        <span><strong class="keycap">Control+Shift+Enter</strong></span>.
       (Bug #50747)</p></li><li><p>
        The key sequence <span><strong class="keycap">Control+Q</strong></span> has been added as a
        shortcut for the main menu item <span class="guimenu">File</span>,
        <span class="guimenu">Exit</span>.
       (Bug #50727)</p></li><li><p>
        In the SQL Editor a comment has been added to the EDIT statement
        to clarify its functionality.
       (Bug #50705)</p></li><li><p>
        The <span class="guilabel">Manage DB Connections</span> dialog now
        prevents removal of a connection used by a server instance.
       (Bug #50547)</p></li><li><p>
        In the <span class="guilabel">Logs</span> tab of the Administrator it was
        not possible to view long queries, or copy their text.
        MySQL Workbench has been changed so that double-clicking an entry in
        the <span class="guilabel">Logs</span> tab pops up a dialog with the
        complete text, and also provides a <span class="guibutton">Copy
        Detail</span> button to copy the text of the entry.
       (Bug #49442)</p></li><li><p>
        The data dump facility, used for exporting data to disk, has
        been modified to enable the
        <code class="option">--single-transaction</code> option to be specified.
      </p><p>
        If <code class="option">--single-transaction</code> is enabled, the table
        selection will be restricted the following ways:
      </p><div class="itemizedlist"><ul type="circle"><li><p>
            If a single schema is selected, it is possible to
            select/deselect its tables as required.
          </p></li><li><p>
            If more than one schema is selected, all tables from these
            schemas must be selected because <span><strong class="command">mysqldump
            <code class="option">--databases</code></strong></span> will be used in this
            case.
          </p></li></ul></div><p>(Bug #49220)</p></li><li><p>
        When a model with multiple EER Diagrams was opened, all EER
        Diagrams would be displayed in tabs. This happened whether or
        not a EER Diagram had been displayed in a tab prior to saving
        the model.
      </p><p>
        MySQL Workbench has been changed so that the <span class="guilabel">EER
        Diagram</span> tab state is saved, so that when a model is
        opened, only those EER Diagram tabs that were open on save are
        restored. This prevents unnecessary cluttering of the interface.
       (Bug #44454, Bug #50732)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p><span class="bold"><strong>Security Fix</strong></span>: 
        Passwords were stored in plain text format in the file
        <code class="filename">server_instances.xml</code>.
      </p><p>
        To improve security MySQL Workbench has been changed in the
        following ways:
      </p><div class="itemizedlist"><ul type="circle"><li><p>
            The password is no longer stored in the connection XML file.
          </p></li><li><p>
            When a connection is opened, a password request dialog is
            displayed and the password requested. The password can
            optionally be stored in the system keychain/vault/keyring.
          </p></li><li><p>
            When editing a connection profile, you can also store the
            password in the system keychain.
          </p></li><li><p>
            For compatibility, when MySQL Workbench starts it will look for
            passwords stored in the XML file. If any password is found,
            it will be removed from the XML file and automatically
            stored in the keychain. When MySQL Workbench exits, the
            connections file will be free from passwords.
          </p></li></ul></div><p>(Bug #50194)</p></li><li><p>
        When using the <span class="guilabel">Server Administration</span> link,
        or <span class="guilabel">Manage Security</span> link, on the
        <span class="guilabel">Home</span> screen, to log in to a remote server
        through an SSH connection, if the password dialog was closed,
        and cancellation of the SSH connection dialog acknowledged, this
        exception was generated:
      </p><pre class="programlisting">Exception = System.Runtime.InteropServices.SEHException
Message = External component has thrown an exception.
FullText = System.Runtime.InteropServices.SEHException: External component has thrown an
exception.
   at MySQL.Forms.DrawBoxImpl.drawbox_mouse_click(Object sender, MouseEventArgs e)
...</pre><p>(Bug #51088)</p></li><li><p>
        In the <span class="guilabel">Create a new server instance</span> wizard,
        on the last page of the wizard if the
        <span class="guibutton">Back</span> button was pressed and then the
        <span class="guibutton">Next</span> button pressed, an error was
        generated stating the server instance already existed.
       (Bug #51060)</p></li><li><p>
        Using <span class="guimenu">File</span>, <span class="guimenu">Export</span>,
        <span class="guimenu">Forward Engineer ALTER Script</span> to export a
        model resulted in MySQL Workbench generating the exception
        <code class="literal">AccessViolationException</code>.
       (Bug #51053)</p></li><li><p>
        In the SQL Editor, if using the <span class="guilabel">Alter Table</span>
        dialog, attempting to apply changes after renaming an index
        resulted in this error:
      </p><pre class="programlisting">SQL Error 1091: Can't DROP 'username_foo'; check that column/key exists</pre><p>(Bug #50970)</p></li><li><p>
        In the <span class="guilabel">System Profile</span> tab of the
        <span class="guilabel">Manage Server Instances</span> dialog, if the
        <span class="guilabel">Path to configuration file</span> textfield was
        set using the browse button, <span class="guibutton">...</span>, the
        value in the textfield appeared to be set correctly to the
        selected file. However, if the dialog was closed and reopened,
        the new path was not displayed in the text field. If the path
        was manually entered, rather than using the browse button, the
        textfield would display the correct path even if the dialog was
        closed and reopened.
       (Bug #50965)</p></li><li><p>
        In the SQL Editor, if the <span class="guilabel">Edit Data</span> dialog
        was invoked for a table, and some data edited, MySQL Workbench
        crashed when the <span class="guibutton">Apply SQL</span> button was
        clicked.
       (Bug #50920)</p></li><li><p>
        An exported script containing triggers and views resulted in the
        error <code class="literal">#1046 - No database selected</code> when run
        on the MySQL Server. This was due to a missing <code class="literal">USE
        DATABASE</code> statement in the generated script.
       (Bug #50900)</p></li><li><p>
        The second invocation of <span class="guimenu">File</span>,
        <span class="guimenu">Print</span> caused MySQL Workbench to crash.
       (Bug #50885)</p></li><li><p>
        The SQL code editors used in the modeling functionality within
        MySQL Workbench, for example in the <span class="guilabel">Triggers</span>
        tab of the Table Editor, failed to identify and highlight SQL
        code errors.
       (Bug #50835)</p></li><li><p>
        In the SQL Editor the text “<span class="quote">Parsing SQL ...</span>”
        displayed in the status bar remained once the parsing was
        complete.
      </p><p>
        MySQL Workbench has been changed to display “<span class="quote">No errors
        found</span>” once parsing has successfully completed.
       (Bug #50833)</p></li><li><p>
        If a MySQL server was set to accept named pipe connections only,
        and then a server instance created in MySQL Workbench using a named
        pipe connection, it was not possible to subsequently connect to
        the server with MySQL Workbench.
       (Bug #50830)</p></li><li><p>
        Expanded Schemata Palettes in the SQL Editor would collapse when
        switching between SQL Editor tabs.
       (Bug #50815)</p></li><li><p>
        In the SQL Editor the toolbar button to execute SQL statements
        was missing.
      </p><p>
        MySQL Workbench also now includes a new toolbar button to execute a
        single statement.
       (Bug #50791)</p></li><li><p>
        In the MySQL Model tab, if the Table Editor was launched and
        then the Home screen tab clicked, MySQL Workbench displayed the
        MySQL Workbench <span class="guilabel">Unexpected Error</span> dialog.
       (Bug #50768)</p></li><li><p>
        On the MySQL Model page using Roles and Users to grant
        privileges to a schema resulted in errors when the model was
        forward engineered, and the resulting script applied against a
        MySQL server. The script failed due to invalid SQL syntax
        because the SQL created did not correctly apply the privileges
        to all schema objects.
       (Bug #50762)</p></li><li><p>
        In the <span class="guilabel">Data Dump</span> facility of the
        Administrator, attempting to export a schema to disk failed if a
        table name contained a space.
       (Bug #50728)</p></li><li><p>
        In the Workbench Scripting Shell dialog, clicking an item in the value inspector
        panel (lower left corner) caused an exception:
      </p><pre class="programlisting">System.Runtime.InteropServices.SEHException: External component has thrown an
exception.
   at MySQL.Grt.TreeModel.expand_node(NodeId node)
   at MySQL.Grt.GrtTreeModel.TreeViewExpanding(Object sender, TreeViewAdvEventArgs e)
   at System.EventHandler`1.Invoke(Object sender, TEventArgs e)
   at Aga.Controls.Tree.TreeViewAdv.OnExpanding(TreeNodeAdv node)
   ...</pre><p>(Bug #50683)</p></li><li><p>
        In the <span class="guilabel">Data Dump</span> facility of the
        Administrator it was not possible to import a file where the
        path contained a space.
       (Bug #50609, Bug #50007)</p></li><li><p>
        In the SQL Editor a situation occurred where all results tabs
        could not be closed. Further, results tabs were incorrectly
        created with the same label.
       (Bug #50334, Bug #50865)</p></li><li><p>
        In the <span class="guilabel">Manage DB Connections</span> dialog it was
        not possible to select a default schema for the Socket/Pipe
        connection type because this facility was not provided by the
        dialog user interface.
       (Bug #50283)</p></li><li><p>
        It was possible to connect to a database using a password
        containing a space. However, when this connection was used to
        attempt a backup the operation failed, due to the password not
        being correctly quoted.
       (Bug #50213)</p></li><li><p>
        The messages generated by <span><strong class="command">mysqldump</strong></span> when a
        data export operation failed were difficult to interpret, for
        example:
      </p><pre class="programlisting">Operation failed with exitcode 2</pre><p>(Bug #50137)</p></li><li><p>
        In the SQL Editor, when editing table data, if an operation
        failed when changes were applied, the error message was not
        clearly visible.
       (Bug #50112)</p></li><li><p>
        In the SQL Editor, if a <code class="literal">LONGTEXT</code> field was
        being edited in the table data live editor, when the changes
        were applied an error was generated.
      </p><p>
        MySQL Workbench has also been changed so that large text values need
        to be edited in an external editor and then pasted into the grid
        cell.
       (Bug #50111, Bug #50692, Bug #50948, Bug #50814)</p></li><li><p>
        When synchronizing a schema with a live server, the scale of
        columns with type <code class="literal">DECIMAL</code> was erroneously set
        to zero. For example, a <code class="literal">DECIMAL(17,5)</code> was
        found to be set to <code class="literal">DECIMAL (17,0)</code> in the
        generated script.
       (Bug #50110)</p></li><li><p>
        When a non-SSH server instance was created, and a connection
        made to a remote server, only the <span class="guilabel">Data Dump</span>
        facility of the Administrator was available. The same problem
        occurred if SSH-based administration was deselected for the
        server instance.
       (Bug #50098)</p></li><li><p>
        In the SQL Editor, if a database was selected in the
        <span class="guilabel">Overview</span> tab and then either the
        <span class="guimenu">Drop Schema...</span> context menu item was
        selected, or the drop schema toolbar button clicked, the DROP
        DATABASE dialog was displayed. However, if the dialog close
        button was then clicked to cancel the dialog, the database was
        still dropped, instead of being unaffected by the cancelling of
        the dialog.
       (Bug #50072, Bug #50960)</p></li><li><p>
        In the <span class="guilabel">Create a new server instance</span> wizard,
        if an operating system of type <span class="guilabel">Windows (MySQL 5.1
        Installer Package)</span> was selected, this error was
        generated on the <span class="guilabel">Test Settings</span> page:
      </p><pre class="programlisting">Error: File C:\Program Files\MySQL\MySQL Server 5.1\my.ini doesn't exist</pre><p>
        This was because the file was actually stored in
        <code class="filename">C:\Programas\MySQL\MySQL Server 5.1\my.ini</code>.
      </p><p>
        Similar bugs where the configuration file could not be found
        were reported on both English and non-English systems.
       (Bug #50050, Bug #50635, Bug #50966, Bug #50873, Bug #51008)</p></li><li><p>
        If a table was dropped from a live database, and then the model
        synchronized, the dropped table would be detected, but the table
        was not dropped from the model concerned.
       (Bug #50000)</p></li><li><p>
        For a default MySQL Server installation, no
        <code class="filename">my.ini</code> or <code class="filename">my.cnf</code> file
        is created. This proved problematic when creating a server
        instance in MySQL Workbench because the <span class="guilabel">Create a new
        server instance</span> wizard expected a configuration file
        to be specified. If the path to the configuration file was left
        blank, a model error dialog was displayed by the wizard. If
        alternatively, one of the standard locations for the
        configuration file was entered, problems arose when an attempt
        was made to subsequently change configuration values in the
        configuration section of the Admin screen. The problems included
        MySQL Workbench hanging, and repetitive requests for a 'super user'
        password.
       (Bug #49766, Bug #50317)</p></li><li><p>
        In the SQL Editor, in the add routine dialog, if the template
        was used, and a simple <code class="literal">SELECT 1;</code> statement
        added to the template, this error was generated when changes
        were applied:
      </p><pre class="programlisting">ERROR 1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 3
SQL Statement:
CREATE PROCEDURE `world`.`new_routine` ()
BEGIN
SELECT 1</pre><p>(Bug #49710)</p></li><li><p>
        In the <span class="guilabel">Forward Engineer SQL Script</span> wizard,
        selecting the check box <span class="guilabel">Omit Schema Qualifier in
        Object Names</span> caused the <code class="literal">CREATE
        SCHEMA</code> statement to be removed. <code class="literal">DROP
        SCHEMA</code> statements were also removed, even if the
        <span class="guilabel">Generate DROP SCHEMA</span> check box was
        selected.
      </p><p>
        MySQL Workbench has been changed so that if the <span class="guilabel">Omit
        Schema Qualifier in Object Names</span> check box is
        selected, it is possible to optionally select the check box
        <span class="guilabel">Insert USE Statements</span>, to enable or disable
        the use of <code class="literal">USE</code> statements.
       (Bug #49682)</p></li><li><p>
        If the <span class="guilabel">Data Dump</span> facility in Administrator
        was used to export to a self-contained file, then when that file
        was imported an unhandled exception was generated.
       (Bug #49529)</p></li><li><p>
        If the MySQL Server was stopped then attempting to access the
        <span class="guilabel">Logs</span>, <span class="guilabel">Accounts</span>,
        <span class="guilabel">Connections</span>, <span class="guilabel">Variables</span>
        or <span class="guilabel">Data Dump</span> tabs in the Administrator
        resulted in unhandled exceptions.
       (Bug #49439)</p></li><li><p>
        MySQL Workbench did not support SSH keys that required a passphrase
        to be entered.
       (Bug #49418)</p></li><li><p>
        When using an SSH connection to manage a remote server,
        MySQL Workbench repeatedly prompted the user to enter a password,
        even though a key file had been specified.
       (Bug #49307)</p></li><li><p>
        In the SQL Editor, when using the live editor, if
        <span class="guimenu">Query</span>, <span class="guimenu">Export Results</span> was
        selected from the main menu and a CSV output format chosen, the
        exported data was found to be in tab delimited format, rather
        than CSV format.
       (Bug #49303)</p></li><li><p>
        When MySQL Workbench was connected to a remote server using an SSH
        connection, and a data export operation performed, MySQL Workbench
        actually attempted to perform the data export on a local server
        instance, rather than on the connected remote server. If the
        remote and local server had a common user account, a backup
        could be performed that appeared to complete successfully, but
        which contained data from the local server rather than the
        connected remote server.
       (Bug #49295)</p></li><li><p>
        In the <span class="guilabel">Alter Table</span> dialog of the SQL
        Editor, support for triggers appeared to be provided, but
        underlying functionality was missing.
       (Bug #49287)</p></li><li><p>
        In the SQL Editor, if Alter Table was invoked, and the collation
        for a column changed, no changes were detected after clicking
        <span class="guibutton">Apply</span>.
       (Bug #49277)</p></li><li><p>
        The descriptions used for options in the <span class="guilabel">Advanced
        Options</span> tab in the <span class="guilabel">Data Dump</span>
        section of the administrator were lacking clarity and in some
        cases dated.
       (Bug #49224)</p></li><li><p>
        The import log contained messages with redundant parentheses.
       (Bug #49218)</p></li><li><p>
        There was no facility to cancel the Export to Disk process, once
        started, in the Administrator. Further, the <span class="guibutton">Start
        Export</span> button erroneously remained enabled during
        the export process, enabling the user to start new export
        processes, resulting in errors.
       (Bug #49115)</p></li><li><p>
        In the <span class="guilabel">Data Dump</span> facility of the
        Administrator, if a schema was selected, but its corresponding
        check box not selected, and then several of its tables selected
        for export, this error occurred when the <span class="guibutton">Start
        Export</span> button was clicked:
      </p><pre class="programlisting">Nothing to do, no schemas or tables selected.</pre><p>(Bug #49110)</p></li><li><p>
        In the <span class="guilabel">Create a new server instance</span> wizard,
        using the default SSH Key Path,
        <code class="filename">~/.ssh/id_rsa</code>, resulted in a 'file not
        found' error when testing the connection. However, if the path
        was entered as <code class="filename">/home/username/.ssh/id_rsa</code>
        the connection test was successful. The same problem was also
        present in the <span class="guilabel">Manage DB Connections</span>
        dialog.
       (Bug #49090)</p></li><li><p>
        The first connection created with New Connection did not appear
        immediately in the list of available connections.
       (Bug #49079, Bug #49801)</p></li><li><p>
        Numerous variables were missing from the DDL section of the
        <span class="guilabel">Status Variables</span> tab in the administrator.
       (Bug #49073, Bug #49077)</p></li><li><p>
        In the configuration file editor it was possible to select a
        directory, such as <span class="guilabel">Temp directory</span> on the
        General tab, without specifying a corresponding path.
       (Bug #49035)</p></li><li><p>
        In the <span class="guilabel">General</span> tab of the configuration
        file editor, the option <span class="guilabel">Default table type</span>
        was present, even though it was deprecated in MySQL Server 5.0.
        Further, selecting this option and applying changes did not
        change the server configuration file.
       (Bug #49006)</p></li><li><p>
        If the command for checking server status was changed in a
        server instance, the change did not take effect unless
        MySQL Workbench was restarted.
       (Bug #48992)</p></li><li><p>
        MySQL Workbench did not correctly detect the status of MySQL Servers
        where multiple servers were running on the same host, and so
        displayed incorrect server status on the Admin screen.
       (Bug #48975)</p></li><li><p>
        In the <span class="guilabel">Forward Engineer SQL Script</span> wizard,
        selection of the <span class="guilabel">Skip Creation of FOREIGN
        KEYS</span> check box was not reflected in the generated
        script.
       (Bug #47969)</p></li><li><p>
        When using MySQL Workbench to create an <code class="literal">ALTER</code>
        script, the generated script did not reflect columns where only
        the case of the column name had changed.
       (Bug #45556)</p></li><li><p>
        If a schema that contained tables with no engine defined was
        reverse engineered, and then the engine type was changed in
        MySQL Workbench, then when the model was exported the ALTER script
        did not contain code to change the engine of the table.
       (Bug #45110)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-catalog-palette.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.5.10. The Catalog Tree Palette</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-model-editor.html" title="7.5. Model Editor"><link rel="prev" href="wb-navigator-panel.html" title="7.5.9. The Model Navigator Panel"><link rel="next" href="wb-layers-palette.html" title="7.5.11. The Layers Palette"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-catalog-palette"></a>7.5.10. The Catalog Tree Palette</h3></div></div></div><p>
      The <code class="literal">Catalog Tree</code> palette shows all the schemata
      that are present in the <code class="literal">Physical Schemata</code>
      section of the <code class="literal">MySQL Model</code> page. Expand the
      view of the objects contained in a specific schema by clicking the
      <span class="guibutton">+</span> button to the left of the schema name.
      This displays the following folder icons:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          Tables
        </p></li><li><p>
          Views
        </p></li><li><p>
          Routine Groups
        </p></li></ul></div><p>
      Expand each of these in turn by clicking the
      <span class="guibutton">+</span> button to the left of the folder icon.
    </p><p>
      Selecting an object in this palette displays its properties in the
      <code class="literal">Properties</code> palette, which can be found in the
      lower left corner of the page.
    </p><p>
      The Catalog Tree palette is primarily used to drag and drop
      objects onto an EER diagram canvas.
    </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
        On Linux, there is a quirk in the GTK tree control, where a
        simple click always generates a new selection. To drag multiple
        objects from the Catalog Tree to the EER diagram canvas, you
        must perform the operation as follows:
      </p><div class="orderedlist"><ol type="1"><li><p>
            Click the first item in the tree.
          </p></li><li><p>
            Hold the <span><strong class="keycap">Shift</strong></span> key, click the last item,
            and <span class="emphasis"><em>do not release the <span><strong class="keycap">Shift</strong></span>
            key</em></span>.
          </p></li><li><p>
            Keep the <span><strong class="keycap">Shift</strong></span> key depressed and commence
            the dragging operation.
          </p></li><li><p>
            Release the <span><strong class="keycap">Shift</strong></span> key before you release
            the mouse button to drop selected objects onto the canvas.
          </p></li></ol></div><p>
        This procedure also applies to use of the
        <span><strong class="keycap">Control</strong></span> key when selecting multiple nonadjacent
        elements in the Catalog Tree.
      </p></div><p>
      You can toggle the sidebar on and off using the <span class="guilabel">Toggle
      Sidebar</span> button, which is located in the top right of
      the application.
    </p></div></body></html>


path: /wb-html-guitools/wb-news-5-2-3.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.37. Changes in MySQL Workbench 5.2.3 (15 September 2009)</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="changes-5.2.x.html" title="A.1. Changes in Release 5.2"><link rel="prev" href="wb-news-5-2-4.html" title="A.1.36. Changes in MySQL Workbench 5.2.4 (07 October 2009)"><link rel="next" href="wb-news-5-2-2.html" title="A.1.38. Changes in MySQL Workbench 5.2.2 (27 July 2009)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-news-5-2-3"></a>A.1.37. Changes in MySQL Workbench 5.2.3 (15 September 2009)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.2.2.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        In the <span class="guilabel">Inserts</span> tab of the Table Editor, if
        a value was entered with quoting then any characters in the
        string requiring escaping were not escaped. However, if the same
        string was entered without quoting then the string would be
        escaped correctly by MySQL Workbench.
      </p><p>
        For 5.0 and 5.1 this is expected behavior. If a value is entered
        without leading and trailing quotation marks, the Inserts Editor
        adds quoting and escapes characters that require it. However, if
        quoted text is entered, the Inserts Editor carries out no
        further checks because it assumes a correctly escaped and quoted
        sequence has been entered.
      </p><p>
        5.2 features a new Inserts Editor. In this case the user enters
        the string without quoting or escaping and the Inserts Editor
        takes care of all quoting and escaping as required.
       (Bug #38906)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        In the <span class="guilabel">Forward Engineer SQL CREATE script</span>
        wizard, in the dialog asking for confirmation to overwrite an
        existing file, clicking the <span class="guibutton">Cancel</span> button
        led to the wizard proceeding to the next step, while clicking
        the <span class="guibutton">Replace</span> button led to cancellation of
        the action. The functionality of the buttons appeared to be
        reversed.
       (Bug #47257)</p></li><li><p>
        When adding inserts with a <code class="literal">NULL</code> value in a
        column, MySQL Workbench incorrectly added single quotation marks to
        the NULL value.
      </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
          Note, when entering a <code class="literal">NULL</code> value
          right-click the button next to the value and select
          <span class="guilabel">Set selection to NULL</span>, otherwise
          <code class="literal">NULL</code> will be interpreted as a string
          literal.
        </p></div><p>(Bug #47122)</p></li><li><p>
        MySQL Workbench crashed on launch on Mac OS X 10.6.0.
       (Bug #46953)</p></li><li><p>
        If the Default Storage Engine was selected as
        <code class="literal">MyISAM</code> in the <span class="guilabel">Model
        Options</span> dialog, when a new table was created in the
        EER Diagram it was found to have a storage engine type of
        <code class="literal">InnoDB</code>.
       (Bug #46752)</p></li><li><p>
        When a model containing invalid/broken foreign key definitions
        was loaded into MySQL Workbench, the errors were detected and
        repaired.
      </p><p>
        However, when the model was saved and reloaded it contained
        changed data types. All <code class="literal">INTEGER</code> columns were
        changed to <code class="literal">INTEGER(11)</code>. Further, some
        <code class="literal">BOOLEAN</code> columns were changed to
        <code class="literal">BOOLEAN(1)</code>.
       (Bug #46467)</p></li><li><p>
        If the Table Editor had been invoked then the Text Boxes in the
        <span class="guimenu">Tools</span>, <span class="guimenu">Preferences</span> dialog
        became vertically misaligned. This only happened for MySQL Workbench
        running on Mac OS X.
       (Bug #46255)</p></li><li><p>
        When a connection was selected in the DB Connection Editor it
        appeared to flicker a number of times before MySQL Workbench
        crashed.
       (Bug #46065)</p></li><li><p>
        When a database with Stored Procedures was reverse-engineered
        into MySQL Workbench the Stored Procedures were not displayed in the
        Routine Editor, and so could not be edited.
       (Bug #45704)</p></li><li><p>
        When running MySQL Workbench on Mac OS X, if a table was added to
        the model diagram and deleted the application crashed. This
        happened for a new diagram from a schema imported from a live
        database.
       (Bug #45692)</p></li><li><p>
        During Forward Engineering, clicking the <span class="guibutton">Copy to
        Clipboard</span> button generated code that contained an
        extra newline per line.
       (Bug #45579)</p></li><li><p>
        Attempts to rebuild the MySQL Workbench source RPM failed. The RPM
        appeared to contain an unmodified template
        <code class="filename">mysql-workbench.spec.in</code> instead of the
        correct spec file with variable placeholders replaced by actual
        values.
      </p><p>
        When using the following command to rebuild the RPM:
      </p><pre class="programlisting">shell&gt; <strong class="userinput"><code>rpmbuild -ba --clean SPECS/mysql-workbench.spec.in</code></strong>
</pre><p>
        This error was generated:
      </p><pre class="programlisting">error: File /usr/src/packages/SOURCES/mysql-workbench-oss-@VERSION@.tar.gz: 
No such file or directory</pre><p>
        Further, the spec file in the package had the incorrect suffix
        “<span class="quote">.spec.in</span>” instead of “<span class="quote">.spec</span>”.
       (Bug #45515)</p></li><li><p>
        On Mac OS X, it was not possible to resize a Text Object on the
        EER Diagram canvas.
       (Bug #45472)</p><p>See also Bug #39887.</p></li><li><p>
        It was not possible to assign columns to indexes because the
        <span class="guilabel">Column</span> check boxes did not respond to mouse
        events.
       (Bug #45260)</p></li><li><p>
        MySQL Workbench generated a segmentation fault when clicking either
        the <span class="guilabel">NN</span> or <span class="guilabel">AI</span> check
        boxes on the <span class="guilabel">Columns</span> tab of the Table
        Editor.
       (Bug #45075)</p></li><li><p>
        In the <span class="guilabel">Columns</span> tab of the Table Editor, if
        the column was of type <code class="literal">ENUM</code> and was given a
        default value, when an attempt was made to forward engineer the
        schema it would not validate.
       (Bug #44368)</p></li><li><p>
        In the Physical Schemata pane if more schema were added than
        could fit within the pane, these schema could not be viewed
        because there was no ability to scroll the pane. Further,
        double-clicking the schema in the Catalog pane did not locate
        the schema in the Physical Schemata pane.
      </p><p>
        MySQL Workbench was changed so that a small down arrow button was
        added to the right side of the Physical Schemata tab bar. This
        provides a list to select a specific schema tab.
       (Bug #39735)</p></li><li><p>
        When <span class="guimenu">Help</span>, <span class="guimenu">About</span> was
        selected from the main menu, it was not possible to copy
        MySQL Workbench version information to the clipboard.
       (Bug #39610)</p></li><li><p>
        When a diagram was exported as PNG it used the height and width
        of the model as displayed in the EER Diagram. This resulted in
        the exported picture being too small or too large, rather than
        being scaled to a consistent size.
       (Bug #36226)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-news-5-2-20.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.20. Changes in MySQL Workbench 5.2.20 (27 April 2010)</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="changes-5.2.x.html" title="A.1. Changes in Release 5.2"><link rel="prev" href="wb-news-5-2-21.html" title="A.1.19. Changes in MySQL Workbench 5.2.21 (12 May 2010 Release Candidate)"><link rel="next" href="wb-news-5-2-19.html" title="A.1.21. Changes in MySQL Workbench 5.2.19 (16 April 2010)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-news-5-2-20"></a>A.1.20. Changes in MySQL Workbench 5.2.20 (27 April 2010)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.2.19.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        The SQL Statements tab and the record set data editor tab now
        indicate when they have unsaved data by displaying an asterisk
        character.
       (Bug #52799)</p></li><li><p>
        If MySQL Workbench was used on an external monitor as part of an
        extended desktop, then when the computer was started without the
        external monitor, MySQL Workbench was not displayed on the primary
        display, and was therefore invisible. MySQL Workbench now checks for
        this condition and locates half of the application window on the
        primary desktop where it can be dragged and resized as required.
       (Bug #52703)</p></li><li><p>
        The foreign key/index mapping implementation has been changed so
        that indexes created for foreign keys no longer need be marked
        as <code class="literal">FOREIGN</code>. They now are created with type
        <code class="literal">INDEX</code> and can be changed to
        <code class="literal">UNIQUE</code> or other types.
      </p><p>
        Although the artificial <code class="literal">FOREIGN</code> index type
        has been removed, MySQL Workbench still automatically creates and
        maintains indexes for each foreign key by naming them after the
        keyname and keeping the names (FK to IDX) synchronized.
       (Bug #48728)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        The MySQL Workbench <code class="filename">configure.in</code> configure
        script contained a construct incompatible with NetBSD. The
        script used <code class="literal">test ==</code> instead of <code class="literal">test
        =</code>.
       (Bug #53175)</p></li><li><p>
        In the SQL Editor, when commands were entered into the SQL
        Statements area, and executed, they appeared on the Output tab.
        However, when the number of statements appearing in the
        <span class="guilabel">Output</span> tab exceeded the number that could
        be displayed in the default area, a vertical scrollbar did not
        appear. This meant any further statements that were executed
        were effectively hidden because it was not possible to scroll
        vertically to display them.
       (Bug #53156)</p></li><li><p>
        If multiple SQL Editor tabs were opened, closing the last one
        caused MySQL Workbench to crash.
       (Bug #53061)</p></li><li><p>
        If a schema was opened and an object editor, such as the Table
        Editor was opened, MySQL Workbench crashed if the schema was closed
        and immediately reopened.
       (Bug #53027)</p></li><li><p>
        In the <span class="guilabel">Variables</span> tab of the Administrator,
        variables with long descriptions were not displayed correctly.
        They appeared wrapped to a new line, and clipped by the height
        of the <span class="guilabel">Description</span> row.
       (Bug #53025)</p></li><li><p>
        On Windows, if SQL Editor was using a named pipe connection, and
        the <span class="guilabel">SQL Editor</span> tab was closed, MySQL Workbench
        stopped responding to user input and had to be killed using the
        Task Manager.
       (Bug #53021)</p></li><li><p>
        The HUD blocked access to other applications that were running.
        This was particularly a problem when Administrator or SQL Editor
        were launched from the Home screen, and took a long time to
        load.
       (Bug #53006)</p></li><li><p>
        In the <span class="guilabel">Export to Disk</span> tab of the
        Administrator's <span class="guilabel">Data Dump</span> facility,
        selecting multiple schemata for export to a self-contained file
        resulted in this exception:
      </p><pre class="programlisting">unhandled exception: local variable
'tables' referenced before assignment.</pre><p>(Bug #52981)</p></li><li><p>
        When an EER Diagram was displayed, the
        <span class="guilabel">Properties</span> tab was empty. Also, if a table
        in the EER Diagram was selected, the
        <span class="guilabel">Properties</span> tab remained empty.
       (Bug #52971)</p></li><li><p>
        In the SQL Editor, field data of type
        <code class="literal">VARBINARY</code> viewed using the <span class="guimenu">Open
        Value in Viewer</span> context-sensitive menu item was
        displayed only up to the first null byte (\0).
       (Bug #52954)</p></li><li><p>
        In the results editor of the SQL Editor, deleting more than two
        hundred records resulted in this error:
      </p><pre class="programlisting">Attempting to Read or Write protected memory. This is often an indication that other
memory is corrupt</pre><p>
        This happened when using either the delete key or the
        <span class="guimenu">Delete Rows</span> context-sensitive menu option.
       (Bug #52951)</p></li><li><p>
        When MySQL Workbench was sized to 1280 x 800, the <span class="guibutton">Start
        Export</span> button was not visible in the
        <span class="guilabel">Export to Disk</span> tab of the <span class="guilabel">Data
        Dump</span> facility.
       (Bug #52932)</p></li><li><p>
        Selecting multiple tables at the same time in the
        <span class="guilabel">Overview</span> tab of the SQL Editor caused
        MySQL Workbench to crash.
       (Bug #52922)</p></li><li><p>
        MySQL Workbench failed to compile from source due to a missing
        <code class="literal">#include &lt;stdarg.h&gt;</code> statement in the
        file
        <code class="filename">library/sql-parser/include/myx_sql_tree_item.h</code>.
       (Bug #52919)</p></li><li><p>
        When building MySQL Workbench, the build process failed if the
        <code class="literal">--no-copy-dt-needed-entries</code> linker option was
        specified (this happens by default when building on Fedora 13).
       (Bug #52918)</p></li><li><p>
        Print to PDF, Print to PS File, and all export functions did not
        work correctly. For example, if Print to PDF was selected,
        MySQL Workbench would attempt to open a new document, and if the
        user proceeded, the current document would be closed.
      </p><p>
        Further, selecting the menu option <span class="guimenu">Save Model
        As</span> resulted in the <span class="guilabel">Open Document</span>
        dialog being displayed. If the user clicked
        <span class="guibutton">Yes</span> the application became stuck in a
        loop, if <span class="guibutton">No</span> was clicked an error dialog
        was displayed.
       (Bug #52909)</p></li><li><p>
        Script editors, such as the editor in the SQL Editor, that used
        the Scintilla component, did not have full integration with the
        Edit menu. Short cuts and menu commands for operations such as
        copy, paste, select all, and find were not implemented.
       (Bug #52834, Bug #51806)</p></li><li><p>
        In the EER Diagram view, layer objects did not respond to edit
        commands (either double-clicking or using the <span class="guimenu">Edit
        Layer</span> context-sensitive menu option).
       (Bug #52822, Bug #52823)</p></li><li><p>
        While MySQL Workbench was starting up, if the Windows screensaver
        activated, this led to unpredictable behavior of MySQL Workbench.
        For example, the application could freeze, fail to redraw its
        main window, or display artifacts. On other occasions the
        application was not able to accept keyboard input, and had to be
        terminated using the Task Manager.
       (Bug #52780)</p></li><li><p>
        When switching between Model Overview Page, and EER Diagram
        View, MySQL Workbench incorrectly rendered the EER Diagram View
        inside the <span class="guilabel">Table Editor</span> panel.
       (Bug #52778)</p></li><li><p>
        The MySQL Workbench dependency on <code class="literal">libmysql</code> has
        changed to use version 16 of the library rather than 15.
       (Bug #52682)</p></li><li><p>
        If a table comment contained a single quote character, an error
        resulted when an attempt was made to synchronize this with a
        live server. This was because the code generated by the
        synchronization process did not escape single quotation marks in
        the table comments.
       (Bug #52608)</p></li><li><p>
        In the <span class="guilabel">Snippets</span> tab of the SQL Editor,
        there appeared to be a third column, with no heading or data, in
        the snippets list. MySQL Workbench now expands the second column to
        fill the available space.
       (Bug #52559)</p></li><li><p>
        The View Editor deleted text pasted into the editor by the user.
        This happened if, for example, a view was copied from the
        editor, a new view created and the copied text pasted into the
        new view. At this point the pasted text would be deleted by the
        auto-parsing facility of the View Editor.
       (Bug #52433)</p></li><li><p>
        In the <span class="guilabel">Reverse Engineer Database</span> wizard, on
        the <span class="guilabel">Connection Options</span> page, if the first
        empty connection was selected from the <span class="guilabel">Stored
        Connection</span> list, and then the <span class="guilabel">Connection
        Method</span> changed, the fields on the
        <span class="guilabel">Parameters</span> tab did not change accordingly.
       (Bug #51742)</p></li><li><p>
        Each time an <span class="guilabel">Admin</span> tab was started an
        instance of <code class="filename">cscript.exe</code> was executed.
        However, when the <span class="guilabel">Admin</span> tab was closed the
        corresponding <code class="literal">cscript.exe</code> process was not
        terminated. This resulted in ever increasing numbers of
        <code class="literal">cscript.exe</code> processes, which consumed
        resources unnecessarily, and constituted a resource leak.
       (Bug #51601)</p></li><li><p>
        When selecting Print Preview for an EER Diagram, the objects in
        the preview appeared primarily as black filled rectangles.
       (Bug #51513)</p></li><li><p>
        In the <span class="guilabel">Columns</span> tab of the Table Editor, the
        bottom button of the comments scrollbar was situated too low,
        making downward scrolling very difficult because only part of
        the scrollbar button was exposed.
       (Bug #51496)</p></li><li><p>
        In the <span class="guilabel">Columns</span> tab of the Table Editor, if
        a comment was added to a column, or a column with a comment was
        selected, then when another table was double-clicked to load it
        into the Table Editor, the comment for the column previously
        selected was still displayed in the inactive
        <span class="guilabel">Comments</span> area.
       (Bug #51495)</p></li><li><p>
        If an SQL statement was selected in the SQL Statements area of
        the SQL Editor, and copied to the snippets list using the
        <span class="guibutton">Save SQL to Snippets List</span> toolbar button,
        then the statement was only partially saved, the beginning of
        the statement being missing. This only happened for lines after
        the first line. Also, the further down the copied statement was
        located, the less text was successfully copied to the snippets
        list. This resulted in statements further down the code being
        heavily truncated, with only the latter portion of the statement
        being saved.
       (Bug #51474)</p></li><li><p>
        If a snippet was deleted from the <span class="guilabel">Snippets</span>
        tab in the SQL Editor, after MySQL Workbench was restarted the
        deleted snippet would reappear as if it had never been deleted.
       (Bug #51335, Bug #52558)</p></li><li><p>
        In the <span class="guilabel">Reverse Engineer Database</span> wizard, on
        the <span class="guilabel">Select Schemata</span> page, any schema name
        containing an underscore was displayed without the underscore
        character. Further, if the <span><strong class="keycap">Alt</strong></span> key was pressed,
        the underscores appeared under the first character located after
        where the underscore should have been displayed, giving the
        character the appearance of being an accelerator key.
       (Bug #51141, Bug #52965)</p></li><li><p>
        In the <span class="guilabel">Columns</span> tab of the Table Editor, if
        a column was right-clicked on, and then <span class="guimenu">Move
        Up</span> selected, the column ordering was not updated
        within the <span class="guilabel">Columns</span> tab, until the area was
        clicked again.
       (Bug #51139)</p></li><li><p>
        The MySQL Workbench make targets, with the exception of
        <code class="literal">make all</code>, were broken by the file
        <code class="filename">ext/ctemplate/Makefile</code>.
       (Bug #51024)</p></li><li><p>
        In the SQL Editor, when a new tab was created, the focus was on
        the Object Explorer, rather than in the SQL Statements area.
        This meant that the user had to press the <span><strong class="keycap">Tab</strong></span>
        key, or click within the SQL Statements area before they could
        start typing SQL code.
       (Bug #50711)</p></li><li><p>
        MySQL Workbench crashed when the <code class="literal">root</code> user,
        located in the <span class="guilabel">Server Access Management</span> tab
        of the Accounts facility in the Administrator, was clicked.
       (Bug #50703)</p></li><li><p>
        SQL Editor syntax highlighting did not correctly recognize
        escaping of the single quote character ('). Queries such as
        <code class="literal">SELECT '\'' FROM DUAL;</code> were therefore not
        highlighted correctly.
       (Bug #50324)</p></li><li><p>
        When using the <span class="guilabel">Forward Engineer SQL Script</span>
        wizard, if an existing script file was selected to be
        overwritten, the wizard would not continue, the file had to be
        deleted first.
       (Bug #46920)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/license-flat-tab-control.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>B.1. .NET Flat TabControl License</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-third-party-licenses.html" title="Appendix B. Third Party Licenses"><link rel="prev" href="wb-third-party-licenses.html" title="Appendix B. Third Party Licenses"><link rel="next" href="license-bitstream-vera.html" title="B.2. Bitstream Vera License"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="license-flat-tab-control"></a>B.1. .NET Flat TabControl License</h2></div></div></div><p>
    The following software may be included in this product:
  </p><div class="itemizedlist"><ul type="disc"><li><p>
        <span class="bold"><strong>.NET Flat TabControl</strong></span>
      </p></li></ul></div><p>
    Use of any of this software is governed by the terms of the license
    below:
  </p><pre class="programlisting">It is free. Public domain!
Oscar Londono</pre></div></body></html>


path: /wb-html-guitools/wb-routine-group-tool.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.6.1.9. The Routine Group Tool</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-vertical-toolbar.html" title="7.6.1. The Vertical Toolbar"><link rel="prev" href="wb-view-tool.html" title="7.6.1.8. The View Tool"><link rel="next" href="wb-reference-relationship-tools.html" title="7.6.1.10. The Relationship Tools"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-routine-group-tool"></a>7.6.1.9. The Routine Group Tool</h4></div></div></div><p>
        Use this tool to create a routine group on the EER Diagram
        canvas. When this tool is activated, a schema list appears on
        the toolbar below the main menu, enabling you to associate the
        routine group with a specific schema. You can also select a
        color for the routine group by choosing from the color list to
        the right of the schema list.
      </p><p>
        After selecting this tool, clicking the canvas creates a new
        group. To edit this view, right-click it and choose
        <span class="guimenuitem">Edit Routine Group...</span> or
        <span class="guimenuitem">Edit in New Window...</span> from the pop-up
        menu.
      </p><p>
        To activate the routine group tool from the keyboard, use the
        <span><strong class="keycap">G</strong></span> key.
      </p><p>
        For more information about creating and editing routine groups,
        see <a href="wb-routine-groups.html" title="7.7.4.2. Routine Groups">Section 7.7.4.2, “Routine Groups”</a>.
      </p></div></body></html>


path: /wb-html-guitools/wb-tutorial-plugins.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>9.6. Tutorial: Writing Plugins</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-extending.html" title="Chapter 9. Extending Workbench"><link rel="prev" href="wb-scripting-modules-palettes.html" title="9.5.3. The Globals, Classes, and Modules Tabs"><link rel="next" href="wb-keys.html" title="Chapter 10. Keyboard Shortcuts"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="wb-tutorial-plugins"></a>9.6. Tutorial: Writing Plugins</h2></div></div></div><p>
    This tutorial shows you how to extend MySQL Workbench by creating a
    plugin.
  </p><p>
    <span class="bold"><strong>The Sample Plugin</strong></span>
  </p><p>
    EER Diagrams are useful for visualizing complex database schemata.
    They are often created for existing databases, to clarify their
    purpose or document them. MySQL Workbench provides facilities for
    reverse engineering existing databases, and then creating an EER
    Diagram automatically. In this case, relationship lines between
    foreign keys in the table will automatically be drawn. This
    graphical representation makes the relationships between the tables
    much easier to understand. However, one of the most popular storage
    engines for MySQL, MyISAM, does not include support for foreign
    keys. This means that MyISAM tables that are reverse engineered will
    not automatically have the relationship lines drawn between tables,
    making the database harder to understand. The plugin that will be
    created in this tutorial gets around this problem by using the fact
    that a naming convention is very often used for foreign keys:
    <code class="literal"> tablename_primarykeyname</code>. Using this convention,
    foreign keys can automatically be created after a database is
    reverse engineered, which will result in relationship lines being
    drawn in the EER diagram.
  </p><p>
    <span class="bold"><strong>Algorithm</strong></span>
  </p><p>
    The basic algorithm for this task would be as follows:
  </p><pre class="programlisting">for each table in the schema
   for each column in the table
      look for another table whose name and primary key name match the current column name
      if such a table is found, add a foreign key referencing it</pre><p>
    As iterating the complete table list to find a match can be slow for
    models with a large number of tables, it is necessary to optimize by
    pre-computing all possible foreign key names in a given schema.
  </p><pre class="programlisting">import grt

def auto_create_fks(schema):
   fk_name_format = "%(table)s_%(pk)s"
   possible_fks = {}
   # create the list of possible foreign keys from the list of tables
   for table in schema.tables:
      if table.primaryKey:
         format_args = {'table':table.name, 'pk':table.primaryKey.name}
         fkname = fk_name_format % format_args
         possible_fks[fkname] = table

   # go through all tables in schema, this time to find columns that may be a fk
   for table in schema.tables:
      for column in table.columns:
         if possible_fks.has_key(column.name):
            ref_table = possible_fks[column.name]
            if ref_table.primaryKey.formattedType != column.type:
               continue
            fk = table.createForeignKey(column.name+"_fk")
            fk.referencedTable = ref_table
            fk.columns.append(column)
            fk.referencedColumn.append(ref_table.primaryKey)
            print "Created foreign key %s from %s.%s to %s.%s" % (fk.name, table.name, column.name, ref_table.name, ref_table.primaryKey.name)

auto_create_fks(grt.root.wb.doc.physicalModels[0].catalog.schemata[0])</pre><p>
    <span class="bold"><strong>Creating a Plugin from a Script</strong></span>
  </p><p>
    To create a plugin from an arbitrary script, it is first necessary
    to make the file a module, and export the required function from it.
    It is then necessary to declare the module as a plugin, and specify
    the return type and input arguments.
  </p><pre class="programlisting">from wb import *
import grt

ModuleInfo = DefineModule(name="AutoFK", author="John Doe", version="1.0")

@ModuleInfo.plugin("sample.createGuessedForeignKeys", caption="Create Foreign Keys from ColumnNames",
input=[wbinputs.objectOfClass("db.mysql.schema")], groups=["Overview/Utility"])
@ModuleInfo.export(grt.INT, grt.classes.db_mysql_Schema)
def auto_create_fks(schema):
   ...</pre><p>
    With the addition of the preceding code, the
    <code class="literal">auto_create_fks()</code> function is exported and will
    be added to the schema context menu in the model overview. When
    invoked, it receives the currently selected schema as its input.
  </p></div></body></html>


path: /wb-html-guitools/wb-news-5-2-11.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.29. Changes in MySQL Workbench 5.2.11 (18 December 2009)</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="changes-5.2.x.html" title="A.1. Changes in Release 5.2"><link rel="prev" href="wb-news-5-2-12.html" title="A.1.28. Changes in MySQL Workbench 5.2.12 (Not released)"><link rel="next" href="wb-news-5-2-10.html" title="A.1.30. Changes in MySQL Workbench 5.2.10 (01 December 2009)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-news-5-2-11"></a>A.1.29. Changes in MySQL Workbench 5.2.11 (18 December 2009)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.2.10.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        MySQL Workbench had confusing and erroneous behavior when attempting
        to handle multiple model tabs. It has now been changed so that
        if a model is currently loaded, and a new model or saved model
        needs to be loaded, the current model will be closed first
        before then opening the new model.
       (Bug #49422)</p></li><li><p>
        In the configuration editor, it was not possible to find, and
        therefore set, the configuration variable “<span class="quote">old</span>”.
      </p><p>
        This has now been added to the <span class="guilabel">General</span> tab
        in the configuration editor of the Admin tab.
       (Bug #49039)</p></li><li><p>
        It was impossible to use a function call as a field value in an
        editable result set, such as for a result set in the Query
        Editor or in the <span class="guilabel">Inserts</span> tab in the Table
        Editor. This was because MySQL Workbench automatically escaped
        string parameters passed to the function call. For example, if
        an attempt was made to enter into a field a function such as
        <code class="literal">md5('fred')</code>, MySQL Workbench would generate the
        SQL code <code class="literal">md5(\'fred\')</code>.
      </p><p>
        MySQL Workbench now makes it possible to enter a function, or any
        other expression, into a field using the
        <code class="literal">\func</code> prefix. For example, <code class="literal">\func
        md5('fred')</code> can be entered. MySQL Workbench will now
        ensure that the string 'fred' is not escaped. See
        <a href="wb-sql-editor-live-editing-tabsheets.html" title="6.7.4.6. Live Editing Tabsheets">Section 6.7.4.6, “Live Editing Tabsheets”</a>.
       (Bug #38600)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p><span class="bold"><strong>Security Fix</strong></span>: 
        When using the <span class="guilabel">Data Dump</span> facility in the
        Admin screen, the full <span><strong class="command">mysqldump</strong></span> command,
        including the password used, was written to the logs.
       (Bug #49294)</p></li><li><p>
        In the SQL Editor the SQL Statements area could only display ten
        lines of code and was not resizeable.
       (Bug #49788)</p></li><li><p>
        In an EER diagram, if the model was synchronized with a live
        database, any foreign key relationship lines that were set to
        hidden became visible.
       (Bug #49631)</p></li><li><p>
        In the Home screen Workspace, in the central panels listing
        connections, models and server instances, the items in the
        panels appeared to be rendered as links. However, clicking these
        “<span class="quote">links</span>” had no effect, and the items could only be
        loaded by double-clicking.
      </p><p>
        MySQL Workbench has been changed to remove the link effect, and
        these items can only be loaded by double-clicking.
       (Bug #49623)</p></li><li><p>
        When MySQL Workbench silently reconnected to a server after a
        communication failure, it failed to reinitialize the connection
        correctly. As a result of this failure Autocommit was silently
        enabled. If a user was working with transactional tables, the
        commit and rollback toolbar buttons appeared to work, although
        they had no effect.
       (Bug #49462)</p></li><li><p>
        If a connection failed MySQL Workbench reconnected silently. This
        caused problems with transactions. If changes were made to a
        table, before a <code class="literal">COMMIT</code>, and the connection
        lost, MySQL Workbench would reconnect silently and enable the user
        to <code class="literal">COMMIT</code>. However, it did not warn that this
        <code class="literal">COMMIT</code> was on a new connection, and that the
        <code class="literal">COMMIT</code> would have no effect.
       (Bug #49461)</p></li><li><p>
        In the <span class="guilabel">Advanced</span> tab of the configuration
        editor, the option <span class="guilabel">Delay key write</span> had a
        file selector button associated with it. This should have been a
        list offering the values <code class="literal">ON</code>,
        <code class="literal">OFF</code>, <code class="literal">ALL</code>.
       (Bug #49424)</p></li><li><p>
        When using the <span class="guilabel">Create a new server instance</span>
        wizard, the panel used to enter the SSH password was hidden by
        the wizard.
       (Bug #49416)</p></li><li><p>
        If the Home screen was closed and then an attempt made to reopen
        it from the <span class="guimenu">View</span>, <span class="guimenu">Home</span>
        main menu option, MySQL Workbench crashed.
       (Bug #49388)</p></li><li><p>
        MySQL Workbench did not have the ability to toggle Autocommit mode,
        or a facility to explicitly start a transaction, in the SQL
        Editor. This was in contrast to Query Browser, which did support
        such facilities.
       (Bug #49384)</p></li><li><p>
        When using the Reverse Engineer SQL Script to import the Sakila
        script file, <code class="filename">sakila-data.sql</code>, MySQL Workbench
        occasionally crashed.
       (Bug #49381)</p></li><li><p>
        In the <span class="guilabel">History</span> tab of the SQL Editor, it
        was possible to simultaneously select multiple entries in the
        <span class="guilabel">Time</span> panel. However, this did not seem to
        serve any useful purpose as the content of the SQL column only
        displayed the code for a single entry.
       (Bug #49375)</p></li><li><p>
        In the Schemata Palette of the SQL Editor the default schema
        selector did not work if the schema name contained a '.'
        character.
       (Bug #49373)</p></li><li><p>
        When using the SQL Snippets palette, right-clicking a snippet,
        and then selecting the menu item <span class="guimenu">Insert text into SQL
        Area</span>, replaced all text in the SQL Statements area.
        This happened after another snippet had previously been inserted
        because the default state was to leave all code in the SQL
        Statements area selected.
       (Bug #49370)</p></li><li><p>
        The <code class="filename">AUTHORS</code> file in the MySQL Workbench
        distribution was empty.
       (Bug #49341)</p></li><li><p>
        In the <span class="guilabel">Overview</span> tab of the SQL Editor the
        drop database button on the toolbar did not work correctly. If
        pressed the dialog presented did not contain the name of the
        current database in its message, and generated text such as:
      </p><pre class="programlisting">Do you want to drop database `` from DB server ...</pre><p>
        Note the empty string where the database name should have been.
        Further, the text on the dialog button
        <span class="guibutton">drop</span> was also missing the database name:
      </p><pre class="programlisting">DROP ``</pre><p>(Bug #49330)</p></li><li><p>
        The path to the an external <code class="literal">mysqldump</code> tool
        set in the <span class="guilabel">MySQL</span> tab of the
        <span class="guilabel">Preferences</span> dialog was ignored by
        MySQL Workbench. This prevented the <span class="guilabel">Data Dump</span>
        facility in the Admin screen from working correctly because the
        required tool could not be found.
       (Bug #49319)</p></li><li><p>
        The live data editor of the SQL Editor, which was launched by
        double-clicking a table in the Overview tab, did not behave
        correctly. If a column value was changed, and the cursor
        remained in the edited cell, then if the <span class="guibutton">Apply made
        changes to data source</span> toolbar button was clicked,
        the contents of the cell reverted to its value prior to editing.
        However, other cell values that had been edited were correctly
        saved.
       (Bug #49301)</p></li><li><p>
        In the SQL Editor, when editing live table data, there was no
        right-click menu item to delete a row.
       (Bug #49300)</p></li><li><p>
        When importing data using the <span class="guilabel">Data Dump</span> tab
        of the Admin screen, MySQL Workbench did not notify the user of
        failed imports because it could not detect failed imports.
       (Bug #49297)</p></li><li><p>
        When a export was performed using the <span class="guilabel">Data
        Dump</span> tab of the Admin screen, and the export failed,
        the resulting SQL file was not deleted.
       (Bug #49296)</p></li><li><p>
        In the SQL Editor, using the <span class="guilabel">Alter Routine</span>
        wizard to generate a script to modify an existing routine in the
        live database results in errors, due to incorrect script code
        being emitted. For example, the statement <code class="literal">DELIMITER
        $$</code> was missing from the start of the script.
       (Bug #49289)</p></li><li><p>
        When an attempt was made to load the
        <code class="filename">sakila.sql</code> script file in the SQL Scripts
        section of the Model tab, MySQL Workbench crashed with this error:
      </p><pre class="programlisting">glibmm-ERROR **: 
unhandled exception (type std::exception) in signal handler:
what: File '/home/kolbe/Downloads/sakila-db/sakila-data.sql' contains invalid UTF-8
data.</pre><p>(Bug #49242)</p></li><li><p>
        In the <span class="guilabel">Overview</span> tab of the SQL Editor, the
        toolbar buttons to add and drop a schema did not function.
        Clicking the buttons appeared to have no effect.
       (Bug #49240)</p></li><li><p>
        In the <span class="guilabel">Overview</span> tab of SQL Editor, the
        toolbar buttons representing large icons, small icons, list,
        add, and delete did not function correctly.
       (Bug #49239)</p></li><li><p>
        The <span class="guilabel">Configuration</span> tab on the Admin screen
        had a text label “<span class="quote">Edit my.cnf File</span>”. This text was
        not appropriate as on Windows the configuration file is called
        <code class="filename">my.ini</code>.
       (Bug #49237)</p></li><li><p>
        In the configuration editor, on the Admin tab, the operation of
        the Apply and Cancel buttons did not work correctly. If an
        option was selected, and then Cancel selected in the view
        changes dialog, and then Apply clicked again, the selected
        option was incorrectly listed twice in the configuration file.
       (Bug #49236)</p></li><li><p>
        In the <span class="guilabel">Create new server instance</span> wizard,
        on the MySQL Config File page, clicking the <span class="guibutton">Check
        path</span> button generated an exception.
       (Bug #49228)</p></li><li><p>
        Even though the server had been stopped, the <span class="guilabel">Server
        Status</span> graphical panel displayed values for active
        connections, traffic and key efficiency, giving the impression
        that the server was still active.
       (Bug #49225)</p></li><li><p>
        The server health graphs Connection Usage and Traffic, in the
        <span class="guilabel">Server Status</span> panel of Admin tab, appeared
        to indicate the server was operating at 100% capacity, even when
        this was not the case.
      </p><p>
        MySQL Workbench has been changed to use variable scaling, rather
        than linear scaling, for these graphs.
       (Bug #49214)</p></li><li><p>
        On the Admin screen the labels for the monitoring graphs were
        difficult to read. Further, the value for Traffic was sometimes
        displayed as a negative number.
       (Bug #49211)</p></li><li><p>
        In the <span class="guilabel">Log Files</span> tab of the configuration
        editor, selected from the Admin tab, the option <span class="guilabel">Write
        Logs to</span> did not work correctly. If either the
        <span class="guilabel">Files</span> or <span class="guilabel">Tables</span>
        options were selected from the option list, the MySQL Server
        would not subsequently start. This was because the options
        should have been <span class="guilabel">File</span> and
        <span class="guilabel">Table</span>.
       (Bug #49123)</p></li><li><p>
        When using the <span class="guilabel">Data Dump</span> facility on the
        Admin screen, the export process appeared to hang when exporting
        with the <span class="guilabel">Export to Backup Project Folder</span>
        radio button selected.
       (Bug #49113)</p></li><li><p>
        When using the <span class="guilabel">Create Table</span> wizard in the
        SQL Editor, the resulting dialog contained certain options that
        could not be deselected once selected. For example, the Merge
        Method option featured a list with three options: Prevent
        Inserts, First Table, Last Table. Note that once one of these
        options was selected, there was no way to clear this selection,
        as there was no facility to select anything other than one of
        these three options.
       (Bug #49048)</p></li><li><p>
        In the <span class="guilabel">General</span> tab of the configuration
        editor, changing the data directory using the file chooser
        control led to an invalid directory being introduced into the
        MySQL configuration file. This prevented the MySQL Server from
        starting.
       (Bug #49036)</p></li><li><p>
        In the <span class="guilabel">General</span> tab of the configuration
        editor in the Admin screen, the option <code class="literal">Default table
        type</code> provided an incomplete, and incorrectly
        capitalized, list of storage engines/table types.
       (Bug #49010)</p></li><li><p>
        In the <span class="guilabel">Configuration</span> tab of the Admin
        screen, any changes made and applied were not reflected in the
        configuration file of a local MySQL Server installation.
       (Bug #49008)</p></li><li><p>
        In the Server Status section of the Admin screen, the values for
        CPU status appeared to be erroneously multiplied by 100, and the
        Memory status appeared to be continually 0.
       (Bug #48994)</p></li><li><p>
        In the <span class="guilabel">Document Properties</span> dialog the
        created date and last changed date values were reversed.
       (Bug #48104)</p></li><li><p>
        When a schema containing tables with foreign key indexes was
        synchronized with a live server, MySQL Workbench attempted to
        erroneously drop and recreate at least one of the foreign key
        indexes.
       (Bug #47766)</p></li><li><p>
        After synchronizing a model with a live database, and saving the
        resulting modified model, MySQL Workbench crashed. On restarting and
        attempting to reopen the model file, MySQL Workbench generated this
        error:
      </p><pre class="programlisting">Error unserializing GRT data inserting null value to not null list</pre><p>(Bug #47518)</p></li><li><p>
        In an EER diagram, if relationship links were laid out as
        desired, and then a synchronization with the live server carried
        out, the relationship links were repositioned by MySQL Workbench.
       (Bug #47234)</p></li><li><p>
        If a relationship link was selected in the EER Diagram view, and
        the menu item <span class="guimenu">Plugins</span>,
        <span class="guimenu">Objects</span>, <span class="guimenu">Copy SQL to
        Clipboard</span> was selected, an error was generated.
      </p><p>
        Note that in version 5.2.11 this menu option is correctly
        disabled for these objects.
       (Bug #39556)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-views-physical-schemata.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.7.3.1. Adding Views to the Physical Schemata</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-creating-views.html" title="7.7.3. Creating Views"><link rel="prev" href="wb-creating-views.html" title="7.7.3. Creating Views"><link rel="next" href="wb-using-view-tool.html" title="7.7.3.2. Adding Views to an EER Diagram"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-views-physical-schemata"></a>7.7.3.1. Adding Views to the Physical Schemata</h4></div></div></div><p>
      To add a view, double-clicking the <code class="literal">Add View</code>
      icon in the <code class="literal">Physical Schemata</code> section of the
      <code class="literal">MySQL Model</code> page. The default name of the view
      is <code class="literal">view1</code>. If a view with this name already
      exists, the new view is named <code class="literal">view2</code>.
    </p><p>
      Adding a new view automatically opens the view editor docked at
      the bottom of the application. For information about using the
      view editor, see <a href="wb-view-editor.html" title="7.7.3.3. The View Editor">Section 7.7.3.3, “The View Editor”</a>.
    </p><p>
      Right-clicking a view opens a pop-up menu with the following
      items:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <span class="guimenuitem">Cut
          '<em class="replaceable"><code>view_name</code></em>'</span>
        </p></li><li><p>
          <span class="guimenuitem">Copy
          '<em class="replaceable"><code>view_name</code></em>'</span>
        </p></li><li><p>
          <span class="guimenuitem">Paste</span>
        </p></li><li><p>
          <span class="guimenuitem">Edit View...</span>
        </p></li><li><p>
          <span class="guimenuitem">Edit in New Window...</span>
        </p></li><li><p>
          <span class="guimenuitem">Copy SQL to Clipboard</span>
        </p></li><li><p>
          <span class="guimenuitem">Delete
          '<em class="replaceable"><code>view_name</code></em>'</span>
        </p></li></ul></div><p>
      If the table editor is not open, the <span class="guimenuitem">Edit
      View...</span> item opens it. If it is already open, the
      selected table replaces the previous one. <span class="guimenuitem">Edit in New
      Window...</span> opens a new view editor tab.
    </p><p>
      The cut and copy items are useful for copying views between
      different schemata. <span class="guimenuitem">Copy SQL to
      Clipboard</span> copies the <code class="literal">CREATE VIEW</code>
      statement to the clipboard.
    </p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Warning</div><p>
        Use the <span class="guimenuitem">Delete
        '<em class="replaceable"><code>view_name</code></em>'</span> item to
        remove a view from the database. There will be
        <span class="bold"><strong>no</strong></span> confirmation dialog box.
      </p></div><p>
      Any views added to the <code class="literal">Physical Schemata</code>
      section also show up in the <code class="literal">Catalog</code> palette on
      the left side of the application. They may be added to an EER
      Diagram, when in the EER Diagram tab, by dragging and dropping
      them from this palette.
    </p></div></body></html>


path: /wb-html-guitools/workbench-faq.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Chapter 11. MySQL Workbench FAQ</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="index.html" title="MySQL Workbench"><link rel="prev" href="wb-keys.html" title="Chapter 10. Keyboard Shortcuts"><link rel="next" href="wb-change-history.html" title="Appendix A. MySQL Workbench Change History"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="workbench-faq"></a>Chapter 11. MySQL Workbench FAQ</h2></div></div></div><p>
    Frequently Asked Questions with answers.
  </p><p><span class="bold"><strong>Questions</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p><a href="workbench-faq.html#qandaitem-11-1-1">11.1: </a>
          How does MySQL Workbench increase import performance?
        </p></li><li><p><a href="workbench-faq.html#qandaitem-11-1-2">11.2: </a>
          MySQL Workbench 5.0 appears to run slowly. How can I increase
          performance?
        </p></li><li><p><a href="workbench-faq.html#qandaitem-11-1-3">11.3: </a>
          I get errors when creating or placing objects on an EER
          Diagram. I am using OpenGL rendering, AMD processor, and ATI
          graphics hardware.
        </p></li></ul></div><p><span class="bold"><strong>Questions and Answers</strong></span></p><p><a name="qandaitem-11-1-1"></a><span class="bold"><strong>11.1: </strong></span><span class="bold"><strong>
          How does MySQL Workbench increase import performance?
        </strong></span></p><p>
          When a model is exported using the main menu item
          <span class="guimenu">File</span>, <span class="guisubmenu">Export</span>,
          <span class="guimenuitem">Forward Engineer SQL CREATE Script</span>,
          some server variables are temporarily set to enable faster SQL
          import by the server. The statements added at the start of the
          code are:
        </p><pre class="programlisting">SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0; 
SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0; 
SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='TRADITIONAL'; </pre><p>
          These statements function as follows:
        </p><div class="itemizedlist"><ul type="disc"><li><p>
              <code class="literal">SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS,
              UNIQUE_CHECKS=0;</code>: Determines whether
              <code class="literal">InnoDB</code> performs duplicate key checks.
              Import is much faster for large data sets if this check is
              not performed.
            </p></li><li><p>
              <code class="literal">SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS,
              FOREIGN_KEY_CHECKS=0;</code>: Determines whether the
              server should check that a referenced table exists when
              defining a foreign key. Due to potential circular
              references, this check must be turned off for the duration
              of the import, to permit defining foreign keys.
            </p></li><li><p>
              <code class="literal">SET @OLD_SQL_MODE=@@SQL_MODE,
              SQL_MODE='TRADITIONAL';</code>: Sets
              <code class="literal">SQL_MODE</code> to
              <code class="literal">TRADITIONAL</code>, causing the server to
              operate in a more restrictive mode.
            </p></li></ul></div><p>
          These server variables are then reset at the end of the script
          using the following statements:
        </p><pre class="programlisting">SET SQL_MODE=@OLD_SQL_MODE; 
SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS; 
SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS; </pre><p><a name="qandaitem-11-1-2"></a><span class="bold"><strong>11.2: </strong></span><span class="bold"><strong>
          MySQL Workbench 5.0 appears to run slowly. How can I increase
          performance?
        </strong></span></p><p>
          Although graphics rendering may appear slow, there are several
          other reasons why performance may be less than expected. The
          following tips may offer improved performance:
        </p><div class="itemizedlist"><ul type="disc"><li><p>
              Upgrade to the latest version. MySQL Workbench 5.0 is still
              being continually maintained and some performance-related
              issues may have been resolved.
            </p></li><li><p>
              Limit the number of steps to save in the <span class="guilabel">Undo
              History</span> facility. Depending on the operations
              performed, having an infinite undo history can use a lot
              of memory after a few hours of work. In
              <span class="guimenu">Tools</span>, <span class="guimenu">Options</span>,
              <span class="guilabel">General</span>, enter a number in the range
              10 to 20 into the <span class="guilabel">Undo History Size</span>
              spinbox.
            </p></li><li><p>
              Disable relationship line crossing rendering. In large
              diagrams, there may be a significant overhead when drawing
              these line crossings. In <span class="guimenu">Tools</span>,
              <span class="guimenu">Options</span>, <span class="guilabel">Diagram</span>,
              uncheck the option named <span class="guilabel">Draw Line
              Crossings</span>.
            </p></li><li><p>
              Check your graphics card driver. The GDI rendering used in
              MySQL Workbench 5.0 is not inherently slow, as most video
              drivers support hardware acceleration for GDI functions.
              It can help if you have the latest native video drivers
              for your graphics card.
            </p></li><li><p>
              Upgrade to MySQL Workbench 5.1. MySQL Workbench 5.1 has had many
              operations optimized. For example, opening an object
              editor, such as the table editor, is much faster, even
              with a large model loaded. However, these core
              optimizations will not be back-ported to 5.0.
            </p></li></ul></div><p><a name="qandaitem-11-1-3"></a><span class="bold"><strong>11.3: </strong></span><span class="bold"><strong>
          I get errors when creating or placing objects on an EER
          Diagram. I am using OpenGL rendering, AMD processor, and ATI
          graphics hardware.
        </strong></span></p><p>
          To solve this problem renew the ATI drivers pack, which can be
          downloaded from the
          <a href="http://game.amd.com/us-en/drivers_catalyst.aspx">AMD
          Web site</a>.
        </p></div></body></html>


path: /wb-html-guitools/wb-modules.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>9.2. Modules</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-extending.html" title="Chapter 9. Extending Workbench"><link rel="prev" href="wb-grt-data-organization.html" title="9.1. GRT and Workbench Data Organization"><link rel="next" href="wb-plugins.html" title="9.3. Plugins"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="wb-modules"></a>9.2. Modules</h2></div></div></div><p>
      In the GRT Modules are libraries containing a list of functions
      that are exported for use by code in other modules, scripts, or
      Workbench itself. Modules can currently be written in C++, Lua, or
      Python, but the data types used for arguments and the return value
      must be GRT types.
    </p><p>
      GRT modules are similar to Python modules, but are imported from
      the built-in <code class="literal">grt</code> module, instead of directly
      from an external file. The list of modules loaded into the
      <code class="literal">grt</code> module is obtained from
      <code class="literal">grt.modules</code>. Modules can be imported in Python
      using statements such as <code class="literal">from grt.modules import
      WbModel</code>.
    </p><p>
      To export functions as a module from Python code, you must carry
      out the following steps:
    </p><div class="orderedlist"><ol type="1"><li><p>
          The source file must be located in the user modules folder.
          This path is displayed in the Workbench Scripting Shell with the label
          <span class="guilabel">Looking for user plugins in...</span>. It is
          also possible to install the file using the main menu item
          <span class="guimenu">Scripting</span>, <span class="guimenuitem">Install
          Plugin/Module File</span>.
        </p></li><li><p>
          The source file name must have the extension
          <code class="filename">_grt.py</code>; for example,
          <code class="filename">my_module_grt.py</code>.
        </p></li><li><p>
          Some module metadata must be defined. This can be done using
          the <code class="literal">DefineModule</code> function from the wb
          module:
        </p><pre class="programlisting">from wb import *
ModuleInfo = DefineModule(name='MyModule', author='Your Name', version='1.0')</pre></li><li><p>
          Functions to be exported require their signature to be
          declared. This is achieved using the export decorator in the
          previously created ModuleInfo object:
        </p><pre class="programlisting">@ModuleInfo.export(grt.INT, grt.STRING)
def checkString(s):
   ...</pre><p>
          For the <code class="literal">export</code> statement, the return type
          is listed first, followed by the input parameter types,
          specified as GRT typenames. The following typenames can be
          used:
        </p><div class="itemizedlist"><ul type="disc"><li><p>
              <code class="literal">grt.INT</code>: An integer value. Also used
              for boolean values.
            </p></li><li><p>
              <code class="literal">grt.DOUBLE</code>: A floating-point numeric
              value.
            </p></li><li><p>
              <code class="literal">grt.STRING</code>: UTF-8 or ASCII string data.
            </p></li><li><p>
              <code class="literal">grt.DICT</code>: A key/value dictionary item.
              Keys must be strings.
            </p></li><li><p>
              <code class="literal">grt.LIST</code>: A list of other values. It is
              possible to specify the type of the contents as a tuple in
              the form <code class="literal">(grt.LIST,
              &lt;type-or-class&gt;)</code>. For example, (grt.LIST,
              grt.STRING) for a list of strings. For a list of table
              objects, the following would be specified:
              <code class="literal">(grt.LIST, grt.classes.db_table)</code>.
            </p></li><li><p>
              <code class="literal">grt.OBJECT</code>: An instance of a GRT object
              or a GRT class object, from
              <code class="literal">grt.classes</code>.
            </p></li></ul></div><p>
          Note that these types are defined in the
          <code class="literal">grt</code> module, which must be imported before
          they can be used.
        </p></li></ol></div><p>
      The following code snippet illustrates declaring a module that
      exports a single function:
    </p><pre class="programlisting">from wb import *
import grt

ModuleInfo = DefineModule(name='MyModule', author="your name", version='1.0')

@ModuleInfo.export(grt.DOUBLE, grt.STRING, (grt.LIST, grt.DOUBLE))
def printListSum(message, doubleList):
   sum = 0
   for d in doubleList:
      sum = sum + d
   print message, sum
   return sum   </pre></div></body></html>


path: /wb-html-guitools/wb-view-tool.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.6.1.8. The View Tool</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-vertical-toolbar.html" title="7.6.1. The Vertical Toolbar"><link rel="prev" href="wb-table-tool.html" title="7.6.1.7. The Table Tool"><link rel="next" href="wb-routine-group-tool.html" title="7.6.1.9. The Routine Group Tool"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-view-tool"></a>7.6.1.8. The View Tool</h4></div></div></div><p>
        Use this tool to create a view on an EER Diagram canvas. When
        the table tool is activated, a schema list appears on the
        toolbar below the main menu, enabling you to associate the new
        view with a specific schema. You can also select a color for the
        object by choosing from the color list to the right of the
        schema list.
      </p><p>
        After selecting this tool, clicking the canvas creates a new
        view. To edit this view, right-click it and choose
        <span class="guimenuitem">Edit View...</span> or <span class="guimenuitem">Edit in
        New Window...</span> from the pop-up menu.
      </p><p>
        To activate the view tool from the keyboard, use the
        <span><strong class="keycap">V</strong></span> key.
      </p><p>
        For more information about creating and editing views, see
        <a href="wb-creating-views.html" title="7.7.3. Creating Views">Section 7.7.3, “Creating Views”</a>.
      </p></div></body></html>


path: /wb-html-guitools/wb-news-5-2-32.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.7. Changes in MySQL Workbench 5.2.32 (05 March 2011)</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="changes-5.2.x.html" title="A.1. Changes in Release 5.2"><link rel="prev" href="wb-news-5-2-33.html" title="A.1.6. Changes in MySQL Workbench 5.2.33 (11 March 2011)"><link rel="next" href="wb-news-5-2-31a.html" title="A.1.8. Changes in MySQL Workbench 5.2.31a (13 December 2010)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-news-5-2-32"></a>A.1.7. Changes in MySQL Workbench 5.2.32 (05 March 2011)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.2.31a.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        Changing the default schema now modifies the selected schema
        name to be bold.
       (Bug #57710, Bug #11764836)</p></li><li><p>
        In the SQL Editor, in the event of a crash, the content and
        state of script tabs was lost if not previously saved.
        MySQL Workbench now autosaves the content and state of the SQL
        Editor.
       (Bug #57667, Bug #11764794)</p></li><li><p>
        MySQL Workbench has been improved so that an errors are more clearly
        identified if they occur when synchronizing with a live server,
        or forward engineering to a live server.
       (Bug #55158, Bug #11762551)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        These query beautifier problems were corrected:
      </p><div class="itemizedlist"><ul type="circle"><li><p>
            Aggregate function text was deleted.
          </p></li><li><p>
            In the SQL Editor, the beautifier did not process functions
            such as <code class="literal">COUNT()</code> or
            <code class="literal">NOW()</code> or correctly. It rendered the
            function with additional spaces, causing a syntax error.
          </p></li></ul></div><p>(Bug #60070, Bug #11766850, Bug #59450, Bug #11766354, Bug #58714, Bug #11765722)</p></li><li><p>
        On Microsoft Windows 7, if a user profile launched MySQL Workbench,
        it crashed if additional user profiles attempted to launch it.
        The first instance needed to be closed before another user
        profile was able to run MySQL Workbench.
       (Bug #59913, Bug #11766733)</p></li><li><p>
        MySQL Workbench crashed when closing the query results tab in the
        SQL Editor.
       (Bug #59774, Bug #11766626)</p></li><li><p>
        When deleting a recursive foreign key constraint, the primary
        key was also mistakenly deleted.
       (Bug #59668, Bug #11766538)</p></li><li><p>
        On the Home screen, right-clicking a connection and selecting
        <span class="guimenu">Start Command Line Client</span> produced this
        error:
      </p><pre class="programlisting">Error calling
PyWbUtils.startCommandLineClientForConnection: see
output for details

output: 
Message: Error executing plugin wb.tools.comdlineClient:
error calling wb.tools.cmdlineClient
Traceback: 
File "C:\Program Files\MySQL\MySQL Workbench 5.2 CE\modules
\wb_utils_grt.py", line 96, in  
startCommandLineClientForConnection

schema = conn.parameterValues["schema"].replace("\\",
  "\\\\").replace('"', '\\"')
AttributeError: 'NoneType' object has no attribute 'replace'</pre><p>(Bug #59638, Bug #11766510)</p></li><li><p>
        Attempting to create a new server instance resulted in this
        error message:
      </p><pre class="programlisting">We are sorry for the inconvenience but an unexpected exception has
been raised by one of the MySQL Workbench modules. In order to fix
this issue we would kindly ask you to file a bug report. You can
do that by pressing the [Report Bug] button below.</pre><p>(Bug #59578, Bug #11766465)</p></li><li><p>
        In the EER Diagram view, clicking a table to edit its details
        sometimes resulted in this error:
      </p><pre class="programlisting">Cannot access a disposed object.
Object name: 'DockedWindowPlugin'      	</pre><p>(Bug #59559, Bug #11766448)</p></li><li><p>
        In the EER Diagram view, MySQL Workbench crashed on selecting a new
        table. This happened if the <span class="guilabel">Privileges</span> tab
        was open for the currently selected table.
       (Bug #59535, Bug #11766431)</p></li><li><p>
        In the SQL Editor, if a <code class="literal">'`'</code> (grave accent)
        character was entered, any subsequently entered control keys
        such as the arrow keys or the backspace key failed to function
        correctly.
       (Bug #59528, Bug #11766425)</p></li><li><p>
        Running the version of <span><strong class="command">mysqldump</strong></span> supplied
        with the MySQL Server package resulted in this error:
      </p><pre class="programlisting">Operation failed with exitcode -1073741819</pre><p>(Bug #59411)</p></li><li><p>
        The collapsed state of Workbench Central, on the Home screen,
        was not saved between MySQL Workbench sessions. If after collapsing
        Workbench Central to save vertical space, the application was
        exited and restarted, Workbench Central was drawn in the
        expanded state.
       (Bug #59399)</p></li><li><p>
        Attempting to create a new user with MySQL Workbench failed with
        this error:
      </p><pre class="programlisting">Unhandled exception: Error adding account accountName@%:</pre><p>(Bug #59000)</p></li><li><p>
        Generated scripts did not manage connection variables cleanly.
        For example, the <code class="literal">autocommit</code> state was not
        preserved by the script produced by forward engineering an SQL
        CREATE script. The script switched off
        <code class="literal">autocommit</code>, but did not then restore it
        correctly to its previous state.
       (Bug #58998, Bug #11765974)</p></li><li><p>
        On Windows, the Python debugger stopped the script being
        executed in MySQL Workbench after about one second. It then
        displayed the message "abort" in the output pane.
       (Bug #58960, Bug #11765943)</p></li><li><p>
        When a model was forward engineered, the primary keys were not
        created in the generated script.
       (Bug #58926, Bug #11765913)</p></li><li><p>
        SQL Editor did not load certain text files correctly, and
        inserted erroneous empty lines between text.
       (Bug #58850)</p></li><li><p>
        In the Administrator, when making a backup with the
        <code class="option">--single-transaction</code> option enabled, the
        <code class="option">--lock-tables</code> option was erroneously still
        enabled.
       (Bug #58562, Bug #11765579)</p></li><li><p>
        Trying to create a relationship between two tables, created in a
        plugin, produced this error:
      </p><pre class="programlisting">MySQL Workbench has encountered a problem
Es wurde versucht, im geschützten Speicher zu lesen oder zu schreiben. Dies ist häufig
ein Hinweis darauf, dass anderer Speicher beschädigt ist.</pre><p>(Bug #58554, Bug #11765571)</p></li><li><p>
        When synchronizing a model with a server, indexes were
        unnecessarily dropped and recreated.
       (Bug #58238, Bug #11765284)</p></li><li><p>
        Forward engineering a model containing two schema resulted in a
        generated script that contained incorrect SQL:
      </p><pre class="programlisting">DELIMITER ;USE `Schema2` ;      	</pre><p>
        The <code class="literal">DELIMITER</code> and <code class="literal">USE</code>
        statements should not have appeared on the same line.
       (Bug #58117, Bug #11765180)</p></li><li><p>
        When running MySQL Workbench with the arguments “<span class="quote">-script
        [FILE.lua] -quit-when-done</span>”, it crashed with this
        message:
      </p><pre class="programlisting">  [MySQL Workbench Unexpected Error]

  MySQL Workbench has encountered a problem

  Cannot access released / disposed object.
  Object name: "MainForm".</pre><p>(Bug #57570, Bug #11764708)</p></li><li><p>
        In the SQL Editor, switching between query tabs did not switch
        the associated results panel.
       (Bug #57486, Bug #11764628)</p></li><li><p>
        In the SQL Editor, when editing table data, this error dialog
        was displayed:
      </p><pre class="programlisting">Either schema or table is not selected.</pre><p>
        Each time the dialog was acknowledged, it was subsequently
        redisplayed, preventing further progress.
       (Bug #57127, Bug #11764305)</p></li><li><p>
        In the <span class="guilabel">Columns</span> tab of the table editor,
        copying and pasting the <span class="guilabel">Datatype</span> field
        using <span><strong class="keycap">Control+C</strong></span> and <span><strong class="keycap">Control+V</strong></span>
        resulted in the text “<span class="quote">table_copy1</span>” being pasted,
        rather than the copied datatype.
       (Bug #56501, Bug #11763749)</p></li><li><p>
        When exporting a model, if the <span class="guilabel">Skip Creation of
        FOREIGN KEYS</span> option was selected, indexes were not
        created.
       (Bug #56389, Bug #11763649)</p></li><li><p>
        At startup, MySQL Workbench displayed a blank screen if it had
        previously been closed after using the menu item
        <span class="guimenu">Help</span>, <span class="guimenu">System Info</span>, and
        then clicking the main application window close button.
       (Bug #55764, Bug #11763097)</p></li><li><p>
        When forward engineering a model, the generated script resulted
        in SQL errors when executed on the server. This happened when
        the following options were selected:
      </p><div class="itemizedlist"><ul type="circle"><li><p>
            DROP Objects Before Each CREATE Object
          </p></li><li><p>
            Omit Schema Qualifier in Object Names
          </p></li><li><p>
            Generate Separate CREATE INDEX Statements
          </p></li><li><p>
            Generate INSERT Statements for Tables
          </p></li></ul></div><p>(Bug #54836, Bug #11762262)</p></li><li><p>
        The generated alter script contained erroneous statements adding
        and deleting indexes and foreign keys.
       (Bug #54180, Bug #11761666)</p></li><li><p>
        The text in the SQL Editor was not anti-aliased, which hindered
        readability by causing the text to visually conflict with
        anti-aliased text elsewhere in MySQL Workbench.
       (Bug #54059, Bug #11761553)</p></li><li><p>
        On Microsoft Windows, if the Windows Firewall application was
        not running, installation of MySQL Workbench would halt with an
        error dialog indicating that it was unable to connect to the
        firewall.
       (Bug #53603, Bug #11761143)</p></li><li><p>
        Primary and foreign keys are now displayed with different icons.
       (Bug #53503, Bug #11761049)</p></li><li><p>
        Dropping a table from the <span class="guilabel">Object Browser</span>
        did not remove the table's icon.
       (Bug #52878, Bug #11760462)</p></li><li><p>
        There were numerous locations within MySQL Workbench where the
        availability of context-sensitive menus (right-clicking) was
        expected and useful, but not available.
       (Bug #49622, Bug #11757556)</p></li><li><p>
        Forward engineering a table containing a multiple-line comment
        resulted in this error:
      </p><pre class="programlisting">ERROR 1105 (HY000) at line 97: Too long comment for table 'motd'</pre><p>(Bug #38597)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-manage-server-configuration-tab.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>8.7.2. The Configuration Tab</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-server-administration-configuration.html" title="8.7. Server Administration and Configuration"><link rel="prev" href="wb-manage-server-startup-tab.html" title="8.7.1. The Startup Tab"><link rel="next" href="wb-manage-server-accounts-tab.html" title="8.7.3. The Accounts Tab"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-manage-server-configuration-tab"></a>8.7.2. The Configuration Tab</h3></div></div></div><p>
        The Configuration tab enables you to edit the
        <code class="filename">my.ini</code> or <code class="filename">my.cnf</code>
        configuration file by selecting check boxes and other GUI
        controls. This tab also features a number of subtabs, which
        provide access to various sub-sections within the configuration
        file. The subtabs are:
      </p><div class="itemizedlist"><ul type="disc"><li><p>
            General
          </p></li><li><p>
            MyISAM
          </p></li><li><p>
            InnoDB
          </p></li><li><p>
            Performance
          </p></li><li><p>
            Log Files
          </p></li><li><p>
            Replication
          </p></li><li><p>
            Networking
          </p></li><li><p>
            Security
          </p></li><li><p>
            Advanced
          </p></li></ul></div><div class="figure"><a name="wb-manage-server-configuration-tab-screenshot"></a><p class="title"><b>Figure 8.5. Administrator - Configuration Tab</b></p><div class="mediaobject"><img src="images/wb-manage-server-configuration-tab.png" width="1024" height="707" alt="Administrator - Configuration Tab"></div></div></div></body></html>


path: /wb-html-guitools/wb-routines.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.7.4.1. Routines</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-routines-routine-groups.html" title="7.7.4. Creating Routines and Routine Groups"><link rel="prev" href="wb-routines-routine-groups.html" title="7.7.4. Creating Routines and Routine Groups"><link rel="next" href="wb-routine-groups.html" title="7.7.4.2. Routine Groups"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-routines"></a>7.7.4.1. Routines</h4></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-routines.html#wb-add-routines">7.7.4.1.1. Adding Routines to the Physical Schemata</a></span></dt><dt><span class="section"><a href="wb-routines.html#wb-routine-editor">7.7.4.1.2. The Routine Editor</a></span></dt></dl></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="wb-add-routines"></a>7.7.4.1.1. Adding Routines to the Physical Schemata</h5></div></div></div><p>
        To add a routine, double-click the <code class="literal">Add
        Routine</code> icon in the <code class="literal">Physical
        Schemata</code> section of the <code class="literal">MySQL Model</code>
        page. The default name of the routine is
        <code class="literal">routine1</code>. If a routine with this name already
        exists, the new routine is named <code class="literal">routine2</code>.
      </p><p>
        Adding a new routine automatically opens the routine editor
        docked at the bottom of the application. For information about
        using the routine editor, see
        <a href="wb-routines.html#wb-routine-editor" title="7.7.4.1.2. The Routine Editor">Section 7.7.4.1.2, “The Routine Editor”</a>.
      </p><p>
        Right-clicking a routine opens a pop-up menu with the following
        items:
      </p><div class="itemizedlist"><ul type="disc"><li><p>
            <span class="guimenuitem">Rename</span>
          </p></li><li><p>
            <span class="guimenuitem">Cut
            '<em class="replaceable"><code>routine_name</code></em>'</span>
          </p></li><li><p>
            <span class="guimenuitem">Copy
            '<em class="replaceable"><code>routine_name</code></em>'</span>
          </p></li><li><p>
            <span class="guimenuitem">Paste</span>
          </p></li><li><p>
            <span class="guimenuitem">Edit Routine...</span>
          </p></li><li><p>
            <span class="guimenuitem">Edit in New Window...</span>
          </p></li><li><p>
            <span class="guimenuitem">Copy SQL to Clipboard</span>
          </p></li><li><p>
            <span class="guimenuitem">Delete
            '<em class="replaceable"><code>routine_name</code></em>'</span>
          </p></li></ul></div><p>
        The <span class="guimenuitem">Edit Routine...</span> item opens the
        routine editor.
      </p><p>
        The cut and paste items are useful for copying routines between
        different schemata.
      </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
          Deleting the code for a routine from the
          <span class="guilabel">Routines</span> tab of the Routine Group Editor
          results in removal of the routine object from the model.
        </p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
          To remove a routine from a routine group, use the controls on
          the <span class="guilabel">Routine Group</span> tab of the Routine
          Group Editor.
        </p></div><p>
        The action of the delete option varies depending upon how you
        have configured MySQL Workbench. For more information, see
        <a href="wb-preferences-model.html" title="5.4.4. The Model Tab">Section 5.4.4, “The Model Tab”</a>.
      </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="wb-routine-editor"></a>7.7.4.1.2. The Routine Editor</h5></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-routines.html#wb-routines-routine-tab">7.7.4.1.2.1. The Routine Tab</a></span></dt><dt><span class="section"><a href="wb-routines.html#wb-routine-editor-privileges">7.7.4.1.2.2. The Privileges Tab</a></span></dt></dl></div><p>
        To invoke the routine editor, double-click a routine in the
        <code class="literal">Physical Schemata</code> section on the
        <code class="literal">MySQL Model</code> page. This opens the routine
        editor docked at the bottom of the application. Any number of
        routines may be open at the same time. Each additional routine
        appears as a tab at the top of the routine editor.
      </p><p>
        <span class="guilabel">Routine</span> and <span class="guilabel">Privileges</span>
        tabs appear at the bottom of the routine editor. Navigate
        between different tabs using the mouse or from the keyboard by
        pressing <span><strong class="keycap">Control+Alt+Tab</strong></span>.
      </p><div class="section" lang="en"><div class="titlepage"><div><div><h6 class="title"><a name="wb-routines-routine-tab"></a>7.7.4.1.2.1. The Routine Tab</h6></div></div></div><p>
          Use the <span class="guilabel">Routine</span> tab of the routine editor
          to perform the following tasks:
        </p><div class="itemizedlist"><ul type="disc"><li><p>
              Rename the routine using the <span class="guilabel">Name</span>
              field.
            </p></li><li><p>
              Enter the SQL to create a routine using the
              <span class="guilabel">SQL</span> field.
            </p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h6 class="title"><a name="wb-routine-editor-privileges"></a>7.7.4.1.2.2. The Privileges Tab</h6></div></div></div><p>
          The <span class="guilabel">Privileges</span> tab of the routine editor
          functions in exactly the same way as the
          <span class="guilabel">Privileges</span> tab of the table editor. For
          more information, see
          <a href="wb-table-editor.html#wb-table-editor-privileges-tab" title="7.7.1.3.10. The Privileges Tab">Section 7.7.1.3.10, “The Privileges Tab”</a>.
        </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
            Privileges are available only in the Standard Edition of
            MySQL Workbench.
          </p></div></div></div></div></body></html>


path: /wb-html-guitools/wb-view-editor.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.7.3.3. The View Editor</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-creating-views.html" title="7.7.3. Creating Views"><link rel="prev" href="wb-using-view-tool.html" title="7.7.3.2. Adding Views to an EER Diagram"><link rel="next" href="wb-modifying-view.html" title="7.7.3.4. Modifying a View Using the Properties Palette"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-view-editor"></a>7.7.3.3. The View Editor</h4></div></div></div><p>
      To invoke the view editor, double-click a view object on the EER
      Diagram canvas or double-click a view in the <code class="literal">Physical
      Schemata</code> section on the <code class="literal">MySQL Model</code>
      page. This opens the view editor docked at the bottom of the
      application. Double-clicking the title bar undocks the editor. Do
      the same to redock it. Any number of views may be open at the same
      time. Each additional view appears as a tab at the top of the view
      editor.
    </p><p>
      There are three tabs at the bottom of the view editor:
      <span class="guilabel">View</span>, <span class="guilabel">Comments</span>, and
      <span class="guilabel">Privileges</span>. Navigate between different tabs
      using the mouse or from the keyboard by pressing
      <span><strong class="keycap">Control+Alt+Tab</strong></span>.
    </p><p>
      <span class="bold"><strong>The View Tab</strong></span>
    </p><p>
      Use the <span class="guilabel">View</span> tab to perform the following
      tasks:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          Rename the view using the <span class="guilabel">Name</span> text box.
        </p></li><li><p>
          Enter the SQL to create a view using the
          <span class="guilabel">SQL</span> field.
        </p></li><li><p>
          Comment a view using the <span class="guilabel">Comments</span> text
          area.
        </p></li></ul></div><p>
      <span class="bold"><strong>The Comments Tab</strong></span>
    </p><p>
      This tab enables you to enter comments for a particular view.
    </p><p>
      <span class="bold"><strong>The Privileges Tab</strong></span>
    </p><p>
      The <span class="guilabel">Privileges</span> tab of the view editor
      functions in exactly the same way as the
      <span class="guilabel">Privileges</span> tab of the table editor. For more
      information, see <a href="wb-table-editor.html#wb-table-editor-privileges-tab" title="7.7.1.3.10. The Privileges Tab">Section 7.7.1.3.10, “The Privileges Tab”</a>.
    </p></div></body></html>


path: /wb-html-guitools/license-cairo.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>B.4. Cairo License</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-third-party-licenses.html" title="Appendix B. Third Party Licenses"><link rel="prev" href="license-boost.html" title="B.3. Boost Library License"><link rel="next" href="license-ctemplate.html" title="B.5. CTemplate (Google Template System) License"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="license-cairo"></a>B.4. Cairo License</h2></div></div></div><p>
    The following software may be included in this product:
  </p><pre class="programlisting">Cairo

You are receiving a copy of the Cairo in both source 
and object code in the following DLL (libcairo.dll) or 
dynamic libraries 
(MySQLWorkbench.app/Contents/Frameworks/libcairo.2.dylib 
and MySQLWorkbench.app/Contents/Frameworks/libpixman-1.0.dylib). 
The terms of the Oracle license do NOT apply to Cairo; 
Oracle distributes it under the GNU Lesser General Public 
License Version 2.1 separately from the Oracle programs you 
receive. You can also separately obtain and use Cairo 
independent of the Oracle programs under a dual license 
subject to the terms of the LGPL or the Mozilla Public 
License Version 1.1. If you do not wish to install this 
program, you may delete libcairo.dll or libcairo.2.dylib 
and libpixman-1.0.dylib from the installation directory
or uninstall MySQL Workbench completely. </pre><p>
    This component is licensed under
    <a href="license-gnu-lgpl-2-1.html" title="B.11. GNU Lesser General Public License Version 2.1, February 1999">Section B.11, “GNU Lesser General Public License Version 2.1, February 1999”</a>.
  </p></div></body></html>


path: /wb-html-guitools/wb-installing.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Chapter 3. Installing and Launching MySQL Workbench</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="index.html" title="MySQL Workbench"><link rel="prev" href="wb-editions.html" title="Chapter 2. MySQL Workbench Editions"><link rel="next" href="wb-requirements-hardware.html" title="3.1. Hardware Requirements"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="wb-installing"></a>Chapter 3. Installing and Launching MySQL Workbench</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="wb-requirements-hardware.html">3.1. Hardware Requirements</a></span></dt><dt><span class="section"><a href="wb-requirements-software.html">3.2. Software Requirements</a></span></dt><dt><span class="section"><a href="wb-starting.html">3.3. Starting MySQL Workbench</a></span></dt><dd><dl><dt><span class="section"><a href="wb-installing-windows.html">3.3.1. Installing MySQL Workbench on Windows</a></span></dt><dt><span class="section"><a href="wb-launching-windows.html">3.3.2. Launching MySQL Workbench on Windows</a></span></dt><dt><span class="section"><a href="wb-windows-uninstalling.html">3.3.3. Uninstalling MySQL Workbench on Windows</a></span></dt><dt><span class="section"><a href="wb-installing-linux.html">3.3.4. Installing MySQL Workbench on Linux</a></span></dt><dt><span class="section"><a href="wb-launching-linux.html">3.3.5. Launching MySQL Workbench on Linux</a></span></dt><dt><span class="section"><a href="wb-linux-uninstalling.html">3.3.6. Uninstalling MySQL Workbench on Linux</a></span></dt><dt><span class="section"><a href="wb-installing-mac.html">3.3.7. Installing MySQL Workbench on Mac OS X</a></span></dt><dt><span class="section"><a href="wb-launching-osx.html">3.3.8. Launching MySQL Workbench on Mac OS X</a></span></dt><dt><span class="section"><a href="wb-mac-uninstalling.html">3.3.9. Uninstalling MySQL Workbench on Mac OS X</a></span></dt></dl></dd><dt><span class="section"><a href="wb-launching-activation.html">3.4. Activation Procedure (Commercial Version)</a></span></dt></dl></div><p>
    MySQL Workbench is available for the following platforms:
  </p><div class="itemizedlist"><ul type="disc"><li><p>
        Windows
      </p></li><li><p>
        Linux
      </p></li><li><p>
        Mac OS X
      </p></li></ul></div><p>
    Binary distributions of MySQL Workbench are available for the preceding
    platforms. Source code distributions are also available as a
    <code class="filename">tar.gz</code> package or an RPM package.
  </p><p>
    The following sections explain the installation process for each of
    these platforms.
  </p></div></body></html>


path: /wb-html-guitools/wb-general-validation.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.10.1. General Validation</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-validation-plugins.html" title="7.10. MySQL Workbench Schema Validation Plugins (Commercial Version)"><link rel="prev" href="wb-validation-plugins.html" title="7.10. MySQL Workbench Schema Validation Plugins (Commercial Version)"><link rel="next" href="wb-mysql-validation.html" title="7.10.2. MySQL-Specific Validation"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-general-validation"></a>7.10.1. General Validation</h3></div></div></div><p>
      The following list names the general validation types and gives
      examples of specific violations:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <span class="bold"><strong>Empty Content Validation</strong></span>
        </p><div class="itemizedlist"><ul type="circle"><li><p>
              A table with no columns
            </p></li><li><p>
              A routine or view with no SQL code defined
            </p></li><li><p>
              A routine group containing no routines
            </p></li><li><p>
              A table, view, or routine not referenced by at least one
              role
            </p></li><li><p>
              A user with no privileges
            </p></li><li><p>
              Objects such as tables that do not appear on at least one
              EER Diagram
            </p></li></ul></div></li><li><p>
          <span class="bold"><strong>Table Efficiency Validation</strong></span>
        </p><div class="itemizedlist"><ul type="circle"><li><p>
              A table with no primary key
            </p></li><li><p>
              A primary key that does not use an integer-based data type
            </p></li><li><p>
              A foreign key that refers to a column with a different
              data type
            </p></li></ul></div></li><li><p>
          <span class="bold"><strong>Duplicated Identifiers
          Validation</strong></span>
        </p><div class="itemizedlist"><ul type="circle"><li><p>
              Duplicate object names
            </p></li><li><p>
              Duplicate role or user names
            </p></li><li><p>
              Duplicate index or routine names
            </p></li></ul></div></li><li><p>
          <span class="bold"><strong>Consistency Validation</strong></span>
        </p><div class="itemizedlist"><ul type="circle"><li><p>
              Use of the same column with columns of differing data
              types
            </p></li></ul></div></li><li><p>
          <span class="bold"><strong>Logic Validation</strong></span>
        </p><div class="itemizedlist"><ul type="circle"><li><p>
              A foreign key that refers to a column other than the
              primary key in the source table
            </p></li><li><p>
              Any object that is object is either read only or write
              only by role definition
            </p></li><li><p>
              Placeholder objects left over from reverse engineering
            </p></li></ul></div></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-news-5-2-24.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.16. Changes in MySQL Workbench 5.2.24 (21 June 2010)</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="changes-5.2.x.html" title="A.1. Changes in Release 5.2"><link rel="prev" href="wb-news-5-2-25.html" title="A.1.15. Changes in MySQL Workbench 5.2.25 (30 June 2010 General Availability)"><link rel="next" href="wb-news-5-2-23.html" title="A.1.17. Changes in MySQL Workbench 5.2.23 (Internal release only)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-news-5-2-24"></a>A.1.16. Changes in MySQL Workbench 5.2.24 (21 June 2010)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.2.23.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        A <span class="guibutton">Kill Query</span> button has been added to the
        <span class="guilabel">Connections</span> tab of the Administrator.
       (Bug #54409)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        In the <span class="guilabel">Configuration</span> tab of the
        Administrator, this error resulted when changes were applied:
      </p><pre class="programlisting">Could not Save Configuration File

There was an error saving the configurationfile: exec_cmd() takes at least 3 arguments (2
given)</pre><p>
        This happened while connecting to a FreeBSD 7.1 server over an
        SSH connection.
       (Bug #54647)</p></li><li><p>
        In the SQL Editor, entering a space into the <span class="guilabel">SQL
        Query</span> tab, selecting an external tab (such as the
        <span class="guilabel">Overview</span> tab or <span class="guilabel">Output</span>
        tab), and then selecting <span class="guimenu">File</span>, <span class="guimenu">Close
        Tab</span> caused MySQL Workbench to crash.
      </p><p>
        Further, the <span class="guilabel">Add Table</span> dialog had numerous
        issues, including inability to select PK and other check boxes,
        failure to validate input, inability to apply changes, and
        deletion of user data in certain cases.
       (Bug #54124)</p></li><li><p>
        The <span class="guilabel">Connections</span> tab in the Administrator
        did not feature automatic refresh. This had to be manually
        triggered using the <span class="guibutton">Refresh</span> button.
        Further, the <span class="guibutton">Kill Connection</span> button was
        sometimes incorrectly disabled.
       (Bug #53703)</p></li><li><p>
        If a foreign key relationship was created, and its
        <code class="literal">modelOnly</code> property set, the relationship was
        correctly excluded when the model was synchronized with a live
        database. However, the DDL code for the foreign key indexes was
        still generated in the synchronization script.
       (Bug #53420)</p></li><li><p>
        Synchronizing a model with a live database generated
        <code class="literal">ALTER</code> statements, even when there appeared to
        be no difference between the database and the model.
       (Bug #50938)</p></li><li><p>
        In the SQL Editor, there was a space between the
        <span class="guibutton">Execute</span> and <span class="guibutton">Stop</span>
        toolbar buttons. Hovering the mouse cursor over this space
        resulted in the tooltip “<span class="quote">Explain selected SQL</span>”
        being displayed, which appeared to indicate a missing icon.
       (Bug #49316)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-installing-mac.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>3.3.7. Installing MySQL Workbench on Mac OS X</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-starting.html" title="3.3. Starting MySQL Workbench"><link rel="prev" href="wb-linux-uninstalling.html" title="3.3.6. Uninstalling MySQL Workbench on Linux"><link rel="next" href="wb-launching-osx.html" title="3.3.8. Launching MySQL Workbench on Mac OS X"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-installing-mac"></a>3.3.7. Installing MySQL Workbench on Mac OS X</h3></div></div></div><p>
        MySQL Workbench for Mac OS X is distributed as a DMG file. The file
        is named
        <code class="filename">mysql-workbench-oss-<em class="replaceable"><code>version</code></em>-osx10.5-i686.dmg</code>,
        where <em class="replaceable"><code>version</code></em> is the MySQL Workbench
        version.
      </p><p>
        To install MySQL Workbench on Mac OS X, download the file.
        Double-click the downloaded file. You will be presented with the
        installation window.
      </p><div class="figure"><a name="wb-installing-mac-install-screen"></a><p class="title"><b>Figure 3.1. MySQL Workbench Mac OS X Installation Window</b></p><div class="mediaobject"><img src="images/wb-installing-mac-install-screen.png" width="526" height="416" alt="MySQL Workbench Mac OS X Installation
            Window"></div></div><p>
        Drag the MySQL Workbench icon onto the Applications icon as
        instructed. MySQL Workbench is now installed.
      </p><p>
        You can now launch MySQL Workbench from the Applications folder.
      </p></div></body></html>


path: /wb-html-guitools/wb-creating-eer-diagram.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.8.1.1. Adding an EER Diagram</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-importing-sql-script.html" title="7.8.1. Importing a Data Definition SQL Script"><link rel="prev" href="wb-importing-sql-script.html" title="7.8.1. Importing a Data Definition SQL Script"><link rel="next" href="wb-default-schema.html" title="7.8.2. Using the Default Schema"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-creating-eer-diagram"></a>7.8.1.1. Adding an EER Diagram</h4></div></div></div><p>
        To create an EER diagram for the <code class="literal">sakila</code>
        database, first add an EER diagram by double-clicking the
        <code class="literal">Add Diagram</code> icon in the <span class="guilabel">EER
        Diagrams</span> panel to create and open a new <code class="literal">EER
        Diagram</code> editor.
      </p><p>
        The <code class="literal">EER Diagram</code> canvas is where object
        modeling takes place. To add a table to the canvas, select the
        <span class="guilabel">Catalog</span> tab in the middle panel on the
        right side of the application to display any schemata that
        appear in the <span class="guilabel">MySQL Model</span> tab. Find the
        <code class="literal">sakila</code> schema and expand the view of its
        objects by clicking the <span class="guibutton">+</span> button to the
        left of the schema name. Expand the tables list in the same way.
      </p><p>
        You can add tables to the EER canvas by dragging them from the
        <span class="guilabel">Catalog</span> panel dropping them onto the
        canvas. Drop the <code class="literal">address</code> table and the
        <code class="literal">city</code> table onto the canvas.
      </p><div class="figure"><a name="wb-sakila-tutorial-image"></a><p class="title"><b>Figure 7.42. Adding Tables to the Canvas</b></p><div class="mediaobject"><img src="images/wb-sakila-tutorial.png" width="443" height="254" alt="Adding tables to the canvas"></div></div><p>
        MySQL Workbench automatically discovers that
        <code class="literal">address.city_id</code> has been defined as a foreign
        key referencing the <code class="literal">city.city_id</code> field. Drop
        the <code class="literal">country</code> table onto the canvas and
        immediately you should see the relationship between the
        <code class="literal">country</code> table and the <code class="literal">city</code>
        table. (To view all the relationships in the
        <code class="literal">sakila</code> database, see
        <a href="wb-sakila-eer-png.html#wb-sakila-eer-image" title="Figure 7.45. The sakila Database EER Diagram">Figure 7.45, “The <code class="literal">sakila</code> Database EER Diagram”</a>.)
      </p><p>
        Click the <span class="guilabel">Properties</span> tab of the panel on
        the lower right, then click one of the tables on the canvas.
        This displays the properties of the table in the
        <code class="literal">Properties</code> window. While a table is selected,
        you can use the <code class="literal">Properties</code> window to change a
        table's properties. For example, entering
        <code class="literal">#FF0000</code> for the color value will change the
        color accent to red.
      </p><p>
        Changing the color of a table is a good way to identify a table
        quickly—something that becomes more important as the
        number of tables increases. Changing the color of a table is
        also an easy way to identify a table in the <code class="literal">Model
        Navigator</code> panel. This panel, the uppermost panel on
        the left side of the page, gives a bird's eye view of the entire
        EER canvas.
      </p><p>
        Save your changes to a <code class="literal">MySQL Workbench Models</code>
        file (<code class="filename">mwb</code> extension) by choosing
        <span class="guimenuitem">Save</span> from the <span class="guimenu">File</span>
        menu or by using the keyboard command
        <span><strong class="keycap">Control+S</strong></span>.
      </p></div></body></html>


path: /wb-html-guitools/wb-basic-modeling.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.8.3. Basic Modeling</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-tutorials.html" title="7.8. Modeling Tutorials"><link rel="prev" href="wb-create-schema-objects.html" title="7.8.2.2. Creating Other Schema Objects"><link rel="next" href="wb-basic-add-table.html" title="7.8.3.1. Adding a Table"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-basic-modeling"></a>7.8.3. Basic Modeling</h3></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-basic-add-table.html">7.8.3.1. Adding a Table</a></span></dt><dt><span class="section"><a href="wb-basic-foreign-key.html">7.8.3.2. Creating a Foreign Key</a></span></dt></dl></div><p>
      On the <code class="literal">MySQL Model</code> page, double-click the
      <span class="guilabel">Add Diagram</span> icon. This creates and opens a
      new <code class="literal"> EER Diagram</code> canvas.
    </p><div class="figure"><a name="wb-add-eer-diagram"></a><p class="title"><b>Figure 7.44. Adding an EER Diagram</b></p><div class="mediaobject"><img src="images/wb-add-eer-diagram.png" width="126" height="125" alt="Adding an EER Diagram"></div></div><p>
      From an EER diagram page you can graphically design a database.
    </p></div></body></html>


path: /wb-html-guitools/license-pixman.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>B.17. Pixman License</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-third-party-licenses.html" title="Appendix B. Third Party Licenses"><link rel="prev" href="license-pcre.html" title="B.16. PCRE License"><link rel="next" href="license-pycrypto.html" title="B.18. PyCrypto License"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="license-pixman"></a>B.17. Pixman License</h2></div></div></div><p>
    The following software may be included in this product:
  </p><pre class="programlisting">Pixman

Pixman v0.21.2
The following is the MIT license, agreed upon by most 
contributors. Copyright holders of new code should use 
this license statement where possible. They may also add 
themselves to the list below.

 Copyright 1987, 1988, 1989, 1998  The Open Group
 Copyright 1987, 1988, 1989 Digital Equipment Corporation
 Copyright 1999, 2004, 2008 Keith Packard
 Copyright 2000 SuSE, Inc.
 Copyright 2000 Keith Packard, member of The XFree86 Project, Inc.
 Copyright 2004, 2005, 2007, 2008, 2009, 2010 Red Hat, Inc.
 Copyright 2004 Nicholas Miell
 Copyright 2005 Lars Knoll &amp; Zack Rusin, Trolltech
 Copyright 2005 Trolltech AS
 Copyright 2007 Luca Barbato
 Copyright 2008 Aaron Plattner, NVIDIA Corporation
 Copyright 2008 Rodrigo Kumpera
 Copyright 2008 André Tupinambá
 Copyright 2008 Mozilla Corporation
 Copyright 2008 Frederic Plourde
 Copyright 2009, Oracle and/or its affiliates. All rights reserved.

 Permission is hereby granted, free of charge, to any 
person obtaining a copy of this software and associated 
documentation files (the "Software"), to deal in the Software 
without restriction, including without limitation the rights 
to use, copy, modify, merge, publish, distribute, sublicense, 
and/or sell copies of the Software, and to permit persons to 
whom the Software is furnished to do so, subject to the 
following conditions:

 The above copyright notice and this permission notice 
(including the next paragraph) shall be included in all 
copies or substantial portions of the Software.
 
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF 
ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED 
TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A 
PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT 
SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR 
ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN 
ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE 
OR OTHER DEALINGS IN THE SOFTWARE.

Pixman v0.17.4 and lower:
The following is the 'standard copyright' agreed upon 
by most contributors, and is currently the canonical 
icense, though a modification is currently under 
discussion.  Copyright holders of new code should use 
this license statement where possible, and append their 
name to this list.  

Copyright 1987, 1988, 1989, 1998  The Open Group
Copyright 1987, 1988, 1989 Digital Equipment Corporation
Copyright 1999, 2004, 2008 Keith Packard
Copyright 2000 SuSE, Inc.
Copyright 2000 Keith Packard, member of The XFree86 Project, Inc.
Copyright 2004, 2005, 2007, 2008 Red Hat, Inc.
Copyright 2004 Nicholas Miell
Copyright 2005 Lars Knoll &amp; Zack Rusin, Trolltech
Copyright 2005 Trolltech AS
Copyright 2007 Luca Barbato
Copyright 2008 Aaron Plattner, NVIDIA Corporation
Copyright 2008 Rodrigo Kumpera
Copyright 2008 AndrÃ© TupinambÃ¡
Copyright 2008 Mozilla Corporation
Copyright 2008 Frederic Plourde
Copyright 2009 Sun Microsystems, Inc.

Permission is hereby granted, free of charge, to 
any person obtaining a copy of this software and 
associated documentation files (the "Software"), 
to deal in the Software without restriction, including 
without limitation the rights to use, copy, modify, 
merge, publish, distribute, sublicense, and/or sell 
copies of the Software, and to permit persons to whom 
the Software is furnished to do so, subject to the 
following conditions:

The above copyright notice and this permission notice
(including the next paragraph) shall be included in 
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF 
ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED 
TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A 
PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT 
SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR 
ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN 
ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE 
OR OTHER DEALINGS IN THE SOFTWARE.</pre></div></body></html>


path: /wb-html-guitools/license-libzip.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>B.14. Libzip License</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-third-party-licenses.html" title="Appendix B. Third Party Licenses"><link rel="prev" href="license-libxml2.html" title="B.13. Libxml2 License"><link rel="next" href="license-lua.html" title="B.15. Lua (liblua) License"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="license-libzip"></a>B.14. Libzip License</h2></div></div></div><p>
    The following software may be included in this product:
  </p><pre class="programlisting">
libzip

Copyright (C) 1999-2008 Dieter Baron and Thomas Klausner
The authors can be contacted at &lt;libzip@nih.at&gt;

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:

1. Redistributions of source code must retain the above copyright
   notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
   notice, this list of conditions and the following disclaimer in
   the documentation and/or other materials provided with the
   distribution.
3. The names of the authors may not be used to endorse or promote
   products derived from this software without specific prior
   written permission.

THIS SOFTWARE IS PROVIDED BY THE AUTHORS "AS IS" AND ANY EXPRESS
OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER
IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
</pre></div></body></html>


path: /wb-html-guitools/license-libxml2.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>B.13. Libxml2 License</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-third-party-licenses.html" title="Appendix B. Third Party Licenses"><link rel="prev" href="license-html-renderer.html" title="B.12. HtmlRenderer (System.Drawing.Html)"><link rel="next" href="license-libzip.html" title="B.14. Libzip License"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="license-libxml2"></a>B.13. Libxml2 License</h2></div></div></div><p>
    The following software may be included in this product:
  </p><pre class="programlisting">Libxml2

Except where otherwise noted in the source code (e.g. 
the files hash.c, list.c and the trio files, which are 
covered by a similar licence but with different Copyright 
notices) all the files are:

 Copyright (C) 1998-2003 Daniel Veillard.  All Rights Reserved.

Permission is hereby granted, free of charge, to any 
person obtaining a copy of this software and associated 
documentation files (the "Software"), to deal in the 
Software without restriction, including without limitation 
the rights to use, copy, modify, merge, publish, distribute, 
sublicense, and/or sell copies of the Software, and to 
permit persons to whom the Software is furnished to do so, 
subject to the following conditions:

The above copyright notice and this permission notice 
shall be included in all copies or substantial portions 
of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF 
ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED 
TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A 
PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT 
SHALL THE DANIEL VEILLARD BE LIABLE FOR ANY CLAIM, 
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF 
CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR 
IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER 
DEALINGS IN THE SOFTWARE.

Except as contained in this notice, the name of Daniel 
Veillard shall not be used in advertising or otherwise 
to promote the sale, use or other dealings in this 
Software without prior written authorization from him.</pre></div></body></html>


path: /wb-html-guitools/wb-manage-db-connections.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>6.6. Manage DB Connections Dialog</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-sql-development.html" title="Chapter 6. SQL Development"><link rel="prev" href="wb-sql-development-manage-connections.html" title="6.5. Manage Connections"><link rel="next" href="wb-manage-db-connections-vault.html" title="6.6.1. The Password Storage Vault"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="wb-manage-db-connections"></a>6.6. Manage DB Connections Dialog</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-manage-db-connections-vault.html">6.6.1. The Password Storage Vault</a></span></dt><dt><span class="section"><a href="wb-manage-db-connections-standard.html">6.6.2. Standard TCP/IP Connection</a></span></dt><dt><span class="section"><a href="wb-manage-db-connections-socket.html">6.6.3. Local Socket/Pipe Connection</a></span></dt><dt><span class="section"><a href="wb-manage-db-connections-ssh.html">6.6.4. Standard TCP/IP over SSH Connection</a></span></dt></dl></div><p>
    MySQL Workbench provides a Manage DB Connections dialog for creating and
    managing connections to servers. The connections created can then be
    used from the wizards that must connect to a server, such as the
    wizard used to reverse engineer a live database. However, it is
    still possible to set connection parameters from these wizards if
    required, without invoking the Manage DB Connections dialog
    directly.
  </p><p>
    The Manage DB Connections dialog is invoked by selecting
    <span class="guimenu">Database</span>, <span class="guimenuitem">Manage
    Connections</span> from the main menu. It can also be invoked
    from any of the wizards requiring access to a live database. This is
    achieved by using the <span class="guilabel">Manage Stored Connections</span>
    item, found in the wizard's <span class="guilabel">Stored Connection</span>
    list.
  </p><p>
    After the Manage DB Connections dialog is launched, you are
    presented with the following dialog, which enables you to create or
    delete connections.
  </p><div class="figure"><a name="wb-manage-db-connections-dialog"></a><p class="title"><b>Figure 6.1. Manage DB Connections - Dialog</b></p><div class="mediaobject"><img src="images/wb-manage-db-connections-dialog.png" width="898" height="498" alt="Manage DB Connections - Dialog"></div></div><p>
    Click <span class="guibutton">New</span> to create a new connection. Once
    created, the connection can be selected from the <span class="guilabel">Stored
    Connections</span> list. You can then set various parameters for
    the connection, including the following:
  </p><div class="itemizedlist"><ul type="disc"><li><p>
        <span class="guilabel">Connection Name</span>: The name used to refer to
        this connection. This connection can then be selected from a
        list in other wizards requiring a connection.
      </p></li><li><p>
        <span class="guilabel">Connection Method</span>: The methods available
        are Standard TCP/IP, Local Socket/Pipe, and Standard TCP/IP over
        SSH.
      </p></li></ul></div><p>
    After you select a connection method, the fields available in the
    <span class="guilabel">Parameters</span> tab and the
    <span class="guilabel">Advanced</span> tab of the dialog changes accordingly.
    More details about these options and parameters are available in the
    following sections.
  </p><p>
    After all parameters have been set as required, you can click the
    <span class="guibutton">Test Connection</span> button to test the connection
    to the live server. After you are satisfied that the connection
    works as expected, you can close the wizard by clicking the
    <span class="guibutton">Close</span> button. The stored connection then is
    available for use from any of the wizards requiring a connection to
    a live server.
  </p><p>
    You can duplicate an existing connection using the
    <span class="guibutton">Duplicate</span> button. This is an easy way to
    begin setting up a new connection that differs only slightly from an
    existing one.
  </p></div></body></html>


path: /wb-html-guitools/wb-plugins.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>9.3. Plugins</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-extending.html" title="Chapter 9. Extending Workbench"><link rel="prev" href="wb-modules.html" title="9.2. Modules"><link rel="next" href="wb-mforms.html" title="9.4. Adding a GUI to a Plugin Using MForms"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="wb-plugins"></a>9.3. Plugins</h2></div></div></div><p>
      Plugins are special Modules that are exposed to the user through
      the Workbench GUI. This is typically done using the main menu, or
      the context-sensitive menu. Much of the MySQL Workbench functionality
      is implemented using plugins; for example, table, view, and
      routine editors are native C++ plugins, as are the forward and
      reverse engineering wizards. The Administrator facility in
      MySQL Workbench is implemented entirely as a plugin in Python.
    </p><p>
      A plugin can be a simple function that performs some action on an
      input, and ends without further interaction with the user.
      Examples of this include auto-arranging a diagram, or making batch
      changes to objects. To create a simple plugin, the function must
      be located in a module and declared as a plugin using the
      <code class="literal">plugin</code> decorator of the
      <code class="literal">ModuleInfo</code> object.
    </p><p>
      Plugins can have an indefinite runtime, such as when they are
      driven by the user through a graphical user interface. This is the
      case for the various object editors and wizards within
      MySQL Workbench. Although this latter type of plugin must be declared
      in the usual way, only the entry point of the plugin will need to
      be executed in the plugin function, as most of the additional
      functionality will be invoked as a result of the user interacting
      with the GUI.
    </p><p>
      Declare a plugin using this syntax:
    </p><pre class="programlisting">@ModuleInfo.plugin(plugin_name, caption, [input], [groups], [pluginMenu])</pre><p>
      These parameters are defined as follows:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <span class="bold"><strong>plugin_name</strong></span>: A unique name
          for the plugin. It may contain only alphanumeric characters,
          dots, and underscores.
        </p></li><li><p>
          <span class="bold"><strong>caption</strong></span>: A caption to use for
          the plugin in menus.
        </p></li><li><p>
          <span class="bold"><strong>input</strong></span>: An optional list of
          input arguments.
        </p></li><li><p>
          <span class="bold"><strong>groups</strong></span>: Optional list of
          groups the plugin belongs to. Recognized values are:
        </p><div class="itemizedlist"><ul type="circle"><li><p>
              <code class="literal">Overview/Utility</code>: The
              <span class="guimenu">Context</span> menu in the Model Overview.
            </p></li><li><p>
              <code class="literal">Model/Utility</code>: The menu for diagram
              objects.
            </p></li><li><p>
              <code class="literal">Menu/&lt;category&gt;</code>: The
              <span class="guimenu">Plugins</span> menu in the main menu.
            </p></li></ul></div></li><li><p>
          <span class="bold"><strong>pluginMenu</strong></span>: Optional name of
          a submenu in the Plugins menu where the plugin should appear.
          For example, <span class="guisubmenu">Catalog</span>,
          <span class="guisubmenu">Objects</span>,
          <span class="guisubmenu">Utiities</span>. This is equivalent to
          adding a <code class="literal">Menu/&lt;category&gt;</code> in the
          groups list.
        </p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-linux-uninstalling.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>3.3.6. Uninstalling MySQL Workbench on Linux</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-starting.html" title="3.3. Starting MySQL Workbench"><link rel="prev" href="wb-launching-linux.html" title="3.3.5. Launching MySQL Workbench on Linux"><link rel="next" href="wb-installing-mac.html" title="3.3.7. Installing MySQL Workbench on Mac OS X"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-linux-uninstalling"></a>3.3.6. Uninstalling MySQL Workbench on Linux</h3></div></div></div><p>
        The procedure for uninstalling MySQL Workbench on Linux depends on
        the package you are using.
      </p><p>
        <span class="bold"><strong>Uninstalling DEB packages</strong></span>
      </p><p>
        To uninstall a Debian package, use this command:
      </p><pre class="programlisting">shell&gt; <strong class="userinput"><code>sudo dpkg -r mysql-workbench-oss</code></strong>
</pre><p>
        This command does not remove the configuration files. If you
        wish to also remove the configuration files, use this command:
      </p><pre class="programlisting">shell&gt; <strong class="userinput"><code>sudo dpkg --purge mysql-workbench-oss</code></strong>
</pre><p>
        <span class="bold"><strong>Uninstalling RPM packages</strong></span>
      </p><p>
        To uninstall an RPM package, use this command:
      </p><pre class="programlisting">shell&gt; <strong class="userinput"><code>sudo rpm -e mysql-workbench-oss</code></strong>
</pre><p>
        This command does not remove the configuration files.
      </p></div></body></html>


path: /wb-html-guitools/wb-news-5-1-11.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.2.9. Changes in MySQL Workbench 5.1.11 (Not yet released)</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="changes-5.1.x.html" title="A.2. Changes in Release 5.1"><link rel="prev" href="wb-news-5-1-12.html" title="A.2.8. Changes in MySQL Workbench 5.1.12 (27 April 2009)"><link rel="next" href="wb-news-5-1-10.html" title="A.2.10. Changes in MySQL Workbench 5.1.10 (10 April 2009)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-news-5-1-11"></a>A.2.9. Changes in MySQL Workbench 5.1.11 (Not yet released)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.1.10.
      </p><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        MySQL Workbench crashed when attempting to delete an EER diagram
        from the <span class="guilabel">EER Diagrams</span> section of the main
        project tab.
       (Bug #44245)</p></li><li><p>
        When using MySQL Workbench on Linux, if a new layer was created it
        was not possible to then change the layer's name in the
        Properties tab.
       (Bug #44202)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-manage-server-export-to-disk.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>8.7.6.1. Export to Disk</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-manage-server-data-dump-tab.html" title="8.7.6. The Data Dump Tab"><link rel="prev" href="wb-manage-server-data-dump-tab.html" title="8.7.6. The Data Dump Tab"><link rel="next" href="wb-manage-server-import-from-disk.html" title="8.7.6.2. Import from Disk"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-manage-server-export-to-disk"></a>8.7.6.1. Export to Disk</h4></div></div></div><p>
          The Export to Disk tab enables you to select the schema and
          tables to export. You also have the option to export tables to
          their own files, or all tables to a single file. Exporting
          tables to individual files enables you to restore on a
          per-table basis.
        </p><div class="figure"><a name="wb-manage-server-data-dump-tab-screenshot"></a><p class="title"><b>Figure 8.9. Administrator - Export to Disk</b></p><div class="mediaobject"><img src="images/wb-manage-server-data-dump-tab.png" width="1024" height="707" alt="Administrator - Export to Disk"></div></div></div></body></html>


path: /wb-html-guitools/wb-installing-windows.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>3.3.1. Installing MySQL Workbench on Windows</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-starting.html" title="3.3. Starting MySQL Workbench"><link rel="prev" href="wb-starting.html" title="3.3. Starting MySQL Workbench"><link rel="next" href="wb-launching-windows.html" title="3.3.2. Launching MySQL Workbench on Windows"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-installing-windows"></a>3.3.1. Installing MySQL Workbench on Windows</h3></div></div></div><p>
        MySQL Workbench for Windows can be installed using the Windows
        Installer package or installed manually from a Zip file.
      </p><div class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Important</div><p>
          Installing MySQL Workbench using the Installer package requires
          either Administrator or Power User privileges. If you are
          using the Zip file without an installer, you do not need
          Administrator or Power User privileges.
        </p></div><p>
        <span class="bold"><strong>Installing MySQL Workbench Using the Installer
        Package</strong></span>
      </p><p>
        MySQL Workbench can be installed using the Windows Installer
        (<code class="literal">.msi</code>) installation package. The MSI package
        bears the name
        <code class="literal">mysql-workbench-<em class="replaceable"><code>version</code></em>-win32.msi</code>,
        where <em class="replaceable"><code>version</code></em> indicates the
        MySQL Workbench version number.
      </p><p>
        Improving the MySQL Installation Wizard depends on the support
        and feedback of users. If you find that the MySQL Installation
        Wizard lacks some feature important to you, or if you discover a
        bug, please report it in our bugs database. Select the
        <span class="guimenuitem">Report a Bug</span> item from the
        <span class="guimenu">Help</span> menu.
      </p><div class="orderedlist"><ol type="1"><li><p>
            To install MySQL Workbench, right-click the MSI file and select
            the <span class="guimenuitem">Install</span> item from the pop-up
            menu, or double-click the file.
          </p></li><li><p>
            In the <span class="guilabel">Setup Type</span> window you may choose
            a <code class="option">Complete</code> or <code class="option">Custom</code>
            installation. To use all features of MySQL Workbench choose the
            <code class="option">Complete</code> option.
          </p></li><li><p>
            Unless you choose otherwise, MySQL Workbench is installed in
            <code class="filename">C:\<em class="replaceable"><code>%PROGRAMFILES%</code></em>\MySQL\MySQL
            Workbench 5.1
            <em class="replaceable"><code>edition_type</code></em>\</code>, where
            <em class="replaceable"><code>%PROGRAMFILES%</code></em> is the default
            directory for programs for your locale. The
            <code class="literal">%PROGRAMFILES%</code> directory may be
            <code class="filename">C:\Program Files</code> or
            <code class="filename">C:\programme</code>.
          </p></li></ol></div><p>
        <span class="bold"><strong>Installing from the Zip File</strong></span>
      </p><p>
        If you have problems running the Installer package, an
        alternative is to install from a Zip file without an installer.
        That file is called
        <code class="literal">mysql-workbench-<em class="replaceable"><code>version</code></em>-win32.zip</code>.
      </p><p>
        To install using the Zip file, download the Zip file to a
        convenient location and decompress the file using a Zip utility.
        You can place the resulting directory anywhere on you system.
        You need not install or configure the application before using
        it. You may want to create a shortcut on your desktop or the
        quick launch bar.
      </p></div></body></html>


path: /wb-html-guitools/wb-table-tool.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.6.1.7. The Table Tool</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-vertical-toolbar.html" title="7.6.1. The Vertical Toolbar"><link rel="prev" href="wb-image-tool.html" title="7.6.1.6. The Image Tool"><link rel="next" href="wb-view-tool.html" title="7.6.1.8. The View Tool"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-table-tool"></a>7.6.1.7. The Table Tool</h4></div></div></div><p>
        Use this tool to create a table on the EER Diagram canvas.
      </p><p>
        Clicking the canvas creates a table. To edit the table with
        MySQL Table Editor, right-click it and choose <span class="guimenuitem">Edit
        Table...</span> or <span class="guimenuitem">Edit in New
        Window...</span> from the pop-up menu. You can also
        double-click the table to load it into the table editor.
      </p><p>
        To activate the table tool from the keyboard, use the
        <span><strong class="keycap">T</strong></span> key.
      </p><p>
        For more information about creating and editing tables, see
        <a href="wb-table-editor.html" title="7.7.1.3. The MySQL Table Editor">Section 7.7.1.3, “The MySQL Table Editor”</a>.
      </p></div></body></html>


path: /wb-html-guitools/wb-news-5-1-14.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.2.6. Changes in MySQL Workbench 5.1.14 (19 June 2009)</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="changes-5.1.x.html" title="A.2. Changes in Release 5.1"><link rel="prev" href="wb-news-5-1-15.html" title="A.2.5. Changes in MySQL Workbench 5.1.15 (26 June 2009)"><link rel="next" href="wb-news-5-1-13.html" title="A.2.7. Changes in MySQL Workbench 5.1.13 (12 June 2009)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-news-5-1-14"></a>A.2.6. Changes in MySQL Workbench 5.1.14 (19 June 2009)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.1.13.
      </p><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        On Mac OS X, MySQL Workbench crashed when creating a new document
        after another one had been worked on.
      </p><p>
        If editing a document, and then selecting to create a new
        document and not saving the current document when prompted,
        MySQL Workbench crashed when the save dialog closed.
       (Bug #45519)</p></li><li><p>
        Printing an EER diagram crashed MySQL Workbench.
       (Bug #45518)</p></li><li><p>
        When right-clicking an item that was not selected, such as a
        table or routine, in the <span class="guilabel">MySQL Model</span> tab,
        the item was selected without the other items being deselected.
      </p><p>
        The expected behavior for applications in both Windows and Linux
        is that right-clicking an item that has not been selected,
        should deselect all other items. Right-clicking an already
        selected item should not alter any of the selections.
       (Bug #44268)</p></li><li><p>
        When synchronizing a model with a database, rather than
        synchronizing only the selected tables, all tables were
        synchronized.
       (Bug #43485)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-printing.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.9. Printing</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-data-modeling.html" title="Chapter 7. Data Modeling"><link rel="prev" href="wb-sakila-eer-png.html" title="7.8.4.1. A PNG File of the sakila Database"><link rel="next" href="wb-printing-options.html" title="7.9.1. Printing Options"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="wb-printing"></a>7.9. Printing</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-printing-options.html">7.9.1. Printing Options</a></span></dt></dl></div><p>
    The printing options used to create printouts of your EER Diagrams
    are found under the <span class="guimenu">File</span> menu. To create
    <span class="emphasis"><em>documentation</em></span> of your models, see
    <a href="wb-model-menu.html#wb-reporting" title="7.5.1.5.1. The DBDoc Model Reporting Dialog Window (Commercial Version)">Section 7.5.1.5.1, “The DBDoc Model Reporting Dialog Window (Commercial Version)”</a>.
  </p></div></body></html>


path: /wb-html-guitools/wb-server-administration-manage-data-import-export.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>8.3. Manage Data Import/Export</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-server-administration.html" title="Chapter 8. Server Administration"><link rel="prev" href="wb-server-administration-new-server-instance.html" title="8.2. New Server Instance"><link rel="next" href="wb-server-administration-manage-security.html" title="8.4. Manage Security"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="wb-server-administration-manage-data-import-export"></a>8.3. Manage Data Import/Export</h2></div></div></div><p>
      This action item enables you to create a dump file from a
      database, or restore data from a file to a live database. Clicking
      this item launches the Import/Export MySQL Data wizard. This
      enables you to select a server instance to connect to.
    </p><p>
      For further details, see
      <a href="wb-manage-server-data-dump-tab.html" title="8.7.6. The Data Dump Tab">Section 8.7.6, “The Data Dump Tab”</a>.
    </p></div></body></html>


path: /wb-html-guitools/wb-arrange-menu.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.5.1.4. The Arrange Menu</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-data-modeling-menus.html" title="7.5.1. Modeling Menus"><link rel="prev" href="wb-view-menu.html" title="7.5.1.3. The View Menu"><link rel="next" href="wb-model-menu.html" title="7.5.1.5. The Model Menu"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-arrange-menu"></a>7.5.1.4. The Arrange Menu</h4></div></div></div><p>
      The <span class="guimenu">Arrange</span> menu items apply only to objects on
      an EER diagram canvas and are enabled only if an EER diagram view
      is active. The <span class="guimenu">Arrange</span> menu has these items:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <span class="guimenuitem">Align to Grid</span>: Aligns items on the
          canvas to the grid lines
        </p></li><li><p>
          <span class="guimenuitem">Bring to Front</span>: Brings objects to
          the foreground
        </p></li><li><p>
          <span class="guimenuitem">Send to Back</span>: Sends objects to the
          background
        </p></li><li><p>
          <span class="guimenuitem">Center Diagram Contents</span>: Centers
          objects on the canvas
        </p></li><li><p>
          <span class="guimenuitem">Autolayout</span>: Automatically arranges
          objects on the canvas
        </p></li><li><p>
          <span class="guimenuitem">Reset Object Size</span>: Expands an
          object on an EER diagram. For example, if a table has a long
          column name that is not fully displayed, this menu item
          expands the table to make the column visible. This menu item
          is not enabled unless an object is selected.
        </p></li><li><p>
          <span class="guimenuitem">Expand All</span>: Use this item to expand
          all objects on an EER diagram. This item will display a
          table's columns if the object notation supports expansion.
          Some object notations, such as <code class="literal">Classic</code>, do
          not permit expansion or contraction. Indexes will not
          automatically be expanded unless they were previously expanded
          and have been collapsed using the <span class="guimenuitem">Collapse
          All</span> menu item.
        </p></li><li><p>
          <span class="guimenuitem">Collapse All</span>: Undo the operation
          performed by <span class="guimenuitem">Expand All</span>.
        </p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-reverse-engineering.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.7.9. Reverse Engineering</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-working-with-models.html" title="7.7. Working with Models"><link rel="prev" href="wb-image-editor.html" title="7.7.8.2. The Image Editor"><link rel="next" href="wb-reverse-engineer-create-script.html" title="7.7.9.1. Reverse Engineering Using a Create Script"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-reverse-engineering"></a>7.7.9. Reverse Engineering</h3></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-reverse-engineer-create-script.html">7.7.9.1. Reverse Engineering Using a Create Script</a></span></dt><dt><span class="section"><a href="wb-reverse-engineer-live.html">7.7.9.2. Reverse Engineering a Live Database</a></span></dt></dl></div><p>
    With MySQL Workbench, you can reverse engineer a database using a MySQL
    create script or you can connect to a live MySQL server and import a
    single database or a number of databases. All versions of
    MySQL Workbench can reverse engineer using a MySQL DDL script. Only
    commercial versions of MySQL Workbench can reverse engineer a database
    directly from a MySQL server.
  </p></div></body></html>


path: /wb-html-guitools/wb-sql-development-new-connection.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>6.2. New Connection</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-sql-development.html" title="Chapter 6. SQL Development"><link rel="prev" href="wb-sql-development-open-connection.html" title="6.1. Open Connection to Start Querying"><link rel="next" href="wb-sql-development-edit-table-data.html" title="6.3. Edit Table Data"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="wb-sql-development-new-connection"></a>6.2. New Connection</h2></div></div></div><p>
      Clicking the New Connection action item launches the Manage DB
      Connections wizard. This wizard enables you to create a new
      connection. Note that the wizard when launched from here does not
      display existing connections, it only enables you to create a new
      connection.
    </p><p>
      To read more about creating and managing connections, see
      <a href="wb-manage-db-connections.html" title="6.6. Manage DB Connections Dialog">Section 6.6, “Manage DB Connections Dialog”</a>.
    </p></div></body></html>


path: /wb-html-guitools/wb-news-5-2-37.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.1. Changes in MySQL Workbench 5.2.37 (Not yet released)</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="changes-5.2.x.html" title="A.1. Changes in Release 5.2"><link rel="prev" href="changes-5.2.x.html" title="A.1. Changes in Release 5.2"><link rel="next" href="wb-news-5-2-36.html" title="A.1.2. Changes in MySQL Workbench 5.2.36 (Not yet released)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-news-5-2-37"></a>A.1.1. Changes in MySQL Workbench 5.2.37 (Not yet released)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied to
        MySQL Workbench since the release of 5.2.36.
      </p><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        Database synchronization would sometimes confuse similar table
        and routine names.
       (Bug #61028, Bug #12656879)</p></li><li><p>
        Case changes to <code class="literal">ENUM</code> values were not
        recognized by MySQL Workbench.
       (Bug #60478, Bug #11889204)</p></li><li><p>
        Within the <span class="guimenu">Database</span>, <span class="guimenu">Forward
        Engineer</span> dialogue for a Model, the <code class="literal">DROP
        Objects Before Each CREATE Object</code> option was ignored
        if the <code class="literal">Export MySQL Table Objects</code> option was
        not selected.
       (Bug #59200, Bug #11766157)</p></li><li><p>
        Altering the case of a table name caused an error, when that was
        the only change and the <code class="literal">SQL Identifiers are Case
        Sensitive</code> option was set to true.
       (Bug #58808, Bug #11765806)</p></li><li><p>
        The Forward engineering feature now preserves case for schema
        names, even on case-insensitive systems. Before it would create
        lowercase variants of the schema names on these systems.
       (Bug #56237, Bug #11763520)</p></li><li><p>
        The <span class="guimenu">Forward engineer</span> feature would sometimes
        create invalid SQL syntax for old MySQL Workbench files with deleted
        routines and roles.
       (Bug #53973, Bug #11761473)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-news-5-2-18.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.22. Changes in MySQL Workbench 5.2.18 (13 April 2010)</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="changes-5.2.x.html" title="A.1. Changes in Release 5.2"><link rel="prev" href="wb-news-5-2-19.html" title="A.1.21. Changes in MySQL Workbench 5.2.19 (16 April 2010)"><link rel="next" href="wb-news-5-2-17.html" title="A.1.23. Changes in MySQL Workbench 5.2.17 (02 April 2010)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-news-5-2-18"></a>A.1.22. Changes in MySQL Workbench 5.2.18 (13 April 2010)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.2.17.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        MySQL Workbench now features the ability to copy field data in the
        SQL Editor results tab in quoted or unquoted mode.
       (Bug #51041)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        When using the <span class="guilabel">Forward Engineer SQL Script</span>
        wizard, the wizard did not terminate <code class="literal">DROP procedure IF
        EXISTS</code> statements with a semicolon. This caused SQL
        syntax errors if the script was executed on a server.
       (Bug #52743)</p></li><li><p>
        In the SQL Editor, if a routine was altered in the routine
        editor, it was possible to close the editor without the editor
        prompting you to save any changes made, and so changes were
        lost.
       (Bug #52728)</p></li><li><p>
        The <span class="guilabel">Triggers</span> tab in the <span class="guilabel">Alter
        Table</span> dialog of the SQL Editor erased all entered
        code, when an attempt was made to copy and paste text within the
        tab.
       (Bug #52587)</p></li><li><p>
        The <span class="guilabel">Data Dump</span> facility in the Administrator
        exported the entire schema into a single file when the
        <span class="guilabel">Dump Views</span> option was selected. Further, if
        tables were selected and the <span class="guilabel">Dump stored
        routines</span> option selected, the routines would be
        stored in their own file, but with the <code class="literal">DROP PROCEDURE
        IF EXISTS</code> statements missing.
       (Bug #52579)</p></li><li><p>
        During the import procedure of the <span class="guilabel">Data
        Dump</span> facility in the Administrator, stored routines
        were not imported.
       (Bug #52577)</p></li><li><p>
        The <span class="guilabel">Connection Information</span> panel in the SQL
        Editor did not display information for the User field.
       (Bug #52560)</p></li><li><p>
        MySQL Workbench crashed when an attempt was made to create an EER
        Diagram from a database containing a large number of tables
        (1500+).
       (Bug #52500)</p></li><li><p>
        MySQL Workbench crashed if <span class="guibutton">No</span> in the
        <span class="guilabel">Delete Object</span> dialog was clicked when
        attempting to delete a view from an EER Diagram.
       (Bug #52310)</p></li><li><p>
        In the SQL Editor, if in the <span class="guilabel">Alter Routine</span>
        dialog, the user had a routine that contained an error, the
        routine would be lost if an attempt was made to close the
        <span class="guilabel">Alter Routine</span> dialog using the close
        button, and then click <span class="guibutton">Yes</span> to apply
        changes.
       (Bug #51921)</p></li><li><p>
        In the <span class="guilabel">Alter Table</span> dialog of the SQL
        Editor, in the columns or indexes tab, the first right-click in
        the dialog central area failed to display the context-sensitive
        menu. However, it was displayed on subsequent clicks.
       (Bug #51796)</p></li><li><p>
        In the SQL Editor, it was not possible to export a result set,
        if the result set was not the first result set. For example, if
        there were two result sets, it would be possible to export the
        first one created, but not the second result set.
       (Bug #51595)</p></li><li><p>
        In the Object Explorer of the Sidebar, if an existing table was
        right-clicked, the context-sensitive menu displayed the option
        <span class="guimenu">Create Table...</span>. However, selecting this
        option appeared to have no effect.
       (Bug #51570)</p></li><li><p>
        In the SQL Editor, in the results editor, it was not possible to
        edit or copy data containing multiple lines of text. Further,
        lines containing new lines were displayed as if the new lines
        did not exist.
      </p><p>
        MySQL Workbench now includes a blob editor. This can be accessed by
        right-clicking in the field to edit and selecting <span class="guimenu">Open
        Value in Editor</span>.
       (Bug #51561)</p></li><li><p>
        In the <span class="guilabel">Alter Routine</span> dialog of the SQL
        editor, there was inconsistency between the operation of the
        close dialog button ('X') on the top right of the window, and
        the <span class="guibutton">Close</span> button on the bottom right.
        When using the close dialog button you were prompted to save
        changes, regardless of whether you actually changed the routine
        or not. When using the <span class="guibutton">Close</span> button, the
        user was not prompted, even if the routine had changed.
       (Bug #51518)</p></li><li><p>
        The Message Log text area in the <span class="guilabel">Forward Engineer to
        Database</span> wizard was in active, preventing scrolling
        of the message when an error occurred.
       (Bug #51417)</p></li><li><p>
        In the SQL Editor, right-clicking a row in the results editor
        (after double-clicking a table), and selecting delete from the
        context-sensitive menu, did not have any effect.
       (Bug #51361)</p></li><li><p>
        The scrollable boxes on the Home screen did not respond to mouse
        wheel events.
       (Bug #51213)</p></li><li><p>
        When editing a row in the SQL Editor, if a column was NOT NULL
        and had a default value, and a value was not entered for it,
        then after changing another column if changes were applied an
        error would be generated. This was because the editor attempted
        to set the NOT NULL column to NULL, rather than to its default
        value.
       (Bug #50781)</p></li><li><p>
        The Log text area in the <span class="guilabel">Reverse Engineer SQL
        Script</span> wizard was inactive, preventing the log
        message from being scrolled.
       (Bug #50758)</p></li><li><p>
        The model Navigator did not redraw itself correctly. The
        Navigator worked correctly for the first model loaded into
        MySQL Workbench, but not for subsequently loaded models.
       (Bug #50580, Bug #50622)</p></li><li><p>
        When editing a table in the SQL Editor, the context sensitive
        menu items did not affect the row under the cursor, but a
        previously selected row. This potentially led to the
        unintentioned deletion of a row.
       (Bug #50113)</p></li><li><p>
        On the Linux platform, no context-sensitive menu was displayed
        when right-clicking a schema tab in the Physical Schemata
        section of the MySQL Model page.
       (Bug #49429)</p></li><li><p>
        In the EER Diagram view, when a table with a name containing
        underscores was right-clicked, the context-sensitive menu
        displayed menu items containing the table name without the
        underscores.
       (Bug #49314)</p></li><li><p>
        In the MySQL Model page it was not possible to delete a schema
        by using the context sensitive menu in the Physical Schemata
        section.
       (Bug #48055)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-news-5-2-15.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.25. Changes in MySQL Workbench 5.2.15 (28 January 2010)</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="changes-5.2.x.html" title="A.1. Changes in Release 5.2"><link rel="prev" href="wb-news-5-2-16.html" title="A.1.24. Changes in MySQL Workbench 5.2.16 (17 February 2010)"><link rel="next" href="wb-news-5-2-14.html" title="A.1.26. Changes in MySQL Workbench 5.2.14 (21 January 2010)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-news-5-2-15"></a>A.1.25. Changes in MySQL Workbench 5.2.15 (28 January 2010)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.2.14.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        The GRT Shell exhibited various issues and could generate
        exceptions in some circumstances.
      </p><p>
        The GRT Shell has been updated and is now implemented as a
        standalone dialog known as the Workbench Scripting Shell.
       (Bug #49298)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        Double-clicking any main tab, just below the main menu toolbar,
        caused MySQL Workbench to generate an exception.
       (Bug #50562)</p></li><li><p>
        If text was entered into the search bar in the SQL Editor, and
        the sidebar button clicked twice, MySQL Workbench crashed. This only
        happened on Mac OS X.
       (Bug #50560)</p></li><li><p>
        In the <span class="guilabel">Columns</span> tab of the Table Editor,
        attempting to change the column data type using the list caused
        MySQL Workbench to crash.
       (Bug #50546, Bug #50598, Bug #50527)</p></li><li><p>
        The Portrait and Landscape icons were missing from the
        <span class="guilabel">Page Setup</span> dialog.
       (Bug #50529)</p></li><li><p>
        It was not possible to print EER Diagrams or schemata. The
        <span class="guimenu">File</span>, <span class="guimenu">Print</span> option was
        grayed out, and <span><strong class="keycap">Control+P</strong></span> did not have any
        effect.
       (Bug #50528)</p></li><li><p>
        On an EER Diagram, when a relationship was placed using the
        toolbar button <span class="guibutton">Place a Relationship using Existing
        Columns</span>, if the relationship was subsequently
        checked in the <span class="guilabel">Foreign Keys</span> tab of the
        Table Editor, it was found to contain incorrect values for
        foreign key names, for example, fk_%dcolumn%1. It was apparent
        that the placeholder had not had its value correctly
        substituted.
       (Bug #50492)</p></li><li><p>
        MySQL Workbench reported the remote server as being down, in the
        Database Server Status section of the Administrator, even though
        the server was in fact running, and queries could be
        successfully run against the database using MySQL Workbench.
       (Bug #50453)</p></li><li><p>
        When the menu item <span class="guimenu">File</span>, <span class="guimenu">Page
        Setup</span> was selected from the main menu, MySQL Workbench
        crashed.
       (Bug #50315)</p></li><li><p>
        When performing a data dump in the Administrator, the operation
        failed with an exit code 7.
      </p><p>
        MySQL Workbench has been changed so that it will generate an error
        if the <span><strong class="command">mysqldump</strong></span> executable cannot be found.
       (Bug #50184)</p></li><li><p>
        Client-side sorting always sorted on an alpha basis, regardless
        of data type. This meant numeric values were not sorted into the
        order expected.
       (Bug #50158)</p></li><li><p>
        With an EER Diagram open, the <span class="guimenu">File</span>,
        <span class="guimenu">Page Setup</span> menu item was unavailable.
       (Bug #49863)</p></li><li><p>
        When working through the <span class="guilabel">Manage DB
        Connections</span> wizard, the prompt to <span class="guilabel">Enter SSH
        password</span> appeared as a sheet behind the modal dialog
        box for the wizard. In some situations, it was not possible to
        see the <span class="guilabel">Enter SSH password</span> sheet, and it
        was not possible to click any buttons on, or close, the modal
        wizard.
      </p><p>
        This meant the user had to move the modal dialog box to see the
        <span class="guilabel">Enter SSH password</span> sheet, but is was not
        obvious that this was possible because the window decorations
        indicated that the modal dialog could not be focused.
      </p><p>
        MySQL Workbench now uses a dialog rather than a wizard used for
        Manage DB Connections when creating a new connection.
       (Bug #49810)</p></li><li><p>
        The <span class="guilabel">Synchronize Model with Database</span> wizard
        generated a script that erroneously dropped schemata that had
        been selected to be ignored.
       (Bug #49587)</p></li><li><p>
        On the <span class="guilabel">General</span> tab of the configuration
        file editor, if a value was set for <span class="guilabel">Temp
        directory</span>, and the changes applied, the value set was
        not displayed in the preview, implying it would not be set in
        the server configuration file.
       (Bug #49423)</p></li><li><p>
        When a MySQL Workbench unhandled exception occurred and the
        exception dialog was displayed, if the user clicked
        <span class="guibutton">Quit</span>, and there were unsaved changes, a
        new dialog was displayed, warning of unsaved changes. If
        <span class="guibutton">Cancel</span> was clicked on this dialog,
        MySQL Workbench would exit, which was not the expected behavior
        because changes would then be lost. If
        <span class="guibutton">Yes</span> was clicked on this dialog, to save
        changes, MySQL Workbench crashed. Overall, the behavior of the
        dialogs was confusing.
      </p><p>
        A new error dialog has been introduced that changes the
        handling. It presents the user options to go to the bug report
        page, copy debug information to the clipboard and to close the
        dialog.
       (Bug #49304)</p></li><li><p>
        In the Administrator, when an attempt was made to import
        multiple tables from the same project folder, MySQL Workbench only
        imported the first table and then stopped, reporting the import
        process as finished.
       (Bug #49217)</p></li><li><p>
        In the SQL Editor, if an attempt was made to change the number
        of partitions in a table, using Alter Table, the SQL code
        produced did not contain the necessary <code class="literal">ALTER
        TABLE</code> statement to effect this change.
       (Bug #49054)</p></li><li><p>
        If the MySQL Server was stopped outside of MySQL Workbench then the
        server status displayed in the Administrator did not update
        correctly until the <span class="guilabel">Startup</span> tab was
        clicked. The log file did however correctly note the change in
        status.
       (Bug #48966)</p></li><li><p>
        When exporting a model to a single file using
        <span class="guimenu">File</span>, <span class="guimenu">Export</span>,
        <span class="guimenu">Export as Single Page PDF</span> or <span class="guimenu">Export
        as Single Page Postscript File</span>, the table positions
        contained in the file were incorrect.
       (Bug #47384)</p></li><li><p>
        If a model contained a table which used a user defined type for
        a column, then when the model was forward engineered an
        erroneous <code class="literal">COLUMN CHANGE</code> statement was
        generated for the column. This only happened for user defined
        types without additional arguments. For example, a user defined
        type using <code class="literal">INTEGER(11)</code> would not create a
        <code class="literal">COLUMN CHANGE</code> statement, but using
        <code class="literal">INTEGER</code> would.
       (Bug #45834)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-edit-menu.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.5.1.2. The Edit Menu</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-data-modeling-menus.html" title="7.5.1. Modeling Menus"><link rel="prev" href="wb-file-menu.html" title="7.5.1.1. The File Menu"><link rel="next" href="wb-view-menu.html" title="7.5.1.3. The View Menu"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-edit-menu"></a>7.5.1.2. The Edit Menu</h4></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-edit-menu.html#wb-find-dialog-window">7.5.1.2.1. Find Dialog Window</a></span></dt><dt><span class="section"><a href="wb-edit-menu.html#wb-edit-preferences">7.5.1.2.2. Workbench Preferences</a></span></dt></dl></div><p>
      Use the <span class="guimenu">Edit</span> menu to make changes to objects.
      The text description for several of the menu items changes to
      reflect the name of the currently selected object.
    </p><p>
      This menu has items for cutting, copying, and pasting. These
      actions can also be performed using the
      <span><strong class="keycap">Control+X</strong></span>, <span><strong class="keycap">Control+C</strong></span>, and
      <span><strong class="keycap">Control+V</strong></span> key combinations. Undo a deletion using
      the <span class="guimenuitem">Undo Delete
      '<em class="replaceable"><code>object_name</code></em>'</span> item. The
      <span><strong class="keycap">Control+Z</strong></span> key combination can also be used to
      undo an operation. It is also possible to carry out a
      <span class="guimenuitem">Redo</span> operation using either the menu
      item, or the key combination <span><strong class="keycap">Control+Y</strong></span>.
    </p><p>
      Also find a <span class="guimenuitem">Delete
      '<em class="replaceable"><code>object_name</code></em>'</span> menu item
      for removing the currently selected object. The keyboard command
      for this action is <span><strong class="keycap">Control+Delete</strong></span>. You can also
      right-click an object and choose the delete option from the pop-up
      menu.
    </p><p>
      The <span class="guimenuitem">Delete
      '<em class="replaceable"><code>object_name</code></em>'</span> menu item
      behaves differently depending upon circumstances. For example, if
      an <span class="guilabel">EER Diagram</span> is active and a table on the
      canvas is the currently selected object, a dialog box may open
      asking whether you want to remove the table from the canvas only
      or from the database as well. For information about setting the
      default behavior when deleting from an EER Diagram, see
      <a href="wb-preferences-model.html" title="5.4.4. The Model Tab">Section 5.4.4, “The Model Tab”</a>.
    </p><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Warning</div><p>
        If the <code class="literal">MySQL Model</code> page is active, the
        selected object is deleted from the catalog and there will be
        <span class="emphasis"><em>no confirmation dialog box</em></span>.
      </p></div><p>
      Choose <span class="guimenuitem">Edit Selected</span> to edit the
      currently selected object. You can also perform edits in a new
      window by selecting <span class="guimenuitem">Edit Selected in New
      Window</span>. The keyboard shortcuts for <span class="guimenuitem">Edit
      Selected</span> and <span class="guimenuitem">Edit Selected in New
      Window</span> are <span><strong class="keycap">Control+E</strong></span> and
      <span><strong class="keycap">Control+Shift+E</strong></span>, respectively.
    </p><p>
      The <span class="guimenuitem">Select</span> item has the following
      submenus:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <span class="guimenuitem">Select All</span> (Keyboard shortcut,
          <span><strong class="keycap">Control+A</strong></span>): Selects all the objects on the
          active EER diagram.
        </p></li><li><p>
          <span class="guimenuitem">Similar Figures</span> (Objects of the
          same type): Finds objects similar to the currently selected
          object.
        </p></li><li><p>
          <span class="guimenuitem">Connected Figures</span>: Finds all the
          objects connected to the currently selected object.
        </p></li></ul></div><p>
      These menu items are active only when an <span class="guilabel">EER
      Diagram</span> tab is selected. The <span class="guimenuitem">Similar
      Figures</span> and the <span class="guimenuitem">Connected
      Figures</span> menu items are disabled if no object is
      currently selected on an EER diagram.
    </p><p>
      When multiple objects have been selected using one of these menu
      items, you can navigate between selected items by choosing the
      <span class="guimenuitem">Go to Next Selected</span> or <span class="guimenuitem">Go
      to previous Selected</span> menu item.
    </p><p>
      Selecting objects changes some of the <span class="guimenu">Edit</span> menu
      items. If only one object is selected, that object's name appears
      after the <span class="guimenuitem">Cut</span>,
      <span class="guimenuitem">Copy</span> and
      <span class="guimenuitem">Delete</span> menu items. If more than one
      object is selected, these menu items show the number of objects
      selected.
    </p><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="wb-find-dialog-window"></a>7.5.1.2.1. Find Dialog Window</h5></div></div></div><p>
        The <span class="guisubmenu">Find</span> submenu displays the following
        menu items:
      </p><div class="itemizedlist"><ul type="disc"><li><p>
            <span class="guimenuitem">Find</span>: Takes you to the toolbar
            search box. You can look for objects in the current view.
            Find can locate objects in the Model view, the EER Diagram
            view, and also in the Catalog palette.
          </p></li><li><p>
            <span class="guimenuitem">Find Next</span>: Finds the next
            occurrence of the object.
          </p></li><li><p>
            <span class="guimenuitem">Find Previous</span>: Finds the previous
            occurrence of the object.
          </p></li><li><p>
            <span class="guimenuitem">Search and Replace</span>: Displays the
            Search and Replace dialog. This is currently for use only
            with the SQL Editor, to enable you to quickly search and
            replace script code items.
          </p></li></ul></div><p>
        The Standard Edition of MySQL Workbench includes a more advanced
        Find facility:
      </p><div class="figure"><a name="wb-find-window"></a><p class="title"><b>Figure 7.2. The Find Window</b></p><div class="mediaobject"><img src="images/wb-find-window.png" width="387" height="276" alt="The find window"></div></div><p>
        You can search the following locations:
      </p><div class="itemizedlist"><ul type="disc"><li><p>
            Entire Model: Searches the entire model.
          </p></li><li><p>
            Current View: Searches the current view only. This may be
            the <code class="literal">MySQL Model</code> page.
          </p></li><li><p>
            All Views: Searches the <code class="literal">MySQL Model Page</code>
            and all EER diagrams.

            
          </p></li><li><p>
            Database Objects: Searches database objects only.
          </p></li><li><p>
            Selected Figures: Searches the currently selected objects.
            This feature works only for EER diagrams.
          </p></li></ul></div><p>
        Enter the text you wish to search for in the <span class="guilabel">Find
        Text</span> list. You may also select any or all of the
        following check boxes:
      </p><div class="itemizedlist"><ul type="disc"><li><p>
            Match Case
          </p></li><li><p>
            Whole Word
          </p></li><li><p>
            Use Regular Expression
          </p></li><li><p>
            Search in Comments
          </p></li><li><p>
            Search in SQL for Views, SPs etc.
          </p></li></ul></div><p>
        Any text you enter into the <span class="guilabel">Find Text</span> list
        is retained for the duration of your session. Use the
        <span class="guibutton">Next</span> or <span class="guibutton">Previous</span>
        buttons to find occurrences of your search criterion.
      </p><p>
        Clicking the <span class="guibutton">Find All</span> button opens a
        <span class="guilabel">Find Results</span> window anchored at the bottom
        of the application. If you wish, you may undock this window as
        you would any other.
      </p><p>
        Use this window to navigate to objects. For example,
        double-clicking the <code class="literal">Description</code> of an object
        located on an EER diagram navigates to the specific diagram and
        selects the object. Notice that the properties of the object are
        displayed in the <code class="literal">Properties</code> palette.
      </p><p>
        The <code class="literal">Find</code> dialog window can also be opened
        using the <span><strong class="keycap">Control+F</strong></span> key combination. Use
        <span><strong class="keycap">Control+G</strong></span> to find the next occurrence and
        <span><strong class="keycap">Control+Shift+G</strong></span> to find a previous occurrence.
        Close the <code class="literal">Find</code> dialog window by clicking the
        <span class="guibutton">x</span> in the top right corner or by pressing
        the <span><strong class="keycap">Esc</strong></span> key.
      </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="wb-edit-preferences"></a>7.5.1.2.2. Workbench Preferences</h5></div></div></div><p>
        This menu item enables you to set global preferences for the
        MySQL Workbench application.
      </p><p>
        For further information, see <a href="wb-preferences.html" title="5.4. Workbench Preferences">Section 5.4, “Workbench Preferences”</a>.
      </p></div></div></body></html>


