# web_object

path: /wb-html-guitools/license-html-renderer.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>B.12. HtmlRenderer (System.Drawing.Html)</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-gnu-lgpl-2-1.html" title="B.11. GNU Lesser General Public License Version 2.1, February 1999"><link rel="next" href="license-libxml2.html" title="B.13. Libxml2 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-html-renderer"></a>B.12. HtmlRenderer (System.Drawing.Html)</h2></div></div></div><p>
    The following software may be included in this product:
  </p><pre class="programlisting">HtmlRenderer (System.Drawing.Html)

Copyright (c) 2009, José Manuel Menéndez Poo
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 menendezpoo.com 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-forward-engineering.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.7.10. Forward Engineering</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-working-with-models.html" title="7.7. Working with Models"><link rel="prev" href="wb-reverse-engineer-live.html" title="7.7.9.2. Reverse Engineering a Live Database"><link rel="next" href="wb-forward-engineering-sql-scripts.html" title="7.7.10.1. Forward Engineering Using an SQL Script"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-forward-engineering"></a>7.7.10. Forward Engineering</h3></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-forward-engineering-sql-scripts.html">7.7.10.1. Forward Engineering Using an SQL Script</a></span></dt><dt><span class="section"><a href="wb-forward-engineering-live-server.html">7.7.10.2. Forward Engineering to a Live Server</a></span></dt><dt><span class="section"><a href="wb-database-synchronization.html">7.7.10.3. Database Synchronization</a></span></dt><dt><span class="section"><a href="wb-database-diff-report.html">7.7.10.4. Creating a Catalog Diff Report</a></span></dt></dl></div><p>
    It is possible to forward engineer a database using an SQL script or
    by connecting to a live database.
  </p></div></body></html>


path: /wb-html-guitools/wb-using-text-object-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.7.1. Adding Text Objects 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-text-objects.html" title="7.7.7. Creating Text Objects"><link rel="prev" href="wb-text-objects.html" title="7.7.7. Creating Text Objects"><link rel="next" href="wb-text-object-editor.html" title="7.7.7.2. The Text Object 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-text-object-tool"></a>7.7.7.1. Adding Text Objects to an EER Diagram</h4></div></div></div><p>
      To add text objects to an EER Diagram, use the <code class="literal">Text
      Object</code> tool on the vertical toolbar. Make sure that the
      <span class="guilabel">EER Diagram</span> tab is selected, then right-click
      the text object icon on the vertical toolbar. The text object icon
      is the rectangular icon found below the label icon.
    </p><p>
      Clicking the mouse on this icon changes the mouse pointer to a
      text object pointer. You can also change the mouse pointer to a
      text object pointer by pressing the <span><strong class="keycap">N</strong></span> key.

      
    </p><p>
      Choosing the <code class="literal">Text Object</code> tool changes the
      contents of the toolbar that appears immediately below the menu
      bar. When the <code class="literal">Text Object</code> pointer is active,
      this toolbar contains a color chart list. Use this list to select
      the color accent for the new text object. The color of your text
      object can be changed later using the
      <code class="literal">Properties</code> palette.
    </p><p>
      Create a text object by clicking anywhere on the EER Diagram
      canvas. This creates a new text object with the default name
      <code class="literal">text1</code>. To revert to the default mouse pointer,
      click the arrow icon at the top of the vertical toolbar.
    </p><p>
      Right-clicking a text object opens a pop-up menu. These menu
      options are identical to the options for other objects. However,
      since a text object is not a database object, there is no
      confirmation dialog box when you delete a text object.
    </p></div></body></html>


path: /wb-html-guitools/dbdoc-templates.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.12. Customizing DBDoc Model Reporting Templates</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-model-reporting.html" title="7.11. The DBDoc Model Reporting Dialog Window (Commercial Version)"><link rel="next" href="dbdoc-templates-markers.html" title="7.12.1. Supported Template Markers"></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="dbdoc-templates"></a>7.12. Customizing DBDoc Model Reporting Templates</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="dbdoc-templates-markers.html">7.12.1. Supported Template Markers</a></span></dt><dt><span class="section"><a href="dbdoc-templates-custom.html">7.12.2. Creating a Custom Template</a></span></dt></dl></div><p>
    This section provides an overview of creating and modifying DBDoc
    Model Reporting templates, as used by MySQL Workbench.
  </p><p>
    The MySQL Workbench DBDoc Model Reporting system is based on the
    <a href="http://google-ctemplate.googlecode.com/svn/trunk/doc/index.html">Google
    Template System</a>. This discussion does not attempt to explain
    the Google Template System in detail. For a useful overview of how
    the Google Template System works, see the Google document,
    <a href="http://google-ctemplate.googlecode.com/svn/trunk/doc/howto.html">How
    To Use the Google Template System</a>.
  </p><p>
    The templates employed by the DBDoc Model Reporting system are text
    files that contain <em class="firstterm">Markers</em>. These text files
    are processed by the template system built into MySQL Workbench, and the
    markers replaced by actual data. The output files are then
    generated. It is these output files, typically HTML or text, that
    are then viewed by the user.
  </p><p>
    Markers can be of six types:
  </p><div class="itemizedlist"><ul type="disc"><li><p>
        Template Include
      </p></li><li><p>
        Comment
      </p></li><li><p>
        Set delimiter
      </p></li><li><p>
        Pragma
      </p></li><li><p>
        Variable
      </p></li><li><p>
        Section start and Section end
      </p></li></ul></div><p>
    The last two are the most commonly used in MySQL Workbench templates and
    these important markers are briefly described in the following
    sections.
  </p><div class="itemizedlist"><ul type="disc"><li><p>
        <span class="bold"><strong>Variables</strong></span>
      </p><p>
        The use of variables in the templates is straightforward. Any
        variables denoted by markers in the template file are replaced
        by their corresponding data prior to the output file being
        generated. The mapping between variables and their corresponding
        data is stored by MySQL Workbench in what is known as a data
        dictionary. In the data dictionary, the variable name is the
        <span class="emphasis"><em>key</em></span> and the variable's corresponding data
        is the <span class="emphasis"><em>value</em></span>. The data dictionaries are
        built by MySQL Workbench and filled with the data contained in the
        model being processed.
      </p><p>
        By way of example, the following code snippet shows part of a
        template file:
      </p><pre class="programlisting">Total number of Schemata: {{SCHEMA_COUNT}}</pre><p>
        In the generated output file, the variable
        <code class="literal">{{SCHEMA_COUNT}}</code> is replaced by the number of
        schemata in the model:
      </p><pre class="programlisting">Total number of Schemata: 2</pre><p>
        A variable can appear as many times as required in the template
        file.
      </p></li><li><p>
        <span class="bold"><strong>Sections</strong></span>
      </p><p>
        Sections are used to perform iteration in the templates. When
        MySQL Workbench exchanges the variables in a section for data, it
        does so iteratively, using all data in the data dictionary in
        which the variable is defined. MySQL Workbench builds the data
        dictionaries according to the model currently being processed.
      </p><p>
        Consider the following code snippet:
      </p><pre class="programlisting">{{#SCHEMATA}}
Schema: {{SCHEMA_NAME}}
{{/SCHEMATA}}</pre><p>
        In the preceding snippet, the section start and end are
        indicated by the <code class="literal">{{#SCHEMATA}}</code> and
        <code class="literal">{{/SCHEMATA}}</code> markers. When MySQL Workbench
        processes the template, it notes the section and iterates it
        until the variable data for <code class="literal">{{SCHEMA_NAME}}</code>
        in the corresponding data dictionary is exhausted. For example,
        if the model being processed contains two schemata, the output
        for the section might resemble the following:
      </p><pre class="programlisting">Schema: Airlines
Schema: Airports</pre></li></ul></div><p>
    <span class="bold"><strong>Data Dictionaries</strong></span>
  </p><p>
    It is important to understand the relationship between sections and
    data dictionaries in more detail. In a data dictionary the
    <span class="emphasis"><em>key</em></span> for a variable is the variable name, a
    marker. The variable <span class="emphasis"><em>value</em></span> is the variable's
    data. The entry for a section in a data dictionary is different. For
    a section entry in a data dictionary, the key is the section name,
    the marker. However, the value associated with the key is a list of
    data dictionaries. In MySQL Workbench each section is usually associated
    with a data dictionary. You can think of a section as
    <span class="emphasis"><em>activating</em></span> its associated dictionary (or
    dictionaries).
  </p><p>
    When a template is processed, data dictionaries are loaded in a
    hierarchical pattern, forming a tree of data dictionaries. This is
    illustrated by the following table.
  </p><div class="table"><a name="dbdoc-templates-dictionary-tree"></a><p class="title"><b>Table 7.1. Data Dictionaries Tree</b></p><table summary="Data Dictionaries Tree" border="1"><colgroup><col><col></colgroup><thead><tr><th>Data Dictionary</th><th>Loads Data Dictionary</th></tr></thead><tbody><tr><td>MAIN</td><td>SCHEMATA</td></tr><tr><td>SCHEMATA</td><td>TABLES, COLUMNS (Detailed is true), FOREIGN_KEYS (Detailed is true),
            INDICES (Detailed is true)</td></tr><tr><td>TABLES</td><td>REL_LISTING, INDICES_LISTING, COLUMNS_LISTING, TABLE_COMMENT_LISTING,
            DDL_LISTING</td></tr><tr><td>COLUMNS_LISTING</td><td>COLUMNS (Detailed is false)</td></tr><tr><td>REL_LISTING</td><td>REL (Detailed is false)</td></tr><tr><td>INDICES_LISTING</td><td>INDICES (Detailed is false)</td></tr></tbody></table></div><p>
    The root of the tree is the <span class="emphasis"><em>main</em></span> dictionary.
    Additional dictionaries are loaded from the root to form the
    dictionary tree.
  </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
      If a template has no sections, any variables used in the template
      are looked up in the main dictionary. If a variable is not found
      in the main dictionary (which can be thought of as associated with
      the default, or main, section), no data is generated in the output
      file for that marker.
    </p></div><p>
    <span class="bold"><strong>Evaluation of variables</strong></span>
  </p><p>
    The tree structure of the data dictionaries is important with
    respect to variable evaluation. As variables are defined in data
    dictionaries, their associated values have meaning only when that
    particular data dictionary is active, and that means when the
    section associated with that data dictionary is active. When a
    variable lookup occurs, the system checks the data dictionary
    associated with the current section. If the variable value can be
    found there, the replacement is made. However, if the variable's
    value is not found in the current data dictionary, the parent data
    dictionary is checked for the variable's value, and so on up the
    tree until the main data dictionary, or root, is reached.
  </p><p>
    Suppose that we want to display the names of all columns in a model.
    Consider the following template as an attempt to achieve this:
  </p><pre class="programlisting">Report
------
Column Name: {{COLUMN_NAME}}</pre><p>
    This template produces no output, even for a model that contains
    many columns. In this example, the only data dictionary active is
    the main dictionary. However, <code class="literal">COLUMN_NAME</code> is
    stored in the <code class="literal">COLUMNS</code> data dictionary, which is
    associated with the <code class="literal">COLUMNS</code> section.
  </p><p>
    With this knowledge, the template can be improved as follows:
  </p><pre class="programlisting">Report
------
{{#COLUMNS}}
Column Name: {{COLUMN_NAME}}
{{/COLUMNS}}</pre><p>
    This still does not produce output. To see why, see
    <a href="dbdoc-templates.html#dbdoc-templates-dictionary-tree" title="Table 7.1. Data Dictionaries Tree">Table 7.1, “Data Dictionaries Tree”</a>. The
    <code class="literal">COLUMNS</code> data dictionary has the parent dictionary
    <code class="literal">COLUMNS_LISTING</code>.
    <code class="literal">COLUMNS_LISTING</code> has the parent
    <code class="literal">TABLES</code>, which has the parent
    <code class="literal">SCHEMATA</code>, whose parent is the main dictionary.
    Remember that for a dictionary to be involved in variable lookup,
    its associated section must currently be active.
  </p><p>
    To achieve the desired output, the template must be something like
    the following:
  </p><pre class="programlisting">Report
------

{{#SCHEMATA}}
{{#TABLES}}
{{#COLUMNS_LISTING}}
{{#COLUMNS}}
Column Name: {{COLUMN_NAME}}
{{/COLUMNS}}
{{/COLUMNS_LISTING}}
{{/TABLES}}
{{/SCHEMATA}}</pre><p>
    The following template is the same, but with explanatory comments
    added:
  </p><pre class="programlisting">Report
------

{{! Main dictionary active}}
{{#SCHEMATA}}  {{! SCHEMATA dictionary active}}
{{#TABLES}}  {{! TABLES dictionary active}}
{{#COLUMNS_LISTING}} {{! COLUMNS_LISTING dictionary active}}
{{#COLUMNS}}  {{! COLUMNS dictionary active}}
Column Name: {{COLUMN_NAME}} {{! COLUMN_NAME variable is looked-up, and found, in COLUMNS data dictionary}}
{{/COLUMNS}}
{{/COLUMNS_LISTING}}
{{/TABLES}}
{{/SCHEMATA}}</pre><p>
    Imagine now that for each column name displayed you also wanted to
    display its corresponding schema name, the template would look like
    this:
  </p><pre class="programlisting">Report
------

{{#SCHEMATA}}
{{#TABLES}}
{{#COLUMNS_LISTING}}
{{#COLUMNS}}
Schema Name: {{SCHEMA_NAME}} Column Name: {{COLUMN_NAME}}
{{/COLUMNS}}
{{/COLUMNS_LISTING}}
{{/TABLES}}
{{/SCHEMATA}}</pre><p>
    When variable lookup is performed for
    <code class="literal">SCHEMA_NAME</code>, the <code class="literal">COLUMNS</code>
    dictionary is checked. As the variable is not found there the parent
    dictionary will be checked, <code class="literal">COLUMNS_LISTING</code>, and
    so on, until the variable is eventually found where it is held, in
    the <code class="literal">SCHEMATA</code> dictionary.
  </p><p>
    If there are multiple schemata in the model, the outer section is
    iterated over a matching number of times, and
    <code class="literal">SCHEMA_NAME</code> accordingly has the correct value on
    each iteration.
  </p><p>
    It's important to always consider which dictionary must be active
    (and which parents) for a variable to be evaluated correctly. The
    following section has a table that helps you identify section
    requirements.
  </p></div></body></html>


path: /wb-html-guitools/wb-preferences.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>5.4. Workbench Preferences</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-size.html" title="5.3. Workbench Application Minimum Window Size"><link rel="next" href="wb-preferences-general.html" title="5.4.1. The General 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-preferences"></a>5.4. Workbench Preferences</h2></div></div></div><div class="toc"><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></div><p>
    The <span class="guimenu">Preferences</span> menu sets MySQL Workbench defaults.
    Choosing this menu item opens the following dialog box.
  </p><div class="figure"><a name="wb-preferences-image"></a><p class="title"><b>Figure 5.2. The <code class="literal">Preferences</code> Dialog Box</b></p><div class="mediaobject"><img src="images/wb-preferences.png" width="700" height="599" alt="The Preferences dialog
        box"></div></div><p>
    The preferences dialog box contains the following tabs:
  </p><div class="itemizedlist"><ul type="disc"><li><p>
        <span class="guimenu">General</span>: Configuration of general-purpose
        options
      </p></li><li><p>
        <span class="guimenu">Administrator</span>: Configuration of tools used by
        the Administrator functionality
      </p></li><li><p>
        <span class="guimenu">SQL Editor</span>: Configuration of the SQL Editor
      </p></li><li><p>
        <span class="guimenu">Model</span>: Default object names
      </p></li><li><p>
        <span class="guimenu">MySQL</span>: Configuration of the default storage
        engine
      </p></li><li><p>
        <span class="guimenu">Diagram</span>: EER diagram settings
      </p></li><li><p>
        <span class="guimenu">Appearance</span>: Change colors and fonts used by
        various Workbench components
      </p></li></ul></div><p>
    A more detailed discussion of these options follows.
  </p></div></body></html>


path: /wb-html-guitools/wb-news-5-1-10.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.2.10. Changes in MySQL Workbench 5.1.10 (10 April 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-11.html" title="A.2.9. Changes in MySQL Workbench 5.1.11 (Not yet released)"><link rel="next" href="wb-news-5-1-9.html" title="A.2.11. Changes in MySQL Workbench 5.1.9 (Not yet released Beta)"></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-10"></a>A.2.10. Changes in MySQL Workbench 5.1.10 (10 April 2009)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.1.9.
      </p><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        It was not possible to edit the cardinality of existing
        relations using the MAC OS X version of MySQL Workbench. Attempting
        to change the cardinality using the radio buttons had no effect.
        For example, it was not possible to change a relation from
        one-to-many to one-to-one.
       (Bug #44043)</p></li><li><p>
        When a nonstandard port was specified in
        <span class="guimenu">Database</span>, <span class="guimenu">Forward
        Engineer...</span>, such as 3307, MySQL Workbench still attempted
        to connect to port 3306.
       (Bug #44014)</p></li><li><p>
        When a foreign key was created, a column was selected in the
        original table, but no column was selected in the foreign table.
        If the project was saved and an attempt was made to reload it,
        this error message was generated:
      </p><pre class="programlisting">Unserializing GRT data - Inserting null value to not null list</pre><p>
        This error prevented MySQL Workbench from opening the project file,
        resulting in all model data being inaccessible.
       (Bug #43997)</p></li><li><p>
        The name of the table displayed on the tab in the Table Editor
        did not update when the table name was changed in the editor.
       (Bug #43960)</p></li><li><p>
        Data entered using the <span class="guilabel">Inserts</span> tab in the
        Table Editor was not displayed in the Inserts tab, but was saved
        to the MWB file when the project was saved. The data could be
        viewed in MySQL Workbench running on platforms other than Mac OS X,
        but the Mac OS X version of MySQL Workbench did not display the data
        entered using the Inserts tab.
       (Bug #43907)</p></li><li><p>
        When a plugin was installed using the <span class="guimenu">Tools</span>,
        <span class="guimenu">Install Plugin/Module File...</span> menu option,
        MySQL Workbench copied the selected plugin and reported:
      </p><pre class="programlisting">'Copied module /Users/tilman/Desktop/SymfonyYmlExport.grt.lua to
'/Users/tilman/Library/Application Support/MySQL/Workbench/modules/SymfonyYmlExport.grt.lua'
Please restart Workbench for the change to take effect.'</pre><p>
        When restarted, MySQL Workbench crashed. MySQL Workbench could only be
        fully restarted by first removing the installed file from the
        modules directory.
       (Bug #43906)</p></li><li><p>
        Soon after MySQL Workbench was launched, error popup dialogs were
        generated with this message:
      </p><pre class="programlisting">"AXDocument" attribute unsupported by &lt;some component&gt;</pre><p>
        This occurred on the Mac OS X version of MySQL Workbench, when a
        third-party usage monitoring utility was running. This error was
        due to the fact that custom exception reporting was disabled by
        default.
       (Bug #43872)</p></li><li><p>
        An attempt to edit a table resulted in this error:
      </p><pre class="programlisting">The plugin db.mysql.editors.mwbplugin does not
  contain the published object DbMysqlTableEditor</pre><p>
        This only happened if the project was opened immediately after
        MySQL Workbench was started.
       (Bug #43863)</p></li><li><p>
        If a MySQL Workbench project file was opened, all tabs closed, and
        then <span class="guimenu">File</span>, <span class="guimenu">New</span> selected,
        MySQL Workbench crashed with this error message:
      </p><pre class="programlisting">Unknown exception caught in c:\users\tax\documents\visual studio 2008\projects\wb
5.1\workbench\backend\windows\wbprivate.wr\src\Wb.h at line 994.</pre><p>(Bug #43850)</p></li><li><p>
        If an attempt was made to use the undo feature after having
        first saved a project, MySQL Workbench crashed.
       (Bug #43849)</p></li><li><p>
        When creating a new 1:n link MySQL Workbench froze.
       (Bug #43812)</p></li><li><p>
        Using the Navigator to zoom in and out of an EER diagram view
        caused MySQL Workbench to crash.
       (Bug #43782)</p></li><li><p>
        The Many-to-Many Table generated by MySQL Workbench was of engine
        type Server Default. It should have been of type
        <code class="literal">InnoDB</code>.
       (Bug #43776)</p></li><li><p>
        On opening a diagram the file tables layout was broken. All
        tables were placed in the top left corner.
      </p><p>
        It appeared that MySQL Workbench stored the diagram layout in the
        MWB file correctly but it was not retrieved correctly on file
        load.
       (Bug #43455)</p></li><li><p>
        In the EER Diagram view, if the Tables folder was expanded in
        the Catalog Palette, and then a table dragged onto the EER
        Diagram, the expanded Tables folder immediately collapsed.
       (Bug #41922)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-news-5-0-17.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.3.14. Changes in MySQL Workbench 5.0.17rc (07 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-18.html" title="A.3.13. Changes in MySQL Workbench 5.0.18rc (not released)"><link rel="next" href="wb-news-5-0-16.html" title="A.3.15. Changes in MySQL Workbench 5.0.16rc (26 March 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-17"></a>A.3.14. Changes in MySQL Workbench 5.0.17rc (07 April 2008)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.0.16rc.
      </p><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        Creating a new view and then deleting it caused a
        <code class="literal">System.AccessViolationException</code>.
       (Bug #35840)</p></li><li><p>
        Editing a stored procedure within Workbench could cause an
        exception.
       (Bug #35828)</p></li><li><p>
        The modified timestamp for an existing model was not correctly
        updated for all changes.
       (Bug #35719)</p></li><li><p>
        Identifiers for field names in DML SQL statements would not be
        quoted correctly, permitting reserved words to be included in
        the SQL statements.
       (Bug #35710)</p></li><li><p>
        Workbench would crash repeatedly when drawing the diagram for a
        table where the referenced column in a foreign key relationship
        was blank.
       (Bug #35677)</p></li><li><p>
        Identifiers using uppercase characters for stored procedures
        would automatically be modified to lowercase.
       (Bug #35650)</p></li><li><p>
        When working with the <span class="guilabel">SQL Script</span> editor, it
        was not possible to select all the text in the display when
        using <span><strong class="keycap">Control+A</strong></span>.
       (Bug #35646)</p></li><li><p>
        The <span class="guilabel">Model Navigation</span> window could not be
        collapsed like other palettes.
       (Bug #35642)</p></li><li><p>
        Modifying the primary key index definition for within the table
        view would not update the entity relationship diagram.
       (Bug #35639)</p></li><li><p>
        When validating an existing model using the Forward Engineer
        Wizard, MySQL-specific validation would fail.
       (Bug #35604)</p></li><li><p>
        Deleting an existing layer on a diagram and then editing other
        objects on the same canvas could generate a number of
        exceptions, and could corrupt the Workbench file.
       (Bug #35603)</p></li><li><p>
        Switching to the Connect to Columns notation with an existing
        model would cause an exception.
       (Bug #35601)</p></li><li><p>
        Data in <code class="literal">BLOG</code> and
        <code class="literal">TEXT</code> columns defined using the
        <span class="guilabel">Inserts</span> tab would not be quoted correctly
        in the resulting SQL.
       (Bug #35525)</p></li><li><p>
        Opening an existing Workbench model with an invalid foreign key
        definition would cause an exception.
       (Bug #35501)</p></li><li><p>
        Moving multiple tables on the same diagram, and then using Undo
        to revert the model to the original layout, only the first table
        selected be returned to its original position.
       (Bug #35465)</p></li><li><p>
        When adding a foreign key relationship within a catalog with an
        existing entity relationship diagram, the foreign key
        relationship is not added to the existing diagram.
       (Bug #35429)</p></li><li><p>
        The precise position of individual connections would not be
        retained when the schema was saved.
       (Bug #35397)</p></li><li><p>
        Opening a GRT shell while the table editor is open would raise
        an exception.
       (Bug #35349)</p></li><li><p>
        When modifying an existing foreign key relationship, the
        generated <code class="literal">ALTER</code> script did not reflect the
        modification.
       (Bug #35265, Bug #35830)</p></li><li><p>
        When creating foreign key relationships that point to more than
        one table, the same foreign key identifier for the same table
        could be created. This would create invalid SQL code for
        creating the table.
       (Bug #35262)</p></li><li><p>
        When importing an existing DB Designer schema, Workbench could
        crash.
       (Bug #35123)</p></li><li><p>
        Setting up indexes in both the index and foreign key list views,
        the mouse pointer would dissappear while the entry box was in
        use.
       (Bug #35062)</p></li><li><p>
        Double-clicking the Catalog title bar undocked the GRT Tree
        window.
       (Bug #34856)</p></li><li><p>
        The font for views and routines was not monospace by default.
       (Bug #34537)</p></li><li><p>
        When using the Forward Engineer Wizard, if an error occurred,
        the dialog showing the error detail would be incomplete, and
        determining the reason for the error would be masked because the
        end of log message would be hidden.
       (Bug #34509)</p></li><li><p>
        When using the <span class="guilabel">Hide Menu Items Not Applicable to this
        Edition</span> option, a simplified version of the
        <span class="guilabel">Find</span> dialog box was not available.
       (Bug #34493)</p></li><li><p>
        Editing the text of the Trigger portion of an existing schemata
        would introduce additional text into the Trigger definition.
       (Bug #34397)</p></li><li><p>
        Creating more than five stored procedures or views in a model
        would cause the dialog box for the operation to move to a
        different layer, making it inaccessible when using the mouse.
       (Bug #34153)</p></li><li><p>
        Selecting <span class="guimenu">Export</span>, <span class="guimenu">Forward Engineer
        ALTER script</span> from the <span class="guimenu">File</span> would
        open a <span class="guilabel">SQL Script Syncrhronization</span> dialog,
        rather than export dialog.
       (Bug #34099)</p></li><li><p>
        When moving more than layer in Model Navigator, only the first
        layer's position would be reflected correctly in the output.
       (Bug #33627)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-news-5-2-9.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.31. Changes in MySQL Workbench 5.2.9 (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-10.html" title="A.1.30. Changes in MySQL Workbench 5.2.10 (01 December 2009)"><link rel="next" href="wb-news-5-2-8.html" title="A.1.32. Changes in MySQL Workbench 5.2.8 (18 November 2009 Beta)"></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-9"></a>A.1.31. Changes in MySQL Workbench 5.2.9 (Internal release only)</h3></div></div></div><p>
        Internal release. This section documents all changes and bug
        fixes applied since the release of 5.2.8.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        If, while editing data in the Inserts Editor, the
        <span><strong class="keycap">ESC</strong></span> key was accidentally pressed, the Inserts
        Editor would close without warning and all data entered to that
        point would be lost.
      </p><p>
        The improved Inserts Editor does not display this
        characteristic. Pressing the <span><strong class="keycap">ESC</strong></span> key will have
        no effect.
       (Bug #48452)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        MySQL Workbench crashed when the <span class="guilabel">Import/Export Server
        Data</span> Action Item on the Home screen was clicked.
       (Bug #49064)</p></li><li><p>
        Clicking the Action Item, <span class="guilabel">Manage Security</span>,
        on the Home screen generated this exception:
      </p><pre class="programlisting">Traceback (most recent call last):
  File "C:\Program Files\MySQL\MySQL Workbench 5.2 OSS/modules\wb_admin_grt.py", line
199, in openSecurityManager
    tab.wait_server_check(4)
  File "C:\Program Files\MySQL\MySQL Workbench 5.2 OSS/modules\wb_admin_grt.py", line 95,
in wait_server_check
    while tab.configuration.last_is_running_check is None and time.time() - t &lt; timeout:
NameError: global name 'tab' is not defined</pre><p>
        Further, if this Action Item was clicked again then MySQL Workbench
        crashed.
       (Bug #49061)</p></li><li><p>
        The Forward Engineer SQL Script failed to generate SQL code when
        the check box <span class="guilabel">Generate INSERT Statements for
        Tables</span> was selected, and the tables contained rows.
       (Bug #49046)</p></li><li><p>
        In the <span class="guilabel">Overview</span> tab of the SQL Editor,
        representing a “<span class="quote">live</span>” view of the database
        currently connected to, if an attempt was made to edit a view,
        the resulting script generated unnecessary, and in fact
        dangerous, <code class="literal">DROP TABLE</code> statements. This had
        the potential side-effect that a table that coincidentally had
        the same name as the view, would be dropped with ensuing data
        loss.
       (Bug #49041)</p></li><li><p>
        In the <span class="guilabel">Configuration</span> tab of the Server
        Administrator screen, if log file configuration changes were
        applied, MySQL Workbench hung if the password request dialog was
        cancelled.
       (Bug #49037)</p></li><li><p>
        The Workbench Configuration editor interface contained a
        backtick character rather than a single apostrophe.
       (Bug #49014)</p></li><li><p>
        In the <span class="guilabel">Advanced</span> tab of the
        <span class="guilabel">Admin</span> screen, the check box <span class="guilabel">SQL
        Mode</span> had an erroneous file chooser button associated
        with it. The button should not have been there.
       (Bug #49012)</p></li><li><p>
        MySQL Workbench did not parse the following entry in the
        <code class="filename">my.ini</code> file correctly:
      </p><pre class="programlisting">default-storage-engine=INNODB</pre><p>
        This resulted in the default storage engine not being detected
        correctly by MySQL Workbench, although this entry was correctly
        recognized by the MySQL server. However, MySQL Workbench did parse
        the following entry correctly, due to the correct capitalization
        being used:
      </p><pre class="programlisting">default-storage-engine=InnoDB</pre><p>(Bug #49007)</p></li><li><p>
        After creating a new Server Instance from the
        <span class="guilabel">Home</span> screen, then clicking the
        <span class="guilabel">Logs</span> tab in the Admin screen, this
        exception was generated:
      </p><pre class="programlisting">Unhandled Exception:  Error executing 'SELECT @@log_output':
Unknown system variable 'log_output';</pre><p>(Bug #49004)</p></li><li><p>
        Clicking the Action Item <span class="guilabel">Manage Security</span> on
        the Home screen resulted in MySQL Workbench crashing.
       (Bug #48990)</p></li><li><p>
        Any <code class="literal">TEXT</code> columns in the Table Editor, or
        <code class="literal">TEXT</code> columns in the SQL Editor results
        tabsheet, were displayed as <code class="literal">BOOLEAN</code> values,
        either 1 or 0.
       (Bug #48982)</p></li><li><p>
        MySQL Workbench crashed on opening a model file. This appeared to be
        due to MySQL Workbench causing corruption in the model file.
       (Bug #48891)</p></li><li><p>
        In the EER Diagram view, the <span class="guibutton">Toggle Grid</span>
        and <span class="guibutton">Align Objects to Grid</span> toolbar buttons
        were not rendered correctly when in the selected state.
       (Bug #48822)</p></li><li><p>
        The Inserts Editor did not display columns of type
        <code class="literal">ENUM</code>.
       (Bug #48288)</p></li><li><p>
        On the <span class="guilabel">Filter Objects</span> page of the
        <span class="guilabel">Forward Engineer SQL Script</span> wizard,
        clicking <span class="guibutton">Show Filter</span>, selecting multiple
        objects from the left panel, and then clicking
        <span class="guibutton">&gt;</span>, would result in only the first of
        the selected objects being moved to the right hand panel.
       (Bug #48116)</p></li><li><p>
        Working through the <span class="guilabel">Synchronize Model with
        Database</span> wizard did not result in the live database
        being updated.
       (Bug #47953)</p></li><li><p>
        Using UTF-8 accented characters in the Stored Routine DDL editor
        caused the DDL parser to raise a syntax error and refuse to save
        the routine.
       (Bug #47730)</p></li><li><p>
        The <span class="guilabel">Forward Engineer SQL Script</span> wizard did
        not generate the export script. On the <span class="guilabel">Review SQL
        Script</span> page of the wizard, the review panel was
        blank. Further, clicking <span class="guibutton">Copy to
        Clipboard</span> generated this exception:
      </p><pre class="programlisting">Unknown Exception caught in c:\documents and settings\mysqldev\my documents\visual
studio 2008\projects\workbench52\backend\windows\wbprivate.wr\src\Wb.h at line 1085.</pre><p>(Bug #47482)</p></li><li><p>
        When using the <span class="guilabel">Forward Engineer SQL Script</span>
        wizard, the script generated for a model containing multiple
        schemata, only included the <code class="literal">CREATE SCHEMA</code>
        statement for the first schema.
       (Bug #47202)</p></li><li><p>
        Running the <span class="guilabel">Forward Engineer an ALTER
        Script</span> wizard resulted in an ALTER script that
        dictated changes were required to tables, even in the case where
        no such changes were necessary.
       (Bug #47063)</p></li><li><p>
        Attempting to use <span class="guimenu">Database</span>, <span class="guimenu">Generate
        Catalog Diff Report</span> resulted in a Segmentation Fault.
       (Bug #46810)</p></li><li><p>
        The <span class="guilabel">Forward Engineer SQL Script</span> wizard did
        not generate correct delimiter syntax for routines. For example,
        it generated this code:
      </p><pre class="programlisting">DELIMITER //
//

CREATE PROCEDURE `sakila`.`film_not_in_stock`(IN p_film_id INT, IN p_store_id INT, OUT
p_film_count INT)

READS SQL DATA
BEGIN
     SELECT inventory_id
     FROM inventory
     WHERE film_id = p_film_id
     AND store_id = p_store_id
     AND NOT inventory_in_stock(inventory_id);
     SELECT FOUND_ROWS() INTO p_film_count;
END //
//</pre><p>
        This resulted in errors when an attempt was made to run the
        generated script on MySQL Server.
       (Bug #46505)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-database-synchronization.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.3. Database Synchronization</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-live-server.html" title="7.7.10.2. Forward Engineering to a Live Server"><link rel="next" href="wb-database-diff-report.html" title="7.7.10.4. Creating a Catalog Diff Report"></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-synchronization"></a>7.7.10.3. Database Synchronization</h4></div></div></div><p>
      It is possible to synchronize a model in MySQL Workbench with a live
      database. By default, the synchronization process will change the
      live database to be the same as the model, but this is
      configurable during the synchronization process.
    </p><p>
      MySQL Workbench enables control over the direction of synchronization,
      and which objects to synchronize, in a completely flexible way.
      You can choose to synchronize only certain tables, enable
      synchronization to the live database only, enable synchronization
      from the live database to the model only, or a combination of
      directions. In effect you have complete control as to whether the
      synchronization is unidirectional or bidirectional, and which
      objects exactly are subject to synchronization. This is all
      controlled in the <span class="guilabel">Select Changes to Apply</span>
      page of the synchronization wizard.
    </p><div class="figure"><a name="wb-database-synchronize-wizard-diff"></a><p class="title"><b>Figure 7.34. Model and Database Differences</b></p><div class="mediaobject"><img src="images/wb-database-synchronize-wizard-diff.png" width="800" height="600" alt="Model and Database Differences"></div></div><p>
      In the preceding example, the live database consists of
      <code class="literal">table1</code>, <code class="literal">table2</code> and
      <code class="literal">table3</code>. In MySQL Workbench an additional table,
      <code class="literal">table4</code>, has been created, along with a
      relationship between it and <code class="literal">table3</code>. Further,
      <code class="literal">table5</code> exists in the live database, but not in
      the model. The actions that are configured to occur would result
      in <code class="literal">table3</code> being altered (to include the
      relationship with <code class="literal">table4</code>),
      <code class="literal">table4</code> being created and
      <code class="literal">table5</code> being dropped, in the live database. It
      is possible to reconfigure this, though.
    </p><p>
      The next example shows how the direction of synchronization can be
      changed.
    </p><div class="figure"><a name="wb-database-synchronize-wizard-diff-direction"></a><p class="title"><b>Figure 7.35. Controlling Synchronization Direction</b></p><div class="mediaobject"><img src="images/wb-database-synchronize-wizard-diff-direction.png" width="800" height="600" alt="Controlling Synchronization
          Direction"></div></div><p>
      In this case, the synchronization direction has been changed so
      that rather than the default action of <code class="literal">table5</code>
      being dropped from the live database, it will be incorporated into
      the MySQL Workbench model.
    </p><p>
      For convenience, the wizard provides three additional buttons to
      enable synchronization directions to be applied to a group of
      selected changes. The <span class="guibutton">Update Model</span> button
      causes the selected changes to be applied only to the model
      itself. In the following example, <code class="literal">table7</code> would
      be added to the model.
    </p><div class="figure"><a name="wb-database-synchronize-wizard-diff-direction-model"></a><p class="title"><b>Figure 7.36. Update Model Button</b></p><div class="mediaobject"><img src="images/wb-database-synchronize-wizard-diff-direction-model.png" width="1202" height="707" alt="Update Model Button"></div></div><p>
      The <span class="guibutton">Ignore</span> button causes the selected
      changes to be ignored. No synchronization will take place for
      those changes. In the following example, no changes would take
      place.
    </p><div class="figure"><a name="wb-database-synchronize-wizard-diff-direction-ignore"></a><p class="title"><b>Figure 7.37. Ignore Button</b></p><div class="mediaobject"><img src="images/wb-database-synchronize-wizard-diff-direction-ignore.png" width="1202" height="707" alt="Ignore Button"></div></div><p>
      The <span class="guibutton">Update Source</span> button causes the
      selected changes to be applied only to the live database. In the
      following example, <code class="literal">table6</code> would be added to the
      live database and <code class="literal">table7</code> would be dropped from
      the live database.
    </p><div class="figure"><a name="wb-database-synchronize-wizard-diff-direction-source"></a><p class="title"><b>Figure 7.38. Update Source Button</b></p><div class="mediaobject"><img src="images/wb-database-synchronize-wizard-diff-direction-source.png" width="800" height="600" alt="Update Source Button"></div></div><p>
      It is also possible to control individual changes by clicking the
      arrows. Clicking an arrow causes it to change between the three
      available synchronization directions: from model to source, from
      source to model, or bidirectionally. In the following example,
      <code class="literal">table6</code> will be created in the live database,
      and <code class="literal">table7</code> will be created in the model.
    </p><div class="figure"><a name="wb-database-synchronize-wizard-diff-direction-arrow"></a><p class="title"><b>Figure 7.39. Click Arrows to Change Direction of Synchronization</b></p><div class="mediaobject"><img src="images/wb-database-synchronize-wizard-diff-direction-arrow.png" width="800" height="600" alt="Click Arrows to Change Direction of
          Synchronization"></div></div></div></body></html>


path: /wb-html-guitools/wb-news-5-2-6.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.34. Changes in MySQL Workbench 5.2.6 (21 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-7.html" title="A.1.33. Changes in MySQL Workbench 5.2.7 (Internal release only)"><link rel="next" href="wb-news-5-2-5.html" title="A.1.35. Changes in MySQL Workbench 5.2.5 (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-6"></a>A.1.34. Changes in MySQL Workbench 5.2.6 (21 October 2009)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.2.5.
      </p><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        If a foreign key relationship was altered to point to a column
        in a different table, the foreign key was updated correctly but
        the EER diagram was not redrawn to reflect the new relationship.
       (Bug #47807)</p></li><li><p>
        After using the <span class="guilabel">Forward Engineer to
        Database</span> wizard, MySQL Workbench would crash if an
        attempt was subsequently made to exit the application.
       (Bug #47276)</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></ul></div></div></body></html>


path: /wb-html-guitools/wb-preferences-appearance.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>5.4.7. The Appearance 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-diagram.html" title="5.4.6. The Diagram Tab"><link rel="next" href="wb-sql-development.html" title="Chapter 6. SQL Development"></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-appearance"></a>5.4.7. The Appearance Tab</h3></div></div></div><p>
      Use this tab to set the available colors for the objects that
      appear on an EER diagram canvas. You can also add colors if you
      wish.
    </p><p>
      Changes made here affect the list of colors that appears on the
      toolbar when adding objects to an EER diagram canvas. For
      information about using this list, see
      <a href="wb-tool-specific-toolbar-items.html" title="7.5.2.1. Tool-Specific Toolbar Items">Section 7.5.2.1, “Tool-Specific Toolbar Items”</a>.
    </p><p>
      You can also use this tab to set the font face, size, and style
      for the following items:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          Editor
        </p></li><li><p>
          Layer Title
        </p></li><li><p>
          Text Figure Text
        </p></li><li><p>
          Text Figure Title
        </p></li><li><p>
          Connection Caption
        </p></li><li><p>
          Routine Group Figure Item
        </p></li><li><p>
          Routine Group Figure Title
        </p></li><li><p>
          Table Figure Items
        </p></li><li><p>
          Table Figure Section
        </p></li><li><p>
          Table Figure Title
        </p></li><li><p>
          View Figure Title
        </p></li></ul></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
        On Windows, the default font for the editor supports only
        <code class="literal">latin-1</code> characters. If you need to use
        characters not supported by the <code class="literal">latin-1</code>
        character set, you must change the font here.
      </p></div></div></body></html>


path: /wb-html-guitools/wb-launching-osx.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>3.3.8. Launching 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-installing-mac.html" title="3.3.7. Installing MySQL Workbench on Mac OS X"><link rel="next" href="wb-mac-uninstalling.html" title="3.3.9. Uninstalling MySQL Workbench on Mac OS X"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-launching-osx"></a>3.3.8. Launching MySQL Workbench on Mac OS X</h3></div></div></div><p>
        To launch MySQL Workbench on Mac OS X, open the Applications folder
        in the Finder, then double-click MySQL Workbench.
      </p><p>
        It is also possible to start MySQL Workbench from the command line:
      </p><pre class="programlisting">shell&gt; <strong class="userinput"><code>open MySQLWorkbench.app <em class="replaceable"><code>model_file</code></em></code></strong>
</pre><p>
        A model file must be specified.
      </p></div></body></html>


path: /wb-html-guitools/wb-image-editor.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.7.8.2. The Image 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-images.html" title="7.7.8. Creating Images"><link rel="prev" href="wb-using-image-tool.html" title="7.7.8.1. Adding Images to an EER Diagram"><link rel="next" href="wb-reverse-engineering.html" title="7.7.9. Reverse Engineering"></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-editor"></a>7.7.8.2. The Image Editor</h4></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-image-editor.html#wb-images-image-tab">7.7.8.2.1. The Image Tab</a></span></dt></dl></div><p>
      To invoke the image editor, double-click an image object on an EER
      Diagram canvas. This opens the image editor docked at the bottom
      of the application. Double-clicking the image editor tab undocks
      the editor. Double-click the title bar to redock it. Any number of
      images may be open at the same time. Each additional image appears
      as a tab at the top of the image editor.
    </p><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="wb-images-image-tab"></a>7.7.8.2.1. The Image Tab</h5></div></div></div><p>
        Use the <span class="guilabel">Image</span> tab of the image editor to
        perform the following tasks:
      </p><div class="itemizedlist"><ul type="disc"><li><p>
            Rename the image using the <span class="guilabel">Name</span> text
            box.
          </p></li><li><p>
            Browse for an image using the <span class="guibutton">Browse</span>
            button.
          </p></li></ul></div></div></div></body></html>


path: /wb-html-guitools/wb-news-5-2-34.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.4. Changes in MySQL Workbench 5.2.34 (26 May 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-35.html" title="A.1.3. Changes in MySQL Workbench 5.2.35 (23 September 2011)"><link rel="next" href="wb-news-5-2-33b.html" title="A.1.5. Changes in MySQL Workbench 5.2.33b (21 March 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-34"></a>A.1.4. Changes in MySQL Workbench 5.2.34 (26 May 2011)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.2.33.
      </p><p>
        This release changed the version of Python version in
        MySQL Workbench to 2.7. However, this produces a problem when
        upgrading from 5.2.33. The reason is that the installer leaves
        all the compiled python files (<code class="filename">*.pyc</code>) in
        the installation folder. The next time MySQL Workbench loads, you
        cannot get beyond the splash screen.
      </p><p>
        As a workaround, uninstall MySQL Workbench before you install
        5.2.34. (This will not do anything to your stored connections,
        starters, settings, and so forth.) Make sure that all compiled
        python files (<code class="filename">*.pyc</code>) have been removed from
        the installation folder after uninstallation is finished, before
        you install 5.2.34.
      </p><p>
        This problem was first encountered on Windows using the MSI
        package, but might also affect the Zip package or even other
        platforms. In any case, remove the old files before installing
        5.2.34.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        Canceling a query used to work by dropping the connection. Now
        only the query itself is canceled.
       (Bug #12394153)</p></li><li><p>
        MySQL Workbench now writes the <code class="filename">wb.log</code> file in
        the <code class="filename">.mysql/workbench</code> directory rather than
        in <code class="filename">~</code> (your home directory).
       (Bug #60930, Bug #12548457)</p></li><li><p>
        The <code class="literal">Check for updates...</code> menu item that was
        removed several releases ago has been restored.
       (Bug #60488, Bug #11879029)</p></li><li><p>
        On Windows, it is possible to open multiple models, but it was
        not clear that enabling this preference requires a MySQL Workbench
        restart. The check box tooltip now indicates this.
       (Bug #59400, Bug #11766312)</p></li><li><p>
        In diagram mode, display of triggers for tables was re-enabled.
       (Bug #57956, Bug #11765044)</p></li><li><p>
        A Check for Updates feature was added.
       (Bug #56612, Bug #11763846)</p></li><li><p>
        If a column value is too long to display, an ellipsis (...) is
        displayed at the end to indicate that there is more data.
       (Bug #55976, Bug #11763283)</p></li><li><p>
        If MySQL Workbench finds that .NET is not installed, it now provides
        a link for the user to get the .NET instaler.
       (Bug #55145, Bug #11762538)</p></li><li><p>
        MySQL Workbench now shows query execution time and query warnings.
       (Bug #51199, Bug #11758933, Bug #58333, Bug #11765373)</p></li><li><p>
        The SQL Editor can now wrap long text lines. This is
        controllable per editor instance using its context menu. By
        default, line wrapping is off.
       (Bug #50569, Bug #11758372)</p></li><li><p>
        Toggle Page Guides is no longer available.
       (Bug #49927, Bug #11757824)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        On Ubuntu Linux 11.04+, part of the main MySQL Workbench menu would
        be hidden when utilizing the Ubuntu Unity display handler.
        Therefore, the Unity style menus have been disabled.
       (Bug #61256, Bug #12581792)</p></li><li><p>
        File import operations failed with these errors:
      </p><pre class="programlisting">Error executing task: 'module' object has no attribute
'STARTF_USESHOWWINDOW' 
Error executing task local variable 'p1' referenced before
assignment </pre><p>(Bug #60982, Bug #12430815)</p></li><li><p>
        Executing an SQL script using the scripting shell is not
        supported, but attempts to do so resulted in a MySQL Workbench crash
        rather than an error.
       (Bug #60977, Bug #12402780)</p></li><li><p>
        MySQL Workbench could crash while applying an SQL script to a
        database.
       (Bug #60966, Bug #12608789)</p></li><li><p>
        Refreshing the Object Browser collapsed the browser tree.
       (Bug #60887, Bug #12366813)</p></li><li><p>
        Multiple <code class="literal">USE</code> statements to change
        databases in the SQL Editor caused MySQL Workbench to crash.
       (Bug #60856, Bug #12358480)</p></li><li><p>
        MySQL Workbench could not view the server logs if the server was
        configured with log output set to
        <code class="literal">'TABLE,FILE'</code>.
       (Bug #60853, Bug #12365454)</p></li><li><p>
        Some color schemes made options difficult to read.
       (Bug #60826, Bug #12368221)</p></li><li><p>
        In the Python workbench shell, files with a nonsupported
        execution generated a warning and could not be run.
       (Bug #60815, Bug #12561562)</p></li><li><p>
        <code class="literal">Find</code> did not work in Query tabs.
       (Bug #60787, Bug #12347063)</p></li><li><p>
        Changing connection parameters in Synchronize Model resulted in
        an error message.
       (Bug #60771, Bug #12329285)</p></li><li><p>
        For import and export command operations using a Unix socket
        file, MySQL Workbench added an incorrect <code class="option">--pipe</code>
        option to the command.
       (Bug #60756, Bug #12325422)</p></li><li><p>
        <span class="guilabel">Forward Engineer SQL Script</span> wizard wrote
        incomplete output.
       (Bug #60751, Bug #12329302)</p></li><li><p>
        These query beautifier problems were corrected:
      </p><div class="itemizedlist"><ul type="circle"><li><p>
            Queries containing table aliases were mishandled.
          </p></li><li><p>
            Spaces between table names and table aliases were
            incorrectly removed.
          </p></li></ul></div><p>(Bug #60742, Bug #11883490, Bug #12327013)</p></li><li><p>
        If a conection name contained a <code class="literal">':'</code>
        character, it did not work.
       (Bug #60700, Bug #12325493)</p></li><li><p>
        When a schema was dropped in the Object Browser view using the
        context menu, the view was not refreshed properly.
       (Bug #60688, Bug #11933806)</p></li><li><p>
        New server instances were not always displayed in the Server
        Adminstration list.
       (Bug #60684, Bug #11933087)</p></li><li><p>
        MySQL Workbench crashed if it was unable to locate a required DLL
        due to security blocking. Now it displays instructions to the
        user how to perform unblocking.
       (Bug #60658, Bug #12545324)</p></li><li><p>
        On Linux, MySQL Workbench was overly aggressive about reading schema
        information from <code class="literal">INFORMATION_SCHEMA</code>, leading
        to slowdowns when connecting to the MySQL server. Now
        information is read only for the default schema.
       (Bug #60644, Bug #11926793)</p></li><li><p>
        Several crashes occurred under KDE with certain GTK+ themes.
       (Bug #60640, Bug #11926917)</p></li><li><p>
        Fixed a possible crash when selecting <span class="guimenu">File</span>,
        <span class="guimenu">Export</span>, <span class="guimenu">Forward Engineer SQL CREATE
        Script</span>, and followed by the browse button.
       (Bug #60626, Bug #12617320)</p></li><li><p>
        MySQL Workbench did not assign a correct tab name when opening an
        SQL script from the recent file list menu.
       (Bug #60610, Bug #11926855)</p></li><li><p>
        <span><strong class="keycap">Control+S</strong></span> did not save models or SQL Editor
        scripts. When opening an SQL script, it did not display the file
        name.
       (Bug #60594, Bug #12402774)</p></li><li><p>
        MySQL Workbench could crash trying to display result sets that
        contained binary data.
       (Bug #60588, Bug #12385959)</p></li><li><p>
        The SQL statement generated by clicking an item in the action
        pane failed to include the qualifying database name.
       (Bug #60562, Bug #11926864)</p></li><li><p>
        The <span class="guilabel">Administrator</span> panel would not load for
        large process ID values of the MySQL server.
       (Bug #60505, Bug #12397312)</p></li><li><p>
        MySQL Workbench crashed trying to execute some
        <code class="literal">CREATE TABLE</code> statements.
       (Bug #60475, Bug #12356405)</p></li><li><p>
        Clicking a user name to obtain details caused MySQL Workbench to
        crash if the name contained an apostrope.
       (Bug #60473, Bug #11889207)</p></li><li><p>
        Query results could not be saved to a directory for which the
        name contained Japanese characters.
       (Bug #60438)</p></li><li><p>
        Exporting query results after entering a file path name did not
        work.
       (Bug #60438, Bug #11868335)</p></li><li><p>
        MySQL Workbench tries to determine whether it can use Aero, but did
        not correctly check the platform. On Windows Server 2003, a call
        was made to a non-existing DLL, causing a .NET crash.
       (Bug #60412, Bug #11872360)</p></li><li><p>
        Multiple-selection copy did not work.
       (Bug #60410, Bug #11865601)</p></li><li><p>
        MySQL Workbench failed to compile on Gentoo Linux.
       (Bug #60358, Bug #12368202)</p></li><li><p>
        Stored procedures could not be opened from the objects tree if
        the SQL Delimiter had been changed to the <code class="literal">';'</code>
        character. Now the label for this option in the
        <code class="literal">Preferences</code> dialog has been changed to
        <code class="literal">Non Standard SQL Delimiter</code> to better reflect
        its actual meaning. The tooltip has also been changed to be more
        descriptive. In addition, if an <code class="literal">Alter
        &lt;object&gt;...</code> operation fails due to a parse
        error, the retrieved DDL code is shown as is in the SQL editor.
       (Bug #60354, Bug #11889184)</p></li><li><p>
        Attempting to connect to a nonexistent server put MySQL Workbench in
        a nonresponsive state.
       (Bug #60329, Bug #11834154)</p></li><li><p>
        Record set export to a file failed unless the file name was
        given as an absolute path name.
       (Bug #60256, Bug #11874435)</p></li><li><p>
        Output from the routine editor added excessive blank lines
        between routine definitions.
       (Bug #60205, Bug #11874345)</p></li><li><p>
        When database connections had process IDs with large values, the
        connection tab displayed an error box rather than process
        information.
       (Bug #60192, Bug #12397794)</p></li><li><p>
        MySQL Workbench lost the connection to the server for long-running
        queries (more than 600 seconds).
       (Bug #60103, Bug #11766876)</p></li><li><p>
        MySQL Workbench sometimes looked for <code class="filename">my.ini</code> in
        the wrong directory.
       (Bug #60076, Bug #11766855)</p></li><li><p>
        Some MWB files created in MySQL Workbench 5.1 could not be loaded in
        5.2.
       (Bug #59862, Bug #11766695)</p></li><li><p>
        Items from the SQL Editor history were not always available to
        be copied into the SQL script.
       (Bug #59807, Bug #1766651)</p></li><li><p>
        Exporting a record set to a file resulted in invalid
        <code class="literal">INSERT</code> statements if the table
        contained a column named <code class="literal">key</code> because the
        column name was not quoted properly.
       (Bug #59787, Bug #11766638)</p></li><li><p>
        It was not possible to import a dump if MySQL Workbench was
        installed in a directory having a name that contained spaces.
       (Bug #59737, Bug #11766595)</p></li><li><p>
        <span><strong class="keycap">Control+Z</strong></span> in the Model Editor did not always
        refresh the screen correctly.
       (Bug #59661, Bug #11766531)</p></li><li><p>
        Selecting the Create Multiple Tables menu item resulted in an
        error.
       (Bug #59586, Bug #11766473)</p></li><li><p>
        Create EER Model from SQL Script reported a syntax error when
        importing legal SQL scripts.
       (Bug #59577, Bug #11766464)</p></li><li><p>
        A problem running MySQL Utilities under the KDE console was
        fixed.
       (Bug #59427, Bug #12430837)</p></li><li><p>
        After using the column headers of the User Accounts list to sort
        the accounts by User or From Host, then selecting various
        accounts in turn, the selected accounts often did not match the
        account being diplayed in the corresponding Login,
        Administrative Roles, or Account Limits tabs.
       (Bug #59391, Bug #11766304)</p></li><li><p>
        Clicking the Manage Security link in the MySQL Workbench Home
        screen opened the Admin screen in the
        <span class="guilabel">Startup</span> tab rather than the
        <span class="guilabel">Accounts</span> tab and produced an error.
       (Bug #59389, Bug #11766302)</p></li><li><p>
        The description given in the <span class="guilabel">Workbench
        Preferences</span> dialog for the
        <code class="option">--safe-updates</code> option was incorrect.
       (Bug #59370, Bug #11766289)</p></li><li><p>
        Connection sorting was lost after a status refresh.
       (Bug #59355, Bug #11766279)</p></li><li><p>
        MySQL Workbench displayed superfluous error messages after the user
        interrupted a query.
       (Bug #59323, Bug #11766255)</p></li><li><p>
        A <code class="literal">SHOW WARNINGS</code> query would return zero
        results, even when warnings existed.
       (Bug #59221, Bug #11766174)</p></li><li><p>
        The Users column in the <span class="guilabel">Schema Privileges</span>
        tab was not sortable.
       (Bug #59138, Bug #11766100)</p></li><li><p>
        On Windows, opening a second instance of MySQL Workbench resulted in
        an error.
       (Bug #59128, Bug #11766090)</p></li><li><p>
        When the user closed the main window with a connection active,
        MySQL Workbench did not terminate the connection. This lead to
        <code class="literal">Aborted_clients</code> errors on the
        server side.
       (Bug #58944, Bug #11765929)</p></li><li><p>
        Opening a connection twice resulted in unexpected errors when
        executing queries on the connection.
       (Bug #58835)</p></li><li><p>
        When the SQL statement history file became large enough,
        MySQL Workbench encountered allocation errors attempting to add to
        it.
       (Bug #58778, Bug #12409656)</p></li><li><p>
        When double-clicking tables in a model diagram, tabs were
        mismanaged such that the proper set of tabs did not remain
        available.
       (Bug #57349, Bug #11764509)</p></li><li><p>
        On Mac OS X, <span><strong class="keycap">Option+Delete</strong></span> functioned as Undo
        rather than deleting the word to the left of the cursor.
       (Bug #57184, Bug #11764360)</p></li><li><p>
        A memory leak occurred during diagram manipulation.
       (Bug #55719, Bug #11763054)</p></li><li><p>
        Using the Description Editor to update a table description did
        not update the Comments column of the Model Overview window.
       (Bug #55235, Bug #11762621)</p></li><li><p>
        EER Diagram Catalog Tree schema folders did not stay collapsed
        when moving tables from a schema to the Diagram.
       (Bug #55088, Bug #11762487)</p></li><li><p>
        Actions that should open a web page did not work.
       (Bug #54827, Bug #11762254)</p></li><li><p>
        With a large table displayed in the SQL Editor object browser,
        keyboard shortcuts for the table information display were not
        working, and the information was not formatted properly.
       (Bug #54191, Bug #11761676)</p></li><li><p>
        On Mac OS X, two-finger scrolling did not work in query windows.
       (Bug #53678, Bug #11761211)</p></li><li><p>
        The <code class="literal">TRIGGER</code> privilege could not
        be assigned at the schema level.
       (Bug #52977, Bug #11760556)</p></li><li><p>
        It was not possible to view or edit long text lines with the
        inline editor.
       (Bug #52087, Bug #11759751)</p></li><li><p>
        After loading a model, zoom levels saved with bookmarks were not
        always used correctly.
       (Bug #50816, Bug #11758594)</p></li><li><p>
        The live schema tree did not update properly to reflect
        modifications to schema objects.
       (Bug #50424, Bug #11758248)</p></li><li><p>
        On Mac OS X, the <span><strong class="keycap">Shift+Alt</strong></span> +
        <span><strong class="keycap">Arrow</strong></span> combination selected individual
        characters instead of words.
       (Bug #50085, Bug #11757963)</p></li><li><p>
        On Windows, a packaging error for the Zip file distribution led
        to spurious GRT Shell warnings at MySQL Workbench startup.
       (Bug #49813, Bug #11757719)</p></li><li><p>
        For data browsing, the Fetch All option sometimes disappeared.
       (Bug #49403, Bug #11757365)</p></li><li><p>
        For SQL Editor tabs where the connection had no name, connection
        information was not shown. Now MySQL Workbench displays the host
        name (up to 21 characters).
       (Bug #49058, Bug #11757060)</p></li><li><p>
        Opening a connection from the list of recently used connections
        caused the user interface to become unresponsive while wanting
        for the connection to open. Now a “<span class="quote">Connecting, please
        wait</span>” message appears and there is a
        <code class="literal">Cancel</code> button to enable the connection
        request to be canceled.
       (Bug #48912, Bug #11756924)</p></li><li><p>
        Dragging tables from the catalog to an EER diagram failed.
       (Bug #47028, Bug #11755277)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-preferences-general.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>5.4.1. The General 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.html" title="5.4. Workbench Preferences"><link rel="next" href="wb-preferences-administrator.html" title="5.4.2. The Administrator 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-general"></a>5.4.1. The General Tab</h3></div></div></div><p>
      The General tab enables you to set the following options:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <span class="bold"><strong>Automatically Reopen Previous Model When
          Started</strong></span>: Check this if you want the model on which
          you previously worked to be automatically reopened when you
          start MySQL Workbench.
        </p></li><li><p>
          <span class="bold"><strong>Place Sidebar on the Right
          Side</strong></span>: By default, the Sidebar is placed on the
          left-hand side of the MySQL Workbench application. Select this
          option to place it on the right-hand side.
        </p></li><li><p>
          <span class="bold"><strong>Force use of software rendering for EER
          diagrams</strong></span>: MySQL Workbench will use OpenGL for rendering
          when available. However, due to faulty drivers, problems do
          occasionally occur. These issues can be resolved by selecting
          the software rendering option here.
        </p></li><li><p>
          <span class="bold"><strong>Undo History Size</strong></span>: You can
          limit the size of the undo history here. Set this value to 0
          to have an unlimited undo history.
        </p></li><li><p>
          <span class="bold"><strong>Auto-save model interval</strong></span>: An
          open model that has not been saved will automatically be saved
          after this period. On loading a model file, MySQL Workbench will
          notify the user if the file was not previously saved
          correctly, due to a crash or power failure. MySQL Workbench can
          then attempt to recover the last auto-saved version. For
          automatic recovery to be available for a new file, it will
          have to have been saved at least once by the user.
        </p></li><li><p>
          <span class="bold"><strong>Interactive GRT Shell
          Language</strong></span>: You can select the language to be used in
          the GRT (Generic RunTime) shell by chosing a language from the
          list <span class="guilabel">Interactive GRT Shell Language</span>.
          Currently, the choices are Lua and Python. Python is the
          recommended option.
        </p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-sql-editor-snippets-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.4. Snippets 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-history-tabsheet.html" title="6.7.4.3. History Tabsheet"><link rel="next" href="wb-sql-editor-results-tabsheets.html" title="6.7.4.5. Results 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-snippets-tabsheet"></a>6.7.4.4. Snippets Tabsheet</h4></div></div></div><p>
          When you enter SQL code into the SQL Query area, you can use
          the Save SQL to Snippets List toolbar button to save your SQL
          code. You will be asked to specify a name. These named
          snippets can be viewed from the SQL Snippets Tab. To load any
          SQL snippet into the SQL Query area, double-click the desired
          snippet in the Snippets Palette.
        </p><div class="figure"><a name="wb-sql-editor-snippets-screenshot"></a><p class="title"><b>Figure 6.9. SQL Editor - Snippets Palette</b></p><div class="mediaobject"><img src="images/wb-sql-editor-snippets-screenshot.png" width="797" height="378" alt="SQL Editor - Snippets Palette"></div></div></div></body></html>


path: /wb-html-guitools/wb-scripting-shell-window.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>9.5.2. The Shell 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="wb-scripting-shell.html" title="9.5. The Workbench Scripting Shell"><link rel="prev" href="wb-exploring-scripting-shell.html" title="9.5.1. Exploring the Workbench Scripting Shell"><link rel="next" href="wb-scripting-modules-palettes.html" title="9.5.3. The Globals, Classes, and Modules Tabs"></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-scripting-shell-window"></a>9.5.2. The Shell Window</h3></div></div></div><p>
        The Workbench Scripting Shell is primarily used for running Lua or Python scripts
        or typing commands in these languages directly. However, you can
        also use it to access the Workbench Scripting Shell Scripting Library functions and
        global functions and objects. To see the available commands,
        type “<span class="quote"><code class="literal">?</code></span>”. You can also cut and
        paste text to and from the shell window.
      </p><p>
        While individual commands can be entered into the shell, it is
        also possible to run a longer script, stored in an external
        file, using the main menu item <span class="guimenu">Scripting</span>,
        <span class="guimenuitem">Run Workbench Script File</span>. When
        scripts are run outside of the shell, to see the output use the
        main menu item <span class="guimenu">View</span>,
        <span class="guimenuitem">Output</span>.
      </p><p>
        It is also possible to run script files directly from the shell.
        For details on running script files, type <span><strong class="command">?
        run</strong></span> at the Workbench Scripting Shell prompt. The following message is
        displayed:
      </p><pre class="programlisting">  Shell Command - shell.run
  -------------------------
  Load and execute a lua script file.

  run filename

  Parameters:
  filename       File that should be loaded and executed.

  Examples:
  run scripts/test.lua
  Runs the script scripts/test.lua.</pre><p>
        Within the Workbench Scripting Shell, on the left side panel, are three tabs:
        <span class="guilabel">Globals</span>, <span class="guilabel">Classes</span>, and
        <span class="guilabel">Modules</span>. Discussion of these additional
        tabs follows.
      </p></div></body></html>


path: /wb-html-guitools/wb-news-5-2-33b.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.5. Changes in MySQL Workbench 5.2.33b (21 March 2011)</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="changes-5.2.x.html" title="A.1. Changes in Release 5.2"><link rel="prev" href="wb-news-5-2-34.html" title="A.1.4. Changes in MySQL Workbench 5.2.34 (26 May 2011)"><link rel="next" href="wb-news-5-2-33.html" title="A.1.6. Changes in MySQL Workbench 5.2.33 (11 March 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-33b"></a>A.1.5. Changes in MySQL Workbench 5.2.33b (21 March 2011)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.2.33.
      </p><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        Creating a relationship broke the model file due to the index
        and foreign key having the same name.
       (Bug #60564, Bug #11926856)</p></li><li><p>
        Attempting to open a saved model produced this error:
      </p><pre class="programlisting">Error unserializing GRT Data.  Expected Type db.mysql.Column, but got 
db.mysql.Table.</pre><p>(Bug #60369, Bug #11840427)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-manage-server-instance-dialog.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>8.6.2. Manage Server Instances Dialog</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-managing-server-instances.html" title="8.6. Creating and Managing Server Instances"><link rel="prev" href="wb-new-server-instance-wizard.html" title="8.6.1. New Server Instance Wizard"><link rel="next" href="wb-server-administration-configuration.html" title="8.7. Server Administration and Configuration"></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-instance-dialog"></a>8.6.2. Manage Server Instances Dialog</h3></div></div></div><p>
        The Manage Server Instances dialog enables you to create,
        delete, and manage server instances. The
        <span class="guilabel">Connection</span> tab of the wizard enables you to
        select a predefined connection to use for connecting to a server
        to be managed. It is also possible to connect to a remote server
        using an SSH connection.
      </p><div class="figure"><a name="wb-manage-server-instances-connections"></a><p class="title"><b>Figure 8.1. Manage Server Instances Dialog</b></p><div class="mediaobject"><img src="images/wb-manage-server-instances-connections.png" width="818" height="698" alt="Manage Server Instances Dialog"></div></div><p>
        The <span class="guilabel">System Profile</span> tab of the wizard
        enables you to specify server-specific information. This is
        achieved primarily through selecting a Profile Template. A
        Profile Template contains standard information used in managing
        the server instance. The following Profile Templates are
        available:
      </p><div class="itemizedlist"><ul type="disc"><li><p>
            Fedora Linux (MySQL Package)
          </p></li><li><p>
            Fedora Linux (Vendor Package)
          </p></li><li><p>
            FreeBSD (MySQL Package)
          </p></li><li><p>
            Generic Linux (MySQL tar package)
          </p></li><li><p>
            Mac OS X (MySQL Package)
          </p></li><li><p>
            OpenSolaris (MySQL Package)
          </p></li><li><p>
            RHEL (MySQL Package)
          </p></li><li><p>
            SLES (MySQL Package)
          </p></li><li><p>
            Ubuntu Linux (MySQL Package)
          </p></li><li><p>
            Ubuntu Linux (Vendor Package)
          </p></li><li><p>
            Windows (MySQL 5.0 Installer Package)
          </p></li><li><p>
            Windows (MySQL 5.1 Installer Package)
          </p></li><li><p>
            Windows (MySQL zip package)
          </p></li><li><p>
            Custom
          </p></li></ul></div><p>
        After you select a profile, a number of default parameters will
        be set, including commands used to start and stop MySQL,
        commands to check server status, and the location of the
        <code class="filename">my.ini</code> or <code class="filename">my.cnf</code>
        configuration file.
      </p><div class="figure"><a name="wb-manage-server-instances-system-profile"></a><p class="title"><b>Figure 8.2. Manage Server Instances Dialog</b></p><div class="mediaobject"><img src="images/wb-manage-server-instances-system-profile.png" width="818" height="698" alt="Manage Server Instances Dialog"></div></div><p>
        After an instance has been created, it can be launched by
        double-clicking its icon in the <span class="guilabel">Server
        Administration</span> panel of the <span class="guilabel">Home</span>
        page. This creates an Admin page, which has two main panels,
        <span class="guilabel">Server Status</span> and
        <span class="guilabel">Configuration</span>. The
        <span class="guilabel">Configuration</span> panel features multiple tabs:
        <span class="guilabel">Startup</span>,
        <span class="guilabel">Configuration</span>,
        <span class="guilabel">Accounts</span>, <span class="guilabel">Connections</span>,
        <span class="guilabel">Variables</span>, <span class="guilabel">Data Dump</span>,
        and <span class="guilabel">Logs</span>.
      </p></div></body></html>


path: /wb-html-guitools/wb-tables.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. Creating Tables</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-working-with-models.html" title="7.7. Working with Models"><link rel="next" href="wb-tables-physical-schemata.html" title="7.7.1.1. Adding Tables to the Physical Schemata"></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-tables"></a>7.7.1. Creating Tables</h3></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-tables-physical-schemata.html">7.7.1.1. Adding Tables to the Physical Schemata</a></span></dt><dt><span class="section"><a href="wb-using-table-tool.html">7.7.1.2. Adding Tables to an EER Diagram</a></span></dt><dt><span class="section"><a href="wb-table-editor.html">7.7.1.3. The MySQL Table Editor</a></span></dt></dl></div></div></body></html>


path: /wb-html-guitools/license-dockpanel.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>B.7. DockPanel Suite 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-libcurl.html" title="B.6. cURL (libcurl) License"><link rel="next" href="license-dojo-toolkit.html" title="B.8. Dojo Toolkit v1.7.0b1 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-dockpanel"></a>B.7. DockPanel Suite License</h2></div></div></div><p>
    The following software may be included in this product:
  </p><pre class="programlisting">DockPanel Suite

The MIT License

Copyright (c) 2007 Weifen Luo (email: weifenluo@yahoo.com)

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.</pre></div></body></html>


path: /wb-html-guitools/wb-preface.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Preface and Legal Notice</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="index.html" title="MySQL Workbench"><link rel="next" href="wb-intro.html" title="Chapter 1. MySQL Workbench Introduction"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="preface" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="wb-preface"></a>Preface and Legal Notice</h2></div></div></div><p>
    This is the User Manual for the MySQL Workbench.
  </p><p>
    For license information, see the <a href="wb-preface.html#legalnotice">Legal
    Notice</a>. This product may contain third-party code. For
    license information on third-party code, see
    <a href="wb-third-party-licenses.html" title="Appendix B. Third Party Licenses">Appendix B, <i>Third Party Licenses</i></a>.
  </p><h2><a name="legalnotice"></a>Legal Notice</h2><p>
    Copyright © 2006, 2011, Oracle and/or its affiliates. All
    rights reserved.
  </p><p>
    This software and related documentation are provided under a license
    agreement containing restrictions on use and disclosure and are
    protected by intellectual property laws. Except as expressly
    permitted in your license agreement or allowed by law, you may not
    use, copy, reproduce, translate, broadcast, modify, license,
    transmit, distribute, exhibit, perform, publish, or display any
    part, in any form, or by any means. Reverse engineering,
    disassembly, or decompilation of this software, unless required by
    law for interoperability, is prohibited.
  </p><p>
    The information contained herein is subject to change without notice
    and is not warranted to be error-free. If you find any errors,
    please report them to us in writing.
  </p><p>
    If this software or related documentation is delivered to the U.S.
    Government or anyone licensing it on behalf of the U.S. Government,
    the following notice is applicable:
  </p><p>
    U.S. GOVERNMENT RIGHTS Programs, software, databases, and related
    documentation and technical data delivered to U.S. Government
    customers are "commercial computer software" or "commercial
    technical data" pursuant to the applicable Federal Acquisition
    Regulation and agency-specific supplemental regulations. As such,
    the use, duplication, disclosure, modification, and adaptation shall
    be subject to the restrictions and license terms set forth in the
    applicable Government contract, and, to the extent applicable by the
    terms of the Government contract, the additional rights set forth in
    FAR 52.227-19, Commercial Computer Software License (December 2007).
    Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
  </p><p>
    This software is developed for general use in a variety of
    information management applications. It is not developed or intended
    for use in any inherently dangerous applications, including
    applications which may create a risk of personal injury. If you use
    this software in dangerous applications, then you shall be
    responsible to take all appropriate fail-safe, backup, redundancy,
    and other measures to ensure the safe use of this software. Oracle
    Corporation and its affiliates disclaim any liability for any
    damages caused by use of this software in dangerous applications.
  </p><p>
    Oracle is a registered trademark of Oracle Corporation and/or its
    affiliates. MySQL is a trademark of Oracle Corporation and/or its
    affiliates, and shall not be used without Oracle's express written
    authorization. Other names may be trademarks of their respective
    owners.
  </p><p>
    This software and documentation may provide access to or information
    on content, products, and services from third parties. Oracle
    Corporation and its affiliates are not responsible for and expressly
    disclaim all warranties of any kind with respect to third-party
    content, products, and services. Oracle Corporation and its
    affiliates will not be responsible for any loss, costs, or damages
    incurred due to your access to or use of third-party content,
    products, or services.
  </p><p>
    This document in any form, software or printed matter, contains
    proprietary information that is the exclusive property of Oracle.
    Your access to and use of this material is subject to the terms and
    conditions of your Oracle Software License and Service Agreement,
    which has been executed and with which you agree to comply. This
    document and information contained herein may not be disclosed,
    copied, reproduced, or distributed to anyone outside Oracle without
    prior written consent of Oracle or as specifically provided below.
    This document is not part of your license agreement nor can it be
    incorporated into any contractual agreement with Oracle or its
    subsidiaries or affiliates.
  </p><p>
    This documentation is NOT distributed under a GPL license. Use of
    this documentation is subject to the following terms:
  </p><p>
    You may create a printed copy of this documentation solely for your
    own personal use. Conversion to other formats is allowed as long as
    the actual content is not altered or edited in any way. You shall
    not publish or distribute this documentation in any form or on any
    media, except if you distribute the documentation in a manner
    similar to how Oracle disseminates it (that is, electronically for
    download on a Web site with the software) or on a CD-ROM or similar
    medium, provided however that the documentation is disseminated
    together with the software on the same medium. Any other use, such
    as any dissemination of printed copies or use of this documentation,
    in whole or in part, in another publication, requires the prior
    written consent from an authorized representative of Oracle. Oracle
    and/or its affiliates reserve any and all rights to this
    documentation not expressly granted above.
  </p><p>
    For more information on the terms of this license, or for details on
    how the MySQL documentation is built and produced, please visit
    <a href="http://dev.mysql.com/contact/">MySQL Contact &amp;
    Questions</a>.
  </p><p>
    For help with using MySQL, please visit either the
    <a href="http://forums.mysql.com">MySQL Forums</a> or
    <a href="http://lists.mysql.com">MySQL Mailing Lists</a>
    where you can discuss your issues with other MySQL users.
  </p><p>
    For additional documentation on MySQL products, including
    translations of the documentation into other languages, and
    downloadable versions in variety of formats, including HTML and PDF
    formats, see the <a href="http://dev.mysql.com/doc">MySQL
    Documentation Library</a>.
  </p></div></body></html>


path: /wb-html-guitools/wb-requirements-hardware.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>3.1. Hardware Requirements</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-installing.html" title="Chapter 3. Installing and Launching MySQL Workbench"><link rel="next" href="wb-requirements-software.html" title="3.2. Software Requirements"></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-requirements-hardware"></a>3.1. Hardware Requirements</h2></div></div></div><p>
      MySQL Workbench requires a system that runs smoothly. The minimum
      hardware requirements are:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          CPU: 32-bit or 64-bit
        </p></li><li><p>
          Cores: Single (Single Core 3GHz or higher, Dual Core 2GHz or
          higher recommended)
        </p></li><li><p>
          RAM: 4 GB (6 GB or higher recommended)
        </p></li><li><p>
          Graphic Accelerators: nVidia or ATI with support of OpenGL 2
          or higher
        </p></li><li><p>
          Display Resolution: 1280×1024 minimum (1920×1200 or higher
          recommended)
        </p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-server-administration-new-server-instance.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>8.2. New Server Instance</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-server-instance.html" title="8.1. Server Administration"><link rel="next" href="wb-server-administration-manage-data-import-export.html" title="8.3. Manage Data Import/Export"></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-new-server-instance"></a>8.2. New Server Instance</h2></div></div></div><p>
      This action item enables you to create a new server instance. A
      server instance is primarily a combination of connection and
      configuration details for a specific server that you wish to
      manage. When you click this item, a wizard is launched that
      enables you to specify the connection and various other
      configuration parameters. After completion of the wizard, a new
      Admin tab is launched, which displays Server Status and
      Configuration.
    </p><p>
      For further details, see
      <a href="wb-new-server-instance-wizard.html" title="8.6.1. New Server Instance Wizard">Section 8.6.1, “New Server Instance Wizard”</a>.
    </p></div></body></html>


path: /wb-html-guitools/wb-sql-development-edit-table-data.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>6.3. Edit Table Data</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-new-connection.html" title="6.2. New Connection"><link rel="next" href="wb-sql-development-edit-sql-script.html" title="6.4. Edit SQL Script"></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-edit-table-data"></a>6.3. Edit Table Data</h2></div></div></div><p>
      Clicking this action item launches the Edit Table Data wizard,
      which enables you to edit table data. This is a two-stage wizard.
      The first stage enables you to select a Stored Connection. The
      second stage enables you to select the Schema and Table you want
      to edit. After the wizard is completed, an SQL Editor tab is
      launched, which displays a data grid that enables you to
      interactively edit table data as required.
    </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-scripting-shell.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>9.5. The Workbench Scripting Shell</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-extending.html" title="Chapter 9. Extending Workbench"><link rel="prev" href="wb-mforms.html" title="9.4. Adding a GUI to a Plugin Using MForms"><link rel="next" href="wb-exploring-scripting-shell.html" title="9.5.1. Exploring the Workbench Scripting Shell"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="wb-scripting-shell"></a>9.5. The Workbench Scripting Shell</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-exploring-scripting-shell.html">9.5.1. Exploring the Workbench Scripting Shell</a></span></dt><dt><span class="section"><a href="wb-scripting-shell-window.html">9.5.2. The Shell Window</a></span></dt><dt><span class="section"><a href="wb-scripting-modules-palettes.html">9.5.3. The Globals, Classes, and Modules Tabs</a></span></dt></dl></div><p>
      The Workbench Scripting Shell provides a means for entering and executing scripts.
      Through the use of the scripting shell, MySQL Workbench can support
      new behavior and data sources using code written in Lua and
      Python. The shell can also be used to explore the current
      Workbench GRT (Generic RunTime) facilities.
    </p><p>
      The scripting shell is not only useful for expanding MySQL Workbench.
      You can use a script file from the scripting shell command line to
      perform repetitive tasks programmatically.
    </p><p>
      The default development language is Lua, a lightweight scripting
      language expressly designed for extending applications. For more
      information about this language, see
      <a href="http://www.lua.org/">lua.org</a>.
    </p><p>
      The Python language is also supported, further details of this
      language can be found from the official
      <a href="http://www.python.org">Python site</a>.
    </p><p>
      The programming language to be used in Workbench Scripting Shell can be selected from
      the General tab of the Workbench Preferences dialog. The Workbench
      Preferences dialog can be displayed using the main menu item
      <span class="guimenu">Edit</span>, <span class="guimenuitem">Preferences</span>.
    </p></div></body></html>


path: /wb-html-guitools/wb-sql-editor-toolbar.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>6.7.2. 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-sql-editor.html" title="6.7. SQL Editor"><link rel="prev" href="wb-sql-editor-main-menu.html" title="6.7.1. Main Menu"><link rel="next" href="wb-sql-editor-query-panel.html" title="6.7.3. SQL Query Panel"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-sql-editor-toolbar"></a>6.7.2. Toolbar</h3></div></div></div><p>
        The toolbar features ten buttons, as shown following.
      </p><div class="figure"><a name="wb-sql-editor-toolbar-screenshot"></a><p class="title"><b>Figure 6.6. SQL Editor - Toolbar</b></p><div class="mediaobject"><img src="images/wb-sql-editor-toolbar-screenshot.png" width="406" height="31" alt="SQL Editor - Toolbar"></div></div><p>
        From left to right, these buttons are:
      </p><div class="itemizedlist"><ul type="disc"><li><p>
            <span class="bold"><strong>Create a New SQL Script
            File</strong></span>: Creates a new SQL Script tab where SQL code
            can be entered.
          </p></li><li><p>
            <span class="bold"><strong>Open a SQL Script File</strong></span>:
            Loads a saved SQL script to be ready for execution. The
            script is displayed in the <span class="guilabel">SQL Query</span>
            area.
          </p></li><li><p>
            <span class="bold"><strong>Save SQL Script to File</strong></span>:
            Saves the currently loaded SQL script to a file specified by
            the user.
          </p></li><li><p>
            <span class="bold"><strong>Save SQL to Snippets List</strong></span>:
            Enables SQL code snippets to be given a name. They will
            appear in the <span class="guilabel">SQL Snippets</span> palette in
            the SQL Editor sidebar.
          </p></li><li><p>
            <span class="bold"><strong>Execute SQL Script in Connected
            Server</strong></span>: Executes the currently loaded SQL script.
            Results are displayed in one or more Results tabs.
          </p></li><li><p>
            <span class="bold"><strong>Execute Current SQL Statement in
            Connected Server</strong></span>: Executes the current SQL
            statement. Results are displayed in one or more Results
            tabs.
          </p></li><li><p>
            <span class="bold"><strong>Explain (All or Selection)</strong></span>:
            Explains SQL statements, or the currently selected one.
          </p></li><li><p>
            <span class="bold"><strong>Stop the query being
            executed</strong></span>: Halts execution of the currently
            executing SQL script. This restarts the connection to the
            database server.
          </p></li><li><p>
            <span class="bold"><strong>Toggle whether execution of SQL script
            should continue after failed statements</strong></span>: If the
            red “<span class="quote">breakpoint</span>” circle is displayed, the
            script terminates on a statement that fails. If the button
            is depressed so that the green arrow is displayed, execution
            continues past the failed code, possibly generating
            additional result sets. In either case, any error generated
            from attempting to execute the faulty statement is recorded
            in the Output tabsheet.
          </p></li><li><p>
            <span class="bold"><strong>Commit</strong></span>: Commits a
            transaction.
          </p></li><li><p>
            <span class="bold"><strong>Rollback</strong></span>: Rolls back a
            transaction.
          </p></li><li><p>
            <span class="bold"><strong>Toggle Auto-Commit Mode</strong></span>: If
            selected, transactions are automatically committed.
          </p></li><li><p>
            <span class="bold"><strong>Reconnect to DBMS</strong></span>:
            Re-establishes the database connection.
          </p></li><li><p>
            <span class="bold"><strong>Refresh state of database
            structures</strong></span>: Refreshes the view of Schemata,
            Tables, Views and Routines that appears in the Live Overview
            Schema tabsheet. For example, if an SQL script creates a new
            table, it will not appear in the Overview tab until the
            refresh toolbar button is clicked.
          </p></li><li><p>
            <span class="bold"><strong>Toggle whether query result tabs
            should be kept between queries by default</strong></span>:
            Normally when a script is executed, results generated from
            previous executions of the script are lost, and the new
            results are displayed in the results tab. If this toggle
            button is pressed, so that the pin appears inserted,
            previous results are retained. Each execution of the script
            creates a new Results tab containing the result set.
          </p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-server-administration.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Chapter 8. Server Administration</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="dbdoc-templates-custom.html" title="7.12.2. Creating a Custom Template"><link rel="next" href="wb-server-administration-server-instance.html" title="8.1. Server Administration"></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-server-administration"></a>Chapter 8. Server Administration</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="wb-server-administration-server-instance.html">8.1. Server Administration</a></span></dt><dt><span class="section"><a href="wb-server-administration-new-server-instance.html">8.2. New Server Instance</a></span></dt><dt><span class="section"><a href="wb-server-administration-manage-data-import-export.html">8.3. Manage Data Import/Export</a></span></dt><dt><span class="section"><a href="wb-server-administration-manage-security.html">8.4. Manage Security</a></span></dt><dt><span class="section"><a href="wb-server-administration-manage-server-instances.html">8.5. Manage Server Instances</a></span></dt><dt><span class="section"><a href="wb-managing-server-instances.html">8.6. Creating and Managing Server Instances</a></span></dt><dd><dl><dt><span class="section"><a href="wb-new-server-instance-wizard.html">8.6.1. New Server Instance Wizard</a></span></dt><dt><span class="section"><a href="wb-manage-server-instance-dialog.html">8.6.2. Manage Server Instances Dialog</a></span></dt></dl></dd><dt><span class="section"><a href="wb-server-administration-configuration.html">8.7. Server Administration and Configuration</a></span></dt><dd><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></dd></dl></div><p>
    Since version 5.2.6, MySQL Workbench has included functionality for
    managing server instances. A server instance is created to provide a
    way of connecting to a server to be managed. The first step is to
    create a server instance if none exists, or to work with an existing
    server instance.
  </p><p>
    MySQL Workbench also provides functionality to administer and configure
    a server using these server instances. Thus, the Server
    Administrator functionality can be broadly grouped into two main
    areas:
  </p><div class="itemizedlist"><ul type="disc"><li><p>
        Creating and managing server instances
      </p></li><li><p>
        Administration and configuration functions using a server
        instance
      </p></li></ul></div><p>
    The Workspace section of the Home window has an area for Server
    Administration tasks. This section of the Workspace has the
    following action items:
  </p><div class="itemizedlist"><ul type="disc"><li><p>
        Server Administration
      </p></li><li><p>
        Server Administration (icon)
      </p></li><li><p>
        New Server Instance
      </p></li><li><p>
        Manage Data Import/Export
      </p></li><li><p>
        Manage Security
      </p></li><li><p>
        Manage Server Instances
      </p></li></ul></div><p>
    The following sections describe each of these action items.
  </p></div></body></html>


path: /wb-html-guitools/license-glitz.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>B.10. Glitz 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-glib-wb.html" title="B.9. GLib License (for MySQL Workbench)"><link rel="next" href="license-gnu-lgpl-2-1.html" title="B.11. GNU Lesser General Public License Version 2.1, February 1999"></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-glitz"></a>B.10. Glitz License</h2></div></div></div><p>
    The following software may be included in this product:
  </p><pre class="programlisting">Glitz

Copyright © 2004 David Reveman, Peter Nilsson

Permission to use, copy, modify, distribute, and sell 
this software and its documentation for any purpose is 
hereby granted without fee, 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 names of
David Reveman and Peter Nilsson not be used in advertising 
or publicity pertaining to distribution of the software 
without specific, written prior permission. David Reveman 
and Peter Nilsson makes no representations about the 
suitability of this software for any purpose. It is 
provided "as is" without express or implied warranty.

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


path: /wb-html-guitools/wb-launching-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.5. Launching 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-installing-linux.html" title="3.3.4. Installing MySQL Workbench on Linux"><link rel="next" href="wb-linux-uninstalling.html" title="3.3.6. Uninstalling 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-launching-linux"></a>3.3.5. Launching MySQL Workbench on Linux</h3></div></div></div><p>
        After MySQL Workbench has been installed, it can be launched by
        selecting <span class="guimenu">Applications</span>,
        <span class="guimenuitem">Programming</span>, <span class="guimenuitem">MySQL
        Workbench</span> from the main menu.
      </p><p>
        MySQL Workbench can also be launched from the command line on Linux.
        Type the command:
      </p><pre class="programlisting">shell&gt; <strong class="userinput"><code>/usr/bin/mysql-workbench --help</code></strong>
</pre><p>
        This will display the available command-line options:
      </p><pre class="programlisting">mysql-workbench [&lt;options&gt;] [&lt;model file&gt;]
Options:
  --force-sw-render       Force Xlib rendering
  --force-opengl-render   Force OpenGL rendering
  --help, -h              Show command line options and exit</pre></div></body></html>


path: /wb-html-guitools/wb-manage-server-import-from-disk.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>8.7.6.2. Import from Disk</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-manage-server-data-dump-tab.html" title="8.7.6. The Data Dump Tab"><link rel="prev" href="wb-manage-server-export-to-disk.html" title="8.7.6.1. Export to Disk"><link rel="next" href="wb-manage-server-advanced-options.html" title="8.7.6.3. Advanced Export Options"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-manage-server-import-from-disk"></a>8.7.6.2. Import from Disk</h4></div></div></div><p>
          The Import from Disk tab enables you to import a previously
          exported project. You can select to import a project where
          tables were stored in individual files. In this case, you will
          also be able to select which of these tables to import. You
          can also import a project saved to a single file.
        </p><div class="figure"><a name="wb-manage-server-data-import-screenshot"></a><p class="title"><b>Figure 8.10. Administrator - Import from Disk</b></p><div class="mediaobject"><img src="images/wb-manage-server-data-import.png" width="1024" height="707" alt="Administrator - Import from
              Disk"></div></div></div></body></html>


path: /wb-html-guitools/wb-news-5-2-36.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.2. Changes in MySQL Workbench 5.2.36 (Not yet released)</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="changes-5.2.x.html" title="A.1. Changes in Release 5.2"><link rel="prev" href="wb-news-5-2-37.html" title="A.1.1. Changes in MySQL Workbench 5.2.37 (Not yet released)"><link rel="next" href="wb-news-5-2-35.html" title="A.1.3. Changes in MySQL Workbench 5.2.35 (23 September 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-36"></a>A.1.2. Changes in MySQL Workbench 5.2.36 (Not yet released)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied to
        MySQL Workbench since the release of 5.2.35.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        The <span class="guimenu">Edit</span>, <span class="guimenu">Format</span>,
        <span class="guimenu">Beautify Query</span> feature no longer quotes
        column names.
       (Bug #13030351)</p></li><li><p>
        The edit context menus, such as <span class="guimenu">Edit Table
        Data</span>, now open as new tabs. Before they reused
        (overwrote) the same tab.
       (Bug #61774, Bug #12731459)</p></li><li><p>
        If only one server instance is defined, then the <span class="guimenu">Server
        administration</span>, <span class="guimenu">Manage security</span>
        option will now automatically connect to it, instead of
        prompting to choose a server instance.
       (Bug #61451, Bug #12647697)</p></li><li><p>
        Indexes are now shown within the schema tree. And indexed
        columns are also indicated within the table information panel.
       (Bug #61295, Bug #12616367)</p></li><li><p>
        The <code class="literal">auto_increment</code> information is now
        displayed within the SQL editor.
       (Bug #60933, Bug #12402845)</p></li><li><p>
        On the SQL Editor tabs, right-clicking a tab now offers the
        following options: <span class="guimenu">New Tab</span>, <span class="guimenu">Save
        Tab</span>, <span class="guimenu">Close Tab</span>, <span class="guimenu">Close
        Other Tabs</span>, and <span class="guimenu">Copy Path to
        Clipboard</span>.
       (Bug #60883, Bug #12399369)</p></li><li><p>
        The query and associated results are no longer displayed in
        separate tabs, but they are now viewable within a single
        interface.
       (Bug #60624, Bug #11926853)</p></li><li><p>
        The SQL editor windows did not have maximize or minimize
        buttons, but these windows are now opened in configurable tabs.
       (Bug #60606, Bug #12617245)</p></li><li><p>
        The export result set dialog has been redesigned, and now saves
        the previously used settings.
       (Bug #60490, Bug #11889185)</p></li><li><p>
        SQL snippets can now be edited, and then saved.
       (Bug #58879, Bug #11765873)</p></li><li><p>
        Tab spacing is now defined as <code class="literal">4</code> on the Linux
        and Mac platforms, to be consistent with Windows.
       (Bug #58867, Bug #11765862)</p></li><li><p>
        A <span class="guimenu">Paste Row</span> context option was added to the
        <span class="guimenu">Edit Table Data</span> menu of the Object browser.
       (Bug #58169, Bug #11765228)</p></li><li><p>
        Additional <span class="guilabel">Export</span> data types were added to
        the SQL Browser, which now includes <code class="literal">JSON</code>,
        Excel spreadsheet, and MySQL formatted XML.
       (Bug #56808, Bug #11764024)</p></li><li><p>
        The Overview tab was replaced, in favor of the new schema tree
        view.
       (Bug #56795, Bug #11764014)</p></li><li><p>
        Added the ability to edit data from a result set after executing
        a query. If MySQL Workbench determines that a returned result cannot
        be edited, then a read-only icon will be displayed, and hovering
        over the icon reveals a tooltip that explains why it cannot be
        edited.
       (Bug #56794, Bug #11764013)</p></li><li><p>
        Added a input field to filter the schema list in the
        <span class="guilabel">Object Browser</span>.
       (Bug #55162, Bug #11762554)</p></li><li><p>
        The <span class="guimenu">Alter table</span> option defaulted to Table
        view, but now uses the new table editor.
       (Bug #55050, Bug #11762454)</p></li><li><p>
        MySQL Workbench did not support the <code class="literal">.dbquery</code> file
        extension.
       (Bug #54321, Bug #11761795)</p></li><li><p>
        Added the <span class="guimenu">Copy Inserts to Clipboard</span> option to
        the <span class="guimenu">Plugins</span>, <span class="guimenu">Objects</span> menu.
       (Bug #54036, Bug #11761531)</p></li><li><p>
        Added toolbar buttons to toggle the sidebars and bottom panel of
        the SQL Editor.
       (Bug #53714, Bug #11761243)</p></li><li><p>
        The table view within the <span class="guilabel">Object Browser</span>
        has changed. The table view includes another level of grouping,
        which includes Columns, Indexes, Foreign Keys, and Triggers.
        Before, only the columns were listed.
       (Bug #53504, Bug #11761050)</p></li><li><p>
        The table information window within the <span class="guilabel">Object
        Browser</span> has been expanded to include foreign keys,
        triggers, indexes, and data types.
       (Bug #53502, Bug #11761048)</p></li><li><p>
        The Overview tab was removed, in favor of the new schema layout.
       (Bug #53323, Bug #11760879)</p></li><li><p>
        New entries to the error log are now shown when restarting the
        MySQL server.
      </p><p>
        When <code class="literal">log_output</code> is set to
        <code class="literal">FILE</code>, the log files are now displayed in the
        MySQL Workbench log page.
       (Bug #52445, Bug #11760073)</p></li><li><p>
        The SQL snippets interface been redesigned and relocated to its
        own sidebar. Its display may also be toggled.
       (Bug #50069, Bug #11757950)</p></li><li><p>
        The SQL Editor history tab now auto-scrolls to the bottom, so
        that the most recent entry is visible.
       (Bug #49317, Bug #11757294)</p></li><li><p>
        Added a new format to the SQL Editor for export, which is
        identical to the XML generated by the <code class="literal">mysql
        --xml</code> command. It's titled <code class="literal">XML (mysql
        format)</code>.
       (Bug #49305, Bug #11757284)</p></li><li><p>
        Added the ability to copy Status and System Variables to the
        clipboard.
       (Bug #49074, Bug #11757074)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        While using the import/restore feature of the server instance
        administration area, views and routines were not imported.
       (Bug #13041684)</p></li><li><p>
        After right-clicking a cell within the insert grid of the model
        table editor, an unhandled exception was generated on Microsoft
        Windows, and a fatal error on Mac OS X.
       (Bug #13029647)</p></li><li><p>
        The <span class="guimenu">Manage Security</span> window initially shows
        the first connection as selected, but it is not.
       (Bug #13026478)</p></li><li><p>
        While administrating a server instance, importing a project
        folder will result in an "Import from Disk" error after the
        following sequence: <span class="guimenu">Data Export and restore</span>,
        <span class="guimenu">Export to Dump project folder</span>, with
        <code class="literal">Dump views and Dump stored routines...</code>
        checked, then exporting a schema with views and/or routines,
        opening the SQL Editor and dropping the exported schema, then
        clicking <span class="guimenu">Import to Disk</span> within the server
        administrator.
       (Bug #13025419)</p></li><li><p>
        Pressing <span class="guibutton">Refresh</span> within the
        <span class="guilabel">Slow Query Log</span> tab resulted in an unhandled
        exception.
       (Bug #12928308)</p></li><li><p>
        Within a diagram view, the <span class="guimenu">Edit</span>,
        <span class="guimenu">Find</span>, <span class="guimenu">Find advanced</span> option
        was unrecognized and performed no function.
       (Bug #12884864)</p></li><li><p>
        A previously selected object could not be dragged, as it would
        instead enter "Edit Name" mode after the second click.
       (Bug #12884796)</p></li><li><p>
        New server instances created by the <span class="guimenu">Manage Server
        Instance</span> wizard would send the incorrect service name
        to the MySQL admin. The command is now constructed at run time
        using the service name from the server instance profile.
       (Bug #12567371)</p></li><li><p>
        Creating a server instance using unicode characters worked, but
        an error would be generated while attempting to open them.
       (Bug #63100, Bug #13350556)</p></li><li><p>
        Using <span class="guimenu">Alter routine</span> to make changes would
        sometimes crash after clicking <span class="guibutton">Apply</span>.
       (Bug #63076, Bug #13340307)</p></li><li><p>
        On Microsoft Windows, upgrading MySQL Workbench required MySQL Workbench
        to be run as a user with Administrator rights.
       (Bug #62709, Bug #13116366)</p></li><li><p>
        Opening model files while using a MySQL Workbench version that was
        installed over a previous MySQL Workbench installation would
        sometimes cause permission issues. The workarounds included
        running MySQL Workbench with administrator privileges, or removing
        the installation folder before upgrading.
       (Bug #62703, Bug #13323929)</p></li><li><p>
        An unhandled exception might be emitted after modifying an
        <code class="literal">EER</code> diagram, with a popup window reading
        "MySQL Workbench has encountered a problem - Queue empty."
       (Bug #62651, Bug #13079826)</p></li><li><p>
        A query history date would incorrectly change when a history
        entry, other than the last one, was selected when the query was
        executed.
       (Bug #62642, Bug #13104635)</p></li><li><p>
        The <span class="guimenu">Create Routine...</span> feature would report
        that it created a routine, but it did not, and the error was
        revealed in the output window.
       (Bug #62624, Bug #13362190)</p></li><li><p>
        The <span class="guimenu">Reconnect to DBMS</span> toolbar option would
        not reconnect after unchecking the <code class="literal">Safe
        Updates</code> preference. A workaround is to uncheck this
        option, then restart MySQL Workbench.
       (Bug #62448, Bug #13014798)</p></li><li><p>
        Expanding then collapsing the query results window within the
        SQL editor, yielded a different appearance.
       (Bug #62371, Bug #13007096)</p></li><li><p>
        On Ubuntu 11.10, MySQL Workbench would freeze at the startup splash
        screen.
       (Bug #62347, Bug #13099521)</p></li><li><p>
        The <code class="literal">Configuration File</code> path within the
        <span class="guimenu">Server Administration</span> panel is now read-only,
        when before it would temporarily set the path. This path should
        be set via the profile setting instead.
       (Bug #62252, Bug #12922746)</p></li><li><p>
        Fixed a typo, where "database" was misspelled as "dabase" within
        the <code class="literal">DBDesigner</code> description.
       (Bug #62250, Bug #12912465)</p></li><li><p>
        The <code class="literal">Auto-save</code> feature would behave with
        unpredictable results, by opening up an incorrect number of
        windows when MySQL Workbench was next loaded.
       (Bug #62192, Bug #12907612)</p></li><li><p>
        Opening <span class="guimenu">Management</span>, <span class="guimenu">Server
        Logs</span> would generate an unhandled exception when using
        table-based logging, while the general log was empty.
       (Bug #62123, Bug #12872836)</p></li><li><p>
        After setting a default schema, choosing <span class="guibutton">Refresh
        all</span> while the schema information is "fetching" would
        result in an unhandled exception.
       (Bug #62086, Bug #12913399)</p></li><li><p>
        Switching between two logins for a single database connection
        required the password to be reentered with each switch.
       (Bug #62052, Bug #12921420)</p></li><li><p>
        On Linux, the <span class="guimenu">Database</span>, <span class="guimenu">Generate
        Catalog Diff Report...</span> model option was disabled.
       (Bug #62040, Bug #12844314)</p></li><li><p>
        Within the <span class="guimenu">Routine Editor</span>, opening multiple
        <span class="guimenu">Apply SQL Script to Database</span> dialogues and
        then executing one, except for the last one opened, would crash
        MySQL Workbench.
       (Bug #61988, Bug #12918227)</p></li><li><p>
        On Microsoft Windows, the EER diagram search did not work across
        multiple pages.
       (Bug #61957, Bug #12818216)</p></li><li><p>
        Fixed <span class="guimenu">Data export</span> so that routines and views
        are only exported when they are selected. In addition,
        individual views may now be selected for export.
       (Bug #61937, Bug #12949918)</p></li><li><p>
        Importing a dump would misquote the
        <code class="option">--defaults-extra-file</code> option,
        which would cause the import to fail.
       (Bug #61910, Bug #12912786)</p></li><li><p>
        A <code class="literal">Download Prerequisites</code> link is now
        displayed when prerequisites, such as the "Visual C++ 2010
        Redistributable Package" requirement, are not met. Before, the
        link was not visible.
       (Bug #61897, Bug #12769499)</p></li><li><p>
        Repeatedly refreshing a schema resulted in an unhandled
        exception.
       (Bug #61892, Bug #12762893)</p></li><li><p>
        The <span class="guimenu">File</span>, <span class="guimenu">Open Recent</span>
        feature would open the incorrect script.
       (Bug #61856, Bug #12912374)</p></li><li><p>
        On Mac OS X, switching from the Model tab to the EER Diagram tab
        caused an error sound.
       (Bug #61809, Bug #12757337)</p></li><li><p>
        <span class="guimenu">File</span>, <span class="guimenu">Export</span>,
        <span class="guimenu">Forward Engineer SQL CREATE Script</span> would
        append an extra space to <code class="literal">TINYINT(1)</code> after
        converting it from <code class="literal">BOOL</code>.
       (Bug #61696, Bug #12711138)</p></li><li><p>
        MySQL Workbench would not recognize the active schema with case
        insensitive servers. As a result, an active schema within the
        Object browser would be unselected after a
        <code class="literal">USE</code> statement was executed.
       (Bug #61641, Bug #12711143)</p></li><li><p>
        The <span class="guimenu">Users and Privileges</span> window did not scale
        to low screen resolutions like 1024x768. It does now, although
        MySQL Workbench still has an official minimum screen resolution of
        1280x800.
       (Bug #61518, Bug #12661556)</p></li><li><p>
        Tab panels within <span class="guimenu">Server Administration</span> would
        not fresh properly.
       (Bug #61452, Bug #12647731)</p></li><li><p>
        The Object editors (such as <span class="guimenu">Alter Table</span>,
        <span class="guimenu">Alter View</span>, and <span class="guimenu">Alter
        Routine</span>) now open as tabs, instead of separate wizard
        windows.
       (Bug #61422, Bug #12642157)</p></li><li><p>
        Exporting SQL for tables that included comments would generate
        invalid SQL statements. A comma was missing immediately before
        the <code class="literal">COMMENT</code>.
       (Bug #61393, Bug #12627762)</p></li><li><p>
        After opening a saved model file, the <span><strong class="keycap">Control+T</strong></span>
        shortcut would not work from within a query window.
       (Bug #61379, Bug #12627716)</p></li><li><p>
        MySQL Workbench could crash while restoring large files.
       (Bug #61365, Bug #12627685)</p></li><li><p>
        The <span class="guibutton">Clear script output</span> and
        <span class="guibutton">Close this script tab</span> buttons are now
        disabled in non-script tabs.
       (Bug #61318, Bug #12616331)</p></li><li><p>
        On Linux, code folding for stored procedures and loops did not
        work properly within the SQL editor.
       (Bug #61302, Bug #12612394)</p></li><li><p>
        On Microsoft Windows, the <span class="guimenu">Find</span> option
        (<span><strong class="keycap">Control+F</strong></span>) for the SQL editor was not
        available.
       (Bug #61233, Bug #12622697)</p></li><li><p>
        Executing a slow query would not notify the user that the query
        was running. The new SQL editor interface does show the
        progress.
       (Bug #61231, Bug #12589710)</p></li><li><p>
        When hovering the mouse pointer over a table figure on a
        diagram, the foreign key tooltip would hide the table column
        names.
       (Bug #61055, Bug #12546715)</p></li><li><p>
        The default schema selection would be lost after synchronizing a
        model.
       (Bug #60975, Bug #12621744)</p></li><li><p>
        On Linux and Mac OS X, using <span class="guibutton">Tab</span> and
        <span class="guibutton">Shift+Tab</span> to jump to next/previous fields
        has been added to the query result view. It had previously only
        worked on Windows. Additionally, the
        <span class="guibutton">Escape</span> key will now cancel editing of the
        current cell, and
        <span class="guibutton">PageUp</span>/<span class="guibutton">PageDown</span>
        scrolls one page up and down in the result set.
       (Bug #60865, Bug #12368205)</p></li><li><p>
        Manipulating multiple SQL editor tabs would sometimes result in
        uncaught exceptions.
       (Bug #60764, Bug #12621640)</p></li><li><p>
        MySQL Workbench would crash when attempting to use <span class="guimenu">Alter
        Table</span> or <span class="guimenu">Create Table</span> from within
        the context menu.
       (Bug #60760, Bug #12621510)</p></li><li><p>
        Fixed a crash bug, which would happen on exit.
       (Bug #60733, Bug #12632325)</p></li><li><p>
        Factory snippet files were fixed, to include proper line-endings
        for all platforms.
       (Bug #60643, Bug #12621434)</p></li><li><p>
        Closing MySQL Workbench would not prompt to save unsaved work from
        modified SQL files and windows.
       (Bug #60557, Bug #11926868)</p></li><li><p>
        The SQL editor output tab did not report the number of affected
        rows.
       (Bug #60535, Bug #12617147)</p></li><li><p>
        The <code class="literal">Syncronize model with Database</code> wizard
        would not properly handle case-sensitive table names.
       (Bug #60523, Bug #12617135)</p></li><li><p>
        Open diagram tabs from a saved MySQL Workbench state were not saved
        properly.
       (Bug #60515, Bug #12617096)</p></li><li><p>
        The <span class="guimenu">Advanced Export Options</span> preferences were
        not saved, and would reset after restarting MySQL Workbench.
       (Bug #60497, Bug #11889197)</p></li><li><p>
        Connection and query tabs can now be reordered, by dragging and
        dropping with the mouse pointer.
       (Bug #60409, Bug #11865602)</p></li><li><p>
        On Linux, viewing the embedded documentation required the
        python-sqlite2 package.
       (Bug #60336, Bug #11874507)</p></li><li><p>
        On Mac OS X, <span><strong class="keycap">Command+W</strong></span> will now close the
        active script editor tab, and <span><strong class="keycap">Command+Shift+W</strong></span>
        will now close the active connection tab. This is now consistent
        with behavior on other operating systems. Before, the
        <span><strong class="keycap">Command+W</strong></span> combination closed the active
        connection tab.
       (Bug #60253, Bug #11829750)</p></li><li><p>
        Pressing <span><strong class="keycap">Esc</strong></span> once now escapes out of edit mode
        within the row editor. Before, it had to be pressed twice.
       (Bug #60131, Bug #11829997)</p></li><li><p>
        The <span class="guimenu">Copy Row Content</span> option would throw an
        unexpected exception, from within a model.
      </p><p>
        In addition, the <span class="guimenu">Paste Row</span> option was added.
       (Bug #60116, Bug #12417533)</p></li><li><p>
        The <code class="literal">USE</code> statement is now properly quoted. For
        example, an invalid <code class="literal">USE</code> query would be
        generated if a schema contained a <code class="literal">-</code>
        character.
       (Bug #59882, Bug #11766711)</p></li><li><p>
        Copying a table column would lose the data type, when only the
        column line number was selected instead of the data type or
        field name.
       (Bug #59285, Bug #11905520)</p></li><li><p>
        Within a server instance administration panel, setting
        <span class="guimenu">Export to Self-Contained File</span> to an invalid
        path resulted in an unhandled exception.
       (Bug #59246, Bug #11766194)</p></li><li><p>
        The Output tab of the SQL editor now adjusts whitespace
        characters, as to display queries on a single line.
       (Bug #58989, Bug #11765966)</p></li><li><p>
        Enabling the <code class="literal">Limit Rows</code> SQL editor preference
        would cause invalid SQL syntax with <code class="literal">SELECT
        INTO</code> statements.
       (Bug #58732, Bug #11765738)</p></li><li><p>
        When viewing text at a size greater than 100% (such as 125%),
        some text field labels would be partially hidden.
       (Bug #58408, Bug #12628507)</p></li><li><p>
        <span class="guimenu">Server Administration</span>, <span class="guimenu">Manage
        Import/Export</span> would return an error about the dump
        module.
       (Bug #58098, Bug #11765164)</p></li><li><p>
        MySQL Workbench would allow the creation of foreign keys on tables
        using engines that do not support them. A warning is now emitted
        if this is attempted.
       (Bug #57875, Bug #11764972)</p></li><li><p>
        MySQL Workbench did not fully adhere to locale settings, which could
        result in unhandled exceptions.
       (Bug #56869, Bug #11764077)</p></li><li><p>
        The <span class="guibutton">Foreign Keys</span> tab of the
        <span class="guimenu">Alter Table</span> wizard only created an index,
        without the foreign key.
       (Bug #56818, Bug #11764033)</p></li><li><p>
        Broken views (e.g., a column no longer exists) are now displayed
        as broken within the schema tree view.
       (Bug #56701, Bug #11763928)</p></li><li><p>
        Editor windows would sometimes lose focus, but they are now
        docked within the main application window, which eliminated this
        problem.
       (Bug #55923, Bug #11763235)</p></li><li><p>
        Auto-scrolling for the SQL output and history windows was added.
       (Bug #55865, Bug #11763183)</p></li><li><p>
        The <span class="guimenu">Find</span> feature (search) was replaced with a
        panel, which offers more consistent behavior across platforms.
        The <span class="guimenu">Find and Replace</span> feature is also now a
        panel, instead of a pop-up window.
       (Bug #54765, Bug #11762197)</p></li><li><p>
        On Linux, the previously set window positions and sizes were not
        saved by MySQL Workbench. These settings are now saved upon closing,
        and used when MySQL Workbench is loaded.
       (Bug #54025, Bug #11761521)</p></li><li><p>
        The <span class="guibutton">Finish</span> button was inactive (grayed
        out) for the <span class="guimenu">Edit Table Data</span> dialog, if the
        database contained exactly one table.
       (Bug #52833, Bug #11760422)</p></li><li><p>
        If a table cannot be edited (e.g., no Primary key), then
        MySQL Workbench now notifies users of the reason, when before the
        edit option was simply not available.
       (Bug #51563, Bug #11759263)</p></li><li><p>
        Closing and opening the SQL Editor now sets the last used schema
        as the default, instead of the schema specified within the
        connection.
       (Bug #51454, Bug #51026, Bug #11759165, Bug #11758776)</p></li><li><p>
        A triple-click was required to change the <span class="guilabel">Referenced
        column</span> of a foreign key, while editing a table within
        an EER diagram.
       (Bug #50725, Bug #11758512)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-news-5-1-8.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.2.12. Changes in MySQL Workbench 5.1.8 (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-9.html" title="A.2.11. Changes in MySQL Workbench 5.1.9 (Not yet released Beta)"><link rel="next" href="wb-news-5-1-7.html" title="A.2.13. Changes in MySQL Workbench 5.1.7 (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-8"></a>A.2.12. Changes in MySQL Workbench 5.1.8 (Not yet released)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.1.7.
      </p><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><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>
        Using the Inserts Editor caused MySQL Workbench to crash. The error
        message generated when used was:
      </p><pre class="programlisting">** Message: ==============================
** Message: refresh_gui_becb unhandled refresh: 20 RefreshTimer</pre><p>
        This was due to the fact that, in the 5.1.4 Alpha version of
        MySQL Workbench, the Inserts Editor had not been implemented.
       (Bug #40671)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/dbdoc-templates-markers.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.12.1. Supported Template Markers</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.html" title="7.12. Customizing DBDoc Model Reporting Templates"><link rel="next" href="dbdoc-templates-custom.html" title="7.12.2. Creating a Custom Template"></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-markers"></a>7.12.1. Supported Template Markers</h3></div></div></div><p>
      The following table shows the supported markers. These markers can
      be used in any template, including custom templates.
    </p><div class="informaltable"><table border="1"><colgroup><col><col><col><col></colgroup><thead><tr><th>Marker text</th><th>Type</th><th>Data Dictionary defined in (if variable) or parent dictionary (if
              section)</th><th>Corresponding data</th></tr></thead><tbody><tr><td>TITLE</td><td>Variable</td><td>MAIN</td><td>Title of the report</td></tr><tr><td>GENERATED</td><td>Variable</td><td>MAIN</td><td>Date and time when the report was generated</td></tr><tr><td>STYLE_NAME</td><td>Variable</td><td>MAIN</td><td>The name of the style selected in MySQL Workbench, this is typically used to
              load the corresponding CSS file, depending on the name of
              the style selected in MySQL Workbench</td></tr><tr><td>SCHEMA_COUNT</td><td>Variable</td><td>MAIN</td><td>The number of schemata in the model</td></tr><tr><td>PROJECT_TITLE</td><td>Variable</td><td>MAIN</td><td>Project title as set for the model in <span class="guimenuitem">Document
              Properties</span></td></tr><tr><td>PROJECT_NAME</td><td>Variable</td><td>MAIN</td><td>Project name as set for the model in <span class="guimenuitem">Document
              Properties</span></td></tr><tr><td>PROJECT_AUTHOR</td><td>Variable</td><td>MAIN</td><td>Project author as set for the model in <span class="guimenuitem">Document
              Properties</span></td></tr><tr><td>PROJECT_VERSION</td><td>Variable</td><td>MAIN</td><td>Project version as set for the model in <span class="guimenuitem">Document
              Properties</span></td></tr><tr><td>PROJECT_DESCRIPTION</td><td>Variable</td><td>MAIN</td><td>Project description as set for the model in <span class="guimenuitem">Document
              Properties</span></td></tr><tr><td>PROJECT_CREATED</td><td>Variable</td><td>MAIN</td><td>Automatically set for the model project, but as displayed in
              <span class="guimenuitem">Document Properties</span></td></tr><tr><td>PROJECT_CHANGED</td><td>Variable</td><td>MAIN</td><td>Automatically set for the model project, but as displayed in
              <span class="guimenuitem">Document Properties</span></td></tr><tr><td>TOTAL_TABLE_COUNT</td><td>Variable</td><td>MAIN</td><td>The number of tables in all schemata in the model</td></tr><tr><td>TOTAL_COLUMN_COUNT</td><td>Variable</td><td>MAIN</td><td>The number of columns in all tables in all schemata in the model</td></tr><tr><td>TOTAL_INDEX_COUNT</td><td>Variable</td><td>MAIN</td><td>The number of indexes in the model</td></tr><tr><td>TOTAL_FK_COUNT</td><td>Variable</td><td>MAIN</td><td>The number of foreign keys in the model</td></tr><tr><td>SCHEMATA</td><td>Section</td><td>MAIN</td><td>Used to mark the start and end of a SCHEMATA section; the SCHEMATA data
              dictionary becomes active in this section</td></tr><tr><td>SCHEMA_NAME</td><td>Variable</td><td>SCHEMATA</td><td>The schema name</td></tr><tr><td>SCHEMA_ID</td><td>Variable</td><td>SCHEMATA</td><td>The schema ID</td></tr><tr><td>TABLE_COUNT</td><td>Variable</td><td>SCHEMATA</td><td>The number of tables in the current schema</td></tr><tr><td>COLUMN_COUNT</td><td>Variable</td><td>SCHEMATA</td><td>The number of columns in the current schema</td></tr><tr><td>INDICES_COUNT</td><td>Variable</td><td>SCHEMATA</td><td>The number of indexes in the current schema</td></tr><tr><td>FOREIGN_KEYS_COUNT</td><td>Variable</td><td>SCHEMATA</td><td>The number of foreign keys in the current schema</td></tr><tr><td>TABLES</td><td>Section</td><td>SCHEMATA</td><td>Marks the start and end of a TABLES section; the TABLES data dictionary
              becomes active in this section</td></tr><tr><td>TABLE_NAME</td><td>Variable</td><td>TABLES</td><td>The table name</td></tr><tr><td>TABLE_ID</td><td>Variable</td><td>TABLES</td><td>The table ID</td></tr><tr><td>COLUMNS_LISTING</td><td>Section</td><td>TABLES</td><td>Marks the start and end of a COLUMNS_LISTING section; the
              COLUMNS_LISTING data dictionary becomes active in this
              section</td></tr><tr><td>COLUMNS</td><td>Section</td><td>COLUMNS_LISTING</td><td>Marks the start and end of a COLUMNS section; the COLUMNS data
              dictionary becomes active in this section</td></tr><tr><td>COLUMN_KEY</td><td>Variable</td><td>COLUMNS</td><td>Whether the column is a primary key</td></tr><tr><td>COLUMN_NAME</td><td>Variable</td><td>COLUMNS</td><td>The column name</td></tr><tr><td>COLUMN_DATATYPE</td><td>Variable</td><td>COLUMNS</td><td>The column data type</td></tr><tr><td>COLUMN_NOTNULL</td><td>Variable</td><td>COLUMNS</td><td>Whether the column permits <code class="literal">NULL</code> values</td></tr><tr><td>COLUMN_DEFAULTVALUE</td><td>Variable</td><td>COLUMNS</td><td>The column default value</td></tr><tr><td>COLUMN_COMMENT</td><td>Variable</td><td>COLUMNS</td><td>The column comment</td></tr><tr><td>COLUMN_ID</td><td>Variable</td><td>COLUMNS</td><td>The column ID</td></tr><tr><td>COLUMN_KEY_PART</td><td>Variable</td><td>COLUMNS (if detailed)</td><td>The column key type</td></tr><tr><td>COLUMN_NULLABLE</td><td>Variable</td><td>COLUMNS (if detailed)</td><td>Can the column contain <code class="literal">NULL</code> values</td></tr><tr><td>COLUMN_AUTO_INC</td><td>Variable</td><td>COLUMNS (if detailed)</td><td>Does the column auto-increment</td></tr><tr><td>COLUMN_CHARSET</td><td>Variable</td><td>COLUMNS (if detailed)</td><td>The column character set</td></tr><tr><td>COLUMN_COLLATION</td><td>Variable</td><td>COLUMNS (if detailed)</td><td>The column collation</td></tr><tr><td>COLUMN_IS_USERTYPE</td><td>Variable</td><td>COLUMNS (if detailed)</td><td>Whether the column is a user type</td></tr><tr><td>INDICES_LISTING</td><td>Section</td><td>TABLES</td><td>Marks the start and end of an INDICES_LISTING section; the
              INDICES_LISTING data dictionary becomes active in this
              section</td></tr><tr><td>INDICES</td><td>Section</td><td>INDICES_LISTING</td><td>Marks the start and end of an INDICES section; the INDICES data
              dictionary becomes active in this section</td></tr><tr><td>INDEX_NAME</td><td>Variable</td><td>INDICES</td><td>The index name</td></tr><tr><td>INDEX_PRIMARY</td><td>Variable</td><td>INDICES</td><td>Whether this is a primary key</td></tr><tr><td>INDEX_UNIQUE</td><td>Variable</td><td>INDICES</td><td>Whether this is a unique index</td></tr><tr><td>INDEX_TYPE</td><td>Variable</td><td>INDICES</td><td>The index type; for example, PRIMARY</td></tr><tr><td>INDEX_KIND</td><td>Variable</td><td>INDICES</td><td>The index kind</td></tr><tr><td>INDEX_COMMENT</td><td>Variable</td><td>INDICES</td><td>The index comment</td></tr><tr><td>INDEX_ID</td><td>Variable</td><td>INDICES</td><td>The index ID</td></tr><tr><td>INDEX_COLUMNS</td><td>Section</td><td>INDICES</td><td>Marks the start and end of an INDEX_COLUMNS section; the INDEX_COLUMNS
              data dictionary becomes active in this section</td></tr><tr><td>INDEX_COLUMN_NAME</td><td>Variable</td><td>INDEX_COLUMNS</td><td>The index column name</td></tr><tr><td>INDEX_COLUMN_ORDER</td><td>Variable</td><td>INDEX_COLUMNS</td><td>The index column order; for example, ascending, descending</td></tr><tr><td>INDEX_COLUMN_COMMENT</td><td>Variable</td><td>INDEX_COLUMNS</td><td>The index comment</td></tr><tr><td>INDEX_KEY_BLOCK_SIZE</td><td>Variable</td><td>INDEX_COLUMNS (if detailed)</td><td>The index key-block size</td></tr><tr><td>REL_LISTING</td><td>Section</td><td>TABLES</td><td>Marks the start and end of a REL_LISTING section; the REL_LISTING data
              dictionary becomes active in this section</td></tr><tr><td>REL</td><td>Section</td><td>REL_LISTING</td><td>Marks the start and end of a REL section; the REL data dictionary
              becomes active in this section</td></tr><tr><td>REL_NAME</td><td>Variable</td><td>REL, FOREIGN_KEYS</td><td>The relationship name</td></tr><tr><td>REL_TYPE</td><td>Variable</td><td>REL, FOREIGN_KEYS</td><td>The relationship type</td></tr><tr><td>REL_PARENTTABLE</td><td>Variable</td><td>REL, FOREIGN_KEYS</td><td>The relationship parent table</td></tr><tr><td>REL_CHILDTABLE</td><td>Variable</td><td>REL, FOREIGN_KEYS</td><td>The relationship child table</td></tr><tr><td>REL_CARD</td><td>Variable</td><td>REL, FOREIGN_KEYS</td><td>The relationship cardinality</td></tr><tr><td>FOREIGN_KEY_ID</td><td>Variable</td><td>REL</td><td>Foreign key ID</td></tr><tr><td>FOREIGN_KEYS</td><td>Section</td><td>SCHEMATA</td><td>Marks the start and end of a FOREIGN_KEYS section; the FOREIGN_KEYS data
              dictionary becomes active in this section</td></tr><tr><td>FK_DELETE_RULE</td><td>Variable</td><td>FOREIGN_KEYS</td><td>The foreign key delete rule</td></tr><tr><td>FK_UPDATE_RULE</td><td>Variable</td><td>FOREIGN_KEYS</td><td>The foreign key update rule</td></tr><tr><td>FK_MANDATORY</td><td>Variable</td><td>FOREIGN_KEYS</td><td>Whether the foreign key is mandatory</td></tr><tr><td>TABLE_COMMENT_LISTING</td><td>Section</td><td>TABLES</td><td>Marks the start and end of a TABLE_COMMENT_LISTING section; the
              TABLE_COMMENT_LISTING data dictionary becomes active in
              this section</td></tr><tr><td>TABLE_COMMENT</td><td>Variable</td><td>TABLE_COMMENT_LISTING</td><td>The table comment</td></tr><tr><td>DDL_LISTING</td><td>Section</td><td>TABLES</td><td>Marks the start and end of a DDL_LISTING section; the DDL_LISTING data
              dictionary becomes active in this section</td></tr><tr><td>DDL_SCRIPT</td><td>Variable</td><td>DDL_LISTING</td><td>Display the DDL script of the currently active entity; for example,
              SCHEMATA, TABLES</td></tr></tbody></table></div><p>
      <span class="bold"><strong>Using the table</strong></span>
    </p><p>
      The table shows which variables are defined in which sections. The
      variable should be used in its correct section or its value will
      not be displayed. However, remember that the data dictionaries
      used to perform variable lookups form a hierarchical tree, so it
      is possible to use a variable in a child section that is defined
      in a parent section.
    </p></div></body></html>


path: /wb-html-guitools/wb-news-5-2-2.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.38. Changes in MySQL Workbench 5.2.2 (27 July 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-3.html" title="A.1.37. Changes in MySQL Workbench 5.2.3 (15 September 2009)"><link rel="next" href="wb-news-5-2-1.html" title="A.1.39. Changes in MySQL Workbench 5.2.1 (22 May 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-2"></a>A.1.38. Changes in MySQL Workbench 5.2.2 (27 July 2009)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.2.1.
      </p><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><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>
        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>
        If MySQL Workbench gave the message that the MySQL Server was no
        longer available (because of timeout due to inactivity) then
        MySQL Workbench crashed when the user tried to reconnect.
       (Bug #45123)</p></li><li><p>
        The UML relationship notation was incorrect.
      </p><p>
        When setting a Foreign Key to NULLable, the table referenced by
        the Foreign Key should be marked as optional. However,
        MySQL Workbench marked the table containing the Foreign Key itself
        as optional.
       (Bug #45069)</p></li><li><p>
        If a user added a <code class="literal">LIMIT</code> clause to a query,
        the automatically added <code class="literal">LIMIT 0,1000</code> clause
        caused a syntax error.
       (Bug #45051)</p></li><li><p>
        The new SQL IDE, introduced in 5.2, did not support returning
        results from procedures. When any routine was called, there were
        no results displayed in the query editor window. However, the
        log contained the message “<span class="quote">Response: OK</span>”.
      </p><p>
        When another query was run on the same connection, the log
        message was:
      </p><pre class="programlisting">Error Code: 2014 Commands out of sync; you can't run this command now</pre><p>(Bug #44910)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-sql-development-edit-sql-script.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>6.4. Edit SQL Script</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-sql-development.html" title="Chapter 6. SQL Development"><link rel="prev" href="wb-sql-development-edit-table-data.html" title="6.3. Edit Table Data"><link rel="next" href="wb-sql-development-manage-connections.html" title="6.5. Manage Connections"></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-edit-sql-script"></a>6.4. Edit SQL Script</h2></div></div></div><p>
      Clicking this action item launches the Edit SQL Script wizard.
      This is a two-stage wizard. The first stage enables you to select
      a Stored Connection. The second stage enables you to select an SQL
      Script file, and optionally have the script executed after it is
      opened. After the wizard is completed, an SQL Editor tab will be
      launched, with the script displayed. If you selected to run the
      script, MySQL Workbench runs the script and displays the results.
    </p></div></body></html>


path: /wb-html-guitools/wb-sql-development.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Chapter 6. SQL Development</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-preferences-appearance.html" title="5.4.7. The Appearance Tab"><link rel="next" href="wb-sql-development-open-connection.html" title="6.1. Open Connection to Start Querying"></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-sql-development"></a>Chapter 6. SQL Development</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="wb-sql-development-open-connection.html">6.1. Open Connection to Start Querying</a></span></dt><dt><span class="section"><a href="wb-sql-development-new-connection.html">6.2. New Connection</a></span></dt><dt><span class="section"><a href="wb-sql-development-edit-table-data.html">6.3. Edit Table Data</a></span></dt><dt><span class="section"><a href="wb-sql-development-edit-sql-script.html">6.4. Edit SQL Script</a></span></dt><dt><span class="section"><a href="wb-sql-development-manage-connections.html">6.5. Manage Connections</a></span></dt><dt><span class="section"><a href="wb-manage-db-connections.html">6.6. Manage DB Connections Dialog</a></span></dt><dd><dl><dt><span class="section"><a href="wb-manage-db-connections-vault.html">6.6.1. The Password Storage Vault</a></span></dt><dt><span class="section"><a href="wb-manage-db-connections-standard.html">6.6.2. Standard TCP/IP Connection</a></span></dt><dt><span class="section"><a href="wb-manage-db-connections-socket.html">6.6.3. Local Socket/Pipe Connection</a></span></dt><dt><span class="section"><a href="wb-manage-db-connections-ssh.html">6.6.4. Standard TCP/IP over SSH Connection</a></span></dt></dl></dd><dt><span class="section"><a href="wb-sql-editor.html">6.7. SQL Editor</a></span></dt><dd><dl><dt><span class="section"><a href="wb-sql-editor-main-menu.html">6.7.1. Main Menu</a></span></dt><dt><span class="section"><a href="wb-sql-editor-toolbar.html">6.7.2. Toolbar</a></span></dt><dt><span class="section"><a href="wb-sql-editor-query-panel.html">6.7.3. SQL Query Panel</a></span></dt><dt><span class="section"><a href="wb-sql-editor-main-tabsheets.html">6.7.4. Main Tabsheets</a></span></dt><dt><span class="section"><a href="wb-sql-editor-sidebar.html">6.7.5. Sidebar</a></span></dt></dl></dd></dl></div><p>
    MySQL Workbench provides extensive facilities for working directly with
    SQL code. Before working directly with a live server, a connection
    must be created. After a connection is established, it is possible
    to execute SQL code directly on the server and manipulate the server
    using SQL code.
  </p><p>
    The starting point for embarking on SQL Development work is the SQL
    Development area of the Home window, which has the following action
    items:
  </p><div class="itemizedlist"><ul type="disc"><li><p>
        Open Connection to start Querying
      </p></li><li><p>
        New Connection
      </p></li><li><p>
        Edit Table Data
      </p></li><li><p>
        Edit SQL Script
      </p></li><li><p>
        Manage Connections
      </p></li></ul></div><p>
    The following sections describe each of these action items.
  </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
      The SQL Development facility in MySQL Workbench provides the
      functionality that was formerly available in MySQL Query Browser.
    </p></div></div></body></html>


path: /wb-html-guitools/wb-routines-routine-groups.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.7.4. Creating Routines and Routine Groups</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-working-with-models.html" title="7.7. Working with Models"><link rel="prev" href="wb-modifying-view.html" title="7.7.3.4. Modifying a View Using the Properties Palette"><link rel="next" href="wb-routines.html" title="7.7.4.1. Routines"></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-routines-routine-groups"></a>7.7.4. Creating Routines and Routine Groups</h3></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-routines.html">7.7.4.1. Routines</a></span></dt><dt><span class="section"><a href="wb-routine-groups.html">7.7.4.2. Routine Groups</a></span></dt></dl></div><p>
    You can add Routine Groups to a database either from the
    <span class="guilabel">Physical Schemata</span> section of the
    <span class="guilabel">MySQL Model</span> page or from an EER Diagram.
    Routines may be added only from the <span class="guilabel">Physical
    Schemata</span> section of the <span class="guilabel">MySQL Model</span>
    page.
  </p><p>
    To view an existing schema, along with its Routines and Routine
    Groups, choose <span class="guimenu">Database</span>, <span class="guimenuitem">Reverse
    Engineer...</span> from the main menu. After the schema has
    been added to the current model, you can see the schema objects on
    the <span class="guilabel">Physical Schemata</span> panel on the
    <span class="guilabel">MySQL Model</span> page. The Routines and Routine
    Groups are listed there.
  </p><p>
    MySQL Workbench unifies both stored procedures and stored functions
    into one logical object called a Routine. Routine Groups are used to
    group routines that are related. You can decide how many Routine
    Groups you want to create and you can use the <span class="guilabel">Routine
    Group Editor</span> to assign specific routines to a group,
    using a drag and drop interface.
  </p><p>
    When designing an EER Diagram, you can place the Routine Groups on
    the canvas by dragging them from the <span class="guilabel">Catalog
    Palette</span>. Placing individual routines on the diagram is
    not permitted, as it would clutter the canvas.
  </p></div></body></html>


path: /wb-html-guitools/wb-tutorials.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.8. Modeling Tutorials</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-database-diff-report.html" title="7.7.10.4. Creating a Catalog Diff Report"><link rel="next" href="wb-importing-sql-script.html" title="7.8.1. Importing a Data Definition SQL Script"></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-tutorials"></a>7.8. Modeling Tutorials</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-importing-sql-script.html">7.8.1. Importing a Data Definition SQL Script</a></span></dt><dt><span class="section"><a href="wb-default-schema.html">7.8.2. Using the Default Schema</a></span></dt><dt><span class="section"><a href="wb-basic-modeling.html">7.8.3. Basic Modeling</a></span></dt><dt><span class="section"><a href="wb-documenting-sakila.html">7.8.4. Documenting the <code class="literal">sakila</code> Database</a></span></dt></dl></div><p>
    This chapter contains three short tutorials intended to familiarize
    you with the basics of MySQL Workbench. These tutorials show how
    MySQL Workbench can be used both to design and to document databases.
  </p><p>
    Creating a database from scratch is the focus of
    <a href="wb-default-schema.html" title="7.8.2. Using the Default Schema">Section 7.8.2, “Using the Default Schema”</a> and exploring the graphic design
    capabilities of MySQL Workbench is touched upon in
    <a href="wb-basic-modeling.html" title="7.8.3. Basic Modeling">Section 7.8.3, “Basic Modeling”</a>. Both these tutorials show the
    database design capabilities of MySQL Workbench.
  </p><p>
    Importing an SQL data definition script is probably the quickest way
    to familiarize yourself with MySQL Workbench—this tutorial makes
    use of the <code class="literal">sakila</code> database and emphasizes the use
    of MySQL Workbench as a documentation tool. Examples taken from the
    <code class="literal">sakila</code> database are used throughout the
    documentation, so doing this tutorial can be very helpful in
    understanding MySQL Workbench.
  </p></div></body></html>


path: /wb-html-guitools/wb-scripting-modules-palettes.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>9.5.3. The Globals, Classes, and Modules Tabs</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-scripting-shell.html" title="9.5. The Workbench Scripting Shell"><link rel="prev" href="wb-scripting-shell-window.html" title="9.5.2. The Shell Window"><link rel="next" href="wb-tutorial-plugins.html" title="9.6. Tutorial: Writing Plugins"></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-scripting-modules-palettes"></a>9.5.3. The Globals, Classes, and Modules Tabs</h3></div></div></div><p>
        The Workbench Scripting Shell features the <span class="guilabel">Globals</span>,
        <span class="guilabel">Classes</span> and <span class="guilabel">Modules</span>
        tabs, in addition to the main <span class="guilabel">Shell</span> tab.
      </p><p>
        <span class="bold"><strong>The Globals Tab</strong></span>
      </p><p>
        At the top of the window is a list that is used to select the
        starting point, or root, of the GRT Globals tree displayed
        beneath it. By default, this starting point is the root of the
        tree, that is, '/'. You can expand or collapse the GRT Globals
        tree as desired. The GRT Globals tree is the structure in which
        MySQL Workbench stores document data. Clicking any item results in
        its name and value being displayed in the panel below the tree.
      </p><p>
        <span class="bold"><strong>The Classes Tab</strong></span>
      </p><p>
        A <code class="literal">class</code> is a user-defined data type formed by
        combining primitive data types: integers, doubles, strings,
        dicts, lists, and objects. This tab shows the definitions of the
        classes used by the objects in the <span class="guilabel">Modules</span>
        tab. Clicking a class causes a brief description of the class to
        be displayed in a panel below the classes explorer.
      </p><p>
        When the <span class="guilabel">Classes</span> tab is selected, the list
        displays the following items:
      </p><div class="itemizedlist"><ul type="disc"><li><p>
            <span class="guilabel">Group by Name</span>: Group by the object name
          </p></li><li><p>
            <span class="guilabel">Group by Hierarchy</span>: Group by
            inheritance
          </p></li><li><p>
            <span class="guilabel">Group by Package</span>: Group by
            functionality
          </p></li></ul></div><p>
        The default view for this tab is <span class="guilabel">Group By
        Name</span>. This view shows all the different objects
        arranged alphabetically. Click the <span class="guibutton">+</span> icon
        or double-click a package to show the properties of the struct.
      </p><p>
        If you switch to the hierarchical view, you will see
        <code class="literal">GrtObject</code>: the parent object from which all
        other objects are derived.
      </p><p>
        <span class="bold"><strong>The Modules Tab</strong></span>
      </p><p>
        The <span class="guilabel">Modules</span> tab enables you to browse the
        MySQL Workbench installed modules and their functions. Clicking a
        module within the explorer causes its details to be displayed in
        a panel below the explorer. This facility is useful for
        exploring the available modules, and their supported functions.
        It is also a way to check whether custom modules have been
        correctly installed.
      </p></div></body></html>


path: /wb-html-guitools/wb-new-server-instance-wizard.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>8.6.1. New Server Instance Wizard</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-managing-server-instances.html" title="8.6. Creating and Managing Server Instances"><link rel="prev" href="wb-managing-server-instances.html" title="8.6. Creating and Managing Server Instances"><link rel="next" href="wb-manage-server-instance-dialog.html" title="8.6.2. Manage Server Instances Dialog"></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-new-server-instance-wizard"></a>8.6.1. New Server Instance Wizard</h3></div></div></div><p>
        Clicking the New Server Instance action item launches the
        <span class="guilabel">Create a new server instance</span> wizard. The
        wizard provides a step-by-step approach to creating a new server
        instance. This is most suitable for beginners. Users who are
        familiar with the various settings and parameters can also
        quickly create a new instance from the Manage Server Instances
        dialog discussed later.
      </p><p>
        The steps presented in the wizard are as follows:
      </p><div class="orderedlist"><ol type="1"><li><p>
            Specify Host Machine
          </p></li><li><p>
            Database Connection
          </p></li><li><p>
            Test DB Connection
          </p></li><li><p>
            Management and OS
          </p></li><li><p>
            SSH Configuration
          </p></li><li><p>
            Windows Management
          </p></li><li><p>
            Test Settings
          </p></li><li><p>
            Review Settings
          </p></li><li><p>
            MySQL Config File
          </p></li><li><p>
            Specify Commands
          </p></li><li><p>
            Complete Setup
          </p></li></ol></div><p>
        <span class="bold"><strong>Specify host machine</strong></span>
      </p><p>
        On this page you can select <span class="guilabel">Localhost</span> if
        you intend to manage a server on your local machine. If you
        select <span class="guilabel">Remote Host</span>, you must provide the IP
        address or the network name of the remote server. Or,
        <span class="guilabel">Take Parameters from Existing Database
        Connection</span> utilizes a pre-existing connection as
        defined within MySQL Workbench. Click <span class="guibutton">Next</span> to
        continue.
      </p><p>
        <span class="bold"><strong>Database Connection</strong></span>
      </p><p>
        This page enables you to select a connection to a specific
        database. The settings entered previously have been concerned
        with the connection to the server required for administrative
        purposes. This page is concerned with connecting to a specific
        database. You can either launch the Manage DB Connections dialog
        or select a pre-existing connection from a list. The former is
        most useful if you have not created any connections. If you must
        create a connection at this point, refer to
        <a href="wb-manage-db-connections.html" title="6.6. Manage DB Connections Dialog">Section 6.6, “Manage DB Connections Dialog”</a>. After a connection
        has been selected, click <span class="guibutton">Next</span> to
        continue.
      </p><p>
        <span class="bold"><strong>Test DB Connection</strong></span>
      </p><p>
        On this page, MySQL Workbench tests your database connection and
        displays the results. If an error occurs, you are directed to
        view the logs, which can be done by clicking the <span class="guibutton">Show
        Logs</span> button.
      </p><p>
        <span class="bold"><strong>Management and OS</strong></span>
      </p><p>
        Used to specify a remote management type and target operating
        system, which is available when the Host Machine is defined as a
        remote host.
      </p><p>
        The SSH login based management option includes configuration
        entries for the Operating System and MySQL Installation Type.
      </p><p>
        <span class="bold"><strong>SSH Configuration</strong></span>
      </p><p>
        If you specified a Remote Host on the Specify Host Machine page,
        you will be presented with the Host SSH Connection page, that
        enables you to use SSH for the connection to the server
        instance. This facility enables you to create a secure
        connection to remotely administer and configure the server
        instance. You must enter the host name and user name of the
        account that will be used to log in to the server for
        administration and configuration activities. If you do not enter
        the optional SSH Key for use with the server, then you will be
        prompted for the password when the connection is established by
        MySQL Workbench.
      </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
          This connection is to enable remote administration and
          configuration of the MySQL Server itself. It is not the same
          as the connection used to connect to a server for general
          database manipulation.
        </p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
          You must use an SSH connection type when managing a remote
          server if you wish to start or stop the server or edit its
          configuration file. Other administrative functions do not
          require an SSH connection.
        </p></div><p>
        <span class="bold"><strong>Windows Management</strong></span>
      </p><p>
        If a Windows server is used, then the Windows configuration
        parameters must be set. Windows management requires a user
        account with the required privileges to query the system status,
        and to control services. And read/write access to the
        configuration file is needed to allow editing of the file.
      </p><p>
        <span class="bold"><strong>Test Settings</strong></span>
      </p><p>
        On the next page your settings are tested and the wizard reports
        back the results after attempting to connect to the server. If
        an error occurs, you are directed to view the logs, which can be
        done by clicking the <span class="guibutton">Show Logs</span> button.
      </p><p>
        MySQL Workbench must know where the MySQL Server configuration file
        is located to be able to display configuration information. The
        wizard is able to determine the most likely location of the
        configuration file, based on the selection made on the Operating
        System page of the wizard. However, it is possible to test that
        this information is correct by clicking the <span class="guibutton">Check
        path</span> and <span class="guibutton">Check section</span>
        buttons. The wizard then reports whether the configuration file
        and server configuration section can in fact be accessed. It is
        also possible to manually enter the location of the
        configuration file, and the section pertaining to MySQL Server
        data; these manually entered values should be tested using the
        buttons provided. Click the <span class="guibutton">Next</span> button
        to continue.
      </p><p>
        <span class="bold"><strong>Review Settings</strong></span>
      </p><p>
        The modified settings may be reviewed, which also includes the
        default values. Check the Change Parameters checkbox if the the
        MySQL Config File section will be edited, and then click
        <span class="guibutton">Next</span> to continue.
      </p><p>
        <span class="bold"><strong>MySQL Config File</strong></span>
      </p><p>
        Allows configuration of the MySQL server version. It also allows
        the editing and validation of the configuration file path, and
        validation of the server instance section. Click
        <span class="guibutton">Next</span> to continue.
      </p><p>
        <span class="bold"><strong>Specify Commands</strong></span>
      </p><p>
        This page enables you to set the commands required to start,
        stop, and check the status of the running server instance. It is
        possible to customize the commands if required, but the defaults
        should be suitable in most cases. The defaults are set based on
        the options selected in the Operating System page of the wizard.
        Click <span class="guibutton">Next</span> to continue.
      </p><p>
        <span class="bold"><strong>Complete Setup</strong></span>
      </p><p>
        On this page, you finally assign a name to the server instance.
        This name is used in various parts of the GUI to enable you to
        refer to this instance. After setting a suitable name, click
        <span class="guibutton">Finish</span> to save the instance.
      </p></div></body></html>


path: /wb-html-guitools/wb-foreign-key-relationships.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.7.2. Creating Foreign Key Relationships</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-table-editor.html" title="7.7.1.3. The MySQL Table Editor"><link rel="next" href="wb-relationship-tools.html" title="7.7.2.1. Adding Foreign Key Relationships Using an EER Diagram"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-foreign-key-relationships"></a>7.7.2. Creating Foreign Key Relationships</h3></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-relationship-tools.html">7.7.2.1. Adding Foreign Key Relationships Using an EER Diagram</a></span></dt><dt><span class="section"><a href="wb-relationship-editor.html">7.7.2.2. The Relationship Editor</a></span></dt><dt><span class="section"><a href="wb-connection-properties.html">7.7.2.3. Connection Properties</a></span></dt></dl></div><p>
    Foreign key constraints are supported for the
    <code class="literal">InnoDB</code> storage engine only. For other storage
    engines, the foreign key syntax is correctly parsed but not
    implemented. For more information, see
    <a href="http://dev.mysql.com/doc/refman/5.1/en/ansi-diff-foreign-keys.html">Foreign Keys</a>.
  </p><p>
    Using MySQL Workbench you may add a foreign key from within the table
    editor or by using the relationship tools on the vertical toolbar of
    an EER Diagram. This section deals with adding a foreign key using
    the foreign key tools. To add a foreign key using the table editor,
    see <a href="wb-table-editor.html#wb-table-editor-foreign-keys-tab" title="7.7.1.3.5. The Foreign Keys Tab">Section 7.7.1.3.5, “The Foreign Keys Tab”</a>.
  </p><p>
    The graphical tools for adding foreign keys are most effective when
    you are building tables from the ground up. If you have imported a
    database using an SQL script and need not add columns to your
    tables, you may find it more effective to define foreign keys using
    the table editor.
  </p></div></body></html>


path: /wb-html-guitools/wb-images.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.7.8. Creating Images</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-text-object-editor.html" title="7.7.7.2. The Text Object Editor"><link rel="next" href="wb-using-image-tool.html" title="7.7.8.1. Adding Images to an EER Diagram"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-images"></a>7.7.8. Creating Images</h3></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-using-image-tool.html">7.7.8.1. Adding Images to an EER Diagram</a></span></dt><dt><span class="section"><a href="wb-image-editor.html">7.7.8.2. The Image Editor</a></span></dt></dl></div><p>
    Images exist only on the EER Diagram canvas; you can add them only
    from the EER Diagram window.

    
  </p></div></body></html>


path: /wb-html-guitools/wb-data-modeling-menus.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. Modeling Menus</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-model-editor.html" title="7.5. Model Editor"><link rel="next" href="wb-file-menu.html" title="7.5.1.1. The File Menu"></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-data-modeling-menus"></a>7.5.1. Modeling Menus</h3></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-file-menu.html">7.5.1.1. The File Menu</a></span></dt><dt><span class="section"><a href="wb-edit-menu.html">7.5.1.2. The Edit Menu</a></span></dt><dt><span class="section"><a href="wb-view-menu.html">7.5.1.3. The View Menu</a></span></dt><dt><span class="section"><a href="wb-arrange-menu.html">7.5.1.4. The Arrange Menu</a></span></dt><dt><span class="section"><a href="wb-model-menu.html">7.5.1.5. The Model Menu</a></span></dt><dt><span class="section"><a href="wb-database-menu.html">7.5.1.6. The Database Menu</a></span></dt><dt><span class="section"><a href="wb-plugins-menu.html">7.5.1.7. The Plugins Menu</a></span></dt><dt><span class="section"><a href="wb-scripting-menu.html">7.5.1.8. The Scripting Menu</a></span></dt><dt><span class="section"><a href="wb-community-menu.html">7.5.1.9. The Community Menu</a></span></dt><dt><span class="section"><a href="wb-help-menu.html">7.5.1.10. The Help Menu</a></span></dt></dl></div><p>
    Some menu items are not available in the OSS version of this
    application, and are available only in the Standard Edition. This is
    indicated where applicable.
  </p></div></body></html>


path: /wb-html-guitools/wb-manage-db-connections-standard.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>6.6.2. Standard TCP/IP 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-vault.html" title="6.6.1. The Password Storage Vault"><link rel="next" href="wb-manage-db-connections-socket.html" title="6.6.3. Local Socket/Pipe Connection"></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-standard"></a>6.6.2. Standard TCP/IP Connection</h3></div></div></div><p>
      This connection method enables MySQL Workbench to connect to MySQL
      Server using TCP/IP.
    </p><p>
      <span class="bold"><strong>Parameters tab</strong></span>
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <span class="guilabel">Hostname</span>: The host name or IP address of
          the MySQL server.
        </p></li><li><p>
          <span class="guilabel">Username</span>: User name to use for the
          connection.
        </p></li><li><p>
          <span class="guilabel">Password</span>: Optional password for the
          account used. If you enter no password here, you will be
          prompted to enter the password when MySQL Workbench attempts to
          establish the connection. MySQL Workbench can store the password
          in a vault (see
          <a href="wb-manage-db-connections-vault.html" title="6.6.1. The Password Storage Vault">Section 6.6.1, “The Password Storage Vault”</a>).
        </p></li><li><p>
          <span class="guilabel">Port</span>: The TCP/IP port on which the MySQL
          server is listening (the default is 3306).
        </p></li><li><p>
          <span class="guilabel">Default Schema</span>: When the connection to
          the server is established, this is the schema that will be
          used by default. It becomes the default schema for use in
          other parts of MySQL Workbench.
        </p></li></ul></div><p>
      <span class="bold"><strong>Advanced tab</strong></span>
    </p><p>
      More parameters can be set for the connection by using the
      <span class="guilabel">Advanced</span> tab.
    </p><div class="figure"><a name="wb-manage-db-connections-advanced"></a><p class="title"><b>Figure 6.2. Manage DB Connections - Advanced Tab</b></p><div class="mediaobject"><img src="images/wb-manage-db-connections-advanced.png" width="898" height="498" alt="Manage DB Connections - Advanced
          Tab"></div></div><p>
      The <span class="guilabel">Advanced</span> tab includes these check boxes:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <span class="guilabel">Use compression protocol</span>: If checked, the
          communication between the application and the MySQL server
          will be compressed, which may increase transfer rates. This
          corresponds to starting a MySQL command-line client with the
          <code class="option">--compress</code> option.
        </p></li><li><p>
          <span class="guilabel">Use SSL if available</span>: This option turns
          on SSL encryption. The client library must support this
          option. Note: This feature is currently not supported.
        </p></li><li><p>
          <span class="guilabel">Use ANSI quotes to quote identifiers</span>:
          Treat “<span class="quote">"</span>” as an identifier quote character (like
          the “<span class="quote">`</span>” quote character) and not as a string
          quote character. You can still use “<span class="quote">`</span>” to quote
          identifiers with this mode enabled. With this option enabled,
          you cannot use double quotation marks to quote literal
          strings, because it is interpreted as an identifier. Note: If
          this option is selected, it overrides the server setting.
        </p></li></ul></div></div></body></html>


path: /wb-html-guitools/license-ctemplate.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>B.5. CTemplate (Google Template System) 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-cairo.html" title="B.4. Cairo License"><link rel="next" href="license-libcurl.html" title="B.6. cURL (libcurl) 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-ctemplate"></a>B.5. CTemplate (Google Template System) License</h2></div></div></div><p>
    The following software may be included in this product:
  </p><pre class="programlisting">CTemplate (Google Template System) 

Copyright (c) 2005, Google Inc.
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 Google Inc. 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-sql-editor-output-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.2. Output 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-overview-tabsheet.html" title="6.7.4.1. Overview Tabsheet"><link rel="next" href="wb-sql-editor-history-tabsheet.html" title="6.7.4.3. History 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-output-tabsheet"></a>6.7.4.2. Output Tabsheet</h4></div></div></div><p>
          The Output tabsheet displays a summary of the communication
          between the script and the server. The messages displayed can
          be information or errors. Each message displays the time, the
          action that was carried out, and the response from the server.
          This output is useful for troubleshooting scripts.
        </p></div></body></html>


path: /wb-html-guitools/license-glib-wb.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>B.9. GLib License (for MySQL Workbench)</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-third-party-licenses.html" title="Appendix B. Third Party Licenses"><link rel="prev" href="license-dojo-toolkit.html" title="B.8. Dojo Toolkit v1.7.0b1 License"><link rel="next" href="license-glitz.html" title="B.10. Glitz 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-glib-wb"></a>B.9. GLib License (for MySQL Workbench)</h2></div></div></div><p>
    The following software may be included in this product:
  </p><pre class="programlisting">
GLib

You are receiving a copy of the GLib library in both source and
object code in the following folder: C:\Program Files
(x86)\MySQL\MySQLWorkbench 5.2\ on Windows and
MySQLWorkbench.app/Contents/Frameworks on Mac OS X. The terms of
the Oracle license do NOT apply to the GLib library; it is licensed
under the following license, separately from the Oracle programs
you receive. If you do not wish to install this library, you may
go to the folder C:\Program Files (x86)\MySQL\MySQL Workbench 5.2\
and remove or replace the libglib-2.0-0.dll, libgmodule-2.0-0.dll,
libgobject-2.0-0.dll and libgthread-2.0-0.dll files if present on
Windows or go to the folder MySQLWorkbench.app/Contents/Frameworks
and remove or replace the files libglib-2.*.dylib, libgmodule-2.*.dylib
and libgthread-2.*.dylib on Mac OS X, but the Oracle program might
not operate properly or at all without the library.
</pre><p>
    This component is licensed under
    <a href="license-gnu-lgpl-2-1.html" title="B.11. GNU Lesser General Public License Version 2.1, February 1999">Section B.11, “GNU Lesser General Public License Version 2.1, February 1999”</a>.
  </p></div></body></html>


path: /wb-html-guitools/wb-table-editor.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.7.1.3. The MySQL Table 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-tables.html" title="7.7.1. Creating Tables"><link rel="prev" href="wb-using-table-tool.html" title="7.7.1.2. Adding Tables to an EER Diagram"><link rel="next" href="wb-foreign-key-relationships.html" title="7.7.2. Creating Foreign Key Relationships"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-table-editor"></a>7.7.1.3. The MySQL Table Editor</h4></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-table-editor.html#wb-table-editor-main-window">7.7.1.3.1. The Main Editor Window</a></span></dt><dt><span class="section"><a href="wb-table-editor.html#wb-table-editor-table-tab">7.7.1.3.2. The Table Tab</a></span></dt><dt><span class="section"><a href="wb-table-editor.html#wb-table-editor-columns-tab">7.7.1.3.3. The Columns Tab</a></span></dt><dt><span class="section"><a href="wb-table-editor.html#wb-table-editor-indexes-tab">7.7.1.3.4. The Indexes Tab</a></span></dt><dt><span class="section"><a href="wb-table-editor.html#wb-table-editor-foreign-keys-tab">7.7.1.3.5. The Foreign Keys Tab</a></span></dt><dt><span class="section"><a href="wb-table-editor.html#wb-table-editor-triggers-tab">7.7.1.3.6. The Triggers Tab</a></span></dt><dt><span class="section"><a href="wb-table-editor.html#wb-table-editor-partitioning-tab">7.7.1.3.7. The Partitioning Tab</a></span></dt><dt><span class="section"><a href="wb-table-editor.html#wb-table-editor-options-tab">7.7.1.3.8. The Options Tab</a></span></dt><dt><span class="section"><a href="wb-table-editor.html#wb-table-editor-inserts-tab">7.7.1.3.9. The Inserts Tab</a></span></dt><dt><span class="section"><a href="wb-table-editor.html#wb-table-editor-privileges-tab">7.7.1.3.10. The Privileges Tab</a></span></dt></dl></div><p>
    The MySQL Table Editor is a component that enables the creation and
    modification of tables. You can add or modify a table's columns or
    indexes, change the engine, add foreign keys, or alter the table's
    name.
  </p><p>
    The MySQL Table Editor can be accessed from the MySQL Workbench by first
    selecting the <span class="guilabel">MySQL Model</span> tab, then
    double-clicking a table in the <code class="literal">Physical Schemata</code>
    panel. You can also access MySQL Table Editor from an EER Diagram by
    double-clicking a table object.
  </p><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="wb-table-editor-main-window"></a>7.7.1.3.1. The Main Editor Window</h5></div></div></div><p>
      Any number of tables may be edited in the MySQL Table Editor at any
      one time. Adding another table creates a new tab at the top of the
      editor. By default, the MySQL Table Editor appears docked at the
      bottom of the application.
    </p><p>
      The MySQL Table Editor is shown in the following figure.
    </p><div class="figure"><a name="wb-table-editor-overview-figure"></a><p class="title"><b>Figure 7.8. The Table Editor</b></p><div class="mediaobject"><img src="images/wb-table-editor-overview.png" width="779" height="296" alt="The table editor"></div></div><p>
      The MySQL Table Editor provides a work space that has tabs used to
      perform these actions:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <span class="guilabel">Table</span>: Edit features that apply to the
          table as a whole
        </p></li><li><p>
          <span class="guilabel">Columns</span>: Add or modify columns
        </p></li><li><p>
          <span class="guilabel">Indices</span>: Add or modify indexes
        </p></li><li><p>
          <span class="guilabel">Foreign Keys</span>: Add or modify foreign keys
        </p></li><li><p>
          <span class="guilabel">Triggers</span>: Add or modify triggers
        </p></li><li><p>
          <span class="guilabel">Partitioning</span>: Manage partitioning
        </p></li><li><p>
          <span class="guilabel">Options</span>: Add or modify various general,
          table, and row options
        </p></li><li><p>
          <span class="guilabel">Inserts</span>: Write <code class="literal">INSERT</code>
          statements
        </p></li><li><p>
          <span class="guilabel">Privileges</span>: Set privileges on the table
        </p></li></ul></div><p>
      The following sections discuss these tabs in further detail.
    </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="wb-table-editor-table-tab"></a>7.7.1.3.2. The Table Tab</h5></div></div></div><p>
      Use the <span class="guilabel">Table</span> tab to edit the table name,
      collation, storage engine, or comment.
    </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="wb-table-editor-columns-tab"></a>7.7.1.3.3. The Columns Tab</h5></div></div></div><p>
      Use the <span class="guilabel">Columns</span> tab to display and edit all
      the column information for a table. With this tab, you can add,
      drop, and alter columns.
    </p><p>
      You can also use the <span class="guilabel">Columns</span> tab to change
      column properties such as name, data type, and default value.
    </p><div class="figure"><a name="wb-table-editor-columns-figure"></a><p class="title"><b>Figure 7.9. The Columns Tab</b></p><div class="mediaobject"><img src="images/wb-table-editor-columns-tab.png" width="782" height="301" alt="The columns tab"></div></div><p>
      Right-click a row under the <code class="literal">Column Name</code> column
      to open a pop-up menu with the following items:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <span class="guimenuitem">Move Up</span>: Move the selected column
          up.
        </p></li><li><p>
          <span class="guimenuitem">Move Down</span>: Move the selected column
          down.
        </p></li><li><p>
          <span class="guimenuitem">Delete Selected Columns</span>: Select
          multiple contiguous columns by right-clicking and pressing the
          <span><strong class="keycap">Shift</strong></span> key. Use the <span><strong class="keycap">Control</strong></span>
          key to select noncontiguous columns.
        </p></li><li><p>
          <span class="guimenuitem">Refresh</span>: Update all information in
          the <span class="guilabel">Columns</span> tab.
        </p></li><li><p>
          <span class="guimenuitem">Clear Default</span>: Clear the assigned
          default value.
        </p></li><li><p>
          <span class="guimenuitem">Default NULL</span>: Set the column
          default value to <code class="literal">NULL</code>.
        </p></li><li><p>
          <span class="guimenuitem">Default 0</span>: Set the column default
          value to <code class="literal">0</code>.
        </p></li></ul></div><p>
      To add a column, click the <code class="literal">Column Name</code> field in
      an empty row and enter an appropriate value. Select a data type
      from the <span class="guilabel">Datatype</span> list. Select a column
      property check box as required according to the following list of
      column properties:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <span class="guilabel">PK</span>: Primary key
        </p></li><li><p>
          <span class="guilabel">NN</span>: Not null
        </p></li><li><p>
          <span class="guilabel">UQ</span>: Unique
        </p></li><li><p>
          <span class="guilabel">BIN</span>: Binary
        </p></li><li><p>
          <span class="guilabel">UN</span>: Unsigned
        </p></li><li><p>
          <span class="guilabel">ZF</span>: Zerofill
        </p></li><li><p>
          <span class="guilabel">AI</span>: Auto-increment
        </p></li></ul></div><p>
      To change the name, data type, default value, or comment of a
      column, double-click the value you wish to change. The content
      then becomes editable.
    </p><p>
      You can also add column comments to the <code class="literal">Column
      Comment</code> field. It is also possible to set the column
      collation, using the list in the <span class="guilabel">Column
      Details</span> panel.
    </p><p>
      To the left of the column name is an icon that indicates whether
      the column is a member of the primary key. If the icon is a small
      key, that column belongs to the primary key, otherwise the icon is
      a blue diamond or a white diamond. A blue diamond indicates the
      column has <span class="guilabel">NN</span> set. To add or remove a column
      from the primary key, double-click the icon. You can also add a
      primary key by checking the <code class="literal">PRIMARY KEY</code> check
      box in the <code class="literal">Column Details</code> section of the table
      editor.
    </p><p>
      If you wish to create a composite primary key you can select
      multiple columns and check the PK check box. However, there is an
      additional step that is required, you must click the Indexes tab,
      then in the Index Columns panel you must set the desired order of
      the primary keys.
    </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
        When entering default values, in the case of
        <code class="literal">CHAR</code> and <code class="literal">VARCHAR</code> data
        types MySQL Workbench will attempt to automatically add quotation
        marks, if the user does not start their entry with one. For
        other data types the user must manage quoting if required, as it
        will not be handled automatically by MySQL Workbench.
      </p></div><div class="caution" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Caution</div><p>
        Care must be taken when entering a default value for
        <code class="literal">ENUM</code> columns because a nonnumeric default
        will not be automatically quoted. You must manually add single
        quote characters for the default value. Note that MySQL Workbench
        will <span class="bold"><strong>not</strong></span> prevent you from
        entering the default value without the single quotation marks.
        If a nonnumeric default value is entered without quotation
        marks, this will lead to errors. For example, if the model is
        reverse engineered, the script will contain unquoted default
        values for <code class="literal">ENUM</code> columns and will fail if an
        attempt is made to run the script on MySQL Server.
      </p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="wb-table-editor-indexes-tab"></a>7.7.1.3.4. The Indexes Tab</h5></div></div></div><p>
      The <span class="guilabel">Indexes</span> tab holds all index information
      for your table. Use this tab to add, drop, and modify indexes.
    </p><div class="figure"><a name="wb-table-editor-indexes-tab-figure"></a><p class="title"><b>Figure 7.10. The Indexes Tab</b></p><div class="mediaobject"><img src="images/wb-table-editor-indexes-tab.png" width="781" height="302" alt="The indexes tab"></div></div><p>
      Select an index by right-clicking it. The <span class="guilabel">Index
      Columns</span> section displays information about the selected
      index.
    </p><p>
      To add an index, click the last row in the index list. Enter a
      name for the index and select the index type from the list. Select
      the column or columns that you wish to index by checking the
      column name in the <span class="guilabel">Index Columns</span> list. You
      can remove a column from the index by removing the check mark from
      the appropriate column.
    </p><p>
      You can also specify the order of an index by choosing
      <code class="literal">ASC</code> or <code class="literal">DESC</code> under the
      <code class="literal">Order</code> column. Create an index prefix by
      specifying a numeric value under the <code class="literal">Length</code>
      column. You cannot enter a prefix value for fields that have a
      data type that does not support prefixing.
    </p><p>
      To drop an index, right-click the row of the index you wish to
      delete, then select the <span class="guimenuitem">Delete Selected
      Indexes</span> menu item.
    </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="wb-table-editor-foreign-keys-tab"></a>7.7.1.3.5. The Foreign Keys Tab</h5></div></div></div><p>
      The <span class="guilabel">Foreign Keys</span> tab is organized in much the
      same fashion as the <span class="guilabel">Indexes</span> tab and adding or
      editing a foreign key is similar to adding or editing an index.
    </p><p>
      To add a foreign key, click the last row in the <code class="literal">Foreign
      Key Name</code> list. Enter a name for the foreign key and
      select the column or columns that you wish to index by checking
      the column name in the <span class="guilabel">Column</span> list. You can
      remove a column from the index by removing the check mark from the
      appropriate column.
    </p><p>
      Under <span class="guilabel">Foreign Key Options</span>, choose an action
      for the update and delete events. The options are:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <span class="guimenuitem">RESTRICT</span>
        </p></li><li><p>
          <span class="guimenuitem">CASCADE</span>
        </p></li><li><p>
          <span class="guimenuitem">SET NULL</span>
        </p></li><li><p>
          <span class="guimenuitem">NO ACTION</span>
        </p></li></ul></div><p>
      To drop a foreign key, right-click the row you wish to delete,
      then select the <span class="guimenuitem">Delete Selected FKs</span>
      menu item.
    </p><p>
      To modify properties of a foreign key, select it and make the
      desired changes.
    </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="wb-table-editor-triggers-tab"></a>7.7.1.3.6. The Triggers Tab</h5></div></div></div><p>
      The <span class="guilabel">Triggers</span> tab opens a field for editing an
      existing trigger or creating a new trigger. Create a trigger as
      you would from the command line.
    </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="wb-table-editor-partitioning-tab"></a>7.7.1.3.7. The Partitioning Tab</h5></div></div></div><p>
      To enable partitioning for your table, check the <span class="guilabel">Enable
      Partitioning</span> check box. This enables the partitioning
      options.
    </p><p>
      The <span class="guimenu">Partition By</span> pop-up menu displays the types
      of partitions you can create:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <span class="guimenuitem">HASH</span>
        </p></li><li><p>
          <span class="guimenuitem">LINEAR HASH</span>
        </p></li><li><p>
          <span class="guimenuitem">KEY</span>
        </p></li><li><p>
          <span class="guimenuitem">LINEAR KEY</span>
        </p></li><li><p>
          <span class="guimenuitem">RANGE</span>
        </p></li><li><p>
          <span class="guimenuitem">LIST</span>
        </p></li></ul></div><p>
      Use the <span class="guilabel">Parameters</span> field to define any
      parameters to be supplied to the partitioning function, such as an
      integer column value.
    </p><p>
      Choose the number of partitions from the <span class="guilabel">Partition
      Count</span> list. To manually configure your partitions,
      check the <span class="guilabel">Manual</span> check box. This enables
      entry of values into the partition configuration table. The
      entries in this table are:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <code class="literal">Partition</code>
        </p></li><li><p>
          <code class="literal">Values</code>
        </p></li><li><p>
          <code class="literal">Data Directory</code>
        </p></li><li><p>
          <code class="literal">Index Directory</code>
        </p></li><li><p>
          <code class="literal">Min Rows</code>
        </p></li><li><p>
          <code class="literal">Max Rows</code>
        </p></li><li><p>
          <code class="literal">Comment</code>
        </p></li></ul></div><p>
      Subpartitioning is also available. For more information about
      partitioning, see <a href="http://dev.mysql.com/doc/refman/5.1/en/partitioning.html">Partitioning</a>.
    </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="wb-table-editor-options-tab"></a>7.7.1.3.8. The Options Tab</h5></div></div></div><p>
      The <span class="guilabel">Options</span> tab enables you to set several
      types of options, which are grouped into the following sections:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          General Options
        </p></li><li><p>
          Row Options
        </p></li><li><p>
          Storage Options
        </p></li><li><p>
          Merge Table options
        </p></li></ul></div><p>
      The following discussion describes these options in more detail.
    </p><p>
      <span class="bold"><strong>General Options Section</strong></span>
    </p><p>
      In the <span class="guilabel">General Options</span> section, choose a pack
      keys option. The options are <code class="literal">Default</code>,
      <code class="literal">Pack None</code>, and <code class="literal">Pack All</code>. You
      may also encrypt the definition of a table. The
      <code class="literal">AUTO_INCREMENT</code> and delayed key update behaviors
      apply only to <code class="literal">MyISAM</code> tables.
    </p><p>
      <span class="bold"><strong>Row Options Section</strong></span>
    </p><p>
      To set the row format, choose the desired row format from the
      list. For more information about the different row formats that
      are available, see <a href="http://dev.mysql.com/doc/refman/5.1/en/myisam-table-formats.html"><code class="literal">MyISAM</code> Table Storage Formats</a>.
    </p><p>
      These options are:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          Default
        </p></li><li><p>
          Dynamic
        </p></li><li><p>
          Fixed
        </p></li><li><p>
          Compressed
        </p></li><li><p>
          Redundant
        </p></li><li><p>
          Compact
        </p></li></ul></div><p>
      When you expect a table to be particularly large, use the
      <span class="guilabel">Avg. Row</span>, <span class="guilabel">Min. Rows</span>, and
      <span class="guilabel">Max. Rows</span> options to enable the MySQL server
      to better accommodate your data. See
      <a href="http://dev.mysql.com/doc/refman/5.1/en/create-table.html"><code class="literal">CREATE TABLE</code> Syntax</a> for more information on how to use
      these options.
    </p><p>
      <span class="bold"><strong>Storage Options Section</strong></span>
    </p><p>
      The <code class="literal">Storage Options</code> section is available only
      for <code class="literal">MyISAM</code> tables. Use it to configure a custom
      path to the table storage and data files. This can help improve
      server performance by locating different tables on different hard
      drives.
    </p><p>
      <span class="bold"><strong>Merge Table Options Section</strong></span>
    </p><p>
      Use the <code class="literal">Merge Table</code> Options section to
      configure <code class="literal">MERGE</code> tables. To create a
      <code class="literal">MERGE</code> table, select <code class="literal">MERGE</code> as
      your storage engine and then specify the <code class="literal">MyISAM</code>
      tables you wish to merge in the <span class="guilabel">Union Tables</span>
      dialog.
    </p><p>
      You may specify the action the server should take when users
      attempt to perform <code class="literal">INSERT</code> statements on the
      merge table. You may also select the <code class="literal">Merge
      Method</code> by selecting from the list. For more information
      about <code class="literal">MERGE</code> tables, see
      <a href="http://dev.mysql.com/doc/refman/5.1/en/merge-storage-engine.html">The <code class="literal">MERGE</code> Storage Engine</a>.
    </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="wb-table-editor-inserts-tab"></a>7.7.1.3.9. The Inserts Tab</h5></div></div></div><p>
      Use the <span class="guilabel">Inserts</span> tab to insert rows into the
      table.
    </p><p>
      To edit a row, click the field you wish to change and enter the
      new data. Right-clicking a row displays a menu with the following
      items:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          Set Field(s) to NULL: Set the column value to
          <code class="literal">NULL</code>.
        </p></li><li><p>
          Delete Row(s): Delete the selected row or rows.
        </p></li><li><p>
          Copy Row Content: Copies the row to the clipboard. Strings are
          copied quoted, and <code class="literal">NULL</code> values are
          preserved.
        </p></li><li><p>
          Copy Row Content (unquoted): Copies the row to the clipboard.
          Strings are not quoted and <code class="literal">NULL</code> are copied
          as a space.
        </p></li><li><p>
          Copy Field Content: Copies the value of the selected field to
          the clipboard. Strings are quoted.
        </p></li><li><p>
          Copy Field Content (unquoted): Copies the value of the
          selected field to the clipboard. Strings are not quoted.
        </p></li></ul></div><p>
      Note that the insert editor features a toolbar. This has the same
      functionality as explained in
      <a href="wb-sql-editor-results-tabsheets.html" title="6.7.4.5. Results Tabsheets">Section 6.7.4.5, “Results Tabsheets”</a> and
      <a href="wb-sql-editor-live-editing-tabsheets.html" title="6.7.4.6. Live Editing Tabsheets">Section 6.7.4.6, “Live Editing Tabsheets”</a>. You can
      also hover the cursor over the toolbar to display tooltips.
    </p><p>
      Any rows you add will be inserted when you forward engineer the
      database (if you choose the <code class="literal">Generate INSERT statements
      for tables</code> option).
    </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
        When entering string values that there is slightly different
        behavior between the 5.0, 5.1, and 5.2 versions of MySQL Workbench.
      </p><p>
        For 5.0 and 5.1, if a string is entered without leading and
        trailing quotation marks, the Inserts Editor adds quoting and
        escapes characters that require it. However, if quoted text is
        entered, the Inserts Editor performs no further checks and
        assumes that a correctly escaped and quoted sequence has been
        entered.
      </p><p>
        5.2 features a new Inserts Editor. In this case, the user enters
        the string without quoting or escaping and the Inserts Editor
        takes care of all quoting and escaping as required.
      </p></div><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></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="wb-table-editor-privileges-tab"></a>7.7.1.3.10. The Privileges Tab</h5></div></div></div><p>
      Use the <span class="guilabel">Privileges</span> tab to assign specific
      roles and privileges to a table. You may also assign privileges to
      a role using the role editor. For a discussion of this topic, see
      <a href="wb-adding-roles.html" title="7.5.5.1. Adding Roles">Section 7.5.5.1, “Adding Roles”</a>.
    </p><p>
      When this tab is first opened, all roles that have been created
      are displayed in the list on the right. Move the roles you wish to
      associate with this table to the <span class="guilabel">Roles</span> list
      on the left. Do this by selecting a role and then clicking the
      <span class="guibutton">&lt;</span> button. Use the <span><strong class="keycap">Shift</strong></span>
      key to select multiple contiguous roles and the
      <span><strong class="keycap">Control</strong></span> key to select noncontiguous roles.
    </p><p>
      To assign privileges to a role, click the role in the
      <span class="guilabel">Roles</span> list. This displays all available
      privileges in the <span class="guilabel">Assigned Privileges</span> list.
      The privileges that display are:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <code class="literal">ALL</code>
        </p></li><li><p>
          <code class="literal">CREATE</code>
        </p></li><li><p>
          <code class="literal">DROP</code>
        </p></li><li><p>
          <code class="literal">GRANT OPTION</code>
        </p></li><li><p>
          <code class="literal">REFERENCES</code>
        </p></li><li><p>
          <code class="literal">ALTER</code>
        </p></li><li><p>
          <code class="literal">DELETE</code>
        </p></li><li><p>
          <code class="literal">INDEX</code>
        </p></li><li><p>
          <code class="literal">INSERT</code>
        </p></li><li><p>
          <code class="literal">SELECT</code>
        </p></li><li><p>
          <code class="literal">UPDATE</code>
        </p></li><li><p>
          <code class="literal">TRIGGER</code>
        </p></li></ul></div><p>
      You can choose to assign all privileges to a specific user or any
      other privilege as listed previously. Privileges irrelevant to a
      specific table, such as the <code class="literal">FILE</code> privilege, are
      not shown.
    </p><p>
      If a role has already been granted privileges on a specific table,
      those privileges show as already checked in the <span class="guilabel">Assigned
      Privileges</span> list.
    </p></div></div></body></html>


path: /wb-html-guitools/wb-relationship-editor.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.7.2.2. The Relationship 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-foreign-key-relationships.html" title="7.7.2. Creating Foreign Key Relationships"><link rel="prev" href="wb-relationship-tools.html" title="7.7.2.1. Adding Foreign Key Relationships Using an EER Diagram"><link rel="next" href="wb-connection-properties.html" title="7.7.2.3. Connection Properties"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-relationship-editor"></a>7.7.2.2. The Relationship Editor</h4></div></div></div><p>
      Double-clicking a relationship on the EER diagram canvas opens the
      relationship editor. This has two tabs:
      <span class="guilabel">Relationship</span>, and <span class="guilabel">Foreign
      Key</span>.
    </p><p>
      <span class="bold"><strong>The Relationship Tab</strong></span>
    </p><p>
      In the <span class="guilabel">Relationship</span> tab, you can set the
      caption of a relationship using the <span class="guilabel">Caption</span>
      field. This name displays on the canvas and is also the name used
      for the constraint itself. The default value for this name is
      <code class="literal">fk_<em class="replaceable"><code>source_table_destination_table</code></em></code>.
      Use the <span class="guimenu">Model</span> menu, <span class="guimenuitem">Menu
      Options</span> menu item to set a project-specific default
      name for foreign keys. To change the global default, see
      <a href="wb-preferences-model.html" title="5.4.4. The Model Tab">Section 5.4.4, “The Model Tab”</a>.
    </p><p>
      You can also add a secondary caption and a caption to a
      relationship.
    </p><p>
      The <span class="guilabel">Visibility Settings</span> section is used to
      determine how the relationship is displayed on the EER Diagram
      canvas. <code class="literal">Fully Visible</code> is the default but you
      can also choose to hide relationship lines or to use split lines.
      The split line style is pictured in the following figure.
    </p><div class="figure"><a name="wb-drawSplit-image"></a><p class="title"><b>Figure 7.12. The Split Connector</b></p><div class="mediaobject"><img src="images/wb-drawSplit.png" width="221" height="180" alt="The split connector"></div></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
        A broken line connector indicates a nonidentifying relationship.
        The split line style can be used with either an identifying
        relationship or a nonidentifying relationship. It is used for
        display purposes only and does not indicate anything about the
        nature of a relationship.
      </p></div><p>
      To set the notation of a relationship use the
      <span class="guimenu">Model</span> menu, <span class="guimenuitem">Relationship
      Notation</span> menu item. For more information, see
      <a href="wb-model-menu.html#wb-relationship-notation-menu" title="7.5.1.5.4. The Relationship Notation Submenu">Section 7.5.1.5.4, “The Relationship Notation Submenu”</a>.
    </p><p>
      <span class="bold"><strong>The Foreign Key Tab</strong></span>
    </p><p>
      The <span class="guilabel">Foreign Key</span> tab contains several
      sections: <span class="guilabel">Referencing Table</span>,
      <span class="guilabel">Cardinality</span> and <span class="guilabel">Referenced
      Table</span>.
    </p><p>
      The <span class="guilabel">Mandatory</span> check boxes are used to select
      whether the referencing table and the referenced table are
      mandatory. By default, both of these constraints are
      <code class="literal">true</code> (indicated by the check boxes being
      checked).
    </p><p>
      The <span class="guilabel">Cardinality</span> section has a set of radio
      buttons that enable you to choose whether the relationship is
      one-to-one or one-to-many. There is also a check box that enables
      you to specify whether the relationship is an identifying
      relationship.
    </p></div></body></html>


