# web_object

path: /wb-html-guitools/wb-create-schema-objects.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.2. Creating Other Schema Objects</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-create-new-table.html" title="7.8.2.1. Creating a New Table"><link rel="next" href="wb-basic-modeling.html" title="7.8.3. Basic 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-create-schema-objects"></a>7.8.2.2. Creating Other Schema Objects</h4></div></div></div><p>
        Additional objects such as views or routines can be added in the
        same way as tables.
      </p><p>
        Any objects you have created can be found in the
        <span class="guilabel">Catalog</span> palette on the right. To view these
        schema objects, select the <span class="guilabel">Catalog</span> tab in
        the middle palette on the right. View all the objects by
        clicking the <span class="guibutton">+</span> button to the left of the
        schema name.
      </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-navigator-panel.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.5.9. The Model Navigator 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-model-editor.html" title="7.5. Model Editor"><link rel="prev" href="wb-history-palette.html" title="7.5.8. The History Palette"><link rel="next" href="wb-catalog-palette.html" title="7.5.10. The Catalog Tree 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-navigator-panel"></a>7.5.9. The Model Navigator Panel</h3></div></div></div><p>
      Docked at the top left of the application is the <span class="guilabel">Model
      Navigator</span>, or <span class="guilabel">Bird's Eye</span> panel.
      This panel provides an overview of the objects placed on an EER
      diagram canvas and for this reason it is most useful when an EER
      diagram is active. Any objects that you have placed on the canvas
      should be visible in the navigator.
    </p><p>
      The Model Navigator shows the total area of an EER diagram. A
      black rectangular outline indicates the view port onto the visible
      area of the canvas. To change the view port of an EER diagram,
      left-click this black outline and drag it to the desired location.
      You can zoom in on selected areas of an EER diagram by using the
      slider tool at the bottom of this window. The dimensions of the
      view port change as you zoom in and out. If the slider tool has
      the focus, you can also zoom using the arrow keys.
    </p><p>
      The default size of the <code class="literal">Model Navigator</code> is two
      pages. To change this, use the <span class="guimenu">Model</span> menu,
      <span class="guimenuitem">Diagram Size</span> menu item.
    </p><div class="figure"><a name="wb-navigator-image"></a><p class="title"><b>Figure 7.5. The Model Navigator Palette</b></p><div class="mediaobject"><img src="images/wb-navigator.png" width="513" height="167" alt="The Model Navigator palette"></div></div></div></body></html>


path: /wb-html-guitools/wb-grt-data-organization.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>9.1. GRT and Workbench Data Organization</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-extending.html" title="Chapter 9. Extending Workbench"><link rel="next" href="wb-modules.html" title="9.2. Modules"></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-grt-data-organization"></a>9.1. GRT and Workbench Data Organization</h2></div></div></div><p>
      The GRT, or Generic RunTime, is the internal system used by
      Workbench to hold model document data. It is also the mechanism by
      which Workbench can interact with Modules and Plugins. Workbench
      model data, such as diagrams, schemata, and tables, is stored in a
      hierarchy of objects that can be accessed by any plugin. The
      information is represented using standard data types: integers,
      doubles, strings, dicts, lists, and objects.
    </p><p>
      The GRT can be accessed using external scripting languages such as
      Lua and Python. Awareness is required of how the GRT data types
      map into the scripting language. In Python, for example, the GRT
      integer, double, and string data types are seen as corresponding
      Python data types. Lists and dicts are kept in their internal
      representation, but can generally be treated as Python lists and
      dicts, and accessed in the usual way. Objects contain data fields
      and methods, but the GRT recognizes only objects from a
      pre-registered class hierarchy.
    </p><p>
      It is possible to fully examine the classes contained within the
      GRT using the Workbench Scripting Shell. Dots in class names are changed to
      underscores in their Python counterparts. For example,
      <code class="literal">db.mysql.Table</code> becomes
      <code class="literal">db_mysql_Table</code> in Python.
    </p><p>
      <span class="bold"><strong>The Application Objects Tree (GRT
      Tree)</strong></span>
    </p><p>
      As mentioned previously, Workbench document data is stored in an
      object hierarchy. This hierarchy is known as the GRT Tree. The GRT
      Tree can be accessed and modified from supported external
      scripting languages such as Python. Care should be taken when
      modifiying the GRT Tree, to prevent a mistake from leading to
      corruption of the document. Backups should be made before
      manipulating the tree. Read-only access to the tree is the safest
      approach, and is sufficient in most cases.
    </p><p>
      <span class="bold"><strong>The main nodes in the Application Object
      Tree</strong></span>
    </p><div class="informaltable"><table border="1"><colgroup><col><col></colgroup><thead><tr><th>Node</th><th>Description</th></tr></thead><tbody><tr><td>wb.registry</td><td>Application data such as plugin registry, list of editors, and options.</td></tr><tr><td>wb.customData</td><td>A generic dictionary for data you can use to store your own data. This
              dictionary is saved and reloaded with Workbench and is
              global (not document specific).</td></tr><tr><td>wb.options</td><td>Contains some default options that are used by Workbench.</td></tr><tr><td>wb.rdbmsMgmt</td><td>Internal registry of supported RDBMS modules, known data types.</td></tr><tr><td>wb.doc</td><td>The currently loaded model document.</td></tr><tr><td>wb.doc.physicalModels[0]</td><td>The currently loaded model object, containing the database catalog and
              diagrams.</td></tr><tr><td>wb.doc.physicalModels[0].catalog</td><td>The database catalog for the model. Contains the list of schemata.</td></tr><tr><td>wb.doc.physicalModels[0]catalog.schemata</td><td>List of schemata in the model. Individual schema can be accessed as a
              list: schemata[0], schemata[1] ...</td></tr><tr><td>wb.doc.physicalModels[0].catalog.schemata[0].tables (.views, .routines,
              ...)</td><td>Lists of tables, views, routines in the schema.</td></tr><tr><td>wb.doc.physicalModels[0].diagrams</td><td>List of EER diagrams in the model.</td></tr><tr><td>wb.doc.physicalModels[0].diagrams[0].figures (.layers, .connections,
              ...)</td><td>List of figures, layers, connections (relationships) in the diagram.</td></tr></tbody></table></div></div></body></html>


path: /wb-html-guitools/wb-home.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Chapter 5. The Home Window</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-getting-started-tutorial-adding-data.html" title="4.3. Adding Data to Your Database"><link rel="next" href="wb-workbench-central.html" title="5.1. Workbench Central"></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-home"></a>Chapter 5. The Home Window</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="wb-workbench-central.html">5.1. Workbench Central</a></span></dt><dt><span class="section"><a href="wb-workspace.html">5.2. Workspace</a></span></dt><dt><span class="section"><a href="wb-size.html">5.3. Workbench Application Minimum Window Size</a></span></dt><dt><span class="section"><a href="wb-preferences.html">5.4. Workbench Preferences</a></span></dt><dd><dl><dt><span class="section"><a href="wb-preferences-general.html">5.4.1. The General Tab</a></span></dt><dt><span class="section"><a href="wb-preferences-administrator.html">5.4.2. The Administrator Tab</a></span></dt><dt><span class="section"><a href="wb-preferences-sql-editor.html">5.4.3. The SQL Editor Tab</a></span></dt><dt><span class="section"><a href="wb-preferences-model.html">5.4.4. The Model Tab</a></span></dt><dt><span class="section"><a href="wb-preferences-mysql.html">5.4.5. The MySQL Tab</a></span></dt><dt><span class="section"><a href="wb-preferences-diagram.html">5.4.6. The Diagram Tab</a></span></dt><dt><span class="section"><a href="wb-preferences-appearance.html">5.4.7. The Appearance Tab</a></span></dt></dl></dd></dl></div><p>
    When MySQL Workbench first starts, it presents the
    <span class="guilabel">Home</span> window, which has two main sections:
  </p><div class="itemizedlist"><ul type="disc"><li><p>
        Workbench Central
      </p></li><li><p>
        Workspace
      </p></li></ul></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
      MySQL Workbench 5.2 introduced the <span class="guilabel">Home</span> window.
      MySQL Workbench 5.1 displays the MySQL Model workspace rather than the
      Home window. Note that 5.1 does not support the SQL Editor and
      Server Administration functionality of 5.2.
    </p></div><p>
    The two sections can be seen in the following screenshot. For more
    information, see the following sections.
  </p><div class="figure"><a name="wb-homepage"></a><p class="title"><b>Figure 5.1. The Home Window</b></p><div class="mediaobject"><img src="images/wb-homepage.png" width="1024" height="686" alt="The Home Window"></div></div></div></body></html>


path: /wb-html-guitools/wb-using-layer-tool.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.7.5.1. Adding Layers to 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-layers.html" title="7.7.5. Creating Layers"><link rel="prev" href="wb-layers.html" title="7.7.5. Creating Layers"><link rel="next" href="wb-modifying-layer.html" title="7.7.5.2. Modifying a Layer 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-using-layer-tool"></a>7.7.5.1. Adding Layers to an EER Diagram</h4></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-using-layer-tool.html#wb-adding-objects-layer">7.7.5.1.1. Adding Objects to a Layer</a></span></dt></dl></div><p>
      To add layers to an EER Diagram, use the <code class="literal">Layer</code>
      tool on the vertical toolbar. Select an <span class="guilabel">EER
      Diagram</span> tab and right-click the layer icon on the
      vertical toolbar. The layer icon is the rectangle with an
      <code class="literal">‘L’</code> in the lower left corner and it
      is found below the eraser icon.
    </p><p>
      Clicking the mouse on this icon changes the mouse pointer to a
      layer pointer. You can also change the mouse pointer to a layer
      pointer by pressing the <span><strong class="keycap">L</strong></span> key.
    </p><p>
      Choosing the <code class="literal">Layer</code> tool changes the contents of
      the toolbar that appears immediately below the menu bar. When the
      <code class="literal">Layers</code> pointer is active, this toolbar contains
      a color chart list. Use this list to select the color accent for
      the new layer. The color of your layer can be changed later using
      the <code class="literal">Properties</code> palette.
    </p><p>
      Create a layer by clicking anywhere on the EER Diagram canvas and,
      while holding the left mouse button down, draw a rectangle of a
      suitable size. This creates a new layer with the default name
      <code class="literal">layer1</code>. To revert to the default mouse pointer,
      click the arrow icon at the top of the vertical toolbar.
    </p><p>
      The following image shows a layer containing a number of views.
    </p><div class="figure"><a name="wb-layer-image"></a><p class="title"><b>Figure 7.13. The Layer Object</b></p><div class="mediaobject"><img src="images/wb-layer.png" width="393" height="163" alt="The Layer object"></div></div><p>
      To change the name of a layer, use the <code class="literal">name</code>
      property of the <code class="literal">Properties</code> palette.
    </p><p>
      Right-clicking a layer 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>layer_name</code></em>'</span>
        </p></li><li><p>
          <span class="guimenuitem">Copy
          '<em class="replaceable"><code>layer_name</code></em>'</span>
        </p></li><li><p>
          <span class="guimenuitem">Delete
          '<em class="replaceable"><code>layer_name</code></em>'</span>
        </p></li></ul></div><p>
      The cut and copy items are useful for copying layers between
      different schemata.
    </p><p>
      Since layers are not schema objects, no confirmation dialog box
      opens when you delete a layer regardless of how you have
      configured MySQL Workbench. Deleting a layer does
      <span class="bold"><strong>not</strong></span> delete schema objects from
      the catalog.
    </p><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="wb-adding-objects-layer"></a>7.7.5.1.1. Adding Objects to a Layer</h5></div></div></div><p>
        To add an object to a layer, drag and drop it directly from the
        <code class="literal">Catalog</code> palette onto a layer. If you pick up
        an object from an EER diagram, you must press
        <span><strong class="keycap">Control</strong></span> as you drag it onto the layer,
        otherwise it will not be “<span class="quote">locked</span>” inside the layer.
      </p><p>
        Locking objects to a layer prevents their accidental removal.
        You cannot remove them by clicking and dragging; to remove an
        object, you also must press the <span><strong class="keycap">Control</strong></span> key
        while dragging it.
      </p><p>
        As a visual cue that the object is being “<span class="quote">locked</span>”,
        the outline of the layer is highlighted as the object is dragged
        over it.
      </p><p>
        If you drag a layer over a table object, the table object will
        automatically be added to the layer. This also works for
        multiple table objects.
      </p><p>
        Layers cannot be nested. That is, a layer cannot contain another
        layer object.
      </p></div></div></body></html>


path: /wb-html-guitools/license-dojo-toolkit.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>B.8. Dojo Toolkit v1.7.0b1 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-dockpanel.html" title="B.7. DockPanel Suite License"><link rel="next" href="license-glib-wb.html" title="B.9. GLib License (for MySQL Workbench)"></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-dojo-toolkit"></a>B.8. Dojo Toolkit v1.7.0b1 License</h2></div></div></div><p>
    The following software may be included in this product:
  </p><pre class="programlisting">Dojo Toolkit v1.7.0b1
Copyright (c) 2005-2006, The Dojo Foundation
All rights reserved.

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

* Redistributions of source code must retain the above copyright
  notice, this list of conditions and the following disclaimer.
* 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.
* Neither the name of the Dojo Foundation nor the names of its
  contributors may be used to endorse or promote products derived
  from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"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
COPYRIGHT OWNER OR CONTRIBUTORS 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/wb-news-5-0-29.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.3.2. Changes in MySQL Workbench 5.0.29 (12 December 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-30.html" title="A.3.1. Changes in MySQL Workbench 5.0.30 (18 February 2009)"><link rel="next" href="wb-news-5-0-28.html" title="A.3.3. Changes in MySQL Workbench 5.0.28 (06 December 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-29"></a>A.3.2. Changes in MySQL Workbench 5.0.29 (12 December 2008)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.0.28.
      </p><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        Workbench crashed when objects other than tables were moved out
        of a layer.
       (Bug #41358)</p></li><li><p>
        In the EER Diagram view an icon was not displayed for Not-NULL
        items.
       (Bug #41326)</p></li><li><p>
        When a diagram was renamed, the label of the corresponding tab
        was not automatically updated. However, when the focus was
        changed, the text was correctly updated.
       (Bug #38867)</p></li><li><p>
        The table figures in the Diagram view had insufficient
        information. They did not display information such as
        constraints or default values.
       (Bug #38553)</p></li><li><p>
        When the grid was activated, dragged objects on layers were
        incorrectly placed with an offset of -1,-1.
       (Bug #35989)</p></li><li><p>
        The last column in a table disappeared in the table editor, and
        it was not possible to add further columns.
       (Bug #35905)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-news-5-1-16.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.2.4. Changes in MySQL Workbench 5.1.16 (30 June 2009 General Availability)</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-17.html" title="A.2.3. Changes in MySQL Workbench 5.1.17 (14 August 2009)"><link rel="next" href="wb-news-5-1-15.html" title="A.2.5. Changes in MySQL Workbench 5.1.15 (26 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-16"></a>A.2.4. Changes in MySQL Workbench 5.1.16 (30 June 2009 General Availability)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.1.15. This is the first General Availability
        (GA) level release of 5.1.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        The MySQL Workbench <span class="guimenu">Tools</span>,
        <span class="guimenu">Options...</span> menu item has been renamed to
        <span class="guimenu">Preferences...</span>, and the corresponding dialog
        now has the title <span class="guilabel">Workbench Preferences</span>.
       (Bug #44462)</p></li><li><p>
        When a relationship was edited in the EER diagram, a new tab was
        created in the Table Editor, rather than using any existing
        relationship tab. For example, if one relationship tab existed,
        and then another relationship was edited, a new tab would be
        created, rather than using the existing tab.
       (Bug #39624)</p></li><li><p>
        In an EER diagram, if a table contained enums with many values,
        the table was excessively wide, and had to be manually resized.
      </p><p>
        Version 5.1.16 now features a new preference setting which lets
        you specify the maximum length of a data type definition string,
        to be displayed in a table in an EER diagram. This is available
        for <code class="literal">ENUM</code> and <code class="literal">SET</code> types.
        Data type definitions that exceed these lengths are displayed as
        <code class="literal">SET/ENUM(...)</code> in the EER diagram.
      </p><p>
        The new setting can be found by selecting
        <span class="guimenu">Tools</span>, <span class="guimenu">Preferences</span> from
        the main menu, and then selecting the
        <span class="guilabel">Diagram</span> tab. The settings are then
        available in the <span class="guilabel">Tables</span> panel.
       (Bug #34919)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        When an attempt was made to add a new table to a schema page
        other than the default <span class="guilabel">MySQL Model</span> page,
        this error was generated:
      </p><pre class="programlisting">Unknown Exception caught in c:\documents and settings\mysqldev\my documents\visual studio
2008\projects\workbench\backend\windows\wbprivate.wr\src\Wb.h at line 1026</pre><p>(Bug #45821)</p></li><li><p>
        When a model was exported using either <span class="guimenu">File</span>,
        <span class="guimenu">Export</span>, <span class="guimenu">Forward Engineer SQL CREATE
        Script</span> or <span class="guimenu">Database</span>,
        <span class="guimenu">Forward Engineer...</span>, MySQL Workbench crashed with
        a segmentation fault. This occurred after the objects to export
        were selected, it did not matter if one or all objects were
        selected. This occurred using MySQL Workbench 5.1.14 RC on Ubuntu
        Linux and Windows.
       (Bug #45718)</p></li><li><p>
        The data type <code class="literal">ENUM</code> did not accept parenthesis
        in its values.
       (Bug #45607)</p></li><li><p>
        In the <span class="guilabel">Columns</span> tab of the Table Editor,
        when a column was right-clicked to display the context-sensitive
        menu, the <span class="guimenu">Move Up</span> and <span class="guimenu">Move
        Down</span> menu items were disabled. This meant that the
        order of the columns could not be changed in the normal manner.
       (Bug #45590)</p></li><li><p>
        Right-clicking in a blank area of the <span class="guilabel">User
        Types</span> window generated an exception:
      </p><pre class="programlisting">System.NullReferenceException: Object reference not set to an instance of an object.
   at MySQL.GUI.Workbench.UserDatatypesForm.contextMenuStrip1_Opening(Object sender,
CancelEventArgs e)
   at System.Windows.Forms.ToolStripDropDown.OnOpening(CancelEventArgs e)
...</pre><p>(Bug #45490)</p></li><li><p>
        When attempting to enter trigger code into the
        <span class="guilabel">Triggers</span> tab of the Table Editor, a timer
        appeared to periodically fire, which caused the delimiter to be
        added while typing.
      </p><p>
        This only happened when using the Mac OS X version of
        MySQL Workbench.
       (Bug #44264)</p></li><li><p>
        In the <span class="guilabel">Forward Engineer SQL Script</span> wizard,
        the location opened by the <span class="guibutton">Browse</span> button
        defaulted to the MySQL Workbench install directory. However, after
        an output script file was set the location opened by the
        <span class="guibutton">Browse</span> button returned to the default,
        rather than remembering the last location accessed. This
        required navigating to the correct location each time the script
        was regenerated.
       (Bug #43837)</p></li><li><p>
        MySQL Workbench displayed incorrect icons in the Table Editor. The
        icons for columns displayed in the table editor did not match
        those displayed in the EER Diagram.
       (Bug #42794)</p></li><li><p>
        In the <span class="guilabel">Forward Engineer SQL CREATE Script</span>
        wizard, the <span class="guilabel">Generate INSERT Statements for
        Tables</span> option did not take into account which tables
        were excluded in the SQL Export Filters. All insert statements
        were generated, including those for tables that had been
        excluded in the export filters.
       (Bug #40913)</p></li><li><p>
        In the EER Diagram, right-clicking to edit a table sometimes
        failed with the following error:
      </p><pre class="programlisting">Cannot execute db.mysql.plugin.edit.table
Plugin requires unhandled argument type.</pre><p>(Bug #39513)</p></li><li><p>
        When a table was renamed, inserts that had been created for it
        disappeared. Further, when a table was updated in
        <span class="guilabel">Physical Schemata</span> or in the
        <span class="guilabel">Catalog</span> pane, inserts were not updated.
       (Bug #38654)</p></li><li><p>
        If font size was changed in the <span class="guilabel">Appearance</span>
        tab of the <span class="guilabel">Workbench Preferences</span> dialog,
        this had no immediate effect on the visual appearance of the EER
        Diagram.
       (Bug #38198)</p></li><li><p>
        In the <span class="guilabel">Indexes</span> tab of the Table Editor, it
        was not possible to change the order number of a column for an
        index of type <code class="literal">PRIMARY</code> in the <span class="guilabel">Index
        Columns</span> panel, using the list available in the
        <span class="guilabel">#</span> column.
       (Bug #37273)</p></li><li><p>
        When zooming an EER Diagram, the text in a table would sometimes
        extend beyond the edge of the table box.
       (Bug #35407)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-notes.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.7.6. Creating Notes</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-modifying-layer.html" title="7.7.5.2. Modifying a Layer Using the Properties Palette"><link rel="next" href="wb-notes-physical-schemata.html" title="7.7.6.1. Adding Notes"></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-notes"></a>7.7.6. Creating Notes</h3></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-notes-physical-schemata.html">7.7.6.1. Adding Notes</a></span></dt><dt><span class="section"><a href="wb-note-editor.html">7.7.6.2. The Note Editor</a></span></dt></dl></div><p>
    You can add notes to a database only from the <code class="literal">Model
    Notes</code> section of the <code class="literal">MySQL Model</code> page.
    Notes are typically used to help document the design process.
  </p></div></body></html>


path: /wb-html-guitools/dbdoc-templates-custom.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.12.2. Creating a Custom Template</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="dbdoc-templates.html" title="7.12. Customizing DBDoc Model Reporting Templates"><link rel="prev" href="dbdoc-templates-markers.html" title="7.12.1. Supported Template Markers"><link rel="next" href="wb-server-administration.html" title="Chapter 8. Server Administration"></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="dbdoc-templates-custom"></a>7.12.2. Creating a Custom Template</h3></div></div></div><p>
      In the simplest case, a template consists of two files: a template
      file, which has a <code class="filename">.tpl</code> extension, and a
      special file <code class="filename">info.xml</code>. The
      <code class="filename">info.xml</code> file has important metadata about
      the template. A third file is optional, which is the preview image
      file. This preview file provides a thumbnail image illustrating
      the appearance of the generated report.
    </p><p>
      One of the easiest ways to create a custom template is to make a
      copy of any existing template.
    </p><p>
      For example, the following procedure describes how to make a
      custom template based on the <code class="literal">Text Basic</code>
      template.
    </p><div class="orderedlist"><ol type="1"><li><p>
          Navigate to the folder where the templates are stored.
          Assuming that MySQL Workbench has been installed into the default
          location on Windows, this would be <code class="filename">C:\Program
          Files\MySQL\MySQL Workbench 5.0
          SE\modules\data\wb_model_reporting</code>.
        </p></li><li><p>
          Copy the <code class="filename">Text_Basic.tpl</code> folder. The copy
          can be given any suitable name; for example,
          <code class="filename">Custom_Basic.tpl</code>.
        </p></li><li><p>
          Edit the <code class="filename">info.xml</code> file to reflect your
          custom template. The unedited file in this case is shown here:
        </p><pre class="programlisting">&lt;?xml version="1.0"?&gt;
&lt;data&gt;
  &lt;value type="object" struct-name="workbench.model.reporting.TemplateInfo"
  id="{BD6879ED-814C-4CA3-A869-9864F83B88DF}" struct-checksum="0xb46b524d"&gt;
    &lt;value type="string" key="description"&gt;A basic TEXT report listing schemata and objects.&lt;/value&gt;
    &lt;value type="string" key="name"&gt;HTML Basic Frame Report&lt;/value&gt;
    &lt;value type="list" content-type="object"
    content-struct-name="workbench.model.reporting.TemplateStyleInfo"
    key="styles"&gt;
      &lt;value type="object" struct-name="workbench.model.reporting.TemplateStyleInfo"
      id="{7550655C-CD4B-4EB1-8FAB-AAEE49B2261E}" struct-checksum="0xab08451b"&gt;
        &lt;value type="string" key="description"&gt;Designed to be viewed with a fixed sized font.&lt;/value&gt;
        &lt;value type="string" key="name"&gt;Fixed Size Font&lt;/value&gt;
        &lt;value type="string" key="previewImageFileName"&gt;preview_basic.png&lt;/value&gt;
        &lt;value type="string" key="styleTagValue"&gt;fixed&lt;/value&gt;
      &lt;/value&gt;
    &lt;/value&gt;
    &lt;value type="string" key="mainFileName"&gt;report.txt&lt;/value&gt;
  &lt;/value&gt;
&lt;/data&gt;</pre><p>
          The file defines wwo objects: the
          <code class="literal">TemplateInfo</code> object and the
          <code class="literal">TemplateStyleInfo</code> object. These objects
          contain information about the template that will be displayed
          in the DBDoc Model Reporting wizard main page.
        </p></li><li><p>
          Change the object GUIDs that are used in the file. In this
          example, there are two that need replacing:
        </p><pre class="programlisting">id="{BD6879ED-814C-4CA3-A869-9864F83B88DF}"
...
id="{7550655C-CD4B-4EB1-8FAB-AAEE49B2261E}"</pre><p>
          Generate two new GUIDS. This can be done using any suitable
          command-line tool. There are also free online tools that can
          be used to generate GUIDs. Another way to generate GUIDs is by
          using the MySQL <code class="literal">UUID()</code> function:
        </p><pre class="programlisting">mysql&gt; <strong class="userinput"><code>SELECT UUID();</code></strong>
+--------------------------------------+
| UUID()                               |
+--------------------------------------+
| 648f4240-7d7a-11e0-870b-89c43de3bd0a |
+--------------------------------------+
</pre><p>
          Once you have the new GUID values, edit the
          <code class="filename">info.xml</code> file accordingly.
        </p></li><li><p>
          Edit the textual information for the
          <code class="literal">TemplateInfo</code> and
          <code class="literal">TemplateStyleInfo</code> objects to reflect the
          purpose of the custom template.
        </p></li><li><p>
          The modified file will now look something like the following:
        </p><pre class="programlisting">&lt;?xml version="1.0"?&gt;
&lt;data&gt;
  &lt;value type="object" struct-name="workbench.model.reporting.TemplateInfo"
  id="{cac9ba3f-ee2a-49f0-b5f6-32580fab1640}" struct-checksum="0xb46b524d"&gt;
    &lt;value type="string"
    key="description"&gt;Custom basic TEXT report listing schemata and objects.&lt;/value&gt;
    &lt;value type="string" key="name"&gt;Custom Basic text report&lt;/value&gt;
    &lt;value type="list" content-type="object"
    content-struct-name="workbench.model.reporting.TemplateStyleInfo" key="styles"&gt;
      &lt;value type="object"
      struct-name="workbench.model.reporting.TemplateStyleInfo"
      id="{39e3b767-a832-4016-8753-b4cb93aa2dd6}" struct-checksum="0xab08451b"&gt;
        &lt;value type="string" key="description"&gt;Designed to be viewed with a fixed sized font.&lt;/value&gt;
        &lt;value type="string" key="name"&gt;Fixed Size Font&lt;/value&gt;
        &lt;value type="string" key="previewImageFileName"&gt;preview_basic.png&lt;/value&gt;
        &lt;value type="string" key="styleTagValue"&gt;fixed&lt;/value&gt;
      &lt;/value&gt;
    &lt;/value&gt;
    &lt;value type="string" key="mainFileName"&gt;custom_report.txt&lt;/value&gt;
  &lt;/value&gt;
&lt;/data&gt;</pre></li><li><p>
          Create the new template file. This too may best be achieved,
          depending on your requirements, by editing an existing
          template. In this example the template file
          <code class="filename">report.txt.tpl</code> is shown here:
        </p><pre class="programlisting">+--------------------------------------------+
| MySQL Workbench Report                     |
+--------------------------------------------+

Total number of Schemata: {{SCHEMA_COUNT}}
=============================================
{{#SCHEMATA}}
{{SCHEMA_NR}}. Schema: {{SCHEMA_NAME}}
----------------------------------------------
## Tables ({{TABLE_COUNT}}) ##
{{#TABLES}}{{TABLE_NR_FMT}}. Table: {{TABLE_NAME}}
{{#COLUMNS_LISTING}}## Columns ##
Key  Column  Name  Datatype  Not Null  Default  Comment
{{#COLUMNS}}{{COLUMN_KEY}}{{COLUMN_NAME}}{{COLUMN_DATATYPE}} »
{{COLUMN_NOTNULL}}{{COLUMN_DEFAULTVALUE}}{{COLUMN_COMMENT}}
{{/COLUMNS}}{{/COLUMNS_LISTING}}
{{#INDICES_LISTING}}## Indices ##
Index  Name  Columns  Primary  Unique  Type  Kind  Comment
{{#INDICES}}{{INDEX_NAME}}{{#INDICES_COLUMNS}}{{INDEX_COLUMN_NAME}} »
{{INDEX_COLUMN_ORDER}}{{INDEX_COLUMN_COMMENT}}{{/INDICES_COLUMNS}} »
{{INDEX_PRIMARY}}{{INDEX_UNIQUE}}{{INDEX_TYPE}}{{INDEX_KIND}}{{INDEX_COMMENT}}
{{/INDICES}}{{/INDICES_LISTING}}
{{#REL_LISTING}}## Relationships ##
Relationship  Name  Relationship  Type  Parent Table  Child Table Cardinality
{{#REL}}{{REL_NAME}}{{REL_TYPE}}{{REL_PARENTTABLE}}{{REL_CHILDTABLE}}{{REL_CARD}}
{{/REL}}{{/REL_LISTING}}
---------------------------------------------

{{/TABLES}}
{{/SCHEMATA}}
=============================================
End of MySQL Workbench Report</pre><p>
          This template shows details for all schemata in the model.
        </p></li><li><p>
          The preceding template file can be edited in any way you like,
          with new markers being added, and existing markers being
          removed as required. For the custom template example, you
          might want to create a much simpler template, such as the one
          following:
        </p><pre class="programlisting">+--------------------------------------------+
| MySQL Workbench Custom Report              |
+--------------------------------------------+

Total number of Schemata: {{SCHEMA_COUNT}}
=============================================
{{#SCHEMATA}}
Schema Name: {{SCHEMA_NAME}}
----------------------------------------------
## Tables ({{TABLE_COUNT}}) ##

{{#TABLES}}
Table Name: {{TABLE_NAME}}
{{/TABLES}}
{{/SCHEMATA}}

Report Generated On: {{GENERATED}}
=============================================
End of MySQL Workbench Custom Report</pre><p>
          This simplified report just lists the schemata and the tables
          in a model. The date and time the report was generated is also
          displayed as a result of the use of the
          <code class="literal">{{GENERATED}}</code> variable.
        </p></li><li><p>
          The custom template can then be tested. Start MySQL Workbench,
          load the model to generate the report for, select the
          <span class="guimenu">Model</span>, <span class="guimenuitem">DBDOC - Model
          Reporting</span> menu item. Then select the new custom
          template from the list of available templates, select an
          output directory, and click <span class="guibutton">Finish</span> to
          generate the report. Finally, navigate to the output directory
          to view the finished report.
        </p></li></ol></div></div></body></html>


path: /wb-html-guitools/wb-news-5-2-31a.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.8. Changes in MySQL Workbench 5.2.31a (13 December 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-32.html" title="A.1.7. Changes in MySQL Workbench 5.2.32 (05 March 2011)"><link rel="next" href="wb-news-5-2-31.html" title="A.1.9. Changes in MySQL Workbench 5.2.31 (08 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-31a"></a>A.1.8. Changes in MySQL Workbench 5.2.31a (13 December 2010)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.2.31.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        It was not possible to launch the MySQL Command Line Client from
        the SQL Editor. MySQL Workbench has been changed so that it is now
        possible to launch a MySQL Command Line Client from the Home
        screen. This can be done through the context-sensitive menu
        available for items listed in the connections list on the Home
        screen.
       (Bug #56631)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        An unexpected error was generated when attempting to modify the
        script created in the <span class="guilabel">Forward Engineer to
        Database</span> wizard.
       (Bug #58893)</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>
        MySQL Workbench closed silently when the <span class="guilabel">User Defined
        Types Editor</span> dialog was closed using the close button
        on the window frame, or by pressing <span><strong class="keycap">Alt+F4</strong></span>.
       (Bug #58846)</p></li><li><p>
        Opening the <span class="guilabel">Snippets</span> tab in the SQL Editor
        caused MySQL Workbench to crash with the error:
      </p><pre class="programlisting">
** Message: query.explain built-in command is being overwritten
mysql-workbench-bin: /usr/include/boost/smart_ptr/shared_ptr.hpp:418: T*
boost::shared_ptr&lt; &lt;template-parameter-1-1&gt; &gt;::operator-&gt;() const [with T = Sql_editor]:
Assertion `px != 0' failed.
Aborted
</pre><p>(Bug #58833)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-mysql-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.2. MySQL-Specific 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-general-validation.html" title="7.10.1. General Validation"><link rel="next" href="wb-model-reporting.html" title="7.11. The DBDoc Model Reporting Dialog Window (Commercial Version)"></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-mysql-validation"></a>7.10.2. MySQL-Specific Validation</h3></div></div></div><p>
      The following list names the MySQL-specific validation types and
      gives examples of specific violations:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <span class="bold"><strong>Integrity Violation</strong></span>
        </p><div class="itemizedlist"><ul type="circle"><li><p>
              An object name longer than the maximum permitted
            </p></li><li><p>
              A foreign key defined for an engine type that does not
              support foreign keys (not yet implemented)
            </p></li><li><p>
              A view or routine that references a nonexistent table (not
              yet implemented)
            </p></li><li><p>
              A default value that does not match a column's data type
            </p></li><li><p>
              An invalid partitioning scheme
            </p></li></ul></div></li><li><p>
          <span class="bold"><strong>Syntax Violation</strong></span>
        </p><div class="itemizedlist"><ul type="circle"><li><p>
              A routine, trigger, or view with incorrect SQL syntax
            </p></li><li><p>
              A reserved keyword used as an identifier
            </p></li><li><p>
              Use of an invalid character
            </p></li></ul></div></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-sql-editor-main-tabsheets.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>6.7.4. Main Tabsheets</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-query-panel.html" title="6.7.3. SQL Query Panel"><link rel="next" href="wb-sql-editor-overview-tabsheet.html" title="6.7.4.1. Overview Tabsheet"></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-main-tabsheets"></a>6.7.4. Main Tabsheets</h3></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-sql-editor-overview-tabsheet.html">6.7.4.1. Overview Tabsheet</a></span></dt><dt><span class="section"><a href="wb-sql-editor-output-tabsheet.html">6.7.4.2. Output Tabsheet</a></span></dt><dt><span class="section"><a href="wb-sql-editor-history-tabsheet.html">6.7.4.3. History Tabsheet</a></span></dt><dt><span class="section"><a href="wb-sql-editor-snippets-tabsheet.html">6.7.4.4. Snippets Tabsheet</a></span></dt><dt><span class="section"><a href="wb-sql-editor-results-tabsheets.html">6.7.4.5. Results Tabsheets</a></span></dt><dt><span class="section"><a href="wb-sql-editor-live-editing-tabsheets.html">6.7.4.6. Live Editing Tabsheets</a></span></dt></dl></div><p>
        The main tabsheets area contains several tabs:
      </p><div class="itemizedlist"><ul type="disc"><li><p>
            Overview Tabsheet
          </p></li><li><p>
            Output Tabsheet
          </p></li><li><p>
            History Tabsheet
          </p></li><li><p>
            Results Tabsheets
          </p></li><li><p>
            Live Editing Tabsheet
          </p></li></ul></div><div class="figure"><a name="wb-sql-editor-tabsheets-screenshot"></a><p class="title"><b>Figure 6.8. SQL Editor - Main Tabsheets</b></p><div class="mediaobject"><img src="images/wb-sql-editor-tabsheets-screenshot.png" width="379" height="33" alt="SQL Editor - Main Tabsheets"></div></div><p>
        The following sections describe each of these in more detail.
      </p></div></body></html>


path: /wb-html-guitools/license-pcre.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>B.16. PCRE 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-lua.html" title="B.15. Lua (liblua) License"><link rel="next" href="license-pixman.html" title="B.17. Pixman 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-pcre"></a>B.16. PCRE License</h2></div></div></div><p>
    The following software may be included in this product:
  </p><p>
    PCRE (Perl Compatible Regular Expressions) Library
  </p><pre class="programlisting">PCRE LICENCE

PCRE is a library of functions to support regular expressions 
whose syntax and semantics are as close as possible to those 
of the Perl 5 language.

Release 7 of PCRE is distributed under the terms of the "BSD" 
licence, as specified below. The documentation for PCRE, 
supplied in the "doc" directory, is distributed under the same 
terms as the software itself.

The basic library functions are written in C and are 
freestanding. Also included in the distribution is a set 
of C++ wrapper functions.

THE BASIC LIBRARY FUNCTIONS
---------------------------
Written by:       Philip Hazel
Email local part: ph10
Email domain:     cam.ac.uk

University of Cambridge Computing Service,
Cambridge, England. Phone: +44 1223 334714.

Copyright (c) 1997-2006 University of Cambridge
All rights reserved.

THE C++ WRAPPER FUNCTIONS
-------------------------
Contributed by:   Google Inc.

Copyright (c) 2006, Google Inc.
All rights reserved.

THE "BSD" LICENCE
-----------------

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

* Redistributions of source code must retain the above 
  copyright notice, this list of conditions and the 
  following disclaimer.
* 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.
* Neither the name of the University of Cambridge nor 
  the name of Google Inc. nor the names of their contributors 
  may be used to endorse or promote products derived from 
  this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND 
CONTRIBUTORS "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 COPYRIGHT OWNER OR CONTRIBUTORS 
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.

End</pre></div></body></html>


path: /wb-html-guitools/wb-file-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.1. The File 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-data-modeling-menus.html" title="7.5.1. Modeling Menus"><link rel="next" href="wb-edit-menu.html" title="7.5.1.2. The Edit 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-file-menu"></a>7.5.1.1. The File Menu</h4></div></div></div><p>
      Use the <span class="guimenu">File</span> menu to open a project, begin a
      new project, or save a project. Choosing <span class="guimenuitem">New
      Model</span> opens the default schema,
      <code class="literal">mydb</code>. Choosing <span class="guimenuitem">Open
      Model</span> opens a file dialog box with the default file
      type set to MySQL Workbench Models (<code class="filename">mwb</code>
      extension). To display a list of recently opened MWB files, choose
      the <span class="guimenuitem">Open Recent</span> menu item. The keyboard
      shortcut to create a new project is <span><strong class="keycap">Control+N</strong></span> and
      the command to open an existing project is
      <span><strong class="keycap">Control+O</strong></span>.
    </p><p>
      To close the currently active <code class="literal">MySQL Model</code> or
      <code class="literal">EER Diagram</code> tab, use the <span class="guimenuitem">Close
      Tab</span> menu item. You can also do this from the
      keyboard by pressing <span><strong class="keycap">Control+W</strong></span>. To reopen the
      <code class="literal">MySQL Model</code> tab, see
      <a href="wb-view-menu.html" title="7.5.1.3. The View Menu">Section 7.5.1.3, “The View Menu”</a>. To reopen an <code class="literal">EER
      Diagram</code> tab, double-click the <code class="literal">EER
      Diagram</code> icon in the <code class="literal">EER Diagrams</code>
      section of the <code class="literal">MySQL Model</code> page.
    </p><p>
      Use the <span class="guimenuitem">Save Model</span> or <span class="guimenuitem">Save
      Model As</span> menu items to save a model. When you save a
      model, its name appears in the title bar of the application. If
      you have made changes to a project and have not saved those
      changes, an asterisk appears in the title bar following the model
      name. When you save a model, it is saved as a MySQL Workbench file
      with the extension <code class="literal">mwb</code>.
    </p><p>
      Use the <span class="guimenuitem">Import</span> menu item to import a
      MySQL data definition (DDL) script file. For example, this might
      be a file created by issuing the command <span><strong class="command">mysqldump
      <code class="option">--no-data</code></strong></span>. MySQL Workbench handles the
      script as follows:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          If the script does not contain a <code class="literal">CREATE DATABASE
          <em class="replaceable"><code>db_name</code></em>;</code> statement, the
          schema objects are copied to the default schema,
          <code class="literal">mydb</code>.
        </p></li><li><p>
          If the script creates a database, a new tab bearing the
          database name is added to the <code class="literal">Physical
          Schemata</code> section of the <code class="literal">MySQL
          Model</code> page.
        </p></li><li><p>
          If the script contains data, the data is ignored.
        </p></li></ul></div><p>
      For details about importing a DDL script, 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><p>
      Under the <span class="guisubmenu">Import</span> submenu, you can also
      import <code class="literal">DBDesigner4</code> files.
    </p><p>
      There are variety of items under the
      <span class="guisubmenu">Export</span> submenu. You may generate the SQL
      statements necessary to create a new database or alter an existing
      one. For more information about these menu items, see
      <a href="wb-forward-engineering-sql-scripts.html" title="7.7.10.1. Forward Engineering Using an SQL Script">Section 7.7.10.1, “Forward Engineering Using an SQL Script”</a>.
    </p><p>
      Using the <span class="guisubmenu">Export</span> submenu, you can also
      export an EER diagram as a PNG, SVG, PDF, or Postscript file. For
      an example of a PNG file, 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>
      The <span class="guimenuitem">Page Setup</span> menu item enables you to
      set the paper size, orientation, and margins for printing
      purposes.
    </p><p>
      The printing options are enabled only if the <span class="guilabel">EER
      Diagrams</span> tab is selected. You have the choice of
      printing your model directly to your printer, printing it as a PDF
      file, or creating a PostScript file. For more information, see
      <a href="wb-printing.html" title="7.9. Printing">Section 7.9, “Printing”</a>.
    </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
        The printing options are available only in commercial versions
        of MySQL Workbench.
      </p></div><p>
      Use the <span class="guimenuitem">Document Properties</span> menu item
      to set the following properties of your project:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <code class="literal">Name</code>: The model name (default is
          <code class="literal">MySQL Model</code>)
        </p></li><li><p>
          <code class="literal">Version</code>: The project version number
        </p></li><li><p>
          <code class="literal">Author</code>: The project author
        </p></li><li><p>
          <code class="literal">Project</code>: The project name
        </p></li><li><p>
          <code class="literal">Created</code>: Not editable; determined by the
          MWB file attributes
        </p></li><li><p>
          <code class="literal">Last Changed</code>: Not editable; determined by
          the MWB file attributes
        </p></li><li><p>
          <code class="literal">Description</code>: A description of your project
        </p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-news-5-2-35.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.3. Changes in MySQL Workbench 5.2.35 (23 September 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-36.html" title="A.1.2. Changes in MySQL Workbench 5.2.36 (Not yet released)"><link rel="next" href="wb-news-5-2-34.html" title="A.1.4. Changes in MySQL Workbench 5.2.34 (26 May 2011)"></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-35"></a>A.1.3. Changes in MySQL Workbench 5.2.35 (23 September 2011)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied to
        MySQL Workbench since the release of 5.2.34.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        On Microsoft Windows, the standard (common) keyboard and mouse
        shortcuts that control <span class="emphasis"><em>zoom</em></span> were not fully
        implemented. Usage: <span><strong class="keycap">Control++</strong></span> to zoom in,
        <span><strong class="keycap">Control+-</strong></span> to zoom out, and
        <span><strong class="keycap">Control+/</strong></span> to reset to 100%.
       (Bug #57463, Bug #11764608)</p></li><li><p>
        Usernames and schemas can now be sorted.
       (Bug #55318, Bug #11762692)</p></li><li><p>
        The <span class="guimenu">Copy Insert Template to Clipboard</span> option
        was added to the Model View. For more information, see
        <a href="wb-using-table-tool.html#wb-table-eer-view-image" title="Figure 7.7. A Table on an EER Diagram">Figure 7.7, “A Table on an EER Diagram”</a>.
       (Bug #54887, Bug #11762310)</p></li><li><p>
        The query history is now saved between Workbench sessions.
       (Bug #51388, Bug #11759102)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        The unused <span class="guimenu">Start MySQL Utilities Shell for
        Connection</span> connection menu item was removed.
       (Bug #12898126)</p></li><li><p>
        MySQL Workbench would sometimes crash after opening multiple EER
        diagrams.
       (Bug #12875254)</p></li><li><p>
        The <span class="guilabel">Create EER Model from Existing Data
        Base</span> process would incorrectly report that the schema
        was empty.
       (Bug #12875126)</p></li><li><p>
        The <span class="guilabel">Synchronize with Any Source</span> option
        reversed the 'destination' and 'source' database names within
        the generated SQL statement.
       (Bug #62189, Bug #12921676)</p></li><li><p>
        The <code class="literal">is_enabled()</code> method was added to the
        mforms View class.
       (Bug #62140, Bug #12860149)</p></li><li><p>
        MySQL Workbench crashed with a segmentation fault after the
        connection step of a model synchronization.
       (Bug #61822, Bug #12742008)</p></li><li><p>
        The database connection splash screen would freeze after opening
        a server administration instance. It would work perfectly the
        second time.
       (Bug #61693, Bug #12756623)</p></li><li><p>
        MySQL Workbench would crash when pressing <span class="guimenu">Apply</span>
        to an empty SQL field under the <code class="literal">Review the SQL Script
        to be Applied to the Database</code> form, the second time,
        after selecting <span class="guimenu">Go Back</span>.
       (Bug #61632, Bug #12694149)</p></li><li><p>
        On Mac OS X, an unchanged MWB file would prompt to save after
        exiting, and then crash after selecting <code class="literal">Yes</code>.
       (Bug #61547, Bug #12668099)</p></li><li><p>
        On Mac OS X, connecting to remote servers using SSH tunnels
        failed to connect. The workaround was to manually test the
        connection first, via the <span class="guimenu">Manage Connections</span>
        menu.
       (Bug #61537, Bug #12674397)</p></li><li><p>
        Viewing the Admin Management option <span class="guimenu">Server
        Logs</span> with an empty <code class="literal">TABLE</code> resulted
        in an unhandled exception.
       (Bug #61523, Bug #12674989)</p></li><li><p>
        On Mac OS X, the <code class="literal">Operation in progress</code>
        dialogue would stall when using database connections from older
        versions of MySQL Workbench. The workaround was to move the mouse.
       (Bug #61416, Bug #12627853)</p></li><li><p>
        On Microsoft Windows, a <span class="guilabel">MySQL Workbench Unexpected
        Error</span> dialogue is generated when using two SQL Editor
        windows each with their own database connection to the same
        server.
       (Bug #61367, Bug #12612181)</p></li><li><p>
        The SQL Editor <span class="guilabel">Output</span>,
        <span class="guilabel">History</span> window contained escaped
        characters. For example, a "<code class="literal">'</code>" was written as
        "<code class="literal">&amp;apos;</code>".
       (Bug #61345, Bug #12605093)</p></li><li><p>
        On Linux, the <span class="guilabel">Reverse Engineer Database</span>,
        <span class="guilabel">Select Objects to Reverse Engineer</span> dialogue
        contained a menu titled <code class="literal">label</code>.
       (Bug #61327, Bug #12600868)</p></li><li><p>
        The SQL Editor <span class="guilabel">Overview</span> tab did not refresh
        after a schema was deleted.
       (Bug #61314, Bug #12616355)</p></li><li><p>
        <span class="guilabel">Create EER Model</span>, <span class="guilabel">Schema
        Privileges</span>, <span class="guilabel">Add Role</span>,
        <span class="guilabel">Privileges</span>, and then <span class="guilabel">Uncheck All
        Privileges</span> caused MySQL Workbench to crash.
       (Bug #61308, Bug #12613935)</p></li><li><p>
        The <span class="guimenu">Find Plugin in Web Repository</span> option was
        removed from the <code class="literal">MySQL Doc Library</code>
        <code class="literal">action</code>.
       (Bug #61305, Bug #12613922)</p></li><li><p>
        On Ubuntu Linux, MySQL Workbench crashed with a segmentation fault
        when executing the <span class="guimenu">View</span>,
        <span class="guimenu">Output</span> combination twice.
       (Bug #61303, Bug #12601189)</p></li><li><p>
        On Microsoft Windows, installation of 5.2.34 over 5.2.33 would
        sometimes fail due to file collisions, and would then crash at
        startup.
       (Bug #61296, Bug #12600117)</p></li><li><p>
        Creating, then selecting or removing user accounts with invalid
        hosts (such as <code class="literal">'%'</code>, including the single
        quotes) resulted in an unhandled exception.
       (Bug #61244, Bug #12580053)</p></li><li><p>
        Under certain circumstances, closing a query window would not
        prompt to save the query.
       (Bug #61160, Bug #12565971)</p></li><li><p>
        On Microsoft Windows, expensive queries caused MySQL Workbench to be
        unresponsive after other applications were made active, and the
        MySQL Workbench wizard was running. This meant that the main
        MySQL Workbench window could not be selected.
       (Bug #61122, Bug #12543271)</p></li><li><p>
        MySQL Workbench would not compile with GNU C Compiler (GCC) version
        4.6.
       (Bug #60603, Bug #12617226)</p></li><li><p>
        The query beautifier added superfluous identifier quote
        characters to the end of some queries.
       (Bug #60576, Bug #11926859)</p></li><li><p>
        On Microsoft Windows, the following scenario generated an error
        and a bogus SQL editor tab upon MySQL Workbench restoration: Having
        multiple open SQL Editor tabs, closing the first, and then
        closing the database connection (while the <code class="literal">Auto-save
        scripts interval</code> option is enabled).
       (Bug #60569, Bug #12617215)</p></li><li><p>
        The MySQL Workbench SE <code class="literal">MySQL Bug Reporter</code> linked
        to bugs.mysql.com instead of support.oracle.com.
       (Bug #60364, Bug #11872318)</p></li><li><p>
        MySQL Workbench would not connect to multiple database connections
        when the <code class="literal">sql_history</code> folder was too large. A
        workaround was to delete the <code class="literal">sql_history</code>
        folder.
       (Bug #59520, Bug #11766417)</p></li><li><p>
        The SQL Editor <span class="guilabel">History</span> could not be saved
        when the username contained Unicode characters. This was due to
        MySQL Workbench attempting to save files using an invalid file path.
       (Bug #59215, Bug #12403539)</p></li><li><p>
        Closing MySQL Workbench would not prompt to save SQL Editor scratch
        tabs.
       (Bug #58899, Bug #11765889)</p></li><li><p>
        The <span class="guilabel">Management</span>, <span class="guilabel">Server
        Logs</span>, <span class="guilabel">Slow Query Log</span> view
        resulted in an unhandled exception after the initial
        <code class="literal">Newest</code> button usage.
       (Bug #58810, Bug #11765808)</p></li><li><p>
        The <span class="guilabel">Object Browser</span> now automatically
        refreshes after an object is changed.
       (Bug #56704, Bug #11763930)</p></li><li><p>
        It was not possible to drop multiple selected tables or schemas.
       (Bug #55688, Bug #11763027)</p></li><li><p>
        <span class="guimenu">Copy Insert to Clipboard</span> now updates the
        MySQL Workbench status to say “<span class="quote">The table
        <em class="replaceable"><code>schema.table</code></em> has no records for
        insert statements</span>” when no inserts are defined for the
        table.
       (Bug #54887, Bug #11762310)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-news-5-2-14.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.26. Changes in MySQL Workbench 5.2.14 (21 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-15.html" title="A.1.25. Changes in MySQL Workbench 5.2.15 (28 January 2010)"><link rel="next" href="wb-news-5-2-13.html" title="A.1.27. Changes in MySQL Workbench 5.2.13 (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-14"></a>A.1.26. Changes in MySQL Workbench 5.2.14 (21 January 2010)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.2.13.
      </p><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        If a multiline configuration option in the MySQL server
        configuration file was removed using the configuration editor of
        the Administrator tab, MySQL Workbench generated an error.
       (Bug #50470)</p></li><li><p>
        In the SQL Editor, the <span class="guilabel">Alter Table</span> dialog
        created incorrect DDL for changes to the partitioning.
       (Bug #49055)</p></li><li><p>
        In the Physical Schemata section of the MySQL Model tab, the
        tables were not displayed in alphabetic order.
       (Bug #47143)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-intro.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Chapter 1. MySQL Workbench Introduction</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-preface.html" title="Preface and Legal Notice"><link rel="next" href="wb-editions.html" title="Chapter 2. MySQL Workbench Editions"></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-intro"></a>Chapter 1. MySQL Workbench Introduction</h2></div></div></div><p>
    MySQL Workbench provides a graphical tool for working with MySQL Servers
    and databases. MySQL Workbench fully supports MySQL Server versions 5.1
    and above. It is also compatible with MySQL Server 5.0, but not
    every feature of 5.0 may be supported. It does not support MySQL
    Server versions 4.x.
  </p><p>
    MySQL Workbench provides three main areas of functionality:
  </p><div class="itemizedlist"><ul type="disc"><li><p>
        <span class="bold"><strong>SQL Development</strong></span>: Enables you to
        create and manage connections to database servers. As well as
        enabling you to configure connection parameters, MySQL Workbench
        provides the capability to execute SQL queries on the database
        connections using the built-in SQL Editor. This functionality
        replaces that previously provided by the Query Browser
        standalone application.
      </p></li><li><p>
        <span class="bold"><strong>Data Modeling</strong></span>: Enables you to
        create models of your database schema graphically, reverse and
        forward engineer between a schema and a live database, and edit
        all aspects of your database using the comprehensive Table
        Editor. The Table Editor provides easy-to-use facilities for
        editing Tables, Columns, Indexes, Triggers, Partitioning,
        Options, Inserts and Privileges, Routines and Views.
      </p></li><li><p>
        <span class="bold"><strong>Server Administration</strong></span>: Enables
        you to create and administer server instances.
      </p></li></ul></div><p>
    MySQL Workbench is available in two editions, the Community Edition and
    the Standard Edition. The Community Edition is available free of
    charge. The Standard Edition provides additional Enterprise
    features, such as database documentation generation, at low cost.
  </p></div></body></html>


path: /wb-html-guitools/wb-news-5-0-22.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.3.9. Changes in MySQL Workbench 5.0.22 (27 May 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-23.html" title="A.3.8. Changes in MySQL Workbench 5.0.23 (25 June 2008)"><link rel="next" href="wb-news-5-0-21.html" title="A.3.10. Changes in MySQL Workbench 5.0.21 (27 April 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-22"></a>A.3.9. Changes in MySQL Workbench 5.0.22 (27 May 2008)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.0.21.
      </p><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        Can not add values for <code class="literal">TIMESTAMP</code>
        columns in the <span class="guilabel">Inserts</span> editor.
       (Bug #37009)</p></li><li><p>
        When columns are added to, or removed from a table, Workbench
        deletes all <span class="guilabel">Inserts</span> data.
       (Bug #37008)</p></li><li><p>
        Trigger definition auto-formatting resulted in malformed code.
       (Bug #36815, Bug #37685)</p></li><li><p>
        The script generated by the <span class="guimenu">File</span>,
        <span class="guimenu">Export</span>, <span class="guimenu">Forward Engineer SQL CREATE
        Script</span> menu item contains a spurious quotation mark.
       (Bug #36753)</p></li><li><p>
        For <code class="literal">CREATE TABLE</code> statements,
        <code class="literal">TIME</code> column default values were
        not quoted properly.
       (Bug #36669)</p></li><li><p>
        Print preview in landscape orientation did not work correctly.
       (Bug #36647)</p></li><li><p>
        When opening a model created with an earlier version of
        Workbench, the <span class="guilabel">Indexes</span> tab displayed
        indexes of type <code class="literal">FOREIGN</code> as type
        <code class="literal">INDEX</code>, and it was not possible to change them
        back to <code class="literal">FOREIGN</code>.
       (Bug #36453)</p></li><li><p>
        If a table column definition permits <code class="literal">NULL</code> and
        has been set with a default of <code class="literal">NULL</code>,
        integrity validation operations complained that the default
        value for the column is invalid.
       (Bug #36397)</p></li><li><p>
        After use of <span><strong class="keycap">Control+X</strong></span> to cut text from a
        text-edit box and <span><strong class="keycap">Control+Z</strong></span> to undo the
        operation, the canvas was updated correctly but not the text
        box.
       (Bug #36358)</p></li><li><p>
        Shifted content could not be scrolled or navigated.
       (Bug #36328)</p></li><li><p>
        The mousewheel scrolled the overview pane when it was open
        behind the insert-editor.
       (Bug #36253)</p></li><li><p>
        View renaming in overview did not work properly and has been
        disabled.
       (Bug #36202)</p></li><li><p>
        The Copy to SQL operation caused a crash.
       (Bug #36184)</p></li><li><p>
        Dragging objects out of a layer did not work properly.
       (Bug #36053)</p></li><li><p>
        The enabled/disabled status of items in the
        <span class="guimenu">Edit</span> menu was not updated properly.
       (Bug #35962)</p></li><li><p>
        Relationships were drawn over tables.
       (Bug #35867)</p></li><li><p>
        The script generated by database synchronize contained errors.
       (Bug #35644)</p></li><li><p>
        Setting up foreign key relationships across multiple schemas did
        not work.
       (Bug #34546)</p></li><li><p>
        Scrollbars now appear correctly when editor windows are reduced
        in height.
       (Bug #32454)</p></li><li><p>
        Table partitioning information was not exported properly.
       (Bug #32226)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-vertical-toolbar.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. The Vertical Toolbar</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-eer-diagram-editor.html" title="7.6. EER Diagram Editor"><link rel="prev" href="wb-eer-diagram-editor.html" title="7.6. EER Diagram Editor"><link rel="next" href="wb-standard-mouse-pointer.html" title="7.6.1.1. The Standard Mouse Pointer"></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-vertical-toolbar"></a>7.6.1. The Vertical Toolbar</h3></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-standard-mouse-pointer.html">7.6.1.1. The Standard Mouse Pointer</a></span></dt><dt><span class="section"><a href="wb-hand-tool.html">7.6.1.2. The Hand Tool</a></span></dt><dt><span class="section"><a href="wb-eraser-tool.html">7.6.1.3. The Eraser Tool</a></span></dt><dt><span class="section"><a href="wb-layer-tool.html">7.6.1.4. The Layer Tool</a></span></dt><dt><span class="section"><a href="wb-note-tool.html">7.6.1.5. The Text Tool</a></span></dt><dt><span class="section"><a href="wb-image-tool.html">7.6.1.6. The Image Tool</a></span></dt><dt><span class="section"><a href="wb-table-tool.html">7.6.1.7. The Table Tool</a></span></dt><dt><span class="section"><a href="wb-view-tool.html">7.6.1.8. The View Tool</a></span></dt><dt><span class="section"><a href="wb-routine-group-tool.html">7.6.1.9. The Routine Group Tool</a></span></dt><dt><span class="section"><a href="wb-reference-relationship-tools.html">7.6.1.10. The Relationship Tools</a></span></dt></dl></div><p>
      The vertical toolbar shows on the left sidebar when an EER diagram
      tab is selected. The tools on this toolbar assist in creating EER
      diagrams.
    </p><div class="figure"><a name="wb-vertical-toolbar-image"></a><p class="title"><b>Figure 7.6. The Vertical Toolbar</b></p><div class="mediaobject"><img src="images/wb-vertical-toolbar.png" width="789" height="575" alt="The vertical toolbar"></div></div><p>
      Clicking a tool changes the mouse pointer to a pointer that
      resembles the tool icon, indicating which tool is active. These
      tools can also be activated from the keyboard by pressing the key
      associated with the tool. Hover the mouse pointer over a toolbar
      icon to display a description of the tool and its shortcut key.
    </p><p>
      A more detailed description of each of these tools follows.
    </p></div></body></html>


path: /wb-html-guitools/wb-mac-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.9. Uninstalling 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-launching-osx.html" title="3.3.8. Launching MySQL Workbench on Mac OS X"><link rel="next" href="wb-launching-activation.html" title="3.4. Activation Procedure (Commercial Version)"></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-mac-uninstalling"></a>3.3.9. Uninstalling MySQL Workbench on Mac OS X</h3></div></div></div><p>
        To uninstall MySQL Workbench for Mac OS X, locate MySQL Workbench in the
        Applications folder, right-click, and select <span class="guimenuitem">Move
        to Trash</span>.
      </p></div></body></html>


path: /wb-html-guitools/wb-workspace.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>5.2. Workspace</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-home.html" title="Chapter 5. The Home Window"><link rel="prev" href="wb-workbench-central.html" title="5.1. Workbench Central"><link rel="next" href="wb-size.html" title="5.3. Workbench Application Minimum Window Size"></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-workspace"></a>5.2. Workspace</h2></div></div></div><p>
      The Workspace is designed to enable you to quickly get to the task
      you would like to carry out. In alignment with MySQL Workbench
      functionality, it is divided into three main areas:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <span class="bold"><strong>SQL Development</strong></span>. For further
          information, see <a href="wb-sql-development.html" title="Chapter 6. SQL Development">Chapter 6, <i>SQL Development</i></a>.
        </p></li><li><p>
          <span class="bold"><strong>Data Modeling</strong></span>. For further
          information, see <a href="wb-data-modeling.html" title="Chapter 7. Data Modeling">Chapter 7, <i>Data Modeling</i></a>.
        </p></li><li><p>
          <span class="bold"><strong>Server Administration</strong></span>. For
          further information, see
          <a href="wb-server-administration.html" title="Chapter 8. Server Administration">Chapter 8, <i>Server Administration</i></a>.
        </p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-third-party-licenses.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Appendix B. Third Party Licenses</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-news-5-0-14.html" title="A.3.18. Changes in MySQL Workbench 5.0.14beta (25 February 2008)"><link rel="next" href="license-flat-tab-control.html" title="B.1. .NET Flat TabControl License"></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-third-party-licenses"></a>Appendix B. Third Party Licenses</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="license-flat-tab-control.html">B.1. .NET Flat TabControl License</a></span></dt><dt><span class="section"><a href="license-bitstream-vera.html">B.2. Bitstream Vera License</a></span></dt><dt><span class="section"><a href="license-boost.html">B.3. Boost Library License</a></span></dt><dt><span class="section"><a href="license-cairo.html">B.4. Cairo License</a></span></dt><dt><span class="section"><a href="license-ctemplate.html">B.5. CTemplate (Google Template System) License</a></span></dt><dt><span class="section"><a href="license-libcurl.html">B.6. cURL (<code class="literal">libcurl</code>) License</a></span></dt><dt><span class="section"><a href="license-dockpanel.html">B.7. DockPanel Suite License</a></span></dt><dt><span class="section"><a href="license-dojo-toolkit.html">B.8. Dojo Toolkit v1.7.0b1 License</a></span></dt><dt><span class="section"><a href="license-glib-wb.html">B.9. GLib License (for MySQL Workbench)</a></span></dt><dt><span class="section"><a href="license-glitz.html">B.10. Glitz License</a></span></dt><dt><span class="section"><a href="license-gnu-lgpl-2-1.html">B.11. GNU Lesser General Public License Version 2.1, February 1999</a></span></dt><dt><span class="section"><a href="license-html-renderer.html">B.12. HtmlRenderer (System.Drawing.Html)</a></span></dt><dt><span class="section"><a href="license-libxml2.html">B.13. Libxml2 License</a></span></dt><dt><span class="section"><a href="license-libzip.html">B.14. Libzip License</a></span></dt><dt><span class="section"><a href="license-lua.html">B.15. Lua (liblua) License</a></span></dt><dt><span class="section"><a href="license-pcre.html">B.16. PCRE License</a></span></dt><dt><span class="section"><a href="license-pixman.html">B.17. Pixman License</a></span></dt><dt><span class="section"><a href="license-pycrypto.html">B.18. PyCrypto License</a></span></dt><dt><span class="section"><a href="license-python.html">B.19. Python License</a></span></dt><dt><span class="section"><a href="license-scintilla.html">B.20. Scintilla License</a></span></dt><dt><span class="section"><a href="license-scintilla-net.html">B.21. ScintillaNET License</a></span></dt><dt><span class="section"><a href="license-tinyxml.html">B.22. TinyXML License</a></span></dt><dt><span class="section"><a href="license-treeviewadv-net.html">B.23. TreeViewAdv for .NET License</a></span></dt><dt><span class="section"><a href="license-vsqlite.html">B.24. VSQLite++ License</a></span></dt></dl></div><p>
    Use of any of this software is governed by the terms of the licenses
    that follow.
  </p><h2><a name="id310652"></a>MySQL Workbench</h2><div class="itemizedlist"><ul type="disc"><li><p><a href="license-flat-tab-control.html" title="B.1. .NET Flat TabControl License">Section B.1, “.NET Flat TabControl License”</a></p></li><li><p><a href="license-bitstream-vera.html" title="B.2. Bitstream Vera License">Section B.2, “Bitstream Vera License”</a></p></li><li><p><a href="license-boost.html" title="B.3. Boost Library License">Section B.3, “Boost Library License”</a></p></li><li><p><a href="license-cairo.html" title="B.4. Cairo License">Section B.4, “Cairo License”</a></p></li><li><p><a href="license-ctemplate.html" title="B.5. CTemplate (Google Template System) License">Section B.5, “CTemplate (Google Template System) License”</a></p></li><li><p><a href="license-libcurl.html" title="B.6. cURL (libcurl) License">Section B.6, “cURL (<code class="literal">libcurl</code>) License”</a></p></li><li><p><a href="license-dockpanel.html" title="B.7. DockPanel Suite License">Section B.7, “DockPanel Suite License”</a></p></li><li><p><a href="license-dojo-toolkit.html" title="B.8. Dojo Toolkit v1.7.0b1 License">Section B.8, “Dojo Toolkit v1.7.0b1 License”</a></p></li><li><p><a href="license-glib-wb.html" title="B.9. GLib License (for MySQL Workbench)">Section B.9, “GLib License (for MySQL Workbench)”</a></p></li><li><p><a href="license-glitz.html" title="B.10. Glitz License">Section B.10, “Glitz License”</a></p></li><li><p><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></li><li><p><a href="license-html-renderer.html" title="B.12. HtmlRenderer (System.Drawing.Html)">Section B.12, “HtmlRenderer (System.Drawing.Html)”</a></p></li><li><p><a href="license-libxml2.html" title="B.13. Libxml2 License">Section B.13, “Libxml2 License”</a></p></li><li><p><a href="license-libzip.html" title="B.14. Libzip License">Section B.14, “Libzip License”</a></p></li><li><p><a href="license-lua.html" title="B.15. Lua (liblua) License">Section B.15, “Lua (liblua) License”</a></p></li><li><p><a href="license-pcre.html" title="B.16. PCRE License">Section B.16, “PCRE License”</a></p></li><li><p><a href="license-pixman.html" title="B.17. Pixman License">Section B.17, “Pixman License”</a></p></li><li><p><a href="license-pycrypto.html" title="B.18. PyCrypto License">Section B.18, “PyCrypto License”</a></p></li><li><p><a href="license-python.html" title="B.19. Python License">Section B.19, “Python License”</a></p></li><li><p><a href="license-scintilla.html" title="B.20. Scintilla License">Section B.20, “Scintilla License”</a></p></li><li><p><a href="license-scintilla-net.html" title="B.21. ScintillaNET License">Section B.21, “ScintillaNET License”</a></p></li><li><p><a href="license-tinyxml.html" title="B.22. TinyXML License">Section B.22, “TinyXML License”</a></p></li><li><p><a href="license-treeviewadv-net.html" title="B.23. TreeViewAdv for .NET License">Section B.23, “TreeViewAdv for .NET License”</a></p></li><li><p><a href="license-vsqlite.html" title="B.24. VSQLite++ License">Section B.24, “VSQLite++ License”</a></p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-news-5-1-4.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.2.15. Changes in MySQL Workbench 5.1.4 (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-6.html" title="A.2.14. Changes in MySQL Workbench 5.1.6 (Not yet released)"><link rel="next" href="changes-5.0.x.html" title="A.3. Changes in Release 5.0"></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-4"></a>A.2.15. Changes in MySQL Workbench 5.1.4 (Not yet released)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.1.3.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        There was a problem where relationships that were hidden could
        then not be selected to bring up their relationship editor.
        Relationships can now be selected as objects in the Layer
        window. Once selected, the relationship's
        <code class="literal">visible</code> property can be set to
        <code class="literal">True</code> in the Properties window, thus making
        the relationship visible again.
       (Bug #40167)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        Loading a model using the Linux version of Workbench resulted in
        a crash. However, the model loaded correctly with the Windows
        versions of Workbench.
       (Bug #39992)</p></li><li><p>
        A model created using the Windows version of Workbench caused
        the Linux version of Workbench to crash on loading the model.
       (Bug #39983)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-sql-editor-live-editing-tabsheets.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>6.7.4.6. Live Editing Tabsheets</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-main-tabsheets.html" title="6.7.4. Main Tabsheets"><link rel="prev" href="wb-sql-editor-results-tabsheets.html" title="6.7.4.5. Results Tabsheets"><link rel="next" href="wb-sql-editor-sidebar.html" title="6.7.5. Sidebar"></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-live-editing-tabsheets"></a>6.7.4.6. Live Editing Tabsheets</h4></div></div></div><p>
          It is possible to edit data in real time using the Live
          Editing tabsheets. In the Overview tab, if a table is
          double-clicked, a live editing tab is launched, enabling you
          to edit the data maintained in that table. Field data can be
          edited by clicking a field and entering the required data, or
          editing existing data. In addition to the controls offered by
          the Results tabsheet, the Live Editor tab features some
          additional controls. These controls are highlighted in the
          following screenshot.
        </p><div class="figure"><a name="wb-sql-editor-live-editing-controls-screenshot"></a><p class="title"><b>Figure 6.12. SQL Editor - Live Editing Tabsheet Navigation Controls</b></p><div class="mediaobject"><img src="images/wb-sql-editor-live-editing-controls-screenshot.png" width="798" height="380" alt="SQL Editor - Live Editing Tabsheet
              Navigation Controls"></div></div><p>
          These additional controls enable you to make changes to the
          data shown in the table and to apply or discard those changes.
          Applying the changes synchronizes the data with the live
          server. Discarding them leaves the live server unaffected.
        </p><p>
          From left to right, the additional controls are:
        </p><div class="itemizedlist"><ul type="disc"><li><p>
              <span class="bold"><strong>Edit current row</strong></span>: Enters
              edit mode for the currently selected row.
            </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
                It is possible to enter a function, or other expression,
                into a field. Use the prefix <code class="literal">\func</code> to
                prevent MySQL Workbench from escaping quotation marks. For
                example, for the expression
                <code class="literal">md5('fred')</code>, MySQL Workbench normally
                would generate the code
                <code class="literal">md5(\'fred\')</code>. To prevent this, enter
                the expression as <code class="literal">\func md5('fred')</code>
                to ensure that the quoting is not escaped.
              </p></div></li><li><p>
              <span class="bold"><strong>Insert new row</strong></span>: Inserts a
              new row and enables you to enter data. Your changes will
              not be reflected on the live server until you click
              <span class="guibutton">Apply changes to data</span>.
            </p></li><li><p>
              <span class="bold"><strong>Delete selected rows</strong></span>:
              Removes the selected rows. Your changes will not be
              reflected on the live server until you click
              <span class="guibutton">Apply changes to data</span>.
            </p></li><li><p>
              <span class="bold"><strong>Apply changes to data</strong></span>:
              Applies to the live server any changes that have been made
              in the data fields.
            </p></li><li><p>
              <span class="bold"><strong>Discard changes to data</strong></span>:
              Discards any changes that have been made in the data
              fields without applying them to the live server.
            </p></li></ul></div><p>
          See also <a href="wb-table-editor.html#wb-table-editor-inserts-tab" title="7.7.1.3.9. The Inserts Tab">Section 7.7.1.3.9, “The Inserts Tab”</a>.
        </p></div></body></html>


path: /wb-html-guitools/wb-getting-started-tutorial.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Chapter 4. Getting Started Tutorial</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-launching-activation.html" title="3.4. Activation Procedure (Commercial Version)"><link rel="next" href="wb-getting-started-tutorial-admin.html" title="4.1. Administering a MySQL Server"></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-getting-started-tutorial"></a>Chapter 4. Getting Started Tutorial</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="wb-getting-started-tutorial-admin.html">4.1. Administering a MySQL Server</a></span></dt><dt><span class="section"><a href="wb-getting-started-tutorial-creating-a-model.html">4.2. Creating a Model</a></span></dt><dt><span class="section"><a href="wb-getting-started-tutorial-adding-data.html">4.3. Adding Data to Your Database</a></span></dt></dl></div><p>
    This tutorial provides a quick hands-on introduction to using
    MySQL Workbench for beginners. If you have used MySQL Workbench before you
    can safely skip this tutorial.
  </p><p>
    This tutorial uses a locally installed MySQL Server. If you only
    have access to a remote MySQL server, you must enter appropriate
    connection parameters as necessary. This tutorial requires
    MySQL Workbench 5.2.16 or above. It is assumed that you have a basic
    understanding of MySQL concepts. This tutorial demonstrates the
    procedures on Microsoft Windows, but they are the same for all
    supported platforms.
  </p></div></body></html>


path: /wb-html-guitools/wb-preferences-administrator.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>5.4.2. The Administrator 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-preferences.html" title="5.4. Workbench Preferences"><link rel="prev" href="wb-preferences-general.html" title="5.4.1. The General Tab"><link rel="next" href="wb-preferences-sql-editor.html" title="5.4.3. The SQL Editor 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-preferences-administrator"></a>5.4.2. The Administrator Tab</h3></div></div></div><p>
      This section provides configuration options that affect the
      Administrator functionality in MySQL Workbench. It enables you to set
      paths to the <span><strong class="command">mysqldump</strong></span> and
      <span><strong class="command">mysql</strong></span> tools. If these paths are left blank, the
      defaults are used. This panel also enables you to set the
      directory for export dump files.
    </p></div></body></html>


path: /wb-html-guitools/wb-news-5-0-28.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.3.3. Changes in MySQL Workbench 5.0.28 (06 December 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-29.html" title="A.3.2. Changes in MySQL Workbench 5.0.29 (12 December 2008)"><link rel="next" href="wb-news-5-0-27.html" title="A.3.4. Changes in MySQL Workbench 5.0.27 (07 November 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-28"></a>A.3.3. Changes in MySQL Workbench 5.0.28 (06 December 2008)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.0.27.
      </p><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        If you attempted to select several tables in the table list of
        the <span class="guilabel">MySQL Model</span> view, and you accidentally
        included the <span class="guibutton">Add Table</span> button in your
        selection, a message box appeared warning of an unknown
        exception:
      </p><pre class="programlisting">"Unknown Exception caught in: c:\documents and settings\mysqldev\my documents\visual
studio 2005\projects\workbench\backend\windows\wb.wr\src\Wb.h at line 1010"</pre><p>
        The program did not crash. Only the messagebox appeared.
       (Bug #41201)</p></li><li><p>
        If two foreign keys were created in a table that referenced a
        second table and then an attempt was made to delete the
        relations and the referenced table, MySQL Workbench crashed.
       (Bug #41025)</p></li><li><p>
        When clicking the <span class="guibutton">+</span> and
        <span class="guibutton">-</span> buttons in the <span class="guilabel">Physical
        Schemata</span> pane of the <span class="guilabel">MySQL Model</span>
        tab, an <code class="literal">Unhandled Exception</code> was generated:
      </p><pre class="programlisting">System.Runtime.InteropServices.SEHException: External component has thrown an exception.</pre><p>(Bug #40971)</p></li><li><p>
        The <span class="guilabel">Referenced Column</span> pane of the
        <span class="guilabel">Foreign Key</span> tab became cleared if the
        foreign key was renamed. Subsequently, attempting to choose a
        <span class="guilabel">Referenced Column</span> did not display a link in
        the <span class="guilabel">EER Diagram</span> view. To get foreign key
        relationships working again it was necessary to de-select the
        check boxes from the <span class="guilabel">Columns</span> pane,
        re-select them, and then select the <span class="guilabel">Referenced
        Column</span> pane.
       (Bug #40649)</p></li><li><p>
        When a table was renamed the inserted data was lost.
       (Bug #40327)</p></li><li><p>
        A complex EER diagram threw an exception whenever an action was
        peformed on it. However, other diagrams in the same MWB file
        functioned correctly.
      </p><p>
        The exception generated was:
      </p><pre class="programlisting">System.Runtime.InteropServices.SEHException: Un composant externe a levé une exception.
   à wb.ModelViewForm.handle_mouse_button(ModelViewForm* , MouseButton , Boolean , Int32
, Int32 , EventState )
   à MySQL.Workbench.ModelViewForm.OnMouseUp(MouseEventArgs e, Int32 X, Int32 Y, Keys
keystate, MouseButtons buttons)
   à MySQL.GUI.Workbench.ModelViewForm.CanvasPanel_MouseUp(Object sender, MouseEventArgs
e)
   à System.Windows.Forms.Control.OnMouseUp(MouseEventArgs e)
   à MySQL.Utilities.WindowsCanvasViewerPanel.OnMouseUp(MouseEventArgs e)
   à System.Windows.Forms.Control.WmMouseUp(Message&amp; m, MouseButtons button, Int32
clicks)
   à System.Windows.Forms.Control.WndProc(Message&amp; m)
   à System.Windows.Forms.ScrollableControl.WndProc(Message&amp; m)
   à System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message&amp; m)
   à System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message&amp; m)
   à System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam,
IntPtr lparam)</pre><p>(Bug #39360)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-news-5-0-23.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.3.8. Changes in MySQL Workbench 5.0.23 (25 June 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-24.html" title="A.3.7. Changes in MySQL Workbench 5.0.24 (12 August 2008)"><link rel="next" href="wb-news-5-0-22.html" title="A.3.9. Changes in MySQL Workbench 5.0.22 (27 May 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-23"></a>A.3.8. Changes in MySQL Workbench 5.0.23 (25 June 2008)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.0.22.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        It was not clear how a stored connection profile could be edited
        and the changes saved. Tooltips have been added to the relevant
        buttons and the main documentation clarified.
       (Bug #37061)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        The <span class="guimenu">File</span>, <span class="guimenu">Export</span>,
        <span class="guimenu">Forward Engineer SQL CREATE Script</span> menu item
        exports a script it is then unable to import using the
        <span class="guimenu">File</span>, <span class="guimenu">Export</span>,
        <span class="guimenu">Reverse Engineer MySQL Create Script</span> menu
        item because it incorrectly imports comments containing special
        characters.
       (Bug #37563, Bug #37562)</p></li><li><p>
        Workbench was failing to correctly export Trigger DDLs.
       (Bug #37432)</p></li><li><p>
        Using <span class="guimenu">Generate Schema Diff Report</span> resulted in
        a crash. The crash was caused by improper handling of an invalid
        foreign key in a table. While this issue is correctly reported
        by a validation module, in Standard Edition <span class="guimenu">Generate
        Schema Diff Report</span> didn't handle that correctly.
       (Bug #37393)</p></li><li><p>
        When a new column was added to a table
        <code class="literal">Inserts</code> data was deleted.
       (Bug #37192)</p></li><li><p>
        Trying to edit a table in a new window displays an error message
        dialog:
      </p><pre class="programlisting">plugin:wb.edit.editSelectedInNewWindow
Invalid plugin
Invalid plugin wb.edit.editSelectedInNewWindow</pre><p>(Bug #37180)</p></li><li><p>
        If you try to place a new image into an EER Diagram and select
        an invalid filetype, you get a error message dialog with the
        following text:
      </p><p>
        <span class="errortext">cairo error: invalid matrix (not
        invertible)</span>
      </p><p>
        If you then click <span class="guibutton">OK</span> to clear the dialog
        and then try to select <span class="guimenu">Place a New Table</span>, the
        error message dialog is displayed again.
       (Bug #37079)</p></li><li><p>
        The <span class="guimenu">Forward Engineer</span> wizard did not report
        connection status correctly. If invalid database credentials
        were entered, the wizard reported success, even though the
        connection failed.
       (Bug #37060)</p></li><li><p>
        Incorrect behavior when editing a table. When the
        <span class="guilabel">columns</span> tab is selected, if you want to
        delete multiple selected tables at once, Workbench removes the
        wrong columns.
       (Bug #37045)</p></li><li><p>
        The script generated by the <span class="guimenu">File</span>,
        <span class="guimenu">Export</span>, <span class="guimenu">Forward Engineer SQL ALTER
        Script</span> menu item contains syntax errors.
       (Bug #36889)</p></li><li><p>
        The export filter did not properly filter tables.
       (Bug #36739)</p></li><li><p>
        Workbench generated incorrect syntax when attempting to
        synchronize with a live server. The resulting code was missing
        commas which resulted in a syntax error.
       (Bug #36674)</p></li><li><p>
        After reverse engineering an SQL create script and drawing some
        EER diagrams, a subsequent import of the same script destroys
        the EER diagrams. All tables in the catalog are updated, but the
        reference of the table in the diagram to the table in the
        catalog is lost. The tables in the diagram are still visible,
        but do not correspond to the table in the catalog.
      </p><p>
        After closing and re-opening the file, all diagrams are empty
        and it is impossible to delete the diagrams. However, in the
        overview in the upper right corner, the tables placed in the
        diagram are still visible.
       (Bug #36381)</p></li><li><p>
        Mouse wheel does not work when you double-click a table and
        select the <span class="guilabel">Options</span> tab.
       (Bug #36374)</p></li><li><p>
        When <span class="guimenu">File</span>, <span class="guimenu">Export</span>,
        <span class="guimenu">Forward Engineer SQL ALTER Script</span> menu item
        is selected it causes an <code class="literal">ALTER Script Generation
        (Script Synchronization)</code> error.
       (Bug #36355)</p></li><li><p>
        The behavior of the <span class="guimenu">Synchronize</span> wizard was
        inconsistent when cancelled and re-run.
       (Bug #36177)</p></li><li><p>
        Several windows and tabs have fields which are either not
        completely visible or are obscured by labels that overlap the
        field.
       (Bug #36115)</p></li><li><p>
        When creating a <code class="literal">Schema Diff Report</code> from the
        local model to a live database, the wizard crashed with an
        unhandled exception.
       (Bug #35878)</p></li><li><p>
        Collapsing of the EER Diagram section of the <span class="guilabel">MySQL
        Model</span> tab is not retained after program relaunch.
       (Bug #35717)</p></li><li><p>
        In the <span class="guilabel">MySQL Model</span> tab, in the summary line
        for <span class="guilabel">Physical Schemata</span>, there are three
        icons, one for large icon view, one for small icon view, one for
        list view. Changing the view is not saved between application
        launches.
       (Bug #35716)</p></li><li><p>
        Performing a <span class="guimenu">Database Synchronization</span>
        resulted in erroneous <code class="literal">ALTER</code> statements being
        generated.
       (Bug #34812)</p></li><li><p>
        Menu item was incorrectly named <span class="guimenu">Generate Schema Diff
        Report</span>, when it should have been called
        <span class="guimenu">Generate Catalog Diff Report</span>.
       (Bug #34398)</p></li><li><p>
        Workbench failed to restore window states, window positions and
        side-panel sizes from the previous execution of the application.
       (Bug #32442)</p></li><li><p>
        The <code class="literal">AUTO_INCREMENT</code> attribute is now ignored
        on import for column types that do not support it.
       (Bug #31986)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-launching-activation.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>3.4. Activation Procedure (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-installing.html" title="Chapter 3. Installing and Launching MySQL Workbench"><link rel="prev" href="wb-mac-uninstalling.html" title="3.3.9. Uninstalling MySQL Workbench on Mac OS X"><link rel="next" href="wb-getting-started-tutorial.html" title="Chapter 4. Getting Started Tutorial"></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-launching-activation"></a>3.4. Activation Procedure (Commercial Version)</h2></div></div></div></div></body></html>


path: /wb-html-guitools/wb-news-5-2-8.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.32. Changes in MySQL Workbench 5.2.8 (18 November 2009 Beta)</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-9.html" title="A.1.31. Changes in MySQL Workbench 5.2.9 (Internal release only)"><link rel="next" href="wb-news-5-2-7.html" title="A.1.33. Changes in MySQL Workbench 5.2.7 (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-8"></a>A.1.32. Changes in MySQL Workbench 5.2.8 (18 November 2009 Beta)</h3></div></div></div><p>
        First Beta release of 5.2. This section documents all changes
        and bug fixes applied since the release of 5.2.7.
      </p><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        When a table was edited in the EER Diagram view, and
        <span><strong class="keycap">Control+S</strong></span> was pressed to save the model, the
        model file was not saved.
       (Bug #48682)</p></li><li><p>
        If an model object, such as a schema or table, was deleted or
        its creation was undone using the undo feature, while the object
        editor was open, a crash occurred if the editor was then
        subsequently closed.
       (Bug #48664)</p></li><li><p>
        When running MySQL Workbench, this error occurred when an attempt
        was made to change the Windows screen resolution:
      </p><pre class="programlisting">cairo error: out of memory</pre><p>(Bug #48520)</p></li><li><p>
        MySQL Workbench did not start correctly. At startup it generated
        this error:
      </p><pre class="programlisting">Microsoft Visual C++ Runtime Library

Runtime Error!

Program C:\Pro...

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.</pre><p>(Bug #48389)</p></li><li><p>
        Once a default value had been set for a column in the Table
        Editor, it was not possible to remove it.
       (Bug #47085)</p></li><li><p>
        The View text editor was overly aggressive in trimming excess
        whitespace from View definitions. If there was some hesitation
        after the user entered one or more spaces, the editor would trim
        whitespace back to the last non-space character entered.
       (Bug #46894)</p></li><li><p>
        In the EER Diagram view, the auto-resizing of tables did not
        work correctly, tables were too small to permit all columns to
        be visible.
       (Bug #46806)</p></li><li><p>
        When using the Fedora 10 RPM installation packages on Fedora 11,
        opening a database connection produced this error:
      </p><pre class="programlisting">Cannot Connect to Database Server
Connection 'antonia' could not be established: Database driver: Failed to open library
'/usr/lib/mysql-workbench/mysqlcppconn.so'. Check settings.</pre><p>
        The MySQL Workbench libraries were installed in
        <code class="filename">/usr/lib64/</code>, not
        <code class="filename">/usr/lib/</code>.
       (Bug #46428)</p></li><li><p>
        In the <span class="guilabel">Manage DB Connections</span> dialog, the
        text fields <span class="guilabel">Username</span>,
        <span class="guilabel">Password</span>, and <span class="guilabel">Default
        Schema</span> accepted text, but as the text was being
        entered only the top half of the characters entered displayed.
        However, once the text had been submitted, the characters were
        displayed correctly.
       (Bug #45106)</p></li><li><p>
        Printing of an EER Diagram did not work correctly if a table
        vertically spanned multiple pages. In this case pages would be
        printed up to and including the page that contained the first
        part of the table that spanned multiple pages, but the pages
        containing the remaining parts of the table would not be
        printed. This problem typically occurred when a table had more
        fields than could comfortably fit on a single page.
       (Bug #33919)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-default-schema.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. Using the Default Schema</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-creating-eer-diagram.html" title="7.8.1.1. Adding an EER Diagram"><link rel="next" href="wb-create-new-table.html" title="7.8.2.1. Creating a New 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-default-schema"></a>7.8.2. Using the Default Schema</h3></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-create-new-table.html">7.8.2.1. Creating a New Table</a></span></dt><dt><span class="section"><a href="wb-create-schema-objects.html">7.8.2.2. Creating Other Schema Objects</a></span></dt></dl></div><p>
      When you first open MySQL Workbench a default schema,
      <code class="literal">mydb</code> appears as the leftmost tab of the
      <span class="guilabel">Physical Schemata</span> section of MySQL Workbench. You
      can begin designing a database by using this default schema.
    </p><div class="figure"><a name="wb-default-schema-image"></a><p class="title"><b>Figure 7.43. The Default Schema</b></p><div class="mediaobject"><img src="images/wb-default-schema.png" width="169" height="146" alt="The default schema"></div></div><p>
      To change the name of the default schema, double-click the schema
      tab. This opens a schema editor window docked at the bottom of the
      application. To undock or redock this window, double-click
      anywhere in the editor title bar.
    </p><p>
      To rename the schema, use the field labeled
      <span class="guilabel">Name</span>. After you have renamed the schema, a
      lightning bolt icon appears right aligned in the
      <span class="guilabel">Name</span> field, indicating that other changes are
      pending. Click the <span class="guilabel">Comments</span> field and a
      dialog box opens asking if you wish to rename all schema
      occurrences. Clicking <span class="guibutton">Yes</span> ensures that your
      changes are propagated throughout the application. Add comments to
      the database and change the collation if you wish. Close the
      schema editor by clicking the <span class="guibutton">x</span> button.
    </p></div></body></html>


path: /wb-html-guitools/license-boost.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>B.3. Boost Library 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-bitstream-vera.html" title="B.2. Bitstream Vera License"><link rel="next" href="license-cairo.html" title="B.4. Cairo 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-boost"></a>B.3. Boost Library License</h2></div></div></div><p>
    The following software may be included in this product:
  </p><p>
    <span class="bold"><strong>Boost C++ Libraries</strong></span>
  </p><p>
    Use of any of this software is governed by the terms of the license
    below:
  </p><pre class="programlisting">Boost Software License - Version 1.0 - August 17th, 2003

Permission is hereby granted, free of charge, to any person or
organization obtaining a copy of the software and accompanying
documentation covered by this license (the "Software") to use,
reproduce, display, distribute, execute, and transmit the Software,
and to prepare derivative works of the Software, and to permit
third-parties to whom the Software is furnished to do so, all
subject to the following:

The copyright notices in the Software and this entire statement,
including the above license grant, this restriction and the
following disclaimer, must be included in all copies of the
Software, in whole or in part, and all derivative works of the
Software, unless such copies or derivative works are solely in the
form of machine-executable object code generated by a source
language processor.

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, TITLE AND
NON-INFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR ANYONE
DISTRIBUTING THE SOFTWARE BE LIABLE FOR ANY DAMAGES OR OTHER
LIABILITY, WHETHER IN 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/wb-sql-development-open-connection.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>6.1. Open Connection to Start Querying</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.html" title="Chapter 6. SQL Development"><link rel="next" href="wb-sql-development-new-connection.html" title="6.2. New Connection"></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-open-connection"></a>6.1. Open Connection to Start Querying</h2></div></div></div><p>
      Clicking this action item launches the Connect to Database Wizard.
      From this wizard, you can select a predefined connection. A new
      SQL Editor tab is launched.
    </p><p>
      If you already have created a connection to a database, it will
      appear in this panel as an icon. Double-clicking the icon directly
      launches an SQL Editor tab, and connects you to the database as
      defined by the connection.
    </p><p>
      To read more about the SQL Editor, see
      <a href="wb-sql-editor.html" title="6.7. SQL Editor">Section 6.7, “SQL Editor”</a>.
    </p></div></body></html>


path: /wb-html-guitools/wb-news-5-2-23.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.17. Changes in MySQL Workbench 5.2.23 (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-24.html" title="A.1.16. Changes in MySQL Workbench 5.2.24 (21 June 2010)"><link rel="next" href="wb-news-5-2-22.html" title="A.1.18. Changes in MySQL Workbench 5.2.22 (02 June 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-23"></a>A.1.17. Changes in MySQL Workbench 5.2.23 (Internal release only)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.2.22.
      </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, when more result tabs were generated than
        could fit into the current panel, it was not obvious how to
        navigate to those result sets that could not currently be
        displayed. This could be achieved using the left and right arrow
        keys, but MySQL Workbench now also includes a spin control to
        navigate the available tabs.
       (Bug #52998)</p></li><li><p>
        The <span class="guilabel">Overview</span> tab in the SQL Editor now
        supports scrolling of content using the mouse wheel.
       (Bug #50782)</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, attempting to execute a selection in the SQL
        Query tab caused all text to be executed, not just the selected
        text.
       (Bug #54536)</p></li><li><p>
        Clicking a table caused MySQL Workbench to produce this error
        message:
      </p><pre class="programlisting">MySQL Workbench has encountered a problem
Cannot access a disposed object
Object name: 'DockedWindowPlugin'.</pre><p>(Bug #54498)</p></li><li><p>
        In the SQL Editor, exporting a record set failed if the target
        path contained an international character.
       (Bug #54479)</p></li><li><p>
        In the <span class="guilabel">Inserts</span> tab of the Table Editor,
        adding a new row and applying changes had no effect.
       (Bug #54456)</p></li><li><p>
        In the <span class="guilabel">General</span> tab of
        <span class="guilabel">Configuration</span> in the Administrator, when
        the <span class="guilabel">Temp directory</span> option was selected, and
        a directory was selected using the file browser, MySQL Workbench
        inserted backslashes rather than forward slashes. If backslashes
        were used in this location in the configuration file, the server
        crashed at startup.
       (Bug #54445)</p></li><li><p>
        In the SQL Editor, if a table in the
        <span class="guilabel">Overview</span> tab was double-clicked, the query
        generated replaced code already entered into the SQL Query tab,
        resulting in the loss of that code.
       (Bug #54362)</p></li><li><p>
        Synchronizing a model with a live database produced incorrect
        SQL code:
      </p><pre class="programlisting">ALTER TABLE `mydb`.`table1` AUTO_INCREMENT =  ;</pre><p>(Bug #54319)</p></li><li><p>
        In the SQL Editor, for result set exports to a tab-delimited
        file, MySQL Workbench added a <code class="filename">.CSV</code> file name
        extension.
       (Bug #54302)</p></li><li><p>
        In the SQL Editor, selecting <span class="guimenu">Alter Table</span> from
        the context-sensitive menu had no effect.
       (Bug #54283)</p></li><li><p>
        In the SQL Editor, editing a table with a row highlighted,
        right-clicking a <code class="literal">BLOB</code> column and loading a
        value from a file resulted in this error:
      </p><pre class="programlisting">An external component has triggered an exception</pre><p>(Bug #54266)</p></li><li><p>
        Changing the name of a stored procedure in the modeler and
        saving changes caused an erroneous <code class="literal">';'</code>
        character to be added to the SQL code sent to the database. That
        resulted in this error:
      </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 ';

USE `911datashop`' at line 1
SQL Statement:
;
USE `911datashop`</pre><p>(Bug #54258, Bug #11761738)</p></li><li><p>
        Clicking the <span class="guilabel">Edit Table Data</span> action item
        from the Home screen caused MySQL Workbench to crash.
       (Bug #54230)</p></li><li><p>
        The forward engineering <span class="guilabel">Omit Schema Qualifier in
        Object Names</span> option was not correctly applied to some
        statements in Trigger code. In these cases, the schema name
        remained in place.
       (Bug #54222)</p></li><li><p>
        Clicking external links in the embedded browser launched
        Internet Explorer rather than the default browser.
       (Bug #54192)</p></li><li><p>
        When entering binary data into the <span class="guilabel">Inserts</span>
        tab for a table, the data was truncated at the first null byte
        (\0).
       (Bug #54156)</p></li><li><p>
        Select All (<span><strong class="keycap">Control+A</strong></span>) did not work when
        editing comments for a table or column.
       (Bug #54154)</p></li><li><p>
        After a foreign key was created, and the referenced table or
        column was changed, the change was not reflected in the foreign
        key, resulting in errors.
       (Bug #54134)</p></li><li><p>
        MySQL Workbench crashed if a pinned result tab was refreshed in the
        SQL Editor.
       (Bug #54114)</p></li><li><p>
        The integrated docs web server listened on a fixed port (8811),
        and was not able to handle the situation where this port may be
        used by another service, such as another MySQL Workbench instance.
       (Bug #54104)</p></li><li><p>
        In the SQL Editor, attempting to create a new schema using
        <span class="guimenu">Create Schema</span> with a server collation of
        <span class="guilabel">utf8 - default collation</span> produced SQL that
        resulted in an error when applied.
       (Bug #54097)</p></li><li><p>
        Performing an undo operation in SQL Editor actually resulted in
        an undo operation in the Modeler.
       (Bug #54091)</p></li><li><p>
        MySQL Workbench suffered user interface issues when used on a
        KDE-based system using a dark theme.
       (Bug #54083)</p></li><li><p>
        The HTTP server thread started by MySQL Workbench to provide
        documentation to the local web browser listened on all IP
        interfaces, even though it is intended only for local use.
       (Bug #54083)</p></li><li><p>
        Database export failed due to a faulty path in the command line:
      </p><pre class="programlisting">15:42:52 Dumping rma3 (etat_produit)

Running: "mysqldump.exe" --defaults-extra-file=c:\docume~1\user\local
settings\temp\tmp9ypdhd  --no-create-info=FALSE --order-by-primary=FALSE --force=FALSE
--no-data=FALSE --tz-utc=TRUE --flush-privileges=FALSE --compress=FALSE --replace=FALSE
--host=127.0.0.1 --insert-ignore=FALSE --extended-insert=TRUE --user=root
--quote-names=TRUE --hex-blob=FALSE --complete-insert=FALSE --add-locks=TRUE --port=3306
--disable-keys=TRUE --delayed-insert=FALSE --delete-master-logs=FALSE --comments=TRUE
--default-character-set=utf8 --flush-logs=FALSE --dump-date=TRUE --allow-keywords=FALSE
--create-options=TRUE --events=FALSE "rma3" "etat_produit"

Could not open required defaults file: c:\docume~1\user\local

Fatal error in defaults handling. Program aborted

mysqldump: Got error: 1045: Access denied for user 'root'@'localhost' (using password:
NO) when trying to connect

Operation failed with exitcode 2</pre><p>(Bug #54067)</p></li><li><p>
        In the <span class="guilabel">Alter Table</span> dialog of the SQL
        Editor, if an attempt was made to set the NN flag for a column
        that did not have it set, an error was generated when the
        changes are applied.
       (Bug #53918)</p></li><li><p>
        When carrying out an Alter Routine operation in the SQL Editor,
        if a routine was modified, and a statement used that, although
        syntactically correct, was not permitted in a routine, all
        modifications were lost when changes were applied.
       (Bug #53887)</p></li><li><p>
        An EER Diagram appeared to contain hidden tables. Although the
        diagram contained 12 tables, when a 'select all' was performed
        the user was informed that 14 tables were selected. It seemed
        that certain tables had been resized to be so small as to no
        longer be visible in the diagram.
       (Bug #53885)</p></li><li><p>
        In the <span class="guilabel">Layer Tree</span> panel, if a layer was
        given a blank name, MySQL Workbench subsequently crashed, rather
        than warning about the of a blank name.
       (Bug #53807)</p></li><li><p>
        Keyboard shortcuts such as <span><strong class="keycap">Command+C</strong></span>,
        <span><strong class="keycap">Command+V</strong></span>, and <span><strong class="keycap">Command+Z</strong></span> were
        not useable consistently in all parts of MySQL Workbench.
       (Bug #53790)</p></li><li><p>
        Columns defined as <code class="literal">BIT</code> appeared as requiring
        synchronization, even if no changes had been made.
       (Bug #53747)</p></li><li><p>
        In the <span class="guilabel">Alter Routine</span> dialog of the SQL
        Editor, if the <span class="guilabel">Find and Replace</span> dialog was
        invoked with <span><strong class="keycap">Control+F</strong></span>, and
        <span><strong class="keycap">Control+V</strong></span> was used to paste in some search
        text, the text was actually pasted into the routine code area.
       (Bug #53735)</p></li><li><p>
        MySQL Workbench failed to build from source on Debian Linux. This
        error was generated:
      </p><pre class="programlisting">libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I./src -I./src -pthread -DNDEBUG -Wall
-Wwrite-strings -Woverloaded-virtual -Wno-sign-compare -g -O2 -Wextra -Wall -Wno-unused
-Wno-deprecated -c src/template.cc  -fPIC -DPIC -o .libs/libctemplate_wb_la-template.o
In file included from ./src/ctemplate/per_expand_data.h:48,
                 from ./src/ctemplate/template_modifiers.h:69,
                 from src/template_modifiers_internal.h:53,
                 from src/template.cc:61:
./src/ctemplate/template_string.h:88: error: ISO C++ forbids declaration of 'TemplateId'
with no type
./src/ctemplate/template_string.h: In member function 'size_t
ctemplate::TemplateIdHasher::operator()(ctemplate::TemplateId) const':
./src/ctemplate/template_string.h:234: warning: right shift count &gt;= width of type
./src/ctemplate/template_string.h: At global scope:
./src/ctemplate/template_string.h:344: warning: overflow in implicit constant conversion
src/template.cc: In static member function 'static void
ctemplate::Template::AssureGlobalsInitialized()':
src/template.cc:2365: warning: comparison between signed and unsigned integer
expressions
make[5]: *** [libctemplate_wb_la-template.lo] Error 1</pre><p>(Bug #53668)</p></li><li><p>
        In the EER Diagram view, it was not possible to delete a
        relationship by right-clicking the relationship, then selecting
        <span class="guimenu">Delete</span> from the context-sensitive menu.
       (Bug #53659)</p></li><li><p>
        In the <span class="guilabel">SQL Query</span> tab of SQL Editor, tooltip
        error messages were still displayed, even after switching to
        another tab.
       (Bug #53634)</p></li><li><p>
        In the <span class="guilabel">Diagram Size</span> dialog, displayed using
        <span class="guimenu">Model</span>, <span class="guimenu">Diagram Properties and
        Size</span>, it was possible to set the size to 100 pages by
        100 pages, but then click outside this area. This caused a MySQL
        Workbench Unexpected Error.
       (Bug #53559)</p></li><li><p>
        The <span class="guilabel">Document Properties</span> dialog was
        displayed across two screens in a multiple-screen setup.
       (Bug #53262)</p></li><li><p>
        After a default primary key name was set in the
        <span class="guilabel">Workbench Preferences</span> dialog, the PK flag
        was not selected as expected in the Table Editor and the column
        flags could not be selected.
       (Bug #52578)</p></li><li><p>
        When synchronizing with a live database, MySQL Workbench did not
        interpret whitespace in <code class="literal">ENUM</code>s correctly. For
        example, <code class="literal">ENUM('image', 'video', 'swf')</code> was
        seen as different from
        <code class="literal">ENUM('image','video','swf')</code>, causing the live
        server and model to appear unsynchronized.
       (Bug #49182)</p></li><li><p>
        When editing a column in the table editor, pressing
        <span><strong class="keycap">Control+Z</strong></span> to undo the edit resulted in a
        previous operation being undone instead.
       (Bug #46286)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-server-administration-manage-server-instances.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>8.5. Manage Server Instances</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-manage-security.html" title="8.4. Manage Security"><link rel="next" href="wb-managing-server-instances.html" title="8.6. Creating and Managing Server Instances"></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-server-instances"></a>8.5. Manage Server Instances</h2></div></div></div><p>
      Clicking this action item launches the Manage Server Instances
      dialog. Within this dialog, you can change the configuration of
      existing server instances or create a new server instance. For
      further details, see
      <a href="wb-managing-server-instances.html" title="8.6. Creating and Managing Server Instances">Section 8.6, “Creating and Managing Server Instances”</a>.
    </p></div></body></html>


path: /wb-html-guitools/wb-manage-db-connections-ssh.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>6.6.4. Standard TCP/IP over SSH 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-manage-db-connections.html" title="6.6. Manage DB Connections Dialog"><link rel="prev" href="wb-manage-db-connections-socket.html" title="6.6.3. Local Socket/Pipe Connection"><link rel="next" href="wb-sql-editor.html" title="6.7. SQL Editor"></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-db-connections-ssh"></a>6.6.4. Standard TCP/IP over SSH Connection</h3></div></div></div><p>
      This connection method enables MySQL Workbench to connect to MySQL
      Server using TCP/IP over an SSH connection.
    </p><p>
      <span class="bold"><strong>Parameters</strong></span>
    </p><p>
      In addition to a number of parameters that are in common with
      Standard TCP/IP connections, this connection method features a
      number of specialized parameters. These are listed here:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <span class="bold"><strong>SSH Hostname</strong></span>: This is the
          name of the SSH server. An optional port number can also be
          provided.
        </p></li><li><p>
          <span class="bold"><strong>SSH Username</strong></span>: This is the
          name of the SSH user name to connect with.
        </p></li><li><p>
          <span class="bold"><strong>SSH Password</strong></span>: The SSH
          password. It is recommended that an SSH key file is also used.
        </p></li><li><p>
          <span class="bold"><strong>SSH Key File</strong></span>: A path to the
          SSH key file. Note: Only key files in OpenSSH format are
          currently supported.
        </p></li></ul></div><p>
      These options can be seen in the following screenshot.
    </p><div class="figure"><a name="wb-manage-db-connections-ssh-parameters"></a><p class="title"><b>Figure 6.4. Manage DB Connections - SSH Parameters</b></p><div class="mediaobject"><img src="images/wb-manage-db-connections-ssh-parameters.png" width="898" height="498" alt="Manage DB Connections - SSH
          Parameters"></div></div><p>
      <span class="bold"><strong>Advanced</strong></span>
    </p><p>
      The options here are the same as for the Standard TCP/IP
      connection. See
      <a href="wb-manage-db-connections-standard.html" title="6.6.2. Standard TCP/IP Connection">Section 6.6.2, “Standard TCP/IP Connection”</a>.
    </p></div></body></html>


path: /wb-html-guitools/wb-adding-roles.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.5.5.1. Adding Roles</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-overview-privileges.html" title="7.5.5. The Schema Privileges Panel"><link rel="prev" href="wb-model-overview-privileges.html" title="7.5.5. The Schema Privileges Panel"><link rel="next" href="wb-adding-users.html" title="7.5.5.2. Adding Users"></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-adding-roles"></a>7.5.5.1. Adding Roles</h4></div></div></div><p>
        To add a role, double-click the <code class="literal">Add Role</code>
        icon. This creates a role with the default name
        <code class="literal">role1</code>. Right-clicking a role 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>role_name</code></em>'</span>: Cuts
            the role
          </p></li><li><p>
            <span class="guimenuitem">Copy
            '<em class="replaceable"><code>role_name</code></em>'</span>: Copies
            the role
          </p></li><li><p>
            <span class="guimenuitem">Edit Role...</span>: Opens the role
            editor
          </p></li><li><p>
            <span class="guimenuitem">Edit in New Window...</span>: Opens the
            role editor in a new editor window
          </p></li><li><p>
            <span class="guimenuitem">Delete
            '<em class="replaceable"><code>role_name</code></em>'</span>:
            Removes the role
          </p></li><li><p>
            <span class="guimenuitem">Copy SQL to Clipboard</span>: Currently
            not implemented
          </p></li></ul></div><p>
        To rename a role, click the role name. Then you will be able to
        edit the text.
      </p><p>
        All roles that have been defined are listed under
        <code class="literal">Roles</code> on the left side of the role editor.
        Double-clicking a role object opens the role editor docked at
        the bottom of the page.
      </p><div class="figure"><a name="wb-roles-image"></a><p class="title"><b>Figure 7.4. Role Editor</b></p><div class="mediaobject"><img src="images/wb-roles.png" width="595" height="254" alt="Role editor"></div></div><p>
        Select the role to which you wish to add objects. You may drag
        and drop objects from the <code class="literal">Physical Schemata</code>
        to the <code class="literal">Objects</code> section of the role editor. To
        assign privileges to a role, select it from the
        <code class="literal">Roles</code> section, then select an object in the
        <code class="literal">Objects</code> section. In the
        <code class="literal">Privileges</code> section, check the rights you wish
        to assign to this role. For example, a
        <code class="literal">web_user</code> role might have only
        <code class="literal">SELECT</code> privileges and only for database
        objects exposed through a web interface. Creating roles can make
        the process of assigning rights to new users much easier.
      </p></div></body></html>


path: /wb-html-guitools/wb-news-5-2-19.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.21. Changes in MySQL Workbench 5.2.19 (16 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-20.html" title="A.1.20. Changes in MySQL Workbench 5.2.20 (27 April 2010)"><link rel="next" href="wb-news-5-2-18.html" title="A.1.22. Changes in MySQL Workbench 5.2.18 (13 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-19"></a>A.1.21. Changes in MySQL Workbench 5.2.19 (16 April 2010)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.2.18.
      </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">Configuration</span> tab of the
        Administrator, the list showing the section in the configuration
        file has been changed to a read-only control.
       (Bug #52443)</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, when altering a routine, if the Apply SQL
        Script button was clicked, MySQL Workbench froze.
       (Bug #52853)</p></li><li><p>
        When trying to open a saved model file, MySQL Workbench generated
        this error:
      </p><pre class="programlisting">error executing plugin wb.file.openModel: Internal error:
wait box creation must be done on the main thread</pre><p>(Bug #52851)</p></li><li><p>
        Double-clicking a model file (<code class="filename">*.mwb</code>) to
        open it caused MySQL Workbench to crash.
       (Bug #52838)</p></li><li><p>
        When opening a connection to start querying from the Home
        screen, the HUD displayed correctly. However, an error occurred
        with the connection, and the error dialog was displayed beneath
        the HUD. This meant it was not possible to click the dialog,
        although pressing <span><strong class="keycap">ESC</strong></span> cleared it. The error
        dialog should have been displayed in front of the HUD, making it
        clickable.
       (Bug #52812)</p></li><li><p>
        MySQL Workbench crashed when carrying out most tasks in the SQL
        Editor including adding tables, adding columns, and altering
        tables.
       (Bug #52789)</p></li><li><p>
        The MySQL Workbench preference to locate the sidebar on the right
        did not work. Further, the <span class="guibutton">Toggle Sidebar</span>
        button did not function.
       (Bug #52631, Bug #53072)</p></li><li><p>
        Attempting to build MySQL Workbench using the
        <code class="literal">LDFLAGS="-Wl,--as-needed"</code> linker options
        failed.
       (Bug #52570)</p></li><li><p>
        MySQL Workbench listed <code class="literal">gtkmm</code> 2.4 as a dependency
        in <code class="filename">configure.in</code>. However, it used features
        only available in later versions of this library.
       (Bug #52406)</p></li><li><p>
        In the Object Browser of the SQL Editor, if a schema was
        dropped, the schema concerned was not removed from the Object
        Browser, but another schema was. However, if the connection was
        synchronized, the Object Browser displayed the correct
        information.
       (Bug #51919)</p></li><li><p>
        In the <span class="guilabel">Data Dump</span> facility of the
        Administrator, if Export to Self-Contained file was selected and
        a destination file explicitly chosen, the selected schema was
        deselected on return from the file chooser.
       (Bug #51797)</p></li><li><p>
        MySQL Workbench crashed when creating a foreign key relationship in
        the EER Diagram view.
       (Bug #51602)</p></li><li><p>
        In the SQL Editor, the syntax highlighter coloured two dashes as
        a comment. This was incorrect because two dashes should be
        highlighted as a comment only when followed by a space.
       (Bug #51596)</p></li><li><p>
        The internal script MySQL Workbench used to add a new user to MySQL
        Server was incorrect. After MySQL Workbench was started, it was
        possible to create a new user, but attempts to create additional
        users resulted in an unhandled exception.
       (Bug #50947)</p></li><li><p>
        In the Table Editor of the MySQL Model page, and the
        <span class="guilabel">Alter Table</span> dialog of the SQL Editor, the
        text label “<span class="quote">comments:</span>” was truncated to
        “<span class="quote">commen</span>”.
       (Bug #50765)</p></li><li><p>
        In the EER Diagram view, using the context-sensitive menu items
        <span class="guimenu">Copy table</span>, or <span class="guimenu">Edit in New
        Window</span> resulted in this error:
      </p><pre class="programlisting">plugin:wb.edit.editSelectedFigureInNewWindow
Cannot execute plugin
A model diagram must be selected.</pre><p>(Bug #50649)</p></li><li><p>
        MySQL Workbench appeared to perform a Save As operation rather than
        a Save operation when saving a modified script file in the SQL
        Editor. Also, there was no indication that the file being worked
        on had unsaved changes (this is normally indicated by
        <code class="literal">'*'</code> in the title bar). Finally, the file name
        was not displayed on the SQL Editor tab.
       (Bug #50055, Bug #51373)</p></li><li><p>
        The <span class="guimenu">File</span>, <span class="guimenu">Open Recent</span> menu
        item was not being populated with recently opened script files.
       (Bug #50053)</p></li><li><p>
        When two routine groups were being edited, and in both cases the
        <span class="guilabel">Routines</span> tab was selected to display the
        SQL code, switching between the routine groups did not result in
        the target <span class="guilabel">Routines</span> tab contents being
        updated. For example, if <code class="literal">routines1</code> was being
        displayed and the <code class="literal">routines2</code> selected, the
        <code class="literal">routines1</code> code continued to be displayed in
        the <span class="guilabel">Routines</span> tab.
       (Bug #49432)</p></li><li><p>
        In the SQL Editor, the <span class="guilabel">Alter Schema</span> dialog
        had a comments field. However, the comments entered were not
        used in the generated DDL code. The comments field no longer
        appears.
       (Bug #49280)</p></li><li><p>
        In the EER Diagram view, when typing a new value into the
        Navigator Zoom input control, the zoom level of the diagram
        changed as the new value was being entered. The diagram should
        only have been redrawn when the new value being entered in was
        fully entered by pressing the <span><strong class="keycap">Enter</strong></span> key,
        instead of changing dynamically as the zoom level value was
        being entered.
       (Bug #48597)</p></li><li><p>
        In the EER Diagram view, if the cardinality of a relationship
        was changed and then an attempt made to edit a second
        relationship, the cardinality of the first relationship was
        applied to the second relationship.
       (Bug #46906)</p></li><li><p>
        The <span class="guilabel">Assigned Privileges</span> list on the
        <span class="guilabel">Privileges</span> tab in the View Editor lacked
        default grant options such as SELECT, UPDATE, and DROP.
       (Bug #42157)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-manage-server-connections-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.4. The Connections 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-accounts-tab-roles.html" title="8.7.3.1. Administrative Roles"><link rel="next" href="wb-manage-server-variables-tab.html" title="8.7.5. The Variables 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-connections-tab"></a>8.7.4. The Connections Tab</h3></div></div></div><p>
        The Connections tab lists all current connections to the
        monitored server.
      </p><div class="figure"><a name="wb-manage-server-connections-tab-screenshot"></a><p class="title"><b>Figure 8.7. Administrator - Connections Tab</b></p><div class="mediaobject"><img src="images/wb-manage-server-connections-tab.png" width="1024" height="707" alt="Administrator - Connections Tab"></div></div></div></body></html>


path: /wb-html-guitools/wb-using-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.7.1.2. Adding Tables to 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-tables.html" title="7.7.1. Creating Tables"><link rel="prev" href="wb-tables-physical-schemata.html" title="7.7.1.1. Adding Tables to the Physical Schemata"><link rel="next" href="wb-table-editor.html" title="7.7.1.3. The MySQL Table 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-using-table-tool"></a>7.7.1.2. Adding Tables to an EER Diagram</h4></div></div></div><p>
      Tables can also be added to an EER Diagram using the
      <code class="literal">table</code> tool on the vertical toolbar. Make sure
      that the <span class="guilabel">EER Diagram</span> tab is selected, then
      right-click the table icon on the vertical toolbar. The table icon
      is the rectangular tabular icon.
    </p><p>
      Clicking the mouse on this icon changes the mouse pointer to a
      table pointer. You can also change the mouse pointer to a table
      pointer by pressing the <span><strong class="keycap">T</strong></span> key.
    </p><p>
      Choosing the <code class="literal">table</code> tool changes the contents of
      the toolbar that appears immediately below the menu bar. When the
      <code class="literal">Tables</code> pointer is active, this toolbar contains
      a schemata list, an engines list, a collations list, and a color
      chart list. Use these lists to select the appropriate schema,
      engine, collation, and color accent for the new table. Make sure
      that you associate the new table with a database. The engine and
      collation of a table can be changed using the table editor. The
      color of your table can be changed using the
      <code class="literal">Properties</code> palette. The <code class="literal">Default
      Engine</code> and <code class="literal">Default Collation</code> values
      refer to the database defaults.
    </p><p>
      Create a table by clicking anywhere on the EER Diagram canvas.
      This creates a new table with the default name
      <code class="literal">table1</code>. To revert to the default mouse pointer,
      click the arrow icon at the top of the vertical toolbar.
    </p><div class="figure"><a name="wb-table-eer-view-image"></a><p class="title"><b>Figure 7.7. A Table on an EER Diagram</b></p><div class="mediaobject"><img src="images/wb-table-eer-view.png" width="163" height="270" alt="A table on an EER diagram"></div></div><p>
      As shown in the preceding diagram, the primary key is indicated by
      a key icon and indexed fields are indicated by a different colored
      diamond icon. Click the arrow to the right of the table name to
      toggle the display of the fields. Toggle the display of indexes
      and triggers in the same way.
    </p><p>
      Right-clicking a table 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>table_name</code></em>'</span>
        </p></li><li><p>
          <span class="guimenuitem">Copy
          '<em class="replaceable"><code>table_name</code></em>'</span>
        </p></li><li><p>
          <span class="guimenuitem">Edit Table...</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">Copy Insert to Clipboard</span>
        </p></li><li><p>
          <span class="guimenuitem">Delete
          '<em class="replaceable"><code>table_name</code></em>'</span>
        </p></li></ul></div><p>
      With the exception of the deletion item, these menu items function
      as described in <a href="wb-tables-physical-schemata.html" title="7.7.1.1. Adding Tables to the Physical Schemata">Section 7.7.1.1, “Adding Tables to the Physical Schemata”</a>. 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></body></html>


path: /wb-html-guitools/wb-eer-diagrams-section.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.5.3. EER Diagrams</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-tool-specific-toolbar-items.html" title="7.5.2.1. Tool-Specific Toolbar Items"><link rel="next" href="wb-view-overview-physical-schemata.html" title="7.5.4. The Physical Schemata 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-eer-diagrams-section"></a>7.5.3. EER Diagrams</h3></div></div></div><p>
      Use the <code class="literal">Add Diagram</code> icon in the <code class="literal">MySQL
      Model</code> area to create EER diagrams. When you add an EER
      diagram, a new tab appears below the toolbar. Use this tab to
      navigate to the newly created EER diagram. For further discussion
      of EER Diagrams, see <a href="wb-eer-diagram-editor.html" title="7.6. EER Diagram Editor">Section 7.6, “EER Diagram Editor”</a>.
    </p></div></body></html>


path: /wb-html-guitools/wb-news-5-2-1.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.39. Changes in MySQL Workbench 5.2.1 (22 May 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-2.html" title="A.1.38. Changes in MySQL Workbench 5.2.2 (27 July 2009)"><link rel="next" href="wb-news-5-2-0.html" title="A.1.40. Changes in MySQL Workbench 5.2.0 (30 April 2009 Alpha)"></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-1"></a>A.1.39. Changes in MySQL Workbench 5.2.1 (22 May 2009)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.2.0.
      </p><p>This section has no changelog entries.</p></div></body></html>


path: /wb-html-guitools/wb-windows-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.3. Uninstalling 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-launching-windows.html" title="3.3.2. Launching MySQL Workbench on Windows"><link rel="next" href="wb-installing-linux.html" title="3.3.4. Installing MySQL Workbench on Linux"></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-windows-uninstalling"></a>3.3.3. Uninstalling MySQL Workbench on Windows</h3></div></div></div><p>
        The method for uninstalling MySQL Workbench depends on how you
        installed MySQL Workbench in the first place.
      </p><p>
        <span class="bold"><strong>Removing MySQL Workbench After Installation
        Using the Installer Package</strong></span>
      </p><div class="orderedlist"><ol type="1"><li><p>
            To uninstall MySQL Workbench, open the <span class="guilabel">Control
            Panel</span> and Choose <span class="guilabel">Add or Remove
            Programs</span>. Find the MySQL Workbench entry and choose
            the <span class="guibutton">Remove</span> button. This will remove
            MySQL Workbench.
          </p></li><li><p>
            Any modules added to the
            <code class="filename">C:\%PROGRAMFILES%\MySQL\MySQL Workbench
            <em class="replaceable"><code>version</code></em>\modules</code>
            directory will <span class="bold"><strong>not</strong></span> be
            deleted.
          </p></li></ol></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
          If you installed MySQL Workbench using the Installer package, it
          is not possible to remove MySQL Workbench from the command line.
          Although you can manually remove some of the components, there
          is no command-line option for removing MySQL Workbench.
        </p><p>
          Removing the MySQL Workbench directory manually will not remove
          all the files belonging to MySQL Workbench.
        </p></div><p>
        <span class="bold"><strong>Removing MySQL Workbench After Installation
        from a Zip File</strong></span>
      </p><p>
        To remove MySQL Workbench, just delete the MySQL Workbench directory.
      </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
          If you installed any additional modules within the
          <code class="filename">modules</code> directory and you want to keep
          them, make sure you copy those modules to a different
          directory before deleting the MySQL Workbench directory.
        </p></div></div></body></html>


path: /wb-html-guitools/wb-installing-linux.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>3.3.4. Installing 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-windows-uninstalling.html" title="3.3.3. Uninstalling MySQL Workbench on Windows"><link rel="next" href="wb-launching-linux.html" title="3.3.5. Launching MySQL Workbench on Linux"></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-linux"></a>3.3.4. Installing MySQL Workbench on Linux</h3></div></div></div><p>
        There are binary distributions of MySQL Workbench available for
        several variants of Linux, including Fedora, Oracle Linux, and
        Ubuntu.
      </p><p>
        In addition to the binary distributions, it is also possible to
        download the MySQL Workbench source code as a
        <code class="filename">tar.gz</code> or RPM package.
      </p><p>
        Check the MySQL Workbench
        <a href="http://dev.mysql.com/downloads/workbench">download
        page</a> for the latest packages.
      </p><p>
        The procedure for installing on Linux depends on which Linux
        distribution you are using.
      </p><p>
        <span class="bold"><strong>Installing DEB packages</strong></span>
      </p><p>
        On Ubuntu, and other systems that use the Debian package scheme,
        you can install MySQL Workbench using a command such as:
      </p><pre class="programlisting">shell&gt; <strong class="userinput"><code>sudo dpkg -i <em class="replaceable"><code>package</code></em>.deb</code></strong>
</pre><p>
        <code class="filename"><em class="replaceable"><code>package</code></em>.deb</code> is
        the MySQL Workbench package name; for example,
        <code class="filename">mysql-workbench-oss-<em class="replaceable"><code>version</code></em>_i386.deb</code>,
        where <em class="replaceable"><code>version</code></em> is the MySQL Workbench
        version number.
      </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
          You may be warned that certain libraries are not available,
          depending on what you already have installed. Install the
          required libraries and then install the MySQL Workbench package
          again.
        </p></div><p>
        <span class="bold"><strong>Installing RPM packages</strong></span>
      </p><p>
        On Red Hat-based systems, and other systems that use the RPM
        package format, MySQL Workbench can be installed by a command such
        as:
      </p><pre class="programlisting">shell&gt; <strong class="userinput"><code>sudo rpm -i <em class="replaceable"><code>package</code></em>.rpm</code></strong>
</pre><p>
        <code class="filename"><em class="replaceable"><code>package</code></em>.rpm</code> is
        the MySQL Workbench package name; for example,
        <code class="filename">mysql-workbench-oss-<em class="replaceable"><code>version</code></em>-1fc10.x86_64.rpm</code>,
        where <em class="replaceable"><code>version</code></em> is the MySQL Workbench
        version number.
      </p></div></body></html>


path: /wb-html-guitools/wb-eer-diagram-editor.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.6. EER Diagram 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-data-modeling.html" title="Chapter 7. Data Modeling"><link rel="prev" href="wb-properties-palette.html" title="7.5.12. The Properties Palette"><link rel="next" href="wb-vertical-toolbar.html" title="7.6.1. The Vertical Toolbar"></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-eer-diagram-editor"></a>7.6. EER Diagram Editor</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-vertical-toolbar.html">7.6.1. The Vertical Toolbar</a></span></dt></dl></div><p>
    EER diagrams are created by double-clicking the <code class="literal">Add
    Diagram</code> icon. You may create any number of EER diagrams
    just as you may create any number of physical schemata. Each EER
    diagram shows as a tab below the toolbar; a specific EER diagram is
    selected by clicking its tab.
  </p><p>
    Clicking an EER diagram tab navigates to the canvas used for
    graphically manipulating database objects. The <code class="literal">Vertical
    Toolbar</code> is on the left side of this page.
  </p></div></body></html>


path: /wb-html-guitools/wb-sakila-eer-png.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.8.4.1. A PNG File of the sakila Database</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-documenting-sakila.html" title="7.8.4. Documenting the sakila Database"><link rel="prev" href="wb-documenting-sakila.html" title="7.8.4. Documenting the sakila Database"><link rel="next" href="wb-printing.html" title="7.9. Printing"></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-sakila-eer-png"></a>7.8.4.1. A PNG File of the <code class="literal">sakila</code> Database</h4></div></div></div><p>
      Find following an EER digram showing all the tables in the
      <code class="literal">sakila</code> database. This image was created using
      the <span class="guimenu">File</span>, <span class="guisubmenu">Export</span>,
      <span class="guimenuitem">Export as PNG...</span> menu item.
    </p><div class="figure"><a name="wb-sakila-eer-image"></a><p class="title"><b>Figure 7.45. The <code class="literal">sakila</code> Database EER Diagram</b></p><div class="mediaobject"><img src="images/wb-sakila-eer.png" width="800" height="774" alt="The sakila Database EER
          diagram"></div></div><p>
      The object notation style used in
      <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> is <code class="literal">Workbench (PKs
      only)</code>. This notation shows only primary keys and no
      other columns, which is especially useful where space is at a
      premium. The relationship notation is the default, Crow's Foot.
    </p><p>
      As the connection lines show, each table is related to at least
      one other table in the database (with the exception of the
      <code class="literal">film_text</code> table). Some tables have two foreign
      keys that relate to the same table. For example the
      <code class="literal">film</code> table has two foreign keys that relate to
      the <code class="literal">language</code> table, namely
      <code class="literal">fk_film_language_original</code> and
      <code class="literal">fk_film_language</code>. Where more than one
      relationship exists between two tables, the connection lines run
      concurrently.
    </p><p>
      Identifying and nonidentifying relationships are indicated by
      solid and broken lines respectively. For example, the foreign key
      <code class="literal">category_id</code> is part of the primary key in the
      <code class="literal">film_category</code> table so its relationship to the
      <code class="literal">category</code> table is drawn with a solid line. On
      the other hand, in the <code class="literal">city</code> table, the foreign
      key, <code class="literal">country_id</code>, is not part of the primary key
      so the connection uses a broken line.
    </p></div></body></html>


path: /wb-html-guitools/wb-news-5-1-19.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.2.1. Changes in MySQL Workbench 5.1.19 (06 September 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.1.x.html" title="A.2. Changes in Release 5.1"><link rel="prev" href="changes-5.1.x.html" title="A.2. Changes in Release 5.1"><link rel="next" href="wb-news-5-1-18.html" title="A.2.2. Changes in MySQL Workbench 5.1.18 (03 September 2009 General Availability)"></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-19"></a>A.2.1. Changes in MySQL Workbench 5.1.19 (06 September 2010)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.1.18.
      </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">Forward Engineer SQL Script</span> wizard
        the check box <span class="guilabel">Generate DROP SCHEMA</span> now
        causes every <code class="literal">CREATE SCHEMA</code> statement to be
        prepended with <code class="literal">DROP SCHEMA IF EXISTS
        `schemaname`</code>.
       (Bug #46706)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        The <span class="guilabel">Omit Schema Qualifier in Object Names</span>
        option in the <span class="guilabel">Forward Engineer SQL Script</span>
        wizard appeared to have no effect. After selecting this option
        and proceeding through the wizard, the generated script still
        contained schema qualifiers.
       (Bug #46268)</p></li><li><p>
        Synchronizing a model with a live database, without having made
        any changes to the model or the database, caused the model to
        appear as unsaved, indicating that unnecessary changes may have
        been made to the model.
       (Bug #40914)</p></li><li><p>
        When synchronizing with a live database, if the direction of
        synchronization was changed to inbound, the script generated
        indicated that no inbound changes would be made.
       (Bug #40648)</p></li><li><p>
        MySQL Workbench EER Diagram view did not permit the creation of a
        foreign key constraint on a primary key.
       (Bug #39546)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-views-overview-notes.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.5.7. The Model Notes 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-model-editor.html" title="7.5. Model Editor"><link rel="prev" href="wb-views-overview-scripts.html" title="7.5.6. The SQL Scripts Panel"><link rel="next" href="wb-history-palette.html" title="7.5.8. The History 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-views-overview-notes"></a>7.5.7. The Model Notes Panel</h3></div></div></div><p>
      Use the <code class="literal"> Model Notes</code> panel to write project
      notes. Any scripts or notes added will be saved with your project.
    </p></div></body></html>


path: /wb-html-guitools/wb-news-5-1-17.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.2.3. Changes in MySQL Workbench 5.1.17 (14 August 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-18.html" title="A.2.2. Changes in MySQL Workbench 5.1.18 (03 September 2009 General Availability)"><link rel="next" href="wb-news-5-1-16.html" title="A.2.4. Changes in MySQL Workbench 5.1.16 (30 June 2009 General Availability)"></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-17"></a>A.2.3. Changes in MySQL Workbench 5.1.17 (14 August 2009)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.1.16.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        Bug reported: If code with an error was entered into the
        <span class="guilabel">Triggers</span> tab of the Table Editor, the code
        disappeared when typing stopped.
      </p><p>
        What actually happened was when a table name was given that was
        not that of the table currently being edited, the trigger code
        was moved to the table specified.
      </p><p>
        MySQL Workbench has now been changed so that if a table name is
        specified other than other than that of the table being edited,
        then the table name is highlighted as a syntax error, rather
        than moving the trigger code to the table actually specified.
       (Bug #46349)</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><li><p>
        When a Text Object was placed on an EER Diagram it could not be
        resized and also did not appear to automatically resize
        correctly around any text entered.
      </p><p>
        Text Objects on the EER Diagram canvas can now be resized by
        grabbing the sizing handles that appear when the object is
        selected. As with Table Objects, a manual modification of the
        object sets the <code class="literal">manualSizing</code> attribute of the
        Text Object to <code class="literal">true</code>. This property can also
        be set in the Properties pane. This means that these Text
        Objects automatically expand on entering more text, but the size
        isn't automatically reduced when text is removed or wrapped
        manually. By setting this property to <code class="literal">false</code>,
        the Text Object size is also automatically reduced to fit the
        containing text.
       (Bug #39887)</p></li><li><p>
        In the <span class="guilabel">Foreign Keys</span> tab it was not possible
        to rename a foreign key by renaming the corresponding index
        entry.
      </p><p>
        MySQL Workbench has been changed so that it is possible to rename a
        foreign key by renaming its corresponding index. The foreign key
        name is now automatically updated when the index is renamed. The
        index name is also updated when the foreign key name is changed.
       (Bug #39511)</p></li><li><p>
        In MySQL Workbench it was not possible to generate an export script
        without schema information. MySQL Workbench has been changed to
        include the option <span class="guilabel">Omit Schema Qualifier in Object
        Names</span>. This can be found in the <span class="guilabel">Forward
        Engineer SQL Script</span> and <span class="guilabel">Forward Engineer to
        Database</span> wizards.
      </p><p>
        Note that this does not change the script used in Procedures or
        Views. If you are using schema qualifiers in these locations you
        will have to remove them manually.
       (Bug #34827)</p></li><li><p>
        The menu item <span class="guimenu">Help</span>, <span class="guimenu">View Reported
        Bugs</span> has been added to the main menu. This opens the
        bugs listing for MySQL Workbench in the default browser.
       (Bug #32813)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        When trying to connect to a server from MySQL Workbench, this error
        was generated:
      </p><pre class="programlisting">Connection 'Server' could not be established: No bool value passed for CLIENT_COMPRESS</pre><p>
        This occurred when using connections created in MySQL Workbench
        5.2.1 with 5.2.2.
       (Bug #46635)</p></li><li><p>
        On the EER Diagram, if an Undo operation was carried out after
        an Autosize operation, table objects were reduced to their
        minimum size.
       (Bug #46605)</p></li><li><p>
        An Unknown Exception was caught after placing a relationship
        between two tables in the EER Diagram. The exception generated
        was:
      </p><pre class="programlisting">Unknown Exception caught in: c:\documents and settings\mysqldev\my documents\visual
studio 2008\projects\workbench\backend\windows\wbprivate.wr\src\Wb.h at line 1026</pre><p>(Bug #46562)</p></li><li><p>
        In the <span class="guilabel">Columns</span> tab of the Table Editor, if
        a default value was added for a column, it could not then be
        removed.
       (Bug #46509)</p></li><li><p>
        Calling the <span class="guimenu">Plugins</span>,
        <span class="guimenu">Catalog</span>, <span class="guimenu">Dump All Table
        Columns</span> item from the main menu generated this error:
      </p><pre class="programlisting">Error executing plugin wb.catalog.util.dumpColumns: error calling
PyWbUtils.printAllColumns: 'str' object is not callable</pre><p>(Bug #46477)</p></li><li><p>
        In the EER Diagram, if a layer was double-clicked a new tab was
        added to the Table Editor. However, if a relationship or table
        was double-clicked any existing tab would be reused, rather than
        a new tab being created. There appeared to be no consistent
        policy on how double-clicks should be handled.
       (Bug #46466)</p></li><li><p>
        The <code class="literal">INSERT</code> statements generated for columns
        of type <code class="literal">TEXT</code> by the Insert Editor were not
        correct because the values were not quoted. Also, when the
        Insert Editor was closed and then reopened the last column entry
        was lost.
       (Bug #46390)</p></li><li><p>
        When an attempt was made to synchronize Stored Procedures from
        the source database to MySQL Workbench, the Stored Procedures were
        deleted from the source database.
       (Bug #46346)</p></li><li><p>
        If an attempt was made to load a new model file while a model
        file was already loaded, this error dialog was generated:
      </p><pre class="programlisting">OverviewBE::get_node: invalid node 1.1</pre><p>(Bug #46292)</p></li><li><p>
        When <span class="guimenu">Plugins</span>, <span class="guimenu">Catalog</span>,
        <span class="guimenu">Give a Prefix to All Tables in Catalog</span>, was
        selected from the main menu, MySQL Workbench crashed with this
        error:
      </p><pre class="programlisting">** (mysql-workbench-bin:5898): WARNING **:
/home/miguel/.mysql/workbench/wb_options.xml:325: link
'b7ee49b4-67f5-11de-9d1e-0800272fd858' &lt;object GrtObject&gt; key=owner could not be resolved
** Message: item_activated: 0xadbb608 -&gt; 'plugin:wb.file.newDocument'
** Message: unhandled message 4: wb.file.newDocument finished in 0.34s

** Message: item_activated: 0xaacbea8 -&gt; 'plugin:wb.util.prefixTables'

glibmm-ERROR **:
unhandled exception (type std::exception) in signal handler:
what: request_input_becb not implemented

aborting...
Aborted</pre><p>
        This only happened when running on Linux.
       (Bug #46280)</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 an SQL Script was added and then its name changed, the name
        would erroneously revert back to “<span class="quote">Script</span>”.
       (Bug #46246)</p></li><li><p>
        Reverse Engineering from a live database failed if the server
        had <code class="literal">sql_mode</code> set to
        <code class="literal">ANSI_QUOTES</code>.
       (Bug #46185)</p></li><li><p>
        In the <span class="guilabel">Columns</span> tab of the Table Editor,
        selecting the <span class="guilabel">AI</span> check box before entering
        a name for the column caused MySQL Workbench to crash.
       (Bug #46150)</p></li><li><p>
        The Microsoft Windows version of MySQL Workbench leaked GDI objects,
        resulting in a drop in performance.
       (Bug #46101)</p></li><li><p>
        The text contained in a Text Object in an EER Diagram was syntax
        highlighted. This was not appropriate for a simple text note.
       (Bug #46092)</p></li><li><p>
        When using the <span class="guilabel">Reverse Engineer Database</span>
        wizard a Segmentation Fault was generated by MySQL Workbench on
        Ubuntu Linux:
      </p><pre class="programlisting">(mysql-workbench-bin:22735): Gtk-CRITICAL **: gtk_tree_selection_get_selected: assertion
`selection-&gt;type != GTK_SELECTION_MULTIPLE' failed
** Message: item_activated: 0x30d4920 -&gt; 'plugin:db.plugin.database.rev_eng'
** Message: unhandled message 4: db.plugin.database.rev_eng finished in 0,00s</pre><p>(Bug #46078)</p></li><li><p>
        When writing code in the Routine Editor it appeared that the
        code was lost if the Routine Editor was closed.
       (Bug #46049)</p></li><li><p>
        MySQL Workbench crashed if a table was selected, right-clicked, and
        then the menu item <span class="guimenu">Copy SQL to Clipboard</span>
        chosen.
      </p><p>
        MySQL Workbench also crashed with the same model if an attempt was
        made to export the schema using the <span class="guilabel">Forward Engineer
        SQL CREATE Script</span> wizard.
       (Bug #46025)</p></li><li><p>
        In the EER Diagram, when hovering the cursor over a column in a
        table, the hint box contained the text associated with the
        subsequent column, and the first column hint box contained the
        name of the table.
       (Bug #45997)</p></li><li><p>
        The <span class="guilabel">Synchronize Model with Database</span> wizard
        contain a spelling mistake. The word
        “<span class="quote">synchronization</span>” was mispelled as
        “<span class="quote">synchronizatiob</span>”.
       (Bug #45939)</p></li><li><p>
        If an attempt was made to copy and paste a trigger, the trigger
        code would revert to the source trigger, when the pasted trigger
        was edited.
      </p><p>
        MySQL Workbench has been changed so that triggers are associated
        with the table in which they are edited. If a trigger has the
        wrong schema or table pointed to by its <code class="literal">CREATE
        TRIGGER</code> statement, it will be highlighted as a syntax
        error.
       (Bug #45931)</p></li><li><p>
        MySQL Workbench 5.1.16 failed to create INSERTs in the exported DDL
        for some tables.
       (Bug #45920)</p></li><li><p>
        MySQL Workbench crashed at startup on Mac OS X.
       (Bug #45869)</p></li><li><p>
        When a model was synchronized with a live database, and only
        stored procedures needed to be synchronized, this error was
        generated:
      </p><pre class="programlisting">ERROR: Error 1046: No database selected</pre><p>(Bug #45867)</p></li><li><p>
        In MySQL Workbench running on Mac OS X, if any changes were made in
        the <span class="guilabel">Page Setup</span> dialog, this error was
        generated:
      </p><pre class="programlisting">builtin:wb.page_setup

Type mismatch: expected object of type app.PaperType, but got app.PaperType</pre><p>
        Note, the <span class="guilabel">Page Setup</span> dialog is accessed by
        selecting <span class="guimenu">File</span>, <span class="guimenu">Page
        setup...</span> from the main menu.
       (Bug #45861)</p></li><li><p>
        The <span class="guilabel">Forward Engineering SQL ALTER Script</span>
        wizard generated <code class="literal">DROP INDEX</code> and <code class="literal">ADD
        UNIQUE INDEX</code> statements for any unique index, even for
        one that had not been modified. These unnecessary statements had
        to be manually deleted from the script.
       (Bug #45830)</p></li><li><p>
        When compiling the MySQL Workbench source with GNU C Compiler (GCC)
        version 4.4.0, the compilation failed because the version of the
        Boost library used was not compatible with GCC 4.4.0.
      </p><p>
        The version of the Boost library required for compatibility with
        GCC 4.4.0 is 1.37 or later.
       (Bug #45798)</p></li><li><p>
        MySQL Workbench crashed and also lost procedure objects when
        attempting to synchronize with a live database.
       (Bug #45773)</p></li><li><p>
        When building MySQL Workbench on PowerPC/PowerPC64 on Linux, the
        build failed because “<span class="quote">bswap32</span>” was not defined.
      </p><pre class="programlisting">In file included from src/template_string.cc:47:
src/base/arena.h: In member function 'void google::BaseArena::ReturnMemory(void*,
size_t)':
src/base/arena.h:211: warning: comparison between signed and unsigned integer expressions
src/template_string.cc: In function 'uint32 UNALIGNED_LOAD32(const void*)':
src/template_string.cc:120: error: 'bswap32' was not declared in this scope</pre><p>(Bug #45629)</p></li><li><p>
        Relationship lines were not always drawn on the EER Diagram.
       (Bug #45583)</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>
        MySQL Workbench 5.1.13 running on Ubuntu Linux crashed when it
        attempted to load a model file created using MySQL Workbench 5.0 on
        Windows XP. The same model file did load correctly using
        MySQL Workbench 5.1.12.
       (Bug #45491)</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>
        When synchronizing a model with a live database, clicking the
        <span class="guibutton">Update Model</span> actually caused the server
        to be updated as if <span class="guibutton">Update Source</span> had
        been clicked.
       (Bug #45456)</p></li><li><p>
        The settings for <code class="literal">ON UPDATE</code> and <code class="literal">ON
        DELETE</code> in Foreign Key/Relationship Defaults set in the
        <span class="guilabel">Model</span> tab of <span class="guimenu">Tools</span>,
        <span class="guimenu">Preferences</span>, were not taken into account when
        new tables and relationships were created.
       (Bug #45393, Bug #45239)</p></li><li><p>
        The Inserts Editor did not have functionality to remove a row
        once added. This problem only occurred with MySQL Workbench running
        on Linux.
       (Bug #44458)</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 <span class="guilabel">Forward Engineer SQL Script</span> wizard,
        on the <span class="guilabel">SQL Object Export Filter</span> page, if
        <span class="guibutton">Back</span> was clicked to go to the
        <span class="guilabel">SQL Export Options</span> page, and then
        <span class="guibutton">Next</span> was clicked to return to the
        <span class="guilabel">SQL Object Export Filter</span> page, on that page
        all sections were duplicated. If this was repeated the objects
        were triplicated and so on.
       (Bug #44317)</p></li><li><p>
        In the <span class="guilabel">Columns</span> tab of the Table Editor,
        when setting a column data type to <code class="literal">ENUM</code> it
        was not possible to choose Collation for the column details.
        Only the Table Default collation was available.
       (Bug #43352)</p></li><li><p>
        In the <span class="guilabel">Columns</span> tab of the Table Editor, a
        column name could be entered with leading or trailing spaces.
        That led to this error when exporting the schema:
      </p><pre class="programlisting">ERROR 1166 (42000): Incorrect column name 'name  '</pre><p>(Bug #43345)</p></li><li><p>
        The script created by Forward Engineer SQL CREATE Script failed
        with an error if the model contained a view that referenced a
        column defined in another view.
       (Bug #43061)</p></li><li><p>
        In the <span class="guilabel">Columns</span> tab of the Table Editor, if
        a column is dragged and dropped to change its position, after
        the move the column highlighted is not the one moved.
       (Bug #42476)</p></li><li><p>
        In the <span class="guilabel">Columns</span> tab of the Table Editor, if
        a column was deleted, and it had inserts in the
        <span class="guilabel">Inserts</span> tab, in the
        <span class="guilabel">Inserts</span> tab the last entry would be
        incorrectly deleted.
       (Bug #41931)</p></li><li><p>
        In the <span class="guilabel">Foreign Keys</span> tab of the Table
        Editor, the values of the <span class="guilabel">On Update</span> and
        <span class="guilabel">On Delete</span> fields, in the <span class="guilabel">Foreign
        Key Options</span> pane, did not always refresh for each
        Foreign Key constraint selected in the table on the left side.
      </p><p>
        For example, if the currently selected constraint was
        <code class="literal">SET NULL</code> for <span class="guilabel">On Delete</span>,
        and then a different selection was made for a constraint that
        has no action specified for <span class="guilabel">On Delete</span>, the
        field remained with the value from the previous selection, which
        gave a false indication that such action was specified in the
        definition of the newly selected constraint.
      </p><p>
        Note that incorrect field values were only displayed when the
        last selected constraint did not have an action defined.
       (Bug #41887)</p></li><li><p>
        When the flags of a User Defined Type were changed in the
        <span class="guilabel">User Types</span> panel, the change was not
        updated in the EER Diagram, the Table Editor, or the exported
        SQL.
       (Bug #41453)</p></li><li><p>
        A model failed to synchronize with a live database because a
        column of type <code class="literal">DOUBLE</code> was exported as a type
        <code class="literal">DOUBLE(256)</code>.
       (Bug #41290)</p></li><li><p>
        When a MySQL Workbench model was synchronized with a live database,
        a foreign key relationship, recently added to the database, was
        not reflected in the EER Diagram. Although the foreign key was
        created in the table object, the relationship connector widget
        was not drawn on the canvas.
       (Bug #41219)</p></li><li><p>
        In the <span class="guilabel">Columns</span> tab of the Table Editor,
        when moving a column lower in the list of columns using drag and
        drop, the column was incorrectly placed one position below the
        point indicated by the position marker.
       (Bug #40641)</p></li><li><p>
        When <span class="guimenu">Connect to Columns</span> was selected for the
        Relationship Notation option, the line connecting a foreign key
        to its referenced table was drawn to the incorrect column.
       (Bug #40627)</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>
        Foreign Key checks were not enabled before the standard inserts
        section of the script started.
       (Bug #35180)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-news-5-0-24.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.3.7. Changes in MySQL Workbench 5.0.24 (12 August 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-25.html" title="A.3.6. Changes in MySQL Workbench 5.0.25 (12 September 2008)"><link rel="next" href="wb-news-5-0-23.html" title="A.3.8. Changes in MySQL Workbench 5.0.23 (25 June 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-24"></a>A.3.7. Changes in MySQL Workbench 5.0.24 (12 August 2008)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.0.23.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        In the <code class="literal">MySQLGrtShell.exe</code> program the
        <span class="guilabel">Values</span> tab has been renamed to
        <span class="guilabel">GRT Tree</span>. However, the <span class="guilabel">GRT
        Tree</span> tab only shows a root node because there is no
        GRT Tree loaded when the <code class="literal">Shell</code> is started in
        standalone mode.
       (Bug #35052)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        Indexes listed when the <span class="guilabel">Index</span> tab was
        selected could not be deleted if the index type was
        <code class="literal">FOREIGN</code>.
       (Bug #38639)</p></li><li><p>
        When the menu item <span class="guimenu">Model</span>,
        <span class="guimenu">Validation</span>, <span class="guimenu">Validate all</span>
        was selected, and an error dialog subsequently displayed, the
        dialog error message had a missing dot separator between the
        database name and table name.
       (Bug #38632)</p></li><li><p>
        When a DBDesigner 4 model that contained duplicate relationships
        was imported into Workbench, and then exported, the resulting
        script would fail when executed on MySQL server.
       (Bug #38488)</p></li><li><p>
        It was not possible to synchronize a model to an external
        database, if the model contained triggers.
       (Bug #38436)</p></li><li><p>
        When resizing the comment column under <span class="guilabel">Physical
        Schemata</span> view in column format, the column resize was
        reverted when switching between schemas.
       (Bug #38431)</p></li><li><p>
        An attempt to copy a table and then paste it into a new schema
        resulted in an
        <code class="exceptionname">Unknown Exception</code>
        being generated.
       (Bug #38429)</p></li><li><p>
        If you created a new view with an <code class="literal">OR REPLACE</code>
        clause, the <span class="guimenu">Forward Engineer SQL CREATE
        Script</span> output contained the <code class="literal">OR
        REPLACE</code> clause twice.
       (Bug #38337)</p></li><li><p>
        When a DBDesigner 4 XML file was imported into Workbench the
        <code class="literal">INSERT</code> statements were
        incorrectly converted.
       (Bug #38196)</p></li><li><p>
        Importing a script that specified an incorrect data type
        required Workbench to close.
       (Bug #38146)</p></li><li><p>
        Workbench crashed when using the <span class="guimenu">Model</span>,
        <span class="guimenu">Validation(MySQL)</span>, <span class="guimenu">Validate
        All</span> menu item on a model that contained a dangling
        foreign key index.
       (Bug #38115)</p></li><li><p>
        Foreign key options (<code class="literal">onDelete</code>,
        <code class="literal">onUpdate</code>) are not imported from DBDesigner
        schema.
       (Bug #37794)</p></li><li><p>
        In the
        <code class="literal">mysql-workbench-oss-5.0.23-win32-noinstall</code>
        version of Workbench the menu item <span class="guimenu">Plugins</span>,
        <span class="guimenu">Objects</span>, <span class="guimenu">Copy SQL to
        Clipboard</span> did not work.
       (Bug #37736)</p></li><li><p>
        When synchronizing the database, table comments were not
        updated. However, column comments worked as expected.
       (Bug #37686)</p></li><li><p>
        Running <span class="guimenu">Help</span>, <span class="guimenu">Update...</span>
        crashes Workbench when the wizard comes to the point where it is
        trying to close Workbench.
       (Bug #37665)</p></li><li><p>
        <span class="guimenu">Database</span>, <span class="guimenu">Synchronize</span> did
        not update the model view when the table was changed in the
        database, until after Workbench was restarted.
       (Bug #37634)</p></li><li><p>
        <span class="guimenu">Forward Engineer SQL CREATE Script</span> did not
        reflect changes made to the model.
       (Bug #37574)</p></li><li><p>
        When using the <span class="guimenu">Forward Engineer SQL CREATE
        Script</span>, columns marked as <code class="literal">NOT NULL</code>
        were generated as <code class="literal">NOT NULL DEFAULT NULL</code>.
       (Bug #37385)</p></li><li><p>
        Errors were generated in SQL code during <span class="guimenu">Forward
        Engineer Schema</span> for Inserts data in
        <code class="literal">TIMESTAMP</code> columns.
       (Bug #37059)</p></li><li><p>
        If a database was imported using <span class="guimenu">Reverse Engineer SQL
        ALTER Script</span> and the database name changed in
        Workbench, the script then generated by <span class="guimenu">Forward
        Engineer SQL ALTER Script</span> was incorrect.
       (Bug #36178)</p></li><li><p>
        The auto-increment flag was not cleared internally for a column,
        when the type of that column was changed to one for which
        auto-increment is invalid; for example, <code class="literal">char</code>.
        When the model was exported using <span class="guimenu">Export</span>,
        <span class="guimenu">Forward Engineer SQL Create Script</span>, the
        resulting script incorrectly retained the auto-increment flag
        for the changed column.
       (Bug #36085)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-news-5-1-18.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.2.2. Changes in MySQL Workbench 5.1.18 (03 September 2009 General Availability)</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-19.html" title="A.2.1. Changes in MySQL Workbench 5.1.19 (06 September 2010)"><link rel="next" href="wb-news-5-1-17.html" title="A.2.3. Changes in MySQL Workbench 5.1.17 (14 August 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-18"></a>A.2.2. Changes in MySQL Workbench 5.1.18 (03 September 2009 General Availability)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.1.17.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        The Column Editor has been updated to remove the feature whereby
        a column could be toggled to a primary key by double-clicking
        it. Primary key status can now only be set by selecting the
        appropriate check box in the adjacent <span class="guilabel">Column
        Details</span> frame.
       (Bug #46579)</p></li><li><p>
        It was not possible to change column order by dragging and
        dropping columns in the <span class="guilabel">Columns</span> tab of the
        Table Editor. MySQL Workbench has been changed to enable you to drag
        and drop a column to change the column order as required.
       (Bug #40601)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        When editing a stored routine or trigger in the Table Editor,
        the cursor would relocate to the top of the editing window if a
        key was not pressed for a few seconds.
      </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
          On Windows this issue was fixed in 5.1.18. On Mac OS X this
          issue was fixed in 5.2.4. On Linux this issue was fixed in
          5.2.7.
        </p></div><p>(Bug #48156)</p></li><li><p>
        MySQL Workbench generated an unhandled exception when using
        <span class="guimenu">File</span>, <span class="guimenu">Export</span>,
        <span class="guimenu">Forward Engineer SQL CREATE Script</span>. The
        exception was generated if an attempt was made to generate a
        script so that it wrote over a script already created.
       (Bug #47115)</p></li><li><p>
        Clicking the <span class="guibutton">Test Connection</span> button in
        <span class="guilabel">DB Connection Editor</span> wizard did not appear
        to have any effect.
       (Bug #47083)</p></li><li><p>
        MySQL Workbench crashed on launch on Mac OS X 10.6.0.
       (Bug #46953)</p></li><li><p>
        When the data type of a table column was changed in the Table
        Editor, it was not reflected in the EER Diagram, although the
        tooltip was udpated correctly. This only happened in MySQL Workbench
        5.1.17.
       (Bug #46940)</p></li><li><p>
        In the <span class="guilabel">Columns</span> tab of the Table Editor,
        when the empty row at the end of the column list was right
        clicked, MySQL Workbench crashed with this error:
      </p><pre class="programlisting">** (mysql-workbench-bin:15234): WARNING **: /tmp/sakila.mwbd1/document.mwb.xml:26: link
'{591FC376-B82F-4F3D-B185-BA5C65B77080}' &lt;object workbench.Workbench&gt; key=owner could not
be resolved
** Message: unhandled message 4: wb.file.openRecentModel finished in 0.58s

glibmm-ERROR **: 
unhandled exception (type std::exception) in signal handler:
what: Index out of range.

aborting...
Aborted</pre><p>(Bug #46937)</p></li><li><p>
        The DDL was generated without foreign keys, regardless of
        whether the <span class="guilabel">Skip generation of foreign keys</span>
        option was turned on.
       (Bug #46875)</p></li><li><p>
        In the <span class="guilabel">Column</span> tab of the Table Editor, if
        the <span class="guilabel">NN</span> check box was selected or
        deselected, the change was not immediately reflected in the EER
        Diagram, but was seen if some other operation caused the table
        object in the diagram to be refreshed. This also happened with
        the <span class="guilabel">AI</span> check box.
       (Bug #46869)</p></li><li><p>
        The auto-completion of column names in the Table Editor
        completed names unnecessarily, requiring characters in the name
        to be manually deleted. This only happened on the Linux version
        of MySQL Workbench.
       (Bug #46847)</p></li><li><p>
        The <span><strong class="keycap">Esc</strong></span> key did not initiate the closing of an
        active dialog box.
       (Bug #46829)</p></li><li><p>
        Editing of Text Objects did not work correctly. When
        <span><strong class="keycap">Enter</strong></span> was hit, line feed did not move editing
        to the next line, and introduced a box character.
       (Bug #46789)</p></li><li><p>
        The <span class="guilabel">Forward Engineer SQL Script</span> wizard
        generated invalid SQL code for a small model with foreign keys:
      </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';

SET SQL_MODE=@OLD_SQL_MODE;
SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS;
SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS;</pre><p>(Bug #46787)</p></li><li><p>
        MySQL Workbench did not export Foreign Keys when using the
        <span class="guimenu">File</span>, <span class="guimenu">Export</span>,
        <span class="guimenu">Forward Engineer SQL CREATE Script</span> wizard,
        even though the option <span class="guilabel">Skip Creation of FOREIGN
        KEYS</span> check box was cleared. Further, MySQL Workbench
        crashed when a column with a Foreign Key was added to a table.
       (Bug #46783)</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 synchronizing with a live database, the script generated
        included drop statements that were placed in the wrong order,
        this led to the a schema being dropped after it was created.
       (Bug #46740)</p></li><li><p>
        When a N:M identifying relationship was created on a single
        table, a foreign key name collision occurred - both keys were
        given the same name. MySQL Workbench has been changed so that key
        names have a trailing number added to avoid conflicts.
       (Bug #46363)</p></li><li><p>
        MySQL Workbench generated an exception when the mouse wheel was used
        to move between tabs in the Table Editor:
      </p><pre class="programlisting">(mysql-workbench-bin:4864): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion
`node != NULL' failed

glibmm-ERROR **: 
unhandled exception (type std::exception) in signal handler:
what: invalid index

aborting...
Aborted</pre><p>(Bug #46304)</p></li><li><p>
        When an EER Diagram contained tables or views with underscores
        in their names, the context menu associated with them displayed
        their names incorrectly in the menu. The underscores where
        displayed as accelerator keys in the context menu.
       (Bug #46302)</p></li><li><p>
        The <span class="guilabel">User Defined Types</span> dialog, launched
        from <span class="guimenu">Model</span>, <span class="guimenu">User Defined
        Types...</span> on the main menu, did not permit user-defined
        types to be changed. Further, it appeared to be possible to edit
        the new user type in the <span class="guilabel">User Types</span> side
        panel, but no changes made there were retained.
      </p><p>
        MySQL Workbench has been changed to permit User Types to be edited
        only from the <span class="guilabel">User Defined Types</span> dialog,
        and correct operation of this dialog has been restored.
       (Bug #45936)</p></li><li><p>
        When editing a trigger, the trigger editor would automatically
        insert a delimiter during a pause in typing, and also relocate
        the cursor.
       (Bug #45929)</p></li><li><p>
        In the <span class="guilabel">Synchronize Model with Database</span>
        dialog the text in the upper right area of the dialog did not
        wrap correctly, resulting in some text not being visible.
       (Bug #45455)</p></li><li><p>
        The DBDoc documentation generation system did not support
        facilities for Stored Routines, Views and Triggers.
       (Bug #41589)</p></li><li><p>
        After using the <span class="guimenu">Help</span>,
        <span class="guimenu">Update...</span> to upgrade MySQL Workbench, the
        application failed to start correctly. After the splash screen
        was displayed MySQL Workbench displayed an error dialog -
        “<span class="quote">MySQL Workbench has stopped working</span>”.
       (Bug #41460)</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 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><li><p>
        Printing of an EER Diagram did not work correctly if a table
        vertically spanned multiple pages. In this case pages would be
        printed up to and including the page that contained the first
        part of the table that spanned multiple pages, but the pages
        containing the remaining parts of the table would not be
        printed. This problem typically occurred when a table had more
        fields than could comfortably fit on a single page.
       (Bug #33919)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-workbench-central.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>5.1. Workbench Central</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-home.html" title="Chapter 5. The Home Window"><link rel="prev" href="wb-home.html" title="Chapter 5. The Home Window"><link rel="next" href="wb-workspace.html" title="5.2. Workspace"></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-workbench-central"></a>5.1. Workbench Central</h2></div></div></div><p>
      Workbench Central enables you to keep up to date with MySQL Workbench
      news, events, and resources. You can read the developer blogs,
      find out what's new in the release, access the forums, check for
      updates, and file a bug report.
    </p><p>
      Workbench Central includes the following facilities:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          What's new: A list of bug fixes and changes
        </p></li><li><p>
          MySQL Doc Library: Built-in documentation
        </p></li><li><p>
          MySQL Bug Reporter: Links to the MySQL bug system, where you
          can report bugs
        </p></li><li><p>
          Workbench Team Blog: Links to the Workbench team blog
        </p></li><li><p>
          Planet MySQL: Links to MySQL-related blogs and news
        </p></li><li><p>
          Workbench forums: Links to the MySQL user and developer forums
        </p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-data-modeling-create-new-model.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.2. Create New EER Model</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-open-existing-model.html" title="7.1. Open an Existing EER Model"><link rel="next" href="wb-data-modeling-create-model-from-existing-database.html" title="7.3. Create EER Model from Existing Database"></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-new-model"></a>7.2. Create New EER Model</h2></div></div></div><p>
      Clicking this action item launches a new MySQL Model tab, with a
      blank model ready for you to work on.
    </p><p>
      To read more about modeling, see
      <a href="wb-model-editor.html" title="7.5. Model Editor">Section 7.5, “Model Editor”</a>.
    </p></div></body></html>


path: /wb-html-guitools/wb-news-5-2-30.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.10. Changes in MySQL Workbench 5.2.30 (20 November 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-31.html" title="A.1.9. Changes in MySQL Workbench 5.2.31 (08 December 2010)"><link rel="next" href="wb-news-5-2-29.html" title="A.1.11. Changes in MySQL Workbench 5.2.29 (12 October 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-30"></a>A.1.10. Changes in MySQL Workbench 5.2.30 (20 November 2010)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.2.29.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        An advanced search and replace dialog has been added to
        MySQL Workbench. This can be accessed from the main menu
        <span class="guimenu">Edit</span> option, <span class="guimenu">Find and
        replace</span> or the keyboard shortcut
        <span><strong class="keycap">Control+Shift+f</strong></span>.
       (Bug #56629)</p></li><li><p>
        MySQL Workbench has been changed so that the Query Editor in the SQL
        editor includes an SQL formatter. Code can be highlighted and
        formatted using the <span class="guimenu">Edit</span>,
        <span class="guimenu">Format</span> menu item.
       (Bug #50822)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        The default settings for the <span class="guilabel">Export Directory
        Path</span> in the <span class="guilabel">Workbench
        Preferences</span> dialog used mixed file path delimiters
        (both <code class="literal">'/'</code> and <code class="literal">'\'</code>).
       (Bug #57944)</p></li><li><p>
        When importing an SQL script using the <span class="guilabel">Reverse
        Engineer SQL Script</span> wizard, copying a path from the
        clipboard to the <span class="guilabel">Select SQL script</span> file
        input box resulted in an “<span class="quote">invalid path</span>” error.
       (Bug #57927)</p></li><li><p>
        For attempts to connect to a server using SSH, MySQL Workbench
        produced this error message after the user entered the password:
      </p><pre class="programlisting">AttributeError: ServerProfile instance has no attribute 'serverInfo'</pre><p>(Bug #57695)</p></li><li><p>
        The implementation of <code class="literal">get_local_ip_list()</code> had
        several problems:
      </p><div class="itemizedlist"><ul type="circle"><li><p>
            It did not have a graceful fallback state in the event of
            errors.
          </p></li><li><p>
            It failed if <span><strong class="command">ifconfig</strong></span> was not on the
            default user path.
          </p></li><li><p>
            It did not handle IPv6 addresses.
          </p></li></ul></div><p>(Bug #57537)</p></li><li><p>
        When a foreign key was created manually, if the referenced table
        did not exist, MySQL Workbench crashed.
       (Bug #57470)</p></li><li><p>
        In the EER diagram view, the table titles were the same color as
        the background color, making the table titles illegible.
       (Bug #57428)</p></li><li><p>
        After a query was executed, MySQL Workbench crashed when the
        <span class="guibutton">Export</span> button was clicked to export the
        result set to a file.
       (Bug #57379)</p></li><li><p>
        When a model was forward engineered with
        <span class="guimenu">File</span>, <span class="guimenu">Export</span>,
        <span class="guimenu">Forward Engineer SQL CREATE Script</span>, the
        generated script contained a statement that consisted of a
        single delimiter, <code class="literal">';'</code>.
       (Bug #57378)</p></li><li><p>
        In the SQL Editor, it was not possible to close the last
        remaining tab. Closing the last remaining tab should result in a
        new blank tab being displayed.
       (Bug #57137)</p></li><li><p>
        If the SSL option was selected for a standard TCP/IP connection,
        there was no facility provided to enter the SSL certificate
        details.
       (Bug #57101)</p></li><li><p>
        On Linux Fedora 14, MySQL Workbench produced this error at startup:
      </p><pre class="programlisting">/usr/bin/mysql-workbench-bin: error while loading shared libraries: libpython2.6.so.1.0:
cannot open shared object file: No such file or directory</pre><p>(Bug #56863)</p></li><li><p>
        It was not possible to change the name of an EER Diagram. The
        facility was missing from the <span class="guilabel">Diagram Properties and
        Size</span> dialog.
       (Bug #56625)</p></li><li><p>
        The safe updates option on the <span class="guilabel">SQL Editor</span>
        tab of the <span class="guilabel">Preferences</span> dialog required a
        MySQL Workbench restart to take effect.
       (Bug #56159)</p></li><li><p>
        In the Table Editor of the SQL Editor, on the <span class="guilabel">Foreign
        Keys</span> tab, selecting the <span class="guilabel">Referenced
        Table</span> dropdown for a database containing a large
        number of tables caused MySQL Workbench to become unresponsive while
        the dropdown was being populated.
       (Bug #56014)</p></li><li><p>
        In the <span class="guilabel">Create Table</span> dialog of the SQL
        Editor, if a new column was created with a synonym data type
        such as <code class="literal">INTEGER</code>, the datatype would appear
        blank, both in the interface and in the generated SQL. This
        resulted in an error when clicking the <span class="guibutton">Apply
        SQL</span> button.
       (Bug #55620)</p></li><li><p>
        Foreign keys were not updated when a referenced column was
        deleted.
       (Bug #55219)</p></li><li><p>
        The output generated as a result of using the
        <span class="guimenu">Print</span> and <span class="guimenu">Print Preview</span>
        menu items was incorrect. Only the magnified top left corner of
        the EER diagram was displayed.
       (Bug #55139)</p></li><li><p>
        In the <span class="guilabel">Alter Table</span> dialog of the SQL
        Editor, attempts to reorder columns failed. If a column position
        was changed, and then the <span class="guibutton">Apply</span> button
        was clicked, the dialog reported that no changes to the object
        were detected.
       (Bug #54923)</p></li><li><p>
        When a new instance was created to connect using SSH with an SSH
        certificate file, the location of the certificate file was not
        saved.
       (Bug #52048)</p></li><li><p>
        In SQL Editor, when using the <span class="guilabel">Alter Table</span>
        facility to set a column to Auto Increment (AI), the dialog
        reported that “<span class="quote">No changes to object were detected</span>”.
       (Bug #50214)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-keys.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Chapter 10. Keyboard Shortcuts</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-tutorial-plugins.html" title="9.6. Tutorial: Writing Plugins"><link rel="next" href="workbench-faq.html" title="Chapter 11. MySQL Workbench FAQ"></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-keys"></a>Chapter 10. Keyboard Shortcuts</h2></div></div></div><p>
    The following tables list keyboard shortcuts for MySQL Workbench
    commands. <span><strong class="keycap">Modifier</strong></span> in the tables stands for the
    platform-specific modifier key. This is <span><strong class="keycap">Command</strong></span> on
    Mac OS X, <span><strong class="keycap">Control</strong></span> on other platforms. On Mac OS X,
    the <span><strong class="keycap">Alt</strong></span> key is <span><strong class="keycap">Option</strong></span>.
  </p><p>
    <span class="bold"><strong>File Menu</strong></span>
  </p><div class="informaltable"><table border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Function</th><th>Context</th><th>Keyboard Shortcut</th></tr></thead><tbody><tr><td>New Model</td><td>All</td><td>Modifier+N</td></tr><tr><td>Open Model</td><td>All</td><td>Modifier+O</td></tr><tr><td>Open SQL Script</td><td>SQL Editor</td><td>Modifier+Shift+O</td></tr><tr><td>Close Tab</td><td>All</td><td>Modifier+W</td></tr><tr><td>Save Model</td><td>Model</td><td>Modifier+S</td></tr><tr><td>Save Script</td><td>SQL Editor</td><td>Modifier+S</td></tr><tr><td>Save Model As</td><td>Model</td><td>Modifier+Shift+S</td></tr><tr><td>Save Script As</td><td>SQL Editor</td><td>Modifier+Shift+S</td></tr><tr><td>Forward Engineer SQL CREATE Script</td><td>Model</td><td>Modifier+Shift+G</td></tr><tr><td>Forward Engineer SQL ALTER Script</td><td>Model</td><td>Modifier+Alt+Y</td></tr><tr><td>Synchronize With SQL CREATE Script</td><td>Model</td><td>Modifier+Shift+Y</td></tr><tr><td>Print</td><td>EER Diagram mode only</td><td>Modifier+P</td></tr><tr><td>Exit</td><td>All</td><td>Modifer+Q</td></tr></tbody></table></div><p>
    <span class="bold"><strong>Edit Menu</strong></span>
  </p><div class="informaltable"><table border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Function</th><th>Context</th><th>Keyboard Shortcut</th></tr></thead><tbody><tr><td>Undo</td><td>Model, EER Diagram</td><td>Modifier+Z</td></tr><tr><td>Redo</td><td>Model, EER Diagram</td><td>Modifier+Y, Modifier+Shift+Z (Mac OS X)</td></tr><tr><td>Cut</td><td>All</td><td>Modifier+X</td></tr><tr><td>Copy</td><td>All</td><td>Modifier+C</td></tr><tr><td>Paste</td><td>All</td><td>Modifier+V</td></tr><tr><td>Delete</td><td>All</td><td>Modifier+Delete, Command+BackSpace (Mac OS X)</td></tr><tr><td>Edit Selected</td><td>Model, EER Diagram</td><td>Modifier+E</td></tr><tr><td>Edit Selected in New Window</td><td>Model, EER Diagram</td><td>Modifier+Shift+E</td></tr><tr><td>Select All</td><td>EER Diagram</td><td>Modifier+A</td></tr><tr><td>Find</td><td>All</td><td>Modifier+F</td></tr><tr><td>Find Advanced</td><td>All</td><td>Modifier+Alt+F</td></tr><tr><td>Find Next</td><td>All</td><td>F3</td></tr><tr><td>Find Previous</td><td>All</td><td>Shift+F3</td></tr><tr><td>Search and Replace</td><td>All</td><td>Modifier+Shift+F</td></tr></tbody></table></div><p>
    <span class="bold"><strong>View Menu</strong></span>
  </p><div class="informaltable"><table border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Function</th><th>Context</th><th>Keyboard Shortcut</th></tr></thead><tbody><tr><td>Output Window</td><td>All</td><td>Modifier+F2, Modifier+Option+2 (Mac OS X)</td></tr><tr><td>Set Marker n</td><td>EER Diagram</td><td>Modifier+Shift+n (n is integer 1..9)</td></tr><tr><td>Go to Marker n</td><td>EER Diagram</td><td>Modifier+n (n is integer 1..9)</td></tr></tbody></table></div><p>
    <span class="bold"><strong>Arrange Menu</strong></span>
  </p><div class="informaltable"><table border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Function</th><th>Context</th><th>Keyboard Shortcut</th></tr></thead><tbody><tr><td>Bring to Front</td><td>EER Diagram</td><td>Modifier+Shift+F</td></tr><tr><td>Send to Back</td><td>EER Diagram</td><td>Modifier+Shift+B</td></tr></tbody></table></div><p>
    <span class="bold"><strong>Model Menu</strong></span>
  </p><div class="informaltable"><table border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Function</th><th>Context</th><th>Keyboard Shortcut</th></tr></thead><tbody><tr><td>Add Diagram</td><td>Model, EER Diagram</td><td>Modifier+T</td></tr><tr><td>Validate All</td><td>Model, EER Diagram</td><td>Modifier+Alt+V</td></tr><tr><td>Validate All (MySQL)</td><td>Model, EER Diagram</td><td>Modifier+Alt+B</td></tr><tr><td>Model Options</td><td>Model, EER Diagram</td><td>Command+Alt+, (Shorcut available only on Mac OS X)</td></tr></tbody></table></div><p>
    <span class="bold"><strong>Query Menu</strong></span>
  </p><div class="informaltable"><table border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Function</th><th>Context</th><th>Keyboard Shortcut</th></tr></thead><tbody><tr><td>Execute statement</td><td>SQL Editor</td><td>Modifier+Return</td></tr><tr><td>Execute statements</td><td>SQL Editor</td><td>Modifier+Shift+Return</td></tr><tr><td>New Tab</td><td>SQL Editor</td><td>Modifier+T</td></tr></tbody></table></div><p>
    <span class="bold"><strong>Database Menu</strong></span>
  </p><div class="informaltable"><table border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Function</th><th>Context</th><th>Keyboard Shortcut</th></tr></thead><tbody><tr><td>Query Database</td><td>All</td><td>Modifier+U</td></tr><tr><td>Reverse Engineer</td><td>Model, EER Diagram</td><td>Modifier+R</td></tr><tr><td>Forward Engineer</td><td>Model, EER Diagram</td><td>Modifier+G</td></tr><tr><td>Synchronize Model</td><td>Model, EER Diagram</td><td>Modifier+Y</td></tr></tbody></table></div><p>
    <span class="bold"><strong>Scripting menu</strong></span>
  </p><div class="informaltable"><table border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Function</th><th>Context</th><th>Keyboard Shortcut</th></tr></thead><tbody><tr><td>Scripting Shell</td><td>All</td><td>Modifier+F3, Modifier+Option+3 (on Mac OS X)</td></tr><tr><td>Run Workbench Script File</td><td>All</td><td>Modifier+Shift+R</td></tr></tbody></table></div><p>
    <span class="bold"><strong>Help Menu</strong></span>
  </p><div class="informaltable"><table border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Function</th><th>Context</th><th>Keyboard Shortcut</th></tr></thead><tbody><tr><td>Help Index</td><td>All</td><td>F1, Command+Option+question (on Mac OS X)</td></tr></tbody></table></div><p>
    <span class="bold"><strong>EER Diagram Mode</strong></span>
  </p><p>
    In the EER Diagram view, a number of other keyboard shortcuts are
    available.
  </p><div class="informaltable"><table border="1"><colgroup><col><col></colgroup><thead><tr><th>Function</th><th>Keyboard Shortcut</th></tr></thead><tbody><tr><td>Selection tool</td><td>Escape</td></tr><tr><td>Hand tool</td><td>H</td></tr><tr><td>Delete tool</td><td>D</td></tr><tr><td>Layer tool</td><td>L</td></tr><tr><td>Note tool</td><td>N</td></tr><tr><td>Image tool</td><td>I</td></tr><tr><td>Table tool</td><td>T</td></tr><tr><td>View tool</td><td>V</td></tr><tr><td>Routine Group tool</td><td>G</td></tr><tr><td>Non-Identfying Relationship 1:1</td><td>1</td></tr><tr><td>Non-Identfying Relationship 1:n</td><td>2</td></tr><tr><td>Identifying Relationship 1:1</td><td>3</td></tr><tr><td>Identifying Relationship 1:n</td><td>4</td></tr><tr><td>Identifying Relationship n:m</td><td>5</td></tr><tr><td>Relationship Using Existing Columns</td><td>6</td></tr></tbody></table></div></div></body></html>


path: /wb-html-guitools/wb-news-5-2-12.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.28. Changes in MySQL Workbench 5.2.12 (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-13.html" title="A.1.27. Changes in MySQL Workbench 5.2.13 (Not released)"><link rel="next" href="wb-news-5-2-11.html" title="A.1.29. Changes in MySQL Workbench 5.2.11 (18 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-12"></a>A.1.28. Changes in MySQL Workbench 5.2.12 (Not released)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.2.11.
      </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, if a table was edited with the Edit Data
        facility, and table values changed, no warning was given if an
        attempt was made to close the tab without having first applied
        changes using the apply button.
      </p><p>
        MySQL Workbench has been changed so that if the user attempts to
        close a live editing tab, without having applied any changes
        made, a warning dialog is displayed.
       (Bug #49925)</p></li><li><p>
        MySQL Workbench has been changed to permit a connection to be
        created where the password does not have to be stored. In this
        case, MySQL Workbench prompts the user to enter the correct password
        when the connection is established.
       (Bug #49409)</p></li><li><p>
        Undo operations are no longer tracked in the editors that work
        with live databases, such as table editors within the SQL
        Editor.
       (Bug #49284)</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>: 
        The password for the connected MySQL Server was exposed by the
        SQL Administrator in MySQL Workbench. The password was displayed in
        plain text form in the Startup Message Log on the
        <span class="guilabel">Startup</span> tab of the Admin page.
       (Bug #43287)</p></li><li><p>
        In SQL Editor, <code class="literal">SELECT</code> statements that called
        functions, for example <code class="literal">SELECT md5('abcd')</code>,
        did not give the expected result.
       (Bug #50248)</p></li><li><p>
        In the Table Editor, the list for selecting the table engine
        type contained a reference to <code class="literal">calpont</code>. This
        should now be <code class="literal">infinidb</code>.
       (Bug #50159)</p></li><li><p>
        In Mac OS X, the context-sensitive menu was missing from the
        live editing tab of the SQL Editor. Right-clicking in the
        editing tab simply displayed a Mac OS X menu, rather than the
        context-sensitive menu to enable actions such as copying,
        deletion and setting selections to <code class="literal">NULL</code>.
       (Bug #50114)</p></li><li><p>
        Custom Python modules failed to load and were not displayed in
        the MySQL Workbench Plugins menu.
      </p><p>
        In MySQL Workbench 5.2 the syntax used has changed from
        <code class="literal">@wbplugin</code> to
        <code class="literal">@ModuleInfo.Plugin</code>.
       (Bug #50108)</p></li><li><p>
        On the Model page, if some text was entered into a note in Model
        Notes, and then the model was saved and closed, on reloading the
        note would be empty.
      </p><p>
        This also happened for a script added in SQL Scripts. After the
        model was saved and reloaded, the script would be empty.
       (Bug #50108)</p></li><li><p>
        The script code generated from a model for routines did not
        quote schema names in <code class="literal">USE</code> statements.
       (Bug #50051)</p></li><li><p>
        Lower panels such as the <span class="guilabel">Table Editor</span>
        remained open, even when the user returned to the Home screen.
       (Bug #49926)</p></li><li><p>
        In the SQL Editor, when using the <span class="guimenu">Query</span>,
        <span class="guimenu">Export Results...</span> menu item, the file
        extension was omitted when selection of an existing output file
        was made.
       (Bug #49870)</p></li><li><p>
        After selecting Edit Table Data from the Home screen, and
        launching the <span class="guilabel">Edit Table Data</span> wizard,
        MySQL Workbench crashed if a connection was selected and then the
        <span class="guibutton">Next</span> button clicked.
       (Bug #49864)</p></li><li><p>
        In the <span class="guilabel">Manage DB Connections</span> dialog, when
        attempting to create a Standard TCP/IP over SSH connection,
        errors occurred when testing the connection in the case where a
        key file had been specified. If the path to the key file was
        quoted the error was:
      </p><pre class="programlisting">Cannot open SSH Tunnel:  ERROR Invalid request</pre><p>
        If the same path was not quoted the error generated was:
      </p><pre class="programlisting">Could not connect SSH tunnel:  ERROR [Errno 22] invalid mode ('r') or filename:
'D:\\Documents and Settings\\tf221715\\.ssh\\id_dsa'</pre><p>
        It should be noted that currently only key files using the
        OpenSSH format are supported.
       (Bug #49812)</p></li><li><p>
        In the SQL Editor, if a Stored Procedure was executed and then
        immediately executed again, this error was generated:
      </p><pre class="programlisting">Error code 2014
  Commands out of sync; you can't run this command now</pre><p>
        This problem only affected MySQL Workbench running on the Mac OS X
        platform.
       (Bug #49553)</p></li><li><p>
        Right-clicking a Routine Group and then selecting <span class="guimenu">Copy
        SQL to Clipboard</span> did not work. No code was copied to
        the clipboard.
       (Bug #49440)</p></li><li><p>
        Opening a model file, closing it and quickly reopening it caused
        MySQL Workbench to hang.
       (Bug #49428)</p></li><li><p>
        Clicking the <span class="guibutton">Test Connection</span> button in
        the <span class="guilabel">Manage DB Connections</span> dialog caused
        MySQL Workbench to lock up. The error generated on the console was:
      </p><pre class="programlisting">
18743 INFO Connecting to SSH server at 127.0.0.1:22...
Unhandled exception in thread started by &lt;bound method Tunnel._threadloop of
&lt;__main__.Tunnel instance at 0x9acea8&gt;&gt;

      </pre><p>
        This happened for the connection method Standard TCP/IP over
        SSH.
       (Bug #49419)</p></li><li><p>
        Two SSH tunnels were opened for a single connection to an SSH
        server. The user was also prompted for a password when a new
        connection was established, even when the existing tunnel was
        reused.
       (Bug #49412)</p></li><li><p>
        SSH Tunnels opened by MySQL Workbench were never closed. SSH Tunnels
        created when clicking <span class="guibutton">Test Connection</span> in
        the <span class="guilabel">Manage DB Connections</span> dialog, were not
        closed. This was also the case when the SQL Editor and Server
        Administration tabs were closed.
       (Bug #49411)</p></li><li><p>
        In the <span class="guilabel">Partitioning</span> tab of the alter table
        dialog it was possible to enter a number greater than 10 into
        the Partition Count textfield. However, when these changes were
        applied the DDL generated substituted any value entered that was
        greater than 10 with the value 2.
       (Bug #49380)</p></li><li><p>
        MySQL Workbench generated an unhandled exception when trying to add
        a new column using the Alter Table facility in the SQL Editor.
        After the <code class="literal">VARCHAR(45)</code> column was added,
        without selecting any column check boxes, the exception occurred
        when the <span class="guibutton">Apply</span> button was clicked.
       (Bug #49364)</p></li><li><p>
        If a database was reversed engineered from a source, and a table
        renamed, then although this change was detected by MySQL Workbench,
        no DDL code was generated if an attempt was then made to
        synchronize this change with the source.
       (Bug #49313)</p></li><li><p>
        In the SQL Editor, when a schema was dropped, it was still
        displayed in the <span class="guilabel">Overview</span> tab and in the
        schemata explorer of the side panel. Further, MySQL Workbench did
        not provide any confirmation that the schema had been dropped
        successfully or otherwise.
       (Bug #49282)</p></li><li><p>
        The <span class="guilabel">Alter Schema</span> dialog in the SQL Editor
        permitted the schema name to be changed using the
        <span class="guilabel">Name</span> textfield, even though doing this is
        not supported at the server level.
       (Bug #49281)</p></li><li><p>
        In the SQL Editor, if an item in the
        <span class="guilabel">History</span> tab was right-clicked, and the menu
        option <span class="guimenu">Append selected items to SQL script</span>
        selected, MySQL Workbench generated an unhandled exception:
      </p><pre class="programlisting">glibmm-ERROR **: 
unhandled exception (type std::exception) in signal handler:
what: vector::_M_range_check</pre><p>(Bug #49245)</p></li><li><p>
        In the <span class="guilabel">Create a new server instance</span> wizard,
        if the check box <span class="guilabel">Enable SSH login based
        administration</span> was cleared, the wizard still prompted
        the user to enter an SSH password when the
        <span class="guibutton">Next</span> button was clicked.
       (Bug #49226)</p></li><li><p>
        In the Server Status section of the Admin page, the SYSTEM
        graphic showed CPU usage at 50%, while the corresponding text
        label showed CPU usage at 0%. The graphic and label remained out
        of synchronization for around 15 seconds.
       (Bug #49212)</p></li><li><p>
        In the SQL Editor if an <code class="literal">EDIT table</code> operation
        was being carried out, it appeared that data in the table was
        not updated, and also a row already inserted would be
        erroneously deleted when attempting to add a new row of data,
        when changes were applied.
      </p><p>
        MySQL Workbench has been changed so that if an error occurs during
        changes being applied, an error dialog is displayed showing any
        errors that occurred. Also, the status text is now updated to
        say “<span class="quote">Apply Failed</span>”, rather than “<span class="quote">Changes
        Applied</span>”.
       (Bug #49179)</p></li><li><p>
        The <span class="guilabel">Manage DB Connections</span> dialog did not
        prevent duplicate connection names or an empty string as a valid
        connection name.
       (Bug #49150)</p></li><li><p>
        The toolbar buttons on the Home screen did not reflect the order
        of the action items in the Workspace. The Open Server Profile
        button and Open DB Connection Manager buttons needed to exchange
        positions.
       (Bug #49149)</p></li><li><p>
        In the <span class="guilabel">Logs</span> tab of the Administrator, the
        Oldest and Newest buttons appeared to have reversed
        functionality. Oldest displayed the most recent timestamps and
        Newest displayed the oldest.
       (Bug #49065)</p></li><li><p>
        In the <span class="guilabel">Manage DB Connections</span> dialog, many
        textfield labels appeared truncated.
       (Bug #49052, Bug #49378)</p></li><li><p>
        The ID for a connection was displayed in the
        <span class="guilabel">Connections</span> tab of the Admin page, even
        after the corresponding administration session had been closed.
       (Bug #48989)</p></li><li><p>
        The Connections list in the <span class="guilabel">Manage Server
        Instances</span> dialog did not display the user name for
        socket and pipe connections. For example it displayed
        <code class="literal">Localhost - @:0 &lt;Local Socket/Pipe&gt;</code>,
        rather than <code class="literal">Localhost - root@:0 &lt;Local
        Socket/Pipe&gt;</code>.
       (Bug #48969)</p></li><li><p>
        Various errors occurred when attempting to modify the server
        configuration using the <span class="guilabel">Configuration</span> tab
        of the Administrator:
      </p><pre class="programlisting">Unhandled exception: global name 'tempfile' is not defined
      </pre><pre class="programlisting">Unhandled exception: [Errno 22] Invalid argument:
'C:\\users\\tax\\appdata\\local\\temp\\tmpo47ttn'
      </pre><p>
        Also, if the <span class="guilabel">Logs</span> tab was selected to view
        the server log files, this error occurred:
      </p><pre class="programlisting">Unhandled exception: Error executing 'Select @ @
log_output': Unknown system variable 'log_output'</pre><p>(Bug #48906)</p></li><li><p>
        In the <span class="guilabel">Forward Engineer an ALTER Script</span>
        wizard, the textfields and associated buttons for selecting
        input and output files were not positioned correctly within the
        window, when the selected file name was long. Although the files
        could be selected when the wizard was first launched, if the
        wizard was launched subsequently, the text fields would be
        filled with the previously selected file names, causing the
        textfields and Browse buttons to be located beyond the borders
        of the window.
      </p><p>
        A similar problem also affected the <span class="guilabel">Forward Engineer
        SQL Script</span> wizard.
       (Bug #48222)</p></li><li><p>
        In the <span class="guilabel">Partitioning</span> tab of the
        <span class="guilabel">Alter Schema</span> dialog, it was not possible to
        create a single partition. If a partition count of 1 was
        specified this was actually set to 2 in the generated DDL.
       (Bug #48114)</p></li><li><p>
        When performing a Synchronize Model operation, all foreign key
        relationships in the EER diagram that had the setting
        <code class="literal">draw split</code> were redrawn as <code class="literal">fully
        visible</code>.
       (Bug #47767)</p></li><li><p>
        When running MySQL Workbench from the command line, it could not
        open model files where the path contained a space.
       (Bug #46297)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-documenting-sakila.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.8.4. Documenting the sakila Database</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-basic-foreign-key.html" title="7.8.3.2. Creating a Foreign Key"><link rel="next" href="wb-sakila-eer-png.html" title="7.8.4.1. A PNG File of the sakila Database"></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-documenting-sakila"></a>7.8.4. Documenting the <code class="literal">sakila</code> Database</h3></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-sakila-eer-png.html">7.8.4.1. A PNG File of the <code class="literal">sakila</code> Database</a></span></dt></dl></div><p>
    This chapter highlights the capabilities of MySQL Workbench as a
    documentation tool using the <code class="literal">sakila</code> database as
    an example. This is a sample database provided by MySQL that you can
    find by visiting the <a href="http://dev.mysql.com/doc/">http://dev.mysql.com/doc/</a> page, selecting
    the <code class="literal">Other Docs</code> tab, and looking in the
    <code class="literal">Example Databases</code> section
  </p><p>
    An EER diagram is an invaluable aid to a quick understanding of any
    database. There is no need to read through table definition
    statements; glancing at an EER diagram can immediately indicate that
    various tables are related.
  </p><p>
    You can also see how tables are related; what the foreign keys are
    and what the nature of the relationship is.
  </p></div></body></html>


path: /wb-html-guitools/wb-server-administration-configuration.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>8.7. Server Administration and Configuration</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-manage-server-instance-dialog.html" title="8.6.2. Manage Server Instances Dialog"><link rel="next" href="wb-manage-server-startup-tab.html" title="8.7.1. The Startup Tab"></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-configuration"></a>8.7. Server Administration and Configuration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-manage-server-startup-tab.html">8.7.1. The Startup Tab</a></span></dt><dt><span class="section"><a href="wb-manage-server-configuration-tab.html">8.7.2. The Configuration Tab</a></span></dt><dt><span class="section"><a href="wb-manage-server-accounts-tab.html">8.7.3. The Accounts Tab</a></span></dt><dt><span class="section"><a href="wb-manage-server-connections-tab.html">8.7.4. The Connections Tab</a></span></dt><dt><span class="section"><a href="wb-manage-server-variables-tab.html">8.7.5. The Variables Tab</a></span></dt><dt><span class="section"><a href="wb-manage-server-data-dump-tab.html">8.7.6. The Data Dump Tab</a></span></dt><dt><span class="section"><a href="wb-manage-server-logs-tab.html">8.7.7. The Logs Tab</a></span></dt></dl></div><p>
      The Administrator functionality in MySQL Workbench is grouped into
      several tabs:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <span class="bold"><strong>Startup</strong></span>: Enables you to start
          and stop the MySQL server, and view the startup message log
        </p></li><li><p>
          <span class="bold"><strong>Configuration</strong></span>: Enables you to
          view and edit the MySQL Configuration file
          (<code class="filename">my.ini</code> or <code class="filename">my.cnf</code>)
          using GUI controls
        </p></li><li><p>
          <span class="bold"><strong>Accounts</strong></span>: Enables you to
          create user accounts and assign roles and privileges
        </p></li><li><p>
          <span class="bold"><strong>Connections</strong></span>: Displays
          connections to MySQL Server
        </p></li><li><p>
          <span class="bold"><strong>Variables</strong></span>: Displays system
          and status variables
        </p></li><li><p>
          <span class="bold"><strong>Data Dump</strong></span>: Import and export
          of data
        </p></li><li><p>
          <span class="bold"><strong>Logs</strong></span>: Displays server log
          file entries
        </p></li></ul></div><p>
      The Administrator also displays system and server status. System
      status includes:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          CPU utilization
        </p></li><li><p>
          Memory usage
        </p></li><li><p>
          Connection Health
        </p></li></ul></div><p>
      For server health, the following are displayed:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          Connection Usage
        </p></li><li><p>
          Traffic
        </p></li><li><p>
          Query Cache Hit Rate
        </p></li><li><p>
          Key Efficiency
        </p></li></ul></div><div class="figure"><a name="wb-manage-server-admin"></a><p class="title"><b>Figure 8.3. MySQL Workbench - Admin Page</b></p><div class="mediaobject"><img src="images/wb-manage-server-admin.png" width="1024" height="707" alt="MySQL Workbench - Admin Page"></div></div></div></body></html>


path: /wb-html-guitools/wb-database-diff-report.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.7.10.4. Creating a Catalog Diff Report</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-forward-engineering.html" title="7.7.10. Forward Engineering"><link rel="prev" href="wb-database-synchronization.html" title="7.7.10.3. Database Synchronization"><link rel="next" href="wb-tutorials.html" title="7.8. Modeling Tutorials"></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-database-diff-report"></a>7.7.10.4. Creating a Catalog Diff Report</h4></div></div></div><p>
      This facility enables you to create a report detailing the
      differences between your MySQL Workbench model, and a live database or
      script. Choose <span class="guimenu">Database</span>, <span class="guimenuitem">Generate
      Catalog Diff Report</span> from the main menu to run the
      Compare and Report Differences in Catalogs wizard.
    </p><p>
      The first step in the wizard is to specify which catalogs to
      compare. For example, you may wish to compare your live database
      against your current MySQL Workbench model.
    </p><div class="figure"><a name="wb-database-diff-report-wizard-sources"></a><p class="title"><b>Figure 7.40. Catalog Sources</b></p><div class="mediaobject"><img src="images/wb-database-diff-report-wizard-sources.png" width="812" height="604" alt="Catalog Sources"></div></div><p>
      You then proceed through the wizard, providing connection
      information if accessing a live database. The wizard then produces
      a catalog diff report showing the differences between the compared
      catalogs.
    </p><div class="figure"><a name="wb-database-diff-report-wizard-report"></a><p class="title"><b>Figure 7.41. Catalog Diff Report</b></p><div class="mediaobject"><img src="images/wb-database-diff-report-wizard-report.png" width="812" height="604" alt="Catalog Diff Report"></div></div></div></body></html>


path: /wb-html-guitools/wb-database-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.6. The Database 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-model-menu.html" title="7.5.1.5. The Model Menu"><link rel="next" href="wb-plugins-menu.html" title="7.5.1.7. The Plugins 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-database-menu"></a>7.5.1.6. The Database Menu</h4></div></div></div><p>
      The <span class="guimenu">Database</span> menu has these items:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <span class="guimenuitem">Query Database</span>: Launches the SQL
          Editor, which enables you to create SQL code and execute it on
          a live server. For more information, see
          <a href="wb-sql-editor.html" title="6.7. SQL Editor">Section 6.7, “SQL Editor”</a>.
        </p></li><li><p>
          <span class="guimenuitem">Manage Connections</span>: Launches the
          Manage DB Connections dialog, which enables you to create and
          manage multiple connections. For more information, see
          <a href="wb-manage-db-connections.html" title="6.6. Manage DB Connections Dialog">Section 6.6, “Manage DB Connections Dialog”</a>
        </p></li><li><p>
          <span class="guimenuitem">Reverse Engineer</span>: Creates a model
          from an existing database. For more information, see
          <a href="wb-reverse-engineer-live.html" title="7.7.9.2. Reverse Engineering a Live Database">Section 7.7.9.2, “Reverse Engineering a Live Database”</a>.
        </p></li><li><p>
          <span class="guimenuitem">Forward Engineer</span>: Creates a
          database from a model. For more information, see
          <a href="wb-forward-engineering-live-server.html" title="7.7.10.2. Forward Engineering to a Live Server">Section 7.7.10.2, “Forward Engineering to a Live Server”</a>.
        </p></li><li><p>
          <span class="guimenuitem">Synchronize Model</span>: Synchronizes
          your database model with an existing database. For more
          information, see
          <a href="wb-database-synchronization.html" title="7.7.10.3. Database Synchronization">Section 7.7.10.3, “Database Synchronization”</a>.
        </p></li><li><p>
          <span class="guimenuitem">Generate Catalog Diff Report</span>:
          Compares your schema model with a live database or a script
          file. <a href="wb-database-diff-report.html" title="7.7.10.4. Creating a Catalog Diff Report">Section 7.7.10.4, “Creating a Catalog Diff Report”</a>.
        </p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-news-5-1-6.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.2.14. Changes in MySQL Workbench 5.1.6 (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-7.html" title="A.2.13. Changes in MySQL Workbench 5.1.7 (Not yet released)"><link rel="next" href="wb-news-5-1-4.html" title="A.2.15. Changes in MySQL Workbench 5.1.4 (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-1-6"></a>A.2.14. Changes in MySQL Workbench 5.1.6 (Not yet released)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.1.5.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        MySQL Workbench has been changed so that layers and tables listed in
        the Layers palette are sorted in alphabetic order, making it
        easier to find the required object.
       (Bug #39781)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        A dialog displayed a message with a missing file name. The
        message displayed was:
      </p><pre class="programlisting">Import of SQL script file '' has finished successfully.</pre><p>
        Note the file name is missing from the message.
      </p><p>
        This dialog is located in the <span class="guimenu">File</span>,
        <span class="guimenu">Import</span>, <span class="guimenu">Reverse Engineer SQL CREATE
        Script</span> wizard. It is displayed on the page after
        importing the file, clicking <span class="guibutton">Next</span> and
        then <span class="guibutton">Execute</span>.
       (Bug #39922)</p></li><li><p>
        The <span class="guibutton">Advanced</span> button displayed the text
        label <span class="guibutton">&amp;Advanced</span>.
      </p><p>
        This button is located in the <span class="guimenu">File</span>,
        <span class="guimenu">Import</span>, <span class="guimenu">Reverse Engineer SQL CREATE
        Script</span> wizard. It is displayed on the page after
        importing the file.
       (Bug #39921)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-editions.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Chapter 2. MySQL Workbench Editions</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-intro.html" title="Chapter 1. MySQL Workbench Introduction"><link rel="next" href="wb-installing.html" title="Chapter 3. Installing and Launching MySQL Workbench"></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-editions"></a>Chapter 2. MySQL Workbench Editions</h2></div></div></div><p>
    <span class="bold"><strong>The Community Edition (OSS)</strong></span>
  </p><p>
    The Community Edition is the foundation of all MySQL Workbench
    editions—versions that are currently available or those that
    will become available in the future. All editions of MySQL Workbench are
    based on the Community Edition and all future improvements to the
    base framework and feature set will be included in this version. The
    Community Edition is a full feature product that puts a powerful
    database management tool into the hands of the MySQL community.
  </p><p>
    <span class="bold"><strong>The Standard Edition</strong></span>
  </p><p>
    The Standard Edition is a commercial extension that builds on top of
    the OSS Edition and adds modules and plugins, enabling an optimized
    work flow. The highlights of this edition are:
  </p><div class="itemizedlist"><ul type="disc"><li><p>
        MySQL Specific Schema Validation
      </p></li><li><p>
        Model Validation
      </p></li><li><p>
        General Schema Validation
      </p></li><li><p>
        DBDoc
      </p></li></ul></div><p>
    DBDoc provides the following features:
  </p><div class="itemizedlist"><ul type="disc"><li><p>
        Document complex database schemata
      </p></li><li><p>
        Document all SQL object types
      </p></li><li><p>
        Document output available in different file formats
      </p></li></ul></div><p>
    A comparison of edition features can be found at
    <a href="http://dev.mysql.com/workbench/?page_id=11">MySQL
    Workbench Developer Central</a>.
  </p></div></body></html>


path: /wb-html-guitools/wb-news-5-2-25.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.15. Changes in MySQL Workbench 5.2.25 (30 June 2010 General Availability)</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-26.html" title="A.1.14. Changes in MySQL Workbench 5.2.26 (06 August 2010)"><link rel="next" href="wb-news-5-2-24.html" title="A.1.16. Changes in MySQL Workbench 5.2.24 (21 June 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-25"></a>A.1.15. Changes in MySQL Workbench 5.2.25 (30 June 2010 General Availability)</h3></div></div></div><p>
        First GA 5.2 release. This section documents all changes and bug
        fixes applied since the release of 5.2.24.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        MySQL Workbench now prompts the user for a password for attempts to
        connect using a “<span class="quote">TCP over SSH</span>” connection type, if
        a password was not previously provided during configuration of
        the connection.
       (Bug #47892)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        Compiling MySQL Workbench from source failed with this error while
        building <code class="filename">library/grt/src/grtpp_grt.cpp</code>:
      </p><pre class="programlisting">Could not find file cairo_features.h 
(included from cairo.h, which is included from
library/base/src/string_utilities.h, which is included in grtpp_grt.cpp)</pre><p>(Bug #54833)</p></li><li><p>
        On exit, MySQL Workbench prompted the user to save changes for every
        query tab that had been opened in the SQL Editor, even where a
        table had simply been viewed, and no script code had been
        written by the user.
       (Bug #54754)</p></li><li><p>
        When synchronizing a model with the live database, the generated
        SQL included erroneous <code class="literal">DROP COLUMN</code> and
        <code class="literal">ADD COLUMN</code> operations, and also erroneous
        <code class="literal">ADD INDEX</code> and <code class="literal">DROP INDEX</code>
        operations.
       (Bug #54740)</p></li><li><p>
        Inserts data did not appear to be preserved between MySQL Workbench
        versions.
      </p><p>
        A model was created with MySQL Workbench 5.1.18 and data inserted
        using the <span class="guilabel">Insert</span> tab. If the model was then
        saved and loaded into MySQL Workbench 5.2.22, and the model forward
        engineered to an SQL script, the generated script contained
        <code class="literal">INSERT</code> statements that inserted
        <code class="literal">NULL</code> instead of the data originally entered.
       (Bug #54639)</p></li><li><p>
        In the <span class="guilabel">Create Routine</span> dialog of the SQL
        Editor, the text label associated with the
        <span class="guilabel">Name</span> textbox mentioned “<span class="quote">view</span>”,
        rather than “<span class="quote">routine</span>”.
       (Bug #54566)</p></li><li><p>
        Minimizing MySQL Workbench after a connection with a server was
        established produced this error:
      </p><pre class="programlisting">SplitterDistance must be between Panel1MinSize and (Width - Panel2MinSize)</pre><p>(Bug #54482)</p></li><li><p>
        In the <span class="guilabel">Data Dump</span> section of the
        Administrator, using the <span class="guilabel">Export to Backup Project
        Folder</span> option resulted in triggers being exported to
        both the table files and the routines files. Attempting to
        import the exported files produced an error due to the
        duplicated triggers.
       (Bug #54426)</p></li><li><p>
        When a <code class="filename">.dbquery</code> file created with MySQL
        Query Browser was opened in the SQL Editor, the Byte Order Mark
        (BOM) was not removed. This led to an erroneous character being
        prepended to the first statement, making it illegal.
       (Bug #54322)</p></li><li><p>
        When forward engineering to a live database, the generated SQL
        statements contained an erroneous additional carriage return at
        the end of each line. This manifested in two ways. In the first
        case, in the <span class="guilabel">Forward Engineer to Database</span>
        wizard, if <span class="guibutton">Save to File</span> was selected, a
        carriage-return character was appended to each line. In the
        second case, if <span class="guibutton">Copy to Clipboard</span> was
        selected, and the content subsequently pasted from the clipboard
        to an editor, the extra carriage return characters was attached
        only to the DDL statements inside <code class="literal">Create View</code>
        and <code class="literal">Create Trigger</code>.
       (Bug #54272, Bug #54244)</p></li><li><p>
        Printing or previewing an EER Diagram in Landscape/Tabloid
        produced blank output.
       (Bug #54240, Bug #54601)</p></li><li><p>
        MySQL Workbench generated excessive diagnostic messages at startup.
        Now MySQL Workbench does not display diagnostic messages by default
        on Linux, unless activated by starting MySQL Workbench with the
        <code class="option">--verbose</code> option.
       (Bug #54021)</p></li><li><p>
        In the <span class="guilabel">Columns</span> tab of the Table Editor,
        column ordering handling had numerous problems. For example,
        dragging and dropping a column did not locate the column as
        expected.
       (Bug #53749)</p></li><li><p>
        If the <span class="guilabel">Alter Routine</span> dialog was maximized
        in the SQL Editor, the dialog buttons were no longer visible.
       (Bug #53734)</p></li><li><p>
        In the <span class="guilabel">Configuration</span> tab of the
        Administrator, the parameter
        <span class="guilabel">innodb_support_xa</span> on the <span class="guilabel">InnoDB
        Parameters</span> tab has a corresponding check box. If this
        was selected and changes applied, the confirmation dialog
        indicated these changes were made:
      </p><pre class="programlisting">Added:  [mysqld] innodb_support_xa = True</pre><p>
        However, what was added to the <code class="filename">my.cnf</code> file
        was “<span class="quote">innodb_support_xa</span>”. This meant there was no
        way to set this parameter (which defaults to
        <code class="literal">True</code>) to <code class="literal">False</code> using
        MySQL Workbench.
       (Bug #53449)</p></li><li><p>
        In the SQL Editor, if a query was executed and MySQL Workbench was
        minimized, the <span class="guilabel">Results</span> tab window area was
        not correctly redrawn on maximizing the application.
       (Bug #51991)</p></li><li><p>
        When synchronizing a model that contained triggers, MySQL Workbench
        generated erroneous <code class="literal">DROP TRIGGER</code> and
        <code class="literal">CREATE TRIGGER</code> statements, even when the
        triggers had not been changed.
       (Bug #51929)</p></li><li><p>
        MySQL Workbench displayed instability after an SSH connection to the
        server was closed, resultin in hanging or crashing behavior.
       (Bug #50554)</p></li><li><p>
        When creating a table containing columns with a
        <code class="literal">BOOLEAN</code> data type, the model then failed to
        validate, even though <code class="literal">BOOLEAN</code> is offered on
        the list of types available for columns.
       (Bug #49538)</p></li><li><p>
        In the Inserts editor, the underscores in column headings were
        incorrectly displayed as accelerator/shortcut keys.
       (Bug #48831)</p></li><li><p>
        For the <span class="guilabel">Manage DB Connections</span> dialog,
        labels such as user name and password were hidden when the
        dialog was opened at its default size.
       (Bug #47890)</p></li><li><p>
        In the Modeler, when opening a new object such as a table, the
        currently open tab was reused, rather than a new tab being
        opened. This made it difficult to compare objects such as tables
        and routines.
       (Bug #45557)</p></li><li><p>
        When a table was copied in the EER Diagram view, it was found
        that the paste menu option was visible but disabled when an
        attempt was made to paste the table into a new diagram.
       (Bug #38432)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-using-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.7.3.2. Adding Views to 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-creating-views.html" title="7.7.3. Creating Views"><link rel="prev" href="wb-views-physical-schemata.html" title="7.7.3.1. Adding Views to the Physical Schemata"><link rel="next" href="wb-view-editor.html" title="7.7.3.3. The View 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-using-view-tool"></a>7.7.3.2. Adding Views to an EER Diagram</h4></div></div></div><p>
      Views can also be added to an EER Diagram using the
      <code class="literal">View</code> tool on the vertical toolbar. Make sure
      that the <span class="guilabel">EER Diagram</span> tab is selected, then
      left-click the view icon on the vertical toolbar. The view icon is
      the two overlapping rectangles found below the table icon.
    </p><p>
      Clicking this icon changes the mouse pointer to a view pointer. To
      change the mouse pointer to a view pointer from the keyboard, use
      the <span><strong class="keycap">V</strong></span> key.
    </p><p>
      Choosing the <code class="literal">View</code> tool changes the contents of
      the toolbar that appears immediately below the main menu bar. When
      the <code class="literal">Views</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
      view. Make sure that you associate the new view with a database.
      The color of your view can be changed using the
      <code class="literal">Properties</code> palette.
    </p><p>
      Create a view by clicking anywhere on the EER Diagram canvas. This
      creates a new view with the default name <code class="literal">view1</code>.
      To revert to the default mouse pointer, click the arrow icon at
      the top of the vertical toolbar.
    </p><p>
      Right-clicking a view opens a pop-up menu. With the exception of
      the delete item, these menu items function as described in
      <a href="wb-views-physical-schemata.html" title="7.7.3.1. Adding Views to the Physical Schemata">Section 7.7.3.1, “Adding Views to the Physical Schemata”</a>. 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></body></html>


path: /wb-html-guitools/wb-server-administration-manage-security.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>8.4. Manage Security</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-manage-data-import-export.html" title="8.3. Manage Data Import/Export"><link rel="next" href="wb-server-administration-manage-server-instances.html" title="8.5. Manage Server Instances"></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-security"></a>8.4. Manage Security</h2></div></div></div><p>
      This action item takes you quickly to the page that enables you to
      manage user accounts. It launches an Admin page and locates you on
      the Accounts tab. For further details, see
      <a href="wb-manage-server-accounts-tab.html" title="8.7.3. The Accounts Tab">Section 8.7.3, “The Accounts Tab”</a>.
    </p></div></body></html>


path: /wb-html-guitools/license-python.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>B.19. Python 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-pycrypto.html" title="B.18. PyCrypto License"><link rel="next" href="license-scintilla.html" title="B.20. Scintilla 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-python"></a>B.19. Python License</h2></div></div></div><p>
    The following software may be included in this product:
  </p><pre class="programlisting">Python Programming Language

This is the official license for the Python 2.7 release:

A. HISTORY OF THE SOFTWARE
Python was created in the early 1990s by Guido van Rossum at Stichting
Mathematisch Centrum (CWI, see http://www.cwi.nl) in the Netherlands
as a successor of a language called ABC.  Guido remains Python's
principal author, although it includes many contributions from others.

In 1995, Guido continued his work on Python at the Corporation for
National Research Initiatives (CNRI, see http://www.cnri.reston.va.us)
in Reston, Virginia where he released several versions of the
software.

In May 2000, Guido and the Python core development team moved to
BeOpen.com to form the BeOpen PythonLabs team.  In October of the same
year, the PythonLabs team moved to Digital Creations (now Zope
Corporation, see http://www.zope.com).  In 2001, the Python Software
Foundation (PSF, see http://www.python.org/psf/) was formed, a
non-profit organization created specifically to own Python-related
Intellectual Property.  Zope Corporation is a sponsoring member of
the PSF.

All Python releases are Open Source (see http://www.opensource.org for
the Open Source Definition).  Historically, most, but not all, Python
releases have also been GPL-compatible; the table below summarizes
the various releases.

    Release         Derived     Year        Owner       GPL-
                    from                                compatible? (1)

    0.9.0 thru 1.2              1991-1995   CWI         yes
    1.3 thru 1.5.2  1.2         1995-1999   CNRI        yes
    1.6             1.5.2       2000        CNRI        no
    2.0             1.6         2000        BeOpen.com  no
    1.6.1           1.6         2001        CNRI        yes (2)
    2.1             2.0+1.6.1   2001        PSF         no
    2.0.1           2.0+1.6.1   2001        PSF         yes
    2.1.1           2.1+2.0.1   2001        PSF         yes
    2.2             2.1.1       2001        PSF         yes
    2.1.2           2.1.1       2002        PSF         yes
    2.1.3           2.1.2       2002        PSF         yes
    2.2.1           2.2         2002        PSF         yes
    2.2.2           2.2.1       2002        PSF         yes
    2.2.3           2.2.2       2003        PSF         yes
    2.3             2.2.2       2002-2003   PSF         yes
    2.3.1           2.3         2002-2003   PSF         yes
    2.3.2           2.3.1       2002-2003   PSF         yes
    2.3.3           2.3.2       2002-2003   PSF         yes
    2.3.4           2.3.3       2004        PSF         yes
    2.3.5           2.3.4       2005        PSF         yes
    2.4             2.3         2004        PSF         yes
    2.4.1           2.4         2005        PSF         yes
    2.4.2           2.4.1       2005        PSF         yes
    2.4.3           2.4.2       2006        PSF         yes
    2.5             2.4         2006        PSF         yes
    2.5.1 	        2.5 	  2007 	  PSF 	  yes
    2.5.2 	        2.5.1       2008 	  PSF 	  yes
    2.5.3 	        2.5.2 	  2008 	  PSF 	  yes
    2.6 	        2.5 	  2008 	  PSF 	  yes
    2.6.1 	        2.6 	  2008 	  PSF 	  yes
    2.6.2 	        2.6.1 	  2009 	  PSF 	  yes
    2.6.3 	        2.6.2 	  2009 	  PSF 	  yes
    2.6.4 	        2.6.3 	  2010 	  PSF 	  yes
    2.7 	        2.6 	  2010 	  PSF 	  yes


Footnotes:

(1) GPL-compatible doesn't mean that we're distributing Python under
    the GPL.  All Python licenses, unlike the GPL, let you distribute
    a modified version without making your changes open source.  The
    GPL-compatible licenses make it possible to combine Python with
    other software that is released under the GPL; the others don't.

(2) According to Richard Stallman, 1.6.1 is not GPL-compatible,
    because its license has a choice of law clause.  According to
    CNRI, however, Stallman's lawyer has told CNRI's lawyer that 1.6.1
    is "not incompatible" with the GPL.

Thanks to the many outside volunteers who have worked under Guido's
direction to make these releases possible.

B. TERMS AND CONDITIONS FOR ACCESSING OR OTHERWISE USING PYTHON

PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2
--------------------------------------------

1. This LICENSE AGREEMENT is between the Python Software Foundation
("PSF"), and the Individual or Organization ("Licensee") accessing and
otherwise using this software ("Python") in source or binary form and
its associated documentation.

2. Subject to the terms and conditions of this License Agreement, PSF
hereby grants Licensee a nonexclusive, royalty-free, world-wide
license to reproduce, analyze, test, perform and/or display publicly,
prepare derivative works, distribute, and otherwise use Python
alone or in any derivative version, provided, however, that PSF's
License Agreement and PSF's notice of copyright, i.e., "Copyright (c)
2001, 2002, 2003, 2004, 2005, 2006 Python Software Foundation; All Rights
Reserved" are retained in Python alone or in any derivative version 
prepared by Licensee.

3. In the event Licensee prepares a derivative work that is based on
or incorporates Python or any part thereof, and wants to make
the derivative work available to others as provided herein, then
Licensee hereby agrees to include in any such work a brief summary of
the changes made to Python.

4. PSF is making Python available to Licensee on an "AS IS"
basis.  PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
IMPLIED.  BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND
DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON WILL NOT
INFRINGE ANY THIRD PARTY RIGHTS.

5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON
FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS
A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON,
OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.

6. This License Agreement will automatically terminate upon a material
breach of its terms and conditions.

7. Nothing in this License Agreement shall be deemed to create any
relationship of agency, partnership, or joint venture between PSF and
Licensee.  This License Agreement does not grant permission to use PSF
trademarks or trade name in a trademark sense to endorse or promote
products or services of Licensee, or any third party.

8. By copying, installing or otherwise using Python, Licensee
agrees to be bound by the terms and conditions of this License
Agreement.


BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0
-------------------------------------------

BEOPEN PYTHON OPEN SOURCE LICENSE AGREEMENT VERSION 1

1. This LICENSE AGREEMENT is between BeOpen.com ("BeOpen"), having an
office at 160 Saratoga Avenue, Santa Clara, CA 95051, and the
Individual or Organization ("Licensee") accessing and otherwise using
this software in source or binary form and its associated
documentation ("the Software").

2. Subject to the terms and conditions of this BeOpen Python License
Agreement, BeOpen hereby grants Licensee a non-exclusive,
royalty-free, world-wide license to reproduce, analyze, test, perform
and/or display publicly, prepare derivative works, distribute, and
otherwise use the Software alone or in any derivative version,
provided, however, that the BeOpen Python License is retained in the
Software, alone or in any derivative version prepared by Licensee.

3. BeOpen is making the Software available to Licensee on an "AS IS"
basis.  BEOPEN MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
IMPLIED.  BY WAY OF EXAMPLE, BUT NOT LIMITATION, BEOPEN MAKES NO AND
DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT
INFRINGE ANY THIRD PARTY RIGHTS.

4. BEOPEN SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THE
SOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS
AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY
DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.

5. This License Agreement will automatically terminate upon a material
breach of its terms and conditions.

6. This License Agreement shall be governed by and interpreted in all
respects by the law of the State of California, excluding conflict of
law provisions.  Nothing in this License Agreement shall be deemed to
create any relationship of agency, partnership, or joint venture
between BeOpen and Licensee.  This License Agreement does not grant
permission to use BeOpen trademarks or trade names in a trademark
sense to endorse or promote products or services of Licensee, or any
third party.  As an exception, the "BeOpen Python" logos available at
http://www.pythonlabs.com/logos.html may be used according to the
permissions granted on that web page.

7. By copying, installing or otherwise using the software, Licensee
agrees to be bound by the terms and conditions of this License
Agreement.


CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1
---------------------------------------

1. This LICENSE AGREEMENT is between the Corporation for National
Research Initiatives, having an office at 1895 Preston White Drive,
Reston, VA 20191 ("CNRI"), and the Individual or Organization
("Licensee") accessing and otherwise using Python 1.6.1 software in
source or binary form and its associated documentation.

2. Subject to the terms and conditions of this License Agreement, CNRI
hereby grants Licensee a nonexclusive, royalty-free, world-wide
license to reproduce, analyze, test, perform and/or display publicly,
prepare derivative works, distribute, and otherwise use Python 1.6.1
alone or in any derivative version, provided, however, that CNRI's
License Agreement and CNRI's notice of copyright, i.e., "Copyright (c)
1995-2001 Corporation for National Research Initiatives; All Rights
Reserved" are retained in Python 1.6.1 alone or in any derivative
version prepared by Licensee.  Alternately, in lieu of CNRI's License
Agreement, Licensee may substitute the following text (omitting the
quotes): "Python 1.6.1 is made available subject to the terms and
conditions in CNRI's License Agreement.  This Agreement together with
Python 1.6.1 may be located on the Internet using the following
unique, persistent identifier (known as a handle): 1895.22/1013.  This
Agreement may also be obtained from a proxy server on the Internet
using the following URL: http://hdl.handle.net/1895.22/1013".

3. In the event Licensee prepares a derivative work that is based on
or incorporates Python 1.6.1 or any part thereof, and wants to make
the derivative work available to others as provided herein, then
Licensee hereby agrees to include in any such work a brief summary of
the changes made to Python 1.6.1.

4. CNRI is making Python 1.6.1 available to Licensee on an "AS IS"
basis.  CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
IMPLIED.  BY WAY OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO AND
DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 1.6.1 WILL NOT
INFRINGE ANY THIRD PARTY RIGHTS.

5. CNRI SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON
1.6.1 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS
A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 1.6.1,
OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.

6. This License Agreement will automatically terminate upon a material
breach of its terms and conditions.

7. This License Agreement shall be governed by the federal
intellectual property law of the United States, including without
limitation the federal copyright law, and, to the extent such
U.S. federal law does not apply, by the law of the Commonwealth of
Virginia, excluding Virginia's conflict of law provisions.
Notwithstanding the foregoing, with regard to derivative works based
on Python 1.6.1 that incorporate non-separable material that was
previously distributed under the GNU General Public License (GPL), the
law of the Commonwealth of Virginia shall govern this License
Agreement only as to issues arising under or with respect to
Paragraphs 4, 5, and 7 of this License Agreement.  Nothing in this
License Agreement shall be deemed to create any relationship of
agency, partnership, or joint venture between CNRI and Licensee.  This
License Agreement does not grant permission to use CNRI trademarks or
trade name in a trademark sense to endorse or promote products or
services of Licensee, or any third party.

8. By clicking on the "ACCEPT" button where indicated, or by copying,
installing or otherwise using Python 1.6.1, Licensee agrees to be
bound by the terms and conditions of this License Agreement.

        ACCEPT


CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2
--------------------------------------------------

Copyright (c) 1991 - 1995, Stichting Mathematisch Centrum Amsterdam,
The Netherlands.  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, and that the name of Stichting Mathematisch
Centrum or CWI not be used in advertising or publicity pertaining to
distribution of the software without specific, written prior
permission.

STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO
THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM 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.

Licenses and Acknowledgements for Incorporated Software
========================================================

This section is an incomplete, but growing list of licenses and acknowledgements for third-party software incorporated in the Python distribution.

Mersenne Twister
================
The _random module includes code based on a download from http://www.math.keio.ac.jp/ matumoto/MT2002/emt19937ar.html. The following are the verbatim comments from the original code:

A C-program for MT19937, with initialization improved 2002/1/26.
Coded by Takuji Nishimura and Makoto Matsumoto.

Before using, initialize the state by using init_genrand(seed)
or init_by_array(init_key, key_length).

Copyright (C) 1997 - 2002, Makoto Matsumoto and Takuji Nishimura,
All rights reserved.

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 its contributors may not be used to endorse or promote
    products derived from this software without specific prior written
    permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"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 COPYRIGHT OWNER OR CONTRIBUTORS 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.

Any feedback is very welcome.
http://www.math.keio.ac.jp/matumoto/emt.html
email: matumoto@math.keio.ac.jp

Sockets
=======
The socket module uses the functions, getaddrinfo(), and getnameinfo(), which are coded in separate source files from the WIDE Project, http://www.wide.ad.jp/.

Copyright (C) 1995, 1996, 1997, and 1998 WIDE Project.
All rights reserved.

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. Neither the name of the project nor the names of its contributors
   may be used to endorse or promote products derived from this
   software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS "AS IS" AND
GAI_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 PROJECT OR CONTRIBUTORS BE LIABLE FOR GAI_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 GAI_ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN GAI_ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Floating point exception control
================================
The source for the fpectl module includes the following notice:

  ---------------------------------------------------------------------
 /                       Copyright (c) 1996.                           \
|          The Regents of the University of California.                 |
|                        All rights reserved.                           |
|                                                                       |
|   Permission to use, copy, modify, and distribute this software for   |
|   any purpose without fee is hereby granted, provided that this en-   |
|   tire notice is included in all copies of any software which is or   |
|   includes  a  copy  or  modification  of  this software and in all   |
|   copies of the supporting documentation for such software.           |
|                                                                       |
|   This  work was produced at the University of California, Lawrence   |
|   Livermore National Laboratory under  contract  no.  W-7405-ENG-48   |
|   between  the  U.S.  Department  of  Energy and The Regents of the   |
|   University of California for the operation of UC LLNL.              |
|                                                                       |
|                              DISCLAIMER                               |
|                                                                       |
|   This  software was prepared as an account of work sponsored by an   |
|   agency of the United States Government. Neither the United States   |
|   Government  nor the University of California nor any of their em-   |
|   ployees, makes any warranty, express or implied, or  assumes  any   |
|   liability  or  responsibility  for the accuracy, completeness, or   |
|   usefulness of any information,  apparatus,  product,  or  process   |
|   disclosed,   or  represents  that  its  use  would  not  infringe   |
|   privately-owned rights. Reference herein to any specific  commer-   |
|   cial  products,  process,  or  service  by trade name, trademark,   |
|   manufacturer, or otherwise, does not  necessarily  constitute  or   |
|   imply  its endorsement, recommendation, or favoring by the United   |
|   States Government or the University of California. The views  and   |
|   opinions  of authors expressed herein do not necessarily state or   |
|   reflect those of the United States Government or  the  University   |
|   of  California,  and shall not be used for advertising or product   |
 \  endorsement purposes.                                              /
  ---------------------------------------------------------------------

MD5 message digest algorithm
============================
The source code for the md5 module contains the following notice:

Copyright (C) 1999, 2002 Aladdin Enterprises.  All rights reserved.

This software is provided 'as-is', without any express or implied
warranty.  In no event will the authors be held liable for any damages
arising from the use of this software.

Permission is granted to anyone to use this software for any purpose,
including commercial applications, and to alter it and redistribute it
freely, subject to the following restrictions:

1. The origin of this software must not be misrepresented; you must not
   claim that you wrote the original software. If you use this software
   in a product, an acknowledgment in the product documentation would
   be appreciated but is not required.
2. Altered source versions must be plainly marked as such, and must not
   be misrepresented as being the original software.
3. This notice may not be removed or altered from any source
   distribution.

L. Peter Deutsch
ghost@aladdin.com

Independent implementation of MD5 (RFC 1321).

This code implements the MD5 Algorithm defined in RFC 1321, whose
text is available at
      http://www.ietf.org/rfc/rfc1321.txt
The code is derived from the text of the RFC, including the test suite
(section A.5) but excluding the rest of Appendix A.  It does not include
any code or documentation that is identified in the RFC as being
copyrighted.

The original and principal author of md5.h is L. Peter Deutsch
&lt;ghost@aladdin.com&gt;.  Other authors are noted in the change history
that follows (in reverse chronological order):

2002-04-13 lpd Removed support for non-ANSI compilers; removed
      references to Ghostscript; clarified derivation from RFC 1321;
      now handles byte order either statically or dynamically.
1999-11-04 lpd Edited comments slightly for automatic TOC extraction.
1999-10-18 lpd Fixed typo in header comment (ansi2knr rather than md5);
      added conditionalization for C++ compilation from Martin
      Purschke &lt;purschke@bnl.gov&gt;.
1999-05-03 lpd Original version.

Asynchronous socket services
============================
The asynchat and asyncore modules contain the following notice:

Copyright 1996 by Sam Rushing

                        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, and that the name of Sam
Rushing not be used in advertising or publicity pertaining to
distribution of the software without specific, written prior
permission.

SAM RUSHING DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE,
INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN
NO EVENT SHALL SAM RUSHING 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.

Cookie management
=================
The Cookie module contains the following notice:

Copyright 2000 by Timothy O'Malley &lt;timo@alum.mit.edu&gt;

               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, and that the name of
Timothy O'Malley  not be used in advertising or publicity
pertaining to distribution of the software without specific, written
prior permission.

Timothy O'Malley DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS
SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS, IN NO EVENT SHALL Timothy O'Malley 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.

Profiling
=========
The profile and pstats modules contain the following notice:

Copyright 1994, by InfoSeek Corporation, all rights reserved.
Written by James Roskind

Permission to use, copy, modify, and distribute this Python software
and its associated documentation for any purpose (subject to the
restriction in the following sentence) without fee is hereby granted,
provided that the above copyright notice appears in all copies, and
that both that copyright notice and this permission notice appear in
supporting documentation, and that the name of InfoSeek not be used in
advertising or publicity pertaining to distribution of the software
without specific, written prior permission.  This permission is
explicitly restricted to the copying and modification of the software
to remain in Python, compiled Python, or other languages (such as C)
wherein the modified or derived code is exclusively imported into a
Python module.

INFOSEEK CORPORATION DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS
SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS. IN NO EVENT SHALL INFOSEEK CORPORATION 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.

Execution tracing
=================
The trace module contains the following notice:

portions copyright 2001, Autonomous Zones Industries, Inc., all rights...
err...  reserved and offered to the public under the terms of the
Python 2.2 license.
Author: Zooko O'Whielacronx
http://zooko.com/
mailto:zooko@zooko.com

Copyright 2000, Mojam Media, Inc., all rights reserved.
Author: Skip Montanaro

Copyright 1999, Bioreason, Inc., all rights reserved.
Author: Andrew Dalke

Copyright 1995-1997, Automatrix, Inc., all rights reserved.
Author: Skip Montanaro

Copyright 1991-1995, Stichting Mathematisch Centrum, all rights reserved.

Permission to use, copy, modify, and distribute this Python software and its associated documentation for any purpose without fee is hereby
granted, provided that the above copyright notice appears in all copies, and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of neither Automatrix, Bioreason or Mojam Media be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission.

UUencode and UUdecode functions
===============================

The uu module contains the following notice:

Copyright 1994 by Lance Ellinghouse
Cathedral City, California Republic, United States of America.
                       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, and that the name of Lance Ellinghouse
not be used in advertising or publicity pertaining to distribution
of the software without specific, written prior permission.
LANCE ELLINGHOUSE DISCLAIMS ALL WARRANTIES WITH REGARD TO
THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS, IN NO EVENT SHALL LANCE ELLINGHOUSE CENTRUM 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.

Modified by Jack Jansen, CWI, July 1995:
- Use binascii module to do the actual line-by-line conversion
  between ascii and binary. This results in a 1000-fold speedup. The C
  version is still 5 times faster, though.
- Arguments more compliant with Python standard

XML Remote Procedure Calls¶

The xmlrpclib module contains the following notice:

    The XML-RPC client interface is

Copyright (c) 1999-2002 by Secret Labs AB
Copyright (c) 1999-2002 by Fredrik Lundh

By obtaining, using, and/or copying this software and/or its
associated documentation, you agree that you have read, understood,
and will comply with the following terms and conditions:

Permission to use, copy, modify, and distribute this software and
its associated documentation for any purpose and without fee is
hereby granted, provided that the above copyright notice appears in
all copies, and that both that copyright notice and this permission
notice appear in supporting documentation, and that the name of
Secret Labs AB or the author not be used in advertising or publicity
pertaining to distribution of the software without specific, written
prior permission.

SECRET LABS AB AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD
TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANT-
ABILITY AND FITNESS.  IN NO EVENT SHALL SECRET LABS AB OR THE AUTHOR
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.

test_epoll
==========
The test_epoll contains the following notice:

Copyright (c) 2001-2006 Twisted Matrix Laboratories.

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 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.

Select kqueue
=============
The select and contains the following notice for the kqueue interface:

Copyright (c) 2000 Doug White, 2006 James Knight, 2007 Christian Heimes
All rights reserved.

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.

THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``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 AUTHOR OR CONTRIBUTORS 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.

strtod and dtoa
===============
The file Python/dtoa.c, which supplies C functions dtoa and strtod for conversion of C doubles to and from strings, is derived from the file of the same name by David M. Gay, currently available from http://www.netlib.org/fp/. The original file, as retrieved on March 16, 2009, contains the following copyright and licensing notice:

/****************************************************************
 *
 * The author of this software is David M. Gay.
 *
 * Copyright (c) 1991, 2000, 2001 by Lucent Technologies.
 *
 * Permission to use, copy, modify, and distribute this software for
 * any purpose without fee is hereby granted, provided that this entire
 * notice is included in all copies of any software which is or
 * includes a copy or modification of this software and in all copies
 * of the supporting documentation for such software.
 *
 * THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR
 * IMPLIED WARRANTY.  IN PARTICULAR, NEITHER THE AUTHOR NOR LUCENT
 * MAKES ANY REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE
 * MERCHANTABILITY OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR
 * PURPOSE.
 *
 ***************************************************************/</pre></div></body></html>


path: /wb-html-guitools/wb-news-5-0-25.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.3.6. Changes in MySQL Workbench 5.0.25 (12 September 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-26.html" title="A.3.5. Changes in MySQL Workbench 5.0.26 (16 October 2008)"><link rel="next" href="wb-news-5-0-24.html" title="A.3.7. Changes in MySQL Workbench 5.0.24 (12 August 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-25"></a>A.3.6. Changes in MySQL Workbench 5.0.25 (12 September 2008)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.0.24.
      </p><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        If the user closed all tabs and then quit, Workbench crashed.
       (Bug #39346)</p></li><li><p>
        Foreign keys referencing a deleted table were not removed.
       (Bug #39150)</p></li><li><p>
        <span class="guimenu">Forward Engineer SQL CREATE Script</span> and
        <span class="guimenu">Forward Engineer SQL ALTER Script</span> generated
        scripts that did not put index names in quotation marks.
       (Bug #39140)</p></li><li><p>
        When Workbench was started with the <span class="guilabel">GRT
        Shell</span> tab opened, the object tree in the
        <span class="guilabel">GRT Tree</span> pane was not displayed.
       (Bug #39122)</p></li><li><p>
        When triggers were exported with the <span class="guilabel">Generate DROP
        TABLES statements</span> option checked, <code class="literal">DROP
        TRIGGER IF EXISTS</code> did not appear in the exported SQL.
       (Bug #39119)</p></li><li><p>
        The <span class="guilabel">Triggers</span> tab would always enable Insert
        mode when opened.
       (Bug #39118)</p></li><li><p>
        In the <span class="guilabel">Foreign Key</span> tab of the
        <span class="guilabel">Table Editor</span>, the menu that is displayed on
        clicking in the <span class="guilabel">Referenced Table</span> column,
        listed table names by creation date, rather than by sorted name.
       (Bug #38944)</p></li><li><p>
        If any <code class="literal">DEFAULT</code> properties were defined for a
        model, they appeared to be lost after saving the model and
        restarting Workbench.
       (Bug #38825)</p></li><li><p>
        When you loaded a UTF-8 encoded script file into Workbench, the
        embedded SQL editor replaced international characters with the
        <code class="literal">?</code> symbol.
       (Bug #38783)</p></li><li><p>
        When creating Views and Routines, the entry in the
        <span class="guilabel">Undo History</span> window showed “<span class="quote">Parse
        MySQL View</span>” instead of “<span class="quote">View Created</span>”, and
        “<span class="quote">Parse MySQL Routine</span>” instead of “<span class="quote">Routine
        Created</span>”.
      </p><p>
        When subsequently undoing this operation the correct text was
        displayed. Performing a redo then resulted in the incorrect text
        being displayed again.
      </p><p>
        Additionally, when undoing a Routine Group, the previous undo
        action in the history was incorrectly renamed and the last entry
        in the history was deleted.
       (Bug #36047)</p></li><li><p>
        In the <span class="guilabel">Table Editor</span> tab, wherever data
        could be entered, such as in the <span class="guilabel">Foreign Key
        Name</span> entry field, the default wrap protocol was to go
        to a new line. This resulted in text that was only partially
        visible.
       (Bug #34510)</p></li><li><p>
        The synchronization wizard could show a diff tree for schemata
        different from those that had been selected.
       (Bug #32365)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/license-treeviewadv-net.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>B.23. TreeViewAdv for .NET 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-tinyxml.html" title="B.22. TinyXML License"><link rel="next" href="license-vsqlite.html" title="B.24. VSQLite++ 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-treeviewadv-net"></a>B.23. TreeViewAdv for .NET License</h2></div></div></div><p>
    The following software may be included in this product:
  </p><pre class="programlisting">TreeViewAdv for .NET

The BSD License

Copyright (c) 2009, Andrey Gliznetsov (a.gliznetsov@gmail.com)

All rights reserved.

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

- Redistributions of source code must retain the above copyright notice, 
  this list of conditions and the following disclaimer.

- Redistributions in binary form must reproduce the above copyright notice,
  this list of conditions and the following disclaimer in the documentation
  andor other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
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
COPYRIGHT OWNER OR CONTRIBUTORS 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/wb-news-5-0-14a.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.3.17. Changes in MySQL Workbench 5.0.14abeta (28 February 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-15.html" title="A.3.16. Changes in MySQL Workbench 5.0.15rc (17 March 2008)"><link rel="next" href="wb-news-5-0-14.html" title="A.3.18. Changes in MySQL Workbench 5.0.14beta (25 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-14a"></a>A.3.17. Changes in MySQL Workbench 5.0.14abeta (28 February 2008)</h3></div></div></div><p>
        This unscheduled beta release fixes bug#34847. Other bug fixes
        applied since the release of 5.0.14beta are also documented.
      </p><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        MWB files were not saved properly if Workbench crashed.
        Reopening such files caused Workbench to crash.
       (Bug #34848)</p><p>See also Bug #34847.</p></li><li><p>
        Workbench models created in version 5.0.13 crashed when used
        with version 5.0.14. The unscheduled Beta release, 5.0.14a fixes
        this bug.
       (Bug #34847)</p></li><li><p>
        When clicking the <span class="guibutton">Browse</span> button in the
        image editor, the default file name was
        <code class="literal">openFileDialog1</code>. This now defaults to an
        empty string.
       (Bug #34622)</p></li><li><p>
        Repeatedly changing the object notation crashed Workbench. This
        is no longer repeatable.
       (Bug #34499)</p></li><li><p>
        Importing a DBDesigner file immediately threw an exception. This
        happened even when software rendering was used. DBDesigner files
        can now be imported without incident.
       (Bug #33588)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-printing-options.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.9.1. Printing 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-printing.html" title="7.9. Printing"><link rel="prev" href="wb-printing.html" title="7.9. Printing"><link rel="next" href="wb-validation-plugins.html" title="7.10. MySQL Workbench Schema Validation Plugins (Commercial Version)"></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-printing-options"></a>7.9.1. Printing Options</h3></div></div></div><p>
      The printing menu items not enabled unless an EER Diagram is
      active. These items are available:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <span class="guimenuitem">Page Setup...</span>
        </p><p>
          Enables you to choose the paper size, orientation, and
          margins.
        </p></li><li><p>
          <span class="guimenuitem">Print</span>
        </p><p>
          Sends your EER Diagram directly to the printer. This option
          generates a preview before printing. From the preview you can
          adjust the scale of the view and also choose a multi-page
          view. Clicking the printer icon at the top left of this
          window, prints the currently selected EER Diagram. Close the
          print preview window if you need to adjust the placement of
          objects on the EER Diagram canvas.
        </p></li><li><p>
          <span class="guimenuitem">Print to PDF...</span>
        </p><p>
          Creates a PDF file of your EER Diagram.
        </p></li><li><p>
          <span class="guimenuitem">Print to PS...</span>
        </p><p>
          Creates a PostScript file of your EER Diagram.
        </p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-news-5-0-20.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.3.11. Changes in MySQL Workbench 5.0.20 (26 April 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-21.html" title="A.3.10. Changes in MySQL Workbench 5.0.21 (27 April 2008)"><link rel="next" href="wb-news-5-0-19.html" title="A.3.12. Changes in MySQL Workbench 5.0.19 (15 April 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-20"></a>A.3.11. Changes in MySQL Workbench 5.0.20 (26 April 2008)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.0.19.
      </p><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        Re-creating a deleted relationship caused a crash.
       (Bug #36385)</p></li><li><p>
        The message log on the <span class="guilabel">Forward Engineer
        Progess/Results Advanced</span> dialog had no scroll bar.
       (Bug #36192)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-basic-add-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.3.1. Adding a 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-basic-modeling.html" title="7.8.3. Basic Modeling"><link rel="prev" href="wb-basic-modeling.html" title="7.8.3. Basic Modeling"><link rel="next" href="wb-basic-foreign-key.html" title="7.8.3.2. Creating a Foreign Key"></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-basic-add-table"></a>7.8.3.1. Adding a Table</h4></div></div></div><p>
        The tools in the vertical toolbar on the left of the
        <span class="guilabel">EER Diagram</span> tab are used for designing an
        EER diagram. Start by creating a table using the table tool. The
        table tool is the rectangular grid in the middle of the vertical
        toolbar. Mousing over it shows the message, <code class="literal">Place a New
        Table (T)</code>.
      </p><p>
        Clicking this tool changes the mouse pointer to a hand with a
        rectangular grid. Create a table on the canvas by clicking
        anywhere on the <code class="literal">EER Diagram</code> grid.
      </p><p>
        Right-click the table and choose <span class="guimenuitem">Edit in New
        Window</span> from the pop-up menu. This opens the table
        editor, docked at the bottom of the application.
      </p><p>
        The table name defaults to <code class="literal">table1</code>. Change the
        name by entering <code class="literal">invoice</code> into the
        <span class="guilabel">Name:</span> field. Changes here affect the name
        of the tab in the table editor and the name of the table on the
        canvas.
      </p><p>
        Pressing <span><strong class="keycap">Tab</strong></span> or <span><strong class="keycap">Enter</strong></span> while
        the cursor is in the table name field selects the
        <span class="guilabel">Columns</span> tab of the table editor and creates
        a default column named <code class="literal">idinvoice</code>.
      </p><p>
        Pressing <span><strong class="keycap">Tab</strong></span> or <span><strong class="keycap">Enter</strong></span> again
        sets the focus on the <code class="literal">Datatype</code> list with
        <code class="literal">INT</code> selected. Notice that a field has been
        added to the table on the EER canvas.
      </p><p>
        Pressing <span><strong class="keycap">Tab</strong></span> yet again and the focus shifts to
        adding a second column. Add a <code class="literal">Description</code> and
        a <code class="literal">Customer_id</code> column. When you are finished,
        close the table editor, by clicking the <span class="guibutton">x</span>
        button on the top left of the table editor.
      </p></div></body></html>


path: /wb-html-guitools/wb-news-5-1-9.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.2.11. Changes in MySQL Workbench 5.1.9 (Not yet released Beta)</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-10.html" title="A.2.10. Changes in MySQL Workbench 5.1.10 (10 April 2009)"><link rel="next" href="wb-news-5-1-8.html" title="A.2.12. Changes in MySQL Workbench 5.1.8 (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-1-9"></a>A.2.11. Changes in MySQL Workbench 5.1.9 (Not yet released Beta)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.1.8.
      </p><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        In Model View after performing <span class="guimenu">Edit</span>,
        <span class="guimenu">Select</span>, <span class="guimenu">Select All</span>, it was
        not then possible to undo the operation.
       (Bug #43225)</p></li><li><p>
        When a script was processed by <span class="guimenu">File</span>,
        <span class="guimenu">Import</span>, <span class="guimenu">Reverse Engineer MySQL
        CREATE Script</span>, columns with a boolean data type had
        their data type ignored. As a result, the type of the column in
        the Table Editor was empty.
       (Bug #43094)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-help-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.10. The Help 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-community-menu.html" title="7.5.1.9. The Community Menu"><link rel="next" href="wb-toolbar.html" title="7.5.2. The Toolbar"></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-help-menu"></a>7.5.1.10. The Help Menu</h4></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-help-menu.html#wb-system-info">7.5.1.10.1. System Info</a></span></dt></dl></div><p>
      The <span class="guimenu">Help</span> menu has the following items. Use them
      to go online and learn more about MySQL Workbench.
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <span class="guimenuitem">Help Index</span>: Opens a window showing
          the MySQL Workbench documentation. Read, search, or print the
          documentation from this window.
        </p></li><li><p>
          <span class="guimenuitem">Check For Updates</span>: Opens your
          default browser on the MySQL Workbench Web site and checks for a
          newer version.
        </p></li><li><p>
          <span class="guimenuitem">Update</span>: Updates to the latest
          version.
        </p></li><li><p>
          <span class="guimenuitem">MySQL.com Website</span>: Opens your
          default browser on the MySQL Web site home page.
        </p></li><li><p>
          <span class="guimenuitem">Workbench Product Page</span>: Opens your
          default browser on the MySQL Workbench product page.
        </p></li><li><p>
          <span class="guimenuitem">System Info</span>: Displays information
          about your system, which is useful when reporting a bug. For
          more information, see <a href="wb-help-menu.html#wb-system-info" title="7.5.1.10.1. System Info">Section 7.5.1.10.1, “System Info”</a>.
        </p></li><li><p>
          <span class="guimenuitem">Report a Bug</span>: Opens your default
          browser on the MySQL bug report page.
        </p></li><li><p>
          <span class="guimenuitem">View Reported Bugs</span>: Opens your
          default browser to see a list of current bugs.
        </p></li><li><p>
          <span class="guimenuitem">About Workbench</span>: Displays the
          MySQL Workbench <code class="literal">About</code> window.
        </p></li></ul></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="wb-system-info"></a>7.5.1.10.1. System Info</h5></div></div></div><p>
        Use the <span class="guimenuitem">System Info</span> menu item to
        display information about your system. This item is especially
        useful for determining your rendering mode. Sample output
        follows.
      </p><pre class="programlisting">read_mysql_cfg_file  C:\Program Files\MySQL\MySQL Server 5.1\my.ini
[('tmp_table_size', '9M'), 
('myisam_sort_buffer_size', '18M'), 
('table_cache', '256'), 
('read_rnd_buffer_size', '256K'), 
('port', '3306'), ('max_connections', '100'), 
('innodb_buffer_pool_size', '18M'), 
('myisam_max_sort_file_size', '100G'), 
('sql-mode', '"STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"'), 
('basedir', '"C:/Program Files/MySQL/MySQL Server 5.1/"'), 
('default-character-set', 'latin1'), 
('datadir', '"C:/ProgramData/MySQL/MySQL Server 5.1/Data/"'), 
('innodb_log_buffer_size', '1M'), 
('innodb_log_file_size', '10M'), 
('innodb_thread_concurrency', '8'), 
('read_buffer_size', '64K'), 
('innodb_additional_mem_pool_size', '2M'), 
('thread_cache_size', '8'), 
('innodb_flush_log_at_trx_commit', '1'), 
('query_cache_size', '0'), 
('sort_buffer_size', '256K'), 
('default-storage-engine', 'INNODB'), 
('key_buffer_size', '11M')]
MySQL Workbench OSS for Windows version 5.2.8
Cairo Version: 1.8.6
Rendering Mode: GDI requested (create a diagram to confirm)
OpenGL Driver Version: Not Detected
OS: unknown
CPU: Intel(R) Core(TM)2 Duo CPU     T9300  @ 2.50GHz, 1.0 GB RAM
Video adapter info:
Adapter type: VirtualBox Graphics Adapter
Chip Type: VBOX
BIOS String: Version 0xB0C2 or later
Video Memory: 12288 KB</pre></div></div></body></html>


path: /wb-html-guitools/wb-news-5-2-10.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.30. Changes in MySQL Workbench 5.2.10 (01 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-11.html" title="A.1.29. Changes in MySQL Workbench 5.2.11 (18 December 2009)"><link rel="next" href="wb-news-5-2-9.html" title="A.1.31. Changes in MySQL Workbench 5.2.9 (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-10"></a>A.1.30. Changes in MySQL Workbench 5.2.10 (01 December 2009)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.2.9.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        MySQL Workbench now has the command line option
        <code class="option">--version</code>, which is used to display the version
        of the application, when launching the application from the
        command line.
       (Bug #49136)</p></li><li><p>
        The <span class="guimenu">Help</span>, <span class="guimenu">Workbench Product
        Page</span> menu item launched the default web browser, but
        displayed an outdated product page. This was due to a web server
        configuration issue. MySQL Workbench now displays the correct,
        up-to-date product page.
       (Bug #49066)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        When using <span class="guimenu">Alter Table</span> in the SQL Editor, if
        a column name was changed, and the <span class="guibutton">Apply</span>
        button clicked, the <span class="guilabel">Apply Object Changes</span>
        wizard was launched. The <span class="guilabel">Review changes</span>
        page indicated that the script that would be applied would drop
        the altered column then add a new column with the new name. This
        led to column data being lost because the script should instead
        have used <code class="literal">CHANGE COLUMN</code>, to change the name
        of the column.
       (Bug #49286)</p></li><li><p>
        When using <span class="guimenu">Alter Table</span> in the SQL Editor, if
        a table name was changed, and the <span class="guibutton">Apply</span>
        button clicked, the <span class="guilabel">Apply Object Changes</span>
        wizard was launched. The <span class="guilabel">Review changes</span>
        page indicated that the script that would be applied would
        incorrectly create a new table as a duplicate of the table being
        renamed, rather than use <code class="literal">ALTER</code> to rename the
        table.
       (Bug #49275)</p></li><li><p>
        In the configuration editor, in the Admin tab, the
        <span class="guibutton">Discard</span> button simply unchecked all
        options, rather than just those that had been checked during the
        current editing session. This made the button appear to have a
        “<span class="quote">clear all</span>” function, rather than the expected
        “<span class="quote">revert changes</span>” function.
       (Bug #49234)</p></li><li><p>
        When using the <span class="guilabel">Forward Engineer SQL CREATE
        Script</span> wizard, if the check box <span class="guilabel">Omit Schema
        Qualifier in Object Names</span> was selected, the script
        code for views was omitted.
       (Bug #49153)</p></li><li><p>
        In the <span class="guilabel">Administrative Roles</span> tab of
        <span class="guilabel">Server Access Management</span>, selection of
        Roles did not work correctly. For example, selecting the
        <span class="guilabel">DBA</span> check box, and then deselecting it,
        caused all roles to be deselected. Further, using the
        <span class="guibutton">Revert</span> button resulted in the selected
        user disappearing from the <span class="guilabel">User Accounts</span>
        panel.
       (Bug #49071)</p></li><li><p>
        MySQL Workbench did not handle signed and unsigned integers
        correctly. For example, if performing a synchronization between
        a model and a live database where the only difference was a
        column was declared to be of type <code class="literal">INTEGER</code> in
        one case and <code class="literal">UNSIGNED INTEGER</code> in the other,
        the difference would not be detected and the ALTER script would
        imply the databases were the same.
       (Bug #49063)</p></li><li><p>
        A MySQL configuration file caused MySQL Workbench to crash, when an
        attempt was made to view it in the configuration editor of the
        Admin tab. The error generated was:
      </p><pre class="programlisting">Unhandled exception:  'bool' object has no attribute 'strip'</pre><p>(Bug #49060, Bug #49602)</p></li><li><p>
        In the SQL Editor, two buttons on the toolbar had no tooltips.
        These were the green check or tick mark, and the red back arrow
        buttons. Further, they did not seem to become enabled or
        disabled according to the context, making it difficult to
        determine their intended function.
       (Bug #49059)</p></li><li><p>
        On the <span class="guilabel">MySQL Config File</span> page of the
        <span class="guilabel">New Server Profile</span> wizard, clicking
        <span class="guibutton">Check section</span> generated an exception if
        there were options in the MySQL configuration file that did not
        have values assigned:
      </p><pre class="programlisting">Check if mysqld section exists in /tmp/my.cnf
** Message: function call error
Traceback (most recent call last):
  File "/usr/lib/mysql-workbench/modules/wb_admin_grt.py", line 292, in
testInstanceSettingByName
    parser.read([config_file])
  File "/usr/lib/python2.5/ConfigParser.py", line 267, in read
    self._read(fp, filename)
  File "/usr/lib/python2.5/ConfigParser.py", line 490, in _read
    raise e
ConfigParser.ParsingError: File contains parsing errors: /tmp/my.cnf
        [line  2]: 'log-bin\n'

glibmm-ERROR **: 
unhandled exception (type std::exception) in signal handler:
what: error calling WbAdmin.testInstanceSettingByName: see output for details</pre><p>(Bug #49057, Bug #47954)</p></li><li><p>
        On the Admin screen, the server configuration option
        <span class="guilabel">Key buffer</span>, was located under the
        <span class="guilabel">General</span> tab, rather than the
        <span class="guilabel">MyISAM Parameters</span> tab, even though it was a
        <code class="literal">MyISAM</code>-only option.
       (Bug #49017)</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><li><p>
        In the SQL Editor, the database explorer of the Schemata palette
        in the side panel did not work correctly. Incorrect behavior
        included random collapsing of expanded databases and occasional
        crashing.
       (Bug #48981)</p></li><li><p>
        When using the data modeler, MySQL Workbench extended vertically to
        the maximum size of the screen, overlapping the dock, and
        thereby making it impossible to use.
       (Bug #48976)</p></li><li><p>
        In the <span class="guilabel">Manage Server Instances</span> dialog, if
        the <span class="guilabel">Server Instances</span> list pane was empty,
        then on creating a new Server Instance, it was not possible to
        change the instance's name. The instance had to be created, the
        dialog closed. On reopening the dialog, the instance could be
        renamed.
       (Bug #48967)</p></li><li><p>
        The Generate Catalog Diff Report feature did not permit the
        comparison of imported scripts because selecting the radio
        button for this option had no effect.
       (Bug #47230)</p></li><li><p>
        If a collation was changed for a table in the Table Editor,
        there was no facility to then set this back to the schema
        default.
      </p><p>
        A new entry has been now been added to the collation selection
        list: <span class="guilabel">Schema Default</span>.
       (Bug #46513)</p></li><li><p>
        When a model containing stored routines was forward engineered
        to a script, the script contained an erroneous additional
        delimiter after each stored routine. This resulted in a
        “<span class="quote">No query specified</span>” error when an attempt was made
        to run the script on a server.
       (Bug #39929)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-forward-engineering-live-server.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.7.10.2. Forward Engineering to a Live Server</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-forward-engineering.html" title="7.7.10. Forward Engineering"><link rel="prev" href="wb-forward-engineering-sql-scripts.html" title="7.7.10.1. Forward Engineering Using an SQL Script"><link rel="next" href="wb-database-synchronization.html" title="7.7.10.3. Database Synchronization"></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-forward-engineering-live-server"></a>7.7.10.2. Forward Engineering to a Live Server</h4></div></div></div><p>
      Use forward engineering to export your schema design to a MySQL
      server.
    </p><p>
      Select the schema that you wish to forward engineer and then
      choose the <span class="guimenu">Database</span>, <span class="guimenuitem">Forward
      Engineer...</span> menu item from the main menu.
    </p><p>
      The first page to be displayed is Catalog Validation (validation
      is available only in the Standard Edition).
    </p><div class="figure"><a name="wb-forward-engineer-to-database-wizard-catalog"></a><p class="title"><b>Figure 7.28. Catalog Validation</b></p><div class="mediaobject"><img src="images/wb-forward-engineer-to-database-wizard-catalog.png" width="800" height="600" alt="Catalog Validation"></div></div><p>
      Click <span class="guibutton">Run Validations</span> to validate the
      catalog.
    </p><p>
      Click <span class="guibutton">Next</span> to continue.
    </p><p>
      The next page enables you to set options for the database to be
      created. These options are as described in
      <a href="wb-forward-engineering-sql-scripts.html#wb-export-script-create-sql" title="7.7.10.1.1. Creating a Schema">Section 7.7.10.1.1, “Creating a Schema”</a>.
    </p><div class="figure"><a name="wb-forward-engineer-to-database-wizard-options"></a><p class="title"><b>Figure 7.29. Options</b></p><div class="mediaobject"><img src="images/wb-forward-engineer-to-database-wizard-options.png" width="798" height="598" alt="Options"></div></div><p>
      Select the required options and then click
      <span class="guibutton">Next</span>.
    </p><p>
      The next page enables you to select the objects to forward
      engineer.
    </p><div class="figure"><a name="wb-forward-engineer-to-database-wizard-select-objects"></a><p class="title"><b>Figure 7.30. Select Objects to Forward Engineer</b></p><div class="mediaobject"><img src="images/wb-forward-engineer-to-database-wizard-select-objects.png" width="798" height="598" alt="Select Objects to Forward Engineer"></div></div><p>
      To select a subset of objects to forward engineer, use the
      <span class="guibutton">Show Filter</span>/<span class="guibutton">Hide
      Filter</span> button, then select specific objects. After you
      have selected your objects, click <span class="guibutton">Next</span> to
      continue
    </p><p>
      On the <span class="guilabel">Review Script</span> page you may review and
      edit the SQL script that will be executed.
    </p><div class="figure"><a name="wb-forward-engineer-to-database-wizard-review-script"></a><p class="title"><b>Figure 7.31. Review Script</b></p><div class="mediaobject"><img src="images/wb-forward-engineer-to-database-wizard-review-script.png" width="798" height="598" alt="Review Script"></div></div><p>
      Click <span class="guibutton">Next</span> to continue if you are satisfied
      with the generated script.
    </p><p>
      The next step of the process is to connect to a MySQL server in
      order to create the new database schema. This page enables you to
      use a previously stored connection, or enter the connection
      parameters.
    </p><div class="figure"><a name="wb-forward-engineer-to-database-wizard-connect"></a><p class="title"><b>Figure 7.32. Set Parameters for Connecting to a DBMS</b></p><div class="mediaobject"><img src="images/wb-forward-engineer-to-database-wizard-connect.png" width="798" height="598" alt="Set Parameters for Connecting to a
          DBMS"></div></div><p>
      After the connection parameters have been set, click
      <span class="guibutton">Execute</span>. The next page of the wizard
      displays the results of the forward engineering process.
    </p><div class="figure"><a name="wb-forward-engineer-to-database-wizard-progress"></a><p class="title"><b>Figure 7.33. Forward Engineering Progress</b></p><div class="mediaobject"><img src="images/wb-forward-engineer-to-database-wizard-progress.png" width="798" height="598" alt="Forward Engineering Progress"></div></div><p>
      You can confirm that the script created the schema by connecting
      to the target MySQL server and issuing a <code class="literal">SHOW
      DATABASES</code> statement.
    </p></div></body></html>


path: /wb-html-guitools/wb-sql-editor-results-tabsheets.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>6.7.4.5. Results Tabsheets</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-main-tabsheets.html" title="6.7.4. Main Tabsheets"><link rel="prev" href="wb-sql-editor-snippets-tabsheet.html" title="6.7.4.4. Snippets Tabsheet"><link rel="next" href="wb-sql-editor-live-editing-tabsheets.html" title="6.7.4.6. Live Editing Tabsheets"></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-results-tabsheets"></a>6.7.4.5. Results Tabsheets</h4></div></div></div><p>
          The results area of the screen shows the results from any
          queries that have been executed. If the script contains
          multiple queries, a result tab will be generated for each
          query that returns results.
        </p><div class="figure"><a name="wb-sql-editor-results-screenshot"></a><p class="title"><b>Figure 6.10. SQL Editor - Results Tabsheets</b></p><div class="mediaobject"><img src="images/wb-sql-editor-results-screenshot.png" width="798" height="377" alt="SQL Editor - Results Tabsheets"></div></div><p>
          Controls are provided to enable you to easily move over the
          results. These are shown in the following screenshot.
        </p><div class="figure"><a name="wb-sql-editor-results-controls-screenshot"></a><p class="title"><b>Figure 6.11. SQL Editor - Results Tabsheets Navigation Controls</b></p><div class="mediaobject"><img src="images/wb-sql-editor-results-controls-screenshot.png" width="793" height="29" alt="SQL Editor - Results Tabsheets
              Navigation Controls"></div></div><p>
          From left to right, the controls are:
        </p><div class="itemizedlist"><ul type="disc"><li><p>
              <span class="bold"><strong>Move to first row</strong></span>:
              Highlights the first row in the current result set.
            </p></li><li><p>
              <span class="bold"><strong>Move to previous row</strong></span>:
              Highlights the previous row.
            </p></li><li><p>
              <span class="bold"><strong>Move to next row</strong></span>:
              Highlights the next row.
            </p></li><li><p>
              <span class="bold"><strong>Move to last row</strong></span>:
              Highlights the last row in the current result set.
            </p></li><li><p>
              <span class="bold"><strong>Toggle wrapping of cell
              contents</strong></span>: Toggles between truncating or
              wrapping the data in a cell.
            </p></li><li><p>
              <span class="bold"><strong>Sort Ascending</strong></span>: Sorts the
              selected column in ascending order.
            </p></li><li><p>
              <span class="bold"><strong>Sort Descending</strong></span>: Sorts
              the selected column in descending order.
            </p></li><li><p>
              <span class="bold"><strong>Export record set to an external
              file</strong></span>: Writes a result set to a CSV, HTML, or
              XML file as required.
            </p></li><li><p>
              <span class="bold"><strong>Refresh Data from Data
              Source</strong></span>: Refreshes the current result set from
              the data source.
            </p></li><li><p>
              <span class="bold"><strong>Search for substring within
              data</strong></span>: Searches the data for the string entered
              in the search box.
            </p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-view-overview-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.5.4. The Physical Schemata 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-model-editor.html" title="7.5. Model Editor"><link rel="prev" href="wb-eer-diagrams-section.html" title="7.5.3. EER Diagrams"><link rel="next" href="wb-overview-schema-objects.html" title="7.5.4.1. The Schema Objects 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-view-overview-physical-schemata"></a>7.5.4. The Physical Schemata Panel</h3></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-overview-schema-objects.html">7.5.4.1. The Schema Objects Panel</a></span></dt></dl></div><p>
      The <code class="literal">Physical Schemata</code> panel of the
      <code class="literal">MySQL Model</code> page shows the active schemata and
      the objects that they contain.
    </p><p>
      Expand and contract the <code class="literal">Physical Schemata</code>
      section by double-clicking the arrow on the left of the
      <code class="literal">Physical Schemata</code> title bar. When the
      <code class="literal">Physical Schemata</code> section is expanded, it
      displays all currently loaded schemata.
    </p><p>
      Each schema shows as a tab. To select a specific schema, click its
      tab. When MySQL Workbench is first opened, a default schema,
      <code class="literal">mydb</code>, is selected. You can start working with
      this schema or you can load a new MySQL Workbench Models file
      (<code class="filename">mwb</code> extensiona.)
    </p><p>
      There are a variety of ways to add schema to the <code class="literal">Physical
      Schemata</code> panel. You can open an MWB file, reverse
      engineer a MySQL create script, or, if you are using a commercial
      version of MySQL Workbench, you can reverse engineer a database by
      connecting to a MySQL server.
    </p><p>
      You can also add a new schema by clicking the
      <span class="guibutton">+</span> button on the top right of the
      <code class="literal">Physical Schemata</code> panel. To remove a schema,
      click its tab and use the <span class="guibutton">-</span> button found to
      the immediate left of the <span class="guibutton">+</span> button. To the
      left of these buttons are three buttons that control how database
      object icons are displayed:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          The left button displays database objects as large icons.
        </p></li><li><p>
          The middle button displays small icons in multiple rows.
        </p></li><li><p>
          The right button displays small icons in a single list.
        </p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-news-5-2-4.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.36. Changes in MySQL Workbench 5.2.4 (07 October 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-5.html" title="A.1.35. Changes in MySQL Workbench 5.2.5 (Internal Release Only)"><link rel="next" href="wb-news-5-2-3.html" title="A.1.37. Changes in MySQL Workbench 5.2.3 (15 September 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-4"></a>A.1.36. Changes in MySQL Workbench 5.2.4 (07 October 2009)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.2.3.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        Some keyboard shortcuts have been changed.
      </p><p>
        On Microsoft Windows and Linux <span><strong class="keycap">Control+Y</strong></span> is now
        used for Redo. Mac OS X continues to use
        <span><strong class="keycap">Command+Shift+Z</strong></span> as its default for Redo. For
        Synchronize Model, <span><strong class="keycap">Control+Alt+Y</strong></span> is used on
        Windows and Linux, and <span><strong class="keycap">Command+Control+Y</strong></span> is
        used on Mac OS X.
       (Bug #46285)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        When editing a stored routine or trigger in the Table Editor,
        the cursor would relocate to the top of the editing window if a
        key was not pressed for a few seconds.
      </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
          On Windows this issue was fixed in 5.1.18. On Mac OS X this
          issue was fixed in 5.2.4. On Linux this issue was fixed in
          5.2.7.
        </p></div><p>(Bug #48156)</p></li><li><p>
        If a new empty EER diagram was created, then
        <span class="guimenu">Model</span>, <span class="guimenu">Relationship
        Notation</span>, <span class="guimenu">Connect to Columns</span> was
        selected, MySQL Workbench generated these messages:
      </p><pre class="programlisting">** Message: item_activated: 0x28d5cf0 -&gt;
'plugin:wb.view.setRelationshipNotation:fromcolumn'
** Message: unhandled message 4: wb.view.setRelationshipNotation finished in 0.00s</pre><p>
        These messages were not generated if the EER diagram contained
        at least one table.
       (Bug #47565)</p></li><li><p>
        When a model was synchronized, this incorrect SQL was generated:
      </p><pre class="programlisting">CREATE  TABLE IF NOT EXISTS `synthescom`.`adx_clienti` (

  `id` INT(11) UNSIGNED NOT NULL AUTO_INCREMENT ,

  `citta` VARCHAR(100) NULL DEFAULT NULL ,

  `provincia` VARCHAR(100) NULL DEFAULT NULL ,

  PRIMARY KEY (`id`) 

ENGINE = MyISAM

DEFAULT CHARACTER SET = utf8

COLLATE = utf8_general_ci;</pre><p>
        Note that the closing parenthesis, which should have been
        located after the PRIMARY KEY statement, is missing. Thats
        resulted in this error being generated:
      </p><pre class="programlisting">ERROR: 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 'ENGINE = MyISAM

DEFAULT CHARACTER SET = utf8

COLLATE = utf8_general_ci' at line 13</pre><p>(Bug #47407)</p></li><li><p>
        When a table was opened for editing in the Query Editor, the
        <code class="literal">DECIMAL</code> column values appeared in the result
        set as integer values, disregarding precision and scale
        settings. The fractional part of the number was discarded. It
        was also not possible to add the fractional part of the number
        during editing.
       (Bug #47405)</p></li><li><p>
        In the EER Diagram, Layer names were not rendered. This only
        happened with OpenGL rendering (only on Microsoft Windows).
       (Bug #47385)</p></li><li><p>
        When the <span class="guimenu">Query Database</span> menu option was
        selected, the explorer on the right-hand side displayed Tables,
        Views and Routines, but when the Routines folder was expanded
        the routines contained in the model were missing.
       (Bug #47088)</p></li><li><p>
        Clicking the <span class="guibutton">Test Connection</span> button in
        <span class="guilabel">DB Connection Editor</span> wizard did not appear
        to have any effect.
       (Bug #47083)</p></li><li><p>
        In the Query Editor, when an attempt was made to expand a schema
        and select a table, this exception was generated:
      </p><pre class="programlisting">************** Exception Text **************
System.AccessViolationException: Attempted to read or write protected memory. This is
often an indication that other memory is corrupt.
   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)
   at Aga.Controls.Tree.TreeViewAdv.SetIsExpanded(TreeNodeAdv node, Boolean value)
   at Aga.Controls.Tree.TreeViewAdv.SetIsExpanded(ExpandArgs eargs)
   at Aga.Controls.Tree.TreeViewAdv.SetIsExpanded(TreeNodeAdv node, Boolean value, Boolean
ignoreChildren)
...</pre><p>(Bug #47044)</p></li><li><p>
        On Mac OS X using <span><strong class="keycap">cmd</strong></span> +
        <span><strong class="keycap">backspace</strong></span> to delete a column in the table
        editor did not work.
       (Bug #46613)</p></li><li><p>
        In the <span class="guilabel">Synchronize Model with Database</span>
        dialog the text in the upper right area of the dialog did not
        wrap correctly, resulting in some text not being visible.
       (Bug #45455)</p></li><li><p>
        MySQL Workbench EER Diagram view did not permit the creation of a
        foreign key constraint on a primary key.
       (Bug #39546)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-getting-started-tutorial-admin.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>4.1. Administering a MySQL Server</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-getting-started-tutorial.html" title="Chapter 4. Getting Started Tutorial"><link rel="prev" href="wb-getting-started-tutorial.html" title="Chapter 4. Getting Started Tutorial"><link rel="next" href="wb-getting-started-tutorial-creating-a-model.html" title="4.2. Creating a Model"></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-getting-started-tutorial-admin"></a>4.1. Administering a MySQL Server</h2></div></div></div><p>
      In this section, you will use MySQL Workbench to carry out
      administrative functions, such as starting and stopping the
      server.
    </p><div class="orderedlist"><ol type="1"><li><p>
          Launch MySQL Workbench. You will be presented with the Home
          window.
        </p><div class="figure"><a name="wb-getting-started-tutorial-admin-home"></a><p class="title"><b>Figure 4.1. Getting Started Tutorial - Home Window</b></p><div class="mediaobject"><img src="images/wb-getting-started-tutorial-admin-home.png" width="1024" height="708" alt="Getting Started Tutorial - Home
              Window"></div></div></li><li><p>
          To administer your MySQL Server, you must first create a
          Server Instance. The instance contains information about the
          target server, including how to connect to it. From the
          MySQL Workbench Home window, click <span class="guilabel">New Server
          Instance</span>. The <span class="guilabel">Create New Server Instance
          Profile</span> wizard will be displayed.
        </p></li><li><p>
          In this tutorial, you will connect to a locally installed
          server, so click <span class="guibutton">Next</span>.
        </p><div class="figure"><a name="wb-getting-started-tutorial-admin-specify-host"></a><p class="title"><b>Figure 4.2. Getting Started Tutorial - Specify Host Machine</b></p><div class="mediaobject"><img src="images/wb-getting-started-tutorial-admin-specify-host.png" width="800" height="600" alt="Getting Started Tutorial - Specify Host
              Machine"></div></div></li><li><p>
          Next you will set up a connection, or select an existing
          connection to use to connect to the server. Assuming that you
          have not already created a connection, you can use the default
          values here, although if your MySQL Server has a password set
          for the <code class="literal">root</code> account, you can enter it here
          by clicking Store in Vault. This enables you to connect to the
          server without needing to enter a password each time. It is
          also possible to use a different account to connect to the
          server by setting the user name and password here, if
          required.
        </p><div class="figure"><a name="wb-getting-started-tutorial-admin-connection"></a><p class="title"><b>Figure 4.3. Getting Started Tutorial - Database Connection</b></p><div class="mediaobject"><img src="images/wb-getting-started-tutorial-admin-connection.png" width="800" height="600" alt="Getting Started Tutorial - Database
              Connection"></div></div><p>
          You can now click <span class="guibutton">Next</span>.
        </p></li><li><p>
          The connection will now be tested. You should see that the
          connection was successful. If not click
          <span class="guibutton">Back</span> and check that you have entered
          the information required.
        </p><div class="figure"><a name="wb-getting-started-tutorial-admin-test-connection"></a><p class="title"><b>Figure 4.4. Getting Started Tutorial - Connection Test</b></p><div class="mediaobject"><img src="images/wb-getting-started-tutorial-admin-test-connection.png" width="800" height="600" alt="Getting Started Tutorial - Connection
              Test"></div></div><p>
          If the connection test was successful, click
          <span class="guibutton">Next</span>.
        </p></li><li><p>
          Optionally, you may configure a method for remote management
          if a Remote Host was specified. Setting these options enables
          MySQL Workbench to determine the location of configuration files,
          and the correct start and stop commands to use for the server.
        </p><p>
          SSH login based management and Native Windows remote
          management types are available. The Operating System and MySQL
          Installation Type are configured for the SSH login variant.
        </p><div class="figure"><a name="wb-getting-started-tutorial-admin-management-and-os"></a><p class="title"><b>Figure 4.5. Getting Started Tutorial - Management and OS</b></p><div class="mediaobject"><img src="images/wb-getting-started-tutorial-admin-management-and-os.png" width="801" height="601" alt="Getting Started Tutorial - Management
              and OS"></div></div><p>
          Set the configuration method, then click
          <span class="guibutton">Next</span>.
        </p></li><li><p>
          If the SSH login based management was chosen, then you will
          configure its parameters which includes the User Name, Host
          Name, and optionally the SSH key for authentication.
        </p><div class="figure"><a name="wb-getting-started-tutorial-admin-ssh-configuration"></a><p class="title"><b>Figure 4.6. Getting Started Tutorial - SSH Configuration</b></p><div class="mediaobject"><img src="images/wb-getting-started-tutorial-admin-ssh-configuration.png" width="801" height="601" alt="Getting Started Tutorial - SSH
              Configuration"></div></div><p>
          Check that everything is in order, then click
          <span class="guibutton">Next</span>.
        </p></li><li><p>
          If a Windows server is used, then the Windows configuration
          parameters must be set.
        </p><div class="figure"><a name="wb-getting-started-tutorial-admin-windows-management"></a><p class="title"><b>Figure 4.7. Getting Started Tutorial - Windows Management</b></p><div class="mediaobject"><img src="images/wb-getting-started-tutorial-admin-windows-management.png" width="800" height="600" alt="Getting Started Tutorial - Windows
              Management"></div></div><p>
          Check that everything is in order, then click
          <span class="guibutton">Next</span>.
        </p></li><li><p>
          The wizard will now check that it is able to access the MySQL
          Server configuration file, and access the start and stop
          commands.
        </p><div class="figure"><a name="wb-getting-started-tutorial-admin-test-settings"></a><p class="title"><b>Figure 4.8. Getting Started Tutorial - Test Host Settings</b></p><div class="mediaobject"><img src="images/wb-getting-started-tutorial-admin-test-settings.png" width="800" height="600" alt="Getting Started Tutorial - Test Host
              Settings"></div></div><p>
          Check that everything is in order, then click
          <span class="guibutton">Next</span>.
        </p></li><li><p>
          You now have a chance to review the configuration settings so
          far. The information displayed varies slightly depending on
          platform, connection method and installation type.
        </p><div class="figure"><a name="wb-getting-started-tutorial-admin-review-settings"></a><p class="title"><b>Figure 4.9. Getting Started Tutorial - Review Settings</b></p><div class="mediaobject"><img src="images/wb-getting-started-tutorial-admin-review-settings.png" width="800" height="600" alt="Getting Started Tutorial - Review
              Settings"></div></div><p>
          Review the information, then click
          <span class="guibutton">Next</span>.
        </p></li><li><p>
          Finally you can give the server instance a suitable name. This
          will be used to select this particular instance from a list of
          available instances.
        </p><div class="figure"><a name="wb-getting-started-tutorial-admin-instance-name"></a><p class="title"><b>Figure 4.10. Getting Started Tutorial - Instance Name</b></p><div class="mediaobject"><img src="images/wb-getting-started-tutorial-admin-instance-name.png" width="800" height="600" alt="Getting Started Tutorial - Instance
              Name"></div></div><p>
          Set the desired name, then click <span class="guibutton">Finish</span>
          to complete the server instance creation process.
        </p></li><li><p>
          You will now be returned to the Home window. You will see the
          new server instance you created, along with the new connection
          you created as part of the preceding procedure.
        </p><div class="figure"><a name="wb-getting-started-tutorial-admin-home-screen-instance"></a><p class="title"><b>Figure 4.11. Getting Started Tutorial - Home Window Instance</b></p><div class="mediaobject"><img src="images/wb-getting-started-tutorial-admin-home-screen-instance.png" width="1024" height="708" alt="Getting Started Tutorial - Home Window
              Instance"></div></div><p>
          You are now ready to test your new server instance.
        </p></li><li><p>
          From the Home window, double-click the Server Instance you
          created. The Administrator will open on the
          <span class="guilabel">Startup</span> configuration page.
        </p><div class="figure"><a name="wb-getting-started-tutorial-admin-startup"></a><p class="title"><b>Figure 4.12. Getting Started Tutorial - Admin Startup</b></p><div class="mediaobject"><img src="images/wb-getting-started-tutorial-admin-startup.png" width="1024" height="708" alt="Getting Started Tutorial - Admin
              Startup"></div></div></li><li><p>
          Click the <span class="guibutton">Stop Server</span> button. The
          message window will show that the server has stopped.
        </p></li><li><p>
          Click the <span class="guibutton">Start Server</span> button to resume
          the server. The message window will confirm that the server is
          running.
        </p></li></ol></div><p>
      You have now seen how to create a server instance to enable you to
      manage a MySQL server.
    </p><p>
      For further information, see
      <a href="wb-server-administration.html" title="Chapter 8. Server Administration">Chapter 8, <i>Server Administration</i></a>.
    </p></div></body></html>


path: /wb-html-guitools/wb-sql-editor-history-tabsheet.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>6.7.4.3. History Tabsheet</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-main-tabsheets.html" title="6.7.4. Main Tabsheets"><link rel="prev" href="wb-sql-editor-output-tabsheet.html" title="6.7.4.2. Output Tabsheet"><link rel="next" href="wb-sql-editor-snippets-tabsheet.html" title="6.7.4.4. Snippets Tabsheet"></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-history-tabsheet"></a>6.7.4.3. History Tabsheet</h4></div></div></div><p>
          The History tabsheet provides a history of SQL operations
          carried out. The time and SQL code for each operation is
          recorded. To view the SQL executed, click the time, and the
          SQL code executed will be displayed in the
          <span class="guilabel">SQL</span> column.
        </p></div></body></html>


path: /wb-html-guitools/wb-news-5-2-7.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.33. Changes in MySQL Workbench 5.2.7 (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-8.html" title="A.1.32. Changes in MySQL Workbench 5.2.8 (18 November 2009 Beta)"><link rel="next" href="wb-news-5-2-6.html" title="A.1.34. Changes in MySQL Workbench 5.2.6 (21 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-7"></a>A.1.33. Changes in MySQL Workbench 5.2.7 (Internal release only)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.2.6.
      </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">Administrator</span> tab of MySQL Workbench the
        <span class="guilabel">Data Dump</span> (Export/Import Data) feature now
        uses the <code class="option">--comments</code> parameter when executing an
        import or export operation.
       (Bug #23002)</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">Manage Server Instances</span> wizard,
        MySQL Workbench crashed if the <span class="guibutton">New</span> button was
        clicked.
       (Bug #48347)</p></li><li><p>
        On Ubuntu Linux, MySQL Workbench did not warn if a new model was to
        be saved as a file that already existed on the drive.
       (Bug #48345)</p></li><li><p>
        The <code class="literal">Use compression protocol</code> option was not
        working correctly when set in the <span class="guilabel">Manage DB
        Connections</span> wizard.
      </p><p>
        When the checbox <span class="guilabel">Use compression protocol</span>
        was selected in the <span class="guilabel">Advanced</span> tab of the
        <span class="guilabel">Manage DB Connections</span> wizard, this error
        was generated when the connection was tested:
      </p><pre class="programlisting">No bool value passed for CLIENT_COMPRESS</pre><p>
        The same error occurred even if the <span class="guilabel">Use compression
        protocol</span> check box was subsequently cleared.
       (Bug #48202)</p></li><li><p>
        When editing a stored routine or trigger in the Table Editor,
        the cursor would relocate to the top of the editing window if a
        key was not pressed for a few seconds.
      </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
          On Windows this issue was fixed in 5.1.18. On Mac OS X this
          issue was fixed in 5.2.4. On Linux this issue was fixed in
          5.2.7.
        </p></div><p>(Bug #48156)</p></li><li><p>
        Attempting to export the result of an SQL query to CSV using
        <span class="guimenu">Query</span>, <span class="guimenu">Export Results...</span>
        gave the error:
      </p><pre class="programlisting">Failed to open template file: `/usr/share/mysql-workbench/modules/data/sqlide/CSV.tpl`</pre><p>
        This occurred on a Fedora 11 AMD64 install, from RPM. The
        requested file was found in a different directory,
        <code class="filename">/usr/share/mysql-workbench/sqlide/</code>. The
        error did not occur after the file was moved to the required
        location.
       (Bug #48156)</p></li><li><p>
        In the <span class="guilabel">Columns</span> tab of the Table Editor, the
        tooltip for the AI column did not work. If the cursor was placed
        over the column no tooltip text was displayed.
       (Bug #48129)</p></li><li><p>
        If an <span class="guilabel">EER Diagram</span> tab was closed, it was
        not possible to reopen it by clicking its icon on the model
        page.
       (Bug #47545)</p></li><li><p>
        In the GRT shell the <span><strong class="command">help</strong></span> command, which is
        equivalent to <span><strong class="command">?</strong></span>, crashed when no arguments
        were specified.
       (Bug #47503)</p></li><li><p>
        The script generated by <span class="guimenu">File</span>,
        <span class="guimenu">Export</span>, <span class="guimenu">Forward Engineer SQL CREATE
        Script</span> dropped a schema if it existed and then
        recreated it. This resulted in loss of existing data.
       (Bug #47468)</p></li><li><p>
        When an attempt was made to add a database connection, this
        error was generated:
      </p><pre class="programlisting">Test connect failed
Couldn't load library libmysqlclient_r.so: libmysqlclient_r.so: cannot open shared object
file: No such file or directory</pre><p>
        This only happened on Linux.
       (Bug #47238, Bug #48507)</p></li><li><p>
        In the <span class="guilabel">Inserts</span> tab of the Table Editor,
        values entered for a <code class="literal">BIT</code> column were not
        saved. If values were entered and then the changes applied, the
        values in the <code class="literal">BIT</code> column disappeared.
       (Bug #47100)</p></li><li><p>
        When a model was loaded and an EER Diagram opened, the model
        navigator did not display the model correctly.
       (Bug #46970)</p></li><li><p>
        In the Table Editor, when trying to modify a column default
        value, errors occurred.
      </p><div class="itemizedlist"><ul type="circle"><li><p>
            On a <code class="literal">TIMESTAMP</code> column it was not possible
            to enter a valid value of the format yyyy-mm-dd hh:mm:ss.
            This caused an error if forward engineering was attempted.
          </p></li><li><p>
            A <code class="literal">NULL</code> default value for a column could
            not be deleted.
          </p></li></ul></div><p>(Bug #46878)</p></li><li><p>
        In the <span class="guilabel">Inserts</span> tab of the Table Editor, if
        a string that contained spaces was added as an insert, the
        string was truncated to the text before the first space.
       (Bug #46624)</p></li><li><p>
        In the <span class="guilabel">Reverse Engineer Database</span> wizard it
        was not possible to select only one table to reverse engineer,
        and then proceed to the next step.
       (Bug #45881)</p></li><li><p>
        When running a plugin that called a function such as the
        following, the document's status was set to
        “<span class="quote">unsaved</span>”, and an asterisk was displayed in the
        title bar, as soon as the file selection dialog opened. This
        occurred even for a new document, or an unmodified document.
      </p><pre class="programlisting">function rfstest(obj)
  local path
  path = Workbench:requestFileSave("Caption", "SQL Files (*.sql)|*.sql")
end</pre><p>(Bug #44813)</p></li><li><p>
        Forward Engineer SQL CREATE Script generated schema qualifiers
        for Stored Procedure names regardless of the setting of the
        <span class="guilabel">Omit schemata qualifiers from output</span> check
        box. This resulted in the generated script containing Stored
        Procedure names prefixed by the schema name.
       (Bug #43276)</p></li><li><p>
        In the Table Editor, the keyboard shortcuts such as
        <span><strong class="keycap">Control+X</strong></span>, <span><strong class="keycap">Control+V</strong></span> and
        <span><strong class="keycap">Control+C</strong></span>, affected the main document, rather
        than being confined to within the Table Editor. For example, if
        <span><strong class="keycap">Control+C</strong></span> was used to copy a column, this
        erroneously resulted in a duplicate table being created in the
        main model.
       (Bug #42626)</p></li><li><p>
        If a collation was set as the schema default, this was not
        correctly handled when the model was synchronized with a live
        database.
      </p><p>
        If a collation was set as a schema default, and then the model
        forward engineered to a database, the collation was correctly
        set. If however, the model was then synchronized with the live
        database, MySQL Workbench attempted to alter the collations to
        <code class="literal">utf8_general_ci</code>.
       (Bug #38807)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-image-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.6. The Image 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-note-tool.html" title="7.6.1.5. The Text Tool"><link rel="next" href="wb-table-tool.html" title="7.6.1.7. The Table 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-image-tool"></a>7.6.1.6. The Image Tool</h4></div></div></div><p>
        Use the image tool to place an image on the canvas. When this
        tool is selected and you click the canvas, a dialog box opens
        enabling you to select the desired graphic file.
      </p><p>
        To activate the image tool from the keyboard, use the
        <span><strong class="keycap">I</strong></span> key. For more information about images, see
        <a href="wb-images.html" title="7.7.8. Creating Images">Section 7.7.8, “Creating Images”</a>.
      </p></div></body></html>


path: /wb-html-guitools/wb-modifying-layer.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.7.5.2. Modifying a Layer Using the Properties 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-layers.html" title="7.7.5. Creating Layers"><link rel="prev" href="wb-using-layer-tool.html" title="7.7.5.1. Adding Layers to an EER Diagram"><link rel="next" href="wb-notes.html" title="7.7.6. Creating Notes"></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-modifying-layer"></a>7.7.5.2. Modifying a Layer Using the Properties Palette</h4></div></div></div><p>
      When you select a layer on the EER Diagram canvas, its properties
      are displayed in the <code class="literal">Properties</code> palette. The
      properties accessible from the <code class="literal">Properties</code>
      palette apply to the appearance of a layer on the EER Diagram
      canvas.
    </p><p>
      In some circumstances, you may want to make a layer invisible.
      Select the layer and, in the <code class="literal">Properties</code>
      palette, set the <code class="literal">visible</code> property to
      <code class="literal">False</code>. To locate an invisible object, open the
      <code class="literal">Layers</code> palette and select the object by
      double-clicking it. After an object is selected, you can reset the
      <code class="literal">visible</code> property from the
      <code class="literal">Properties</code> palette.
    </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>. In addition to the
      properties listed there, a layer also has a
      <code class="literal">description</code> property. Use this property to
      document the purpose of the layer.
    </p></div></body></html>


