# web_object

path: /wb-html-guitools/wb-using-image-tool.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.7.8.1. Adding Images 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-images.html" title="7.7.8. Creating Images"><link rel="prev" href="wb-images.html" title="7.7.8. Creating Images"><link rel="next" href="wb-image-editor.html" title="7.7.8.2. The Image 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-image-tool"></a>7.7.8.1. Adding Images to an EER Diagram</h4></div></div></div><p>
      To add images to an EER Diagram, use the <code class="literal">Image</code>
      tool on the vertical toolbar. Make sure that the <span class="guilabel">EER
      Diagram</span> tab is selected, then right-click the image
      icon on the vertical toolbar. The image icon is the icon just
      above the table icon.
    </p><p>
      Clicking the mouse on this icon changes the mouse pointer to an
      image pointer. You can also change the mouse pointer to an image
      pointer by pressing the <span><strong class="keycap">I</strong></span> key.
    </p><p>
      Create an image by clicking anywhere on the EER Diagram canvas.
      This opens a file open dialog box. Select the desired image, then
      close the dialog box to create an image on the canvas. To revert
      to the default mouse pointer, click the arrow icon at the top of
      the vertical toolbar.
    </p><p>
      Right-clicking this object opens a pop-up menu with the following
      items:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <span class="guimenuitem">Cut
          <em class="replaceable"><code>'Image'</code></em></span>
        </p></li><li><p>
          <span class="guimenuitem">Copy
          <em class="replaceable"><code>'Image'</code></em></span>
        </p></li><li><p>
          <span class="guimenuitem">Edit Image...</span>
        </p></li><li><p>
          <span class="guimenuitem">Edit in New Window...</span>
        </p></li><li><p>
          <span class="guimenuitem">Delete
          <em class="replaceable"><code>'Image'</code></em></span>
        </p></li></ul></div><p>
      These menu items function in exactly the same way as they do for
      other objects on an EER diagram. However, images are not database
      objects so there is no confirmation dialog box when they are
      deleted.
    </p></div></body></html>


path: /wb-html-guitools/wb-eraser-tool.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.6.1.3. The Eraser Tool</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-vertical-toolbar.html" title="7.6.1. The Vertical Toolbar"><link rel="prev" href="wb-hand-tool.html" title="7.6.1.2. The Hand Tool"><link rel="next" href="wb-layer-tool.html" title="7.6.1.4. The Layer Tool"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-eraser-tool"></a>7.6.1.3. The Eraser Tool</h4></div></div></div><p>
        Use the eraser tool to delete objects from the EER Diagram
        canvas. Change the mouse pointer to the eraser tool, then click
        the object you wish to delete. Depending upon your settings, the
        delete dialog box should open, asking you to confirm the type of
        deletion.
      </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
          The delete action of the <code class="literal">eraser</code> tool is
          controlled by the general option setting for deletion. Before
          using the eraser tool, be sure that you understand the
          available options described in
          <a href="wb-preferences-model.html" title="5.4.4. The Model Tab">Section 5.4.4, “The Model Tab”</a>.
        </p></div><p>
        To activate the eraser tool from the keyboard, use the
        <span><strong class="keycap">D</strong></span> key.
      </p><p>
        You can also delete an object by selecting it and pressing
        <span><strong class="keycap">Control+Delete</strong></span> or by right-clicking it and
        choosing <span class="guimenuitem">Delete</span> from the pop up menu.
      </p></div></body></html>


path: /wb-html-guitools/wb-news-5-0-14.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.3.18. Changes in MySQL Workbench 5.0.14beta (25 February 2008)</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="changes-5.0.x.html" title="A.3. Changes in Release 5.0"><link rel="prev" href="wb-news-5-0-14a.html" title="A.3.17. Changes in MySQL Workbench 5.0.14abeta (28 February 2008)"><link rel="next" href="wb-third-party-licenses.html" title="Appendix B. Third Party Licenses"></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-14"></a>A.3.18. Changes in MySQL Workbench 5.0.14beta (25 February 2008)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.0.13beta.
      </p><p><span class="bold"><strong>Workbench Improvements in this Version</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        <span class="guimenu">Expand All</span> and <span class="guimenu">Collapse
        All</span> menu options have been added under the
        <span class="guimenu">Arrange</span> menu. The <span class="guimenu">Expand
        All</span> option expands all objects on an EER. This option
        will display a table's columns if the object notation supports
        expansion. Indexes will not automatically be expanded unless
        they were previously expanded and have been collapsed using the
        <span class="guimenu">Collapse All</span> menu option. Some object
        notations, such as <code class="literal">Classic</code>, do not permit
        expansion or contraction. <span class="guimenu">Collapse All</span> undoes
        the operation performed by <span class="guimenu">Expand All</span>.
      </p></li><li><p>
        A <span class="guimenu">Fit Objects to Contents</span> option has been
        added under the <span class="guimenu">Arrange</span> menu option. This
        option expands an object on an EER diagram. For example, if a
        table has a long column name that is not fully displayed, using
        this menu option will expand the table making the column name
        visible.
      </p></li><li><p>
        A <span class="guimenu">System Information</span> menu option has been
        added to the <span class="guimenu">Help</span> menu. This option displays
        information about your system that is useful when reporting a
        big.
      </p></li><li><p>
        An <span class="guimenu">Export as SVG</span> menu option has been added
        under the <span class="guimenu">File</span>, <span class="guimenu">Export</span>
        menu option.
      </p></li><li><p>
        Because of serious performance and display issues Workbench no
        longer uses Mesa. For those users who don't have native OpenGL
        support, Workbench now uses the Windows GDI API. The command
        line switch for using this mode is
        <code class="option">-swrendering</code>. For more information about
        running Workbench from the command line see
        <a href="wb-launching-windows.html" title="3.3.2. Launching MySQL Workbench on Windows">Section 3.3.2, “Launching MySQL Workbench on Windows”</a>.
      </p></li><li><p>
        The GRT inspector has been improved to support new types.
        Namely:
      </p><div class="itemizedlist"><ul type="circle"><li><p>
            text
          </p></li><li><p>
            longtext
          </p></li><li><p>
            bool
          </p></li><li><p>
            color
          </p></li><li><p>
            file
          </p></li></ul></div><p>
        This makes it much easier to change object properties manually.
        Multiple selection support has also been improved—you can
        easily change a value for several selected objects at once.
      </p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        When exporting an SQL CREATE script it was possible to create
        two tables in the same schema with the same name.
       (Bug #34668)</p></li><li><p>
        After placing related tables on an EER diagram and then removing
        them using the <span class="guimenu">Undo</span> menu option, the
        connection lines between related tables no longer showed up.
       (Bug #34601)</p></li><li><p>
        When choosing the <span class="guimenu">Export as PNG</span> menu option
        the file dialogue box file type was <code class="literal">All
        Files</code>instead of <code class="literal">PNG</code>. The same was
        true for <span class="guimenu">Export as singlePage PDF</span> and
        <span class="guimenu">Export as singlePage PS</span>. The default is now
        the appropriate file type.
       (Bug #34548)</p></li><li><p>
        If there was a relationship between table <code class="literal">A</code>
        and table <code class="literal">B</code> and also one between table
        <code class="literal">B</code> and table <code class="literal">A</code>, the
        connection lines appeared on top of each other. Connection lines
        now appear attached at the related columns.
       (Bug #34543)</p></li><li><p>
        When there were multiple tables with long identifiers the
        <code class="literal">Physical Schemata</code> section of the
        <code class="literal">MySQL Model</code> page was messy. Table names were
        obscured and sometimes overlapped. Also, the position of the
        <code class="literal">Add Table</code> icon was not optimal. Now the space
        between table names is adjusted to the largest entry and the
        <code class="literal">Add Table</code> icon is fixed in the upper left
        corner.
       (Bug #34536)</p></li><li><p>
        When returning to the <code class="literal">SQL Export Filter</code> page
        after using the <span class="guibutton">Back</span> button, filters were
        no longer selected. Selections now persist.
       (Bug #34503)</p></li><li><p>
        The export filters were applied more than once when forward
        engineering an SQL <code class="literal">CREATE</code> script. This
        happened if you exported the script after using the
        <span class="guibutton">Back</span> button on the <code class="literal">SQL Export
        Filter</code> page.
       (Bug #34501)</p></li><li><p>
        When the object notation was Workbench Classic the width of a
        table on an EER diagram could not be less than the widest
        column. If there was an enum column with many options, this made
        for a disproportionately wide table. Table width can now be less
        than the widest column.
       (Bug #34496)</p></li><li><p>
        When multiple objects on an EER diagram were selected and
        deleted, Workbench crashed. This happened when both connections
        and tables were selected.
       (Bug #34434)</p></li><li><p>
        Setting a column to <code class="literal">AUTO_INCREMENT</code> caused the
        application to crash.
       (Bug #34418)</p></li><li><p>
        It was reported that you could not add a primary key to a table
        imported from a MySQL <code class="literal">CREATE</code> script. This was
        not true but did highlight the fact that the method for adding a
        primary key was not obvious. Now, in addition to adding a
        primary key by double-clicking the icon to the left of a column
        in the table editor view, 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.
       (Bug #34408)</p></li><li><p>
        When using the menu option <span class="guimenu">Generate Schema Diff
        Report</span> an exception was thrown. A new tree-less
        version of the Diff report plugin resolves this problem.
       (Bug #34396)</p></li><li><p>
        Users failed to be created when exporting an SQL
        <code class="literal">CREATE</code> script.
       (Bug #34342)</p></li><li><p>
        When a table's <code class="literal">expanded</code> property was set to
        <code class="literal">0</code>, the connection line between related
        tables, appeared at a diagonal orientation. A connection line is
        now docked on the sides of a table even when the
        <code class="literal">expanded</code> property is set to
        <code class="literal">0</code>.
       (Bug #34249)</p></li><li><p>
        Copying a table from the <code class="literal">MySQL Model</code> page to
        an EER diagram canvas created a duplicate table with the same
        name as the original. This table did not show up in the
        <code class="literal">Catalog</code> palette or in the appropriate schema
        in the<code class="literal">Physical Schemata</code> section of the
        <code class="literal">MySQL Model</code> page.
       (Bug #34230)</p></li><li><p>
        Creating a new foreign key did not update an EER diagram. An EER
        diagram is now updated immediately.
       (Bug #34206)</p></li><li><p>
        When there were many tables on an EER diagram, constant screen
        refreshing made the application unusable. The performance of the
        software rendering mode has been improved.
       (Bug #33646)</p></li><li><p>
        A table with many columns did not display properly. When the
        table was expanded on an EER diagram it was impossible to scroll
        down and view all the columns. Improved rendering has helped
        solve this problem. However, for very large tables you may have
        to increase the size of an EER. To do this use the
        <span class="guimenu">Model</span>, <span class="guimenu">Diagram Size ...</span>
        menu option.
       (Bug #33367)</p></li><li><p>
        When changing the foreign key column of a table on an EER
        diagram, the foreign key did not change color and Workbench
        crashed when attempting to save the MWB file. The application no
        longer crashes and the foreign key is updated.
       (Bug #33139)</p></li><li><p>
        It was not possible to resize a table that used the
        <code class="literal">Workbench (Default)</code> object notation. This was
        problematic for a number of reasons:
      </p><div class="itemizedlist"><ul type="circle"><li><p>
            Long table names make the table very wide.
          </p></li><li><p>
            Column definitions that are long relative to the table name,
            are truncated.
          </p></li><li><p>
            Even if you trimmed column names using the
            <span class="guilabel">Diagram</span> tab of the <code class="literal">Workbench
            Options</code> the names were sometimes truncated bled
            over the table border.
          </p></li></ul></div><p>
        This has been corrected.
       (Bug #32981)</p></li><li><p>
        When there were two schemata and two EER diagrams tables did not
        show up on the EER diagram if tables from different schemata
        were added to different EER diagrams. This was caused by
        defective software rendering.
       (Bug #32588)</p></li><li><p>
        When forward engineering to a live database, objects not
        selected on the <code class="literal">Select Objects</code> page were
        still created. This applied to tables, routines, and users.
       (Bug #32578)</p></li><li><p>
        It was not possible to drag or resize tables on an EER diagram.
        Tables can now be manually resized. To revert a table to
        automatic sizing use the <code class="literal">Property</code> palette and
        set <code class="literal">manualSizing</code>to True.
       (Bug #32549)</p></li><li><p>
        The display turned black when the application was resized. This
        happened when viewing the <code class="literal">MySQL Model</code> page or
        when viewing an EER diagram.
       (Bug #23959)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-sql-development-manage-connections.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>6.5. Manage Connections</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-sql-script.html" title="6.4. Edit SQL Script"><link rel="next" href="wb-manage-db-connections.html" title="6.6. Manage DB Connections Dialog"></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-manage-connections"></a>6.5. Manage Connections</h2></div></div></div><p>
      Clicking this action item launches the Manage DB Connections
      wizard. This wizard also displays Stored Connections, which can be
      selected and changed as desired. This wizard can also be used to
      create new connections.
    </p><p>
      To read more about managing connections, see
      <a href="wb-manage-db-connections.html" title="6.6. Manage DB Connections Dialog">Section 6.6, “Manage DB Connections Dialog”</a>.
    </p></div></body></html>


path: /wb-html-guitools/wb-basic-foreign-key.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.8.3.2. Creating a Foreign Key</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-basic-modeling.html" title="7.8.3. Basic Modeling"><link rel="prev" href="wb-basic-add-table.html" title="7.8.3.1. Adding a Table"><link rel="next" href="wb-documenting-sakila.html" title="7.8.4. Documenting the sakila Database"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-basic-foreign-key"></a>7.8.3.2. Creating a Foreign Key</h4></div></div></div><p>
        Select the table tool again and place another table on the
        canvas. Name this table <code class="literal">invoice_item</code>. Next
        click the <code class="literal">1:n Non-Identifying Relationship</code>
        tool.
      </p><p>
        First, click the <code class="literal">invoice_item</code> table; notice
        that a red border indicates that this table is selected. Next,
        click the <code class="literal">invoice</code> table. This creates a
        foreign key in the <code class="literal">invoice_item</code> table, the
        table on the “<span class="quote">many</span>” side of the relationship. This
        relationship between the two tables is shown graphically in
        crow's foot notation.
      </p><p>
        Revert to the default mouse pointer by clicking the arrow at the
        top of the vertical toolbar. Click on the
        <code class="literal">invoice_item</code> table and select the
        <span class="guilabel">Foreign keys</span> tab.
      </p><p>
        Click the <span class="guilabel">Foreign key Name</span> field. The
        referenced table should show in the <span class="guilabel">Referenced
        Table</span> column and the appropriate column in the
        <span class="guilabel">Referenced Column</span> column.
      </p><p>
        To delete the relationship between two tables, click the line
        joining the tables and then press
        <span><strong class="keycap">Control+Delete</strong></span>.
      </p><p>
        Experiment with the other tools on the vertical toolbar. Delete
        a relationship by selecting the eraser tool and clicking the
        line joining two tables. Create a view, add a text object, or
        add a layer.
      </p><p>
        Save your changes to a <code class="literal">MySQL Workbench Models</code>
        file (<code class="filename">mwb</code> extension) by choosing
        <span class="guimenuitem">Save</span> from the <span class="guimenu">File</span>
        menu or by using the keyboard command
        <span><strong class="keycap">Control+S</strong></span>.
      </p></div></body></html>


path: /wb-html-guitools/wb-adding-users.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.5.5.2. Adding Users</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-model-overview-privileges.html" title="7.5.5. The Schema Privileges Panel"><link rel="prev" href="wb-adding-roles.html" title="7.5.5.1. Adding Roles"><link rel="next" href="wb-views-overview-scripts.html" title="7.5.6. The SQL Scripts Panel"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-adding-users"></a>7.5.5.2. Adding Users</h4></div></div></div><p>
        To add a user, double-click the <code class="literal">Add User</code>
        icon. This creates a user with the default name
        <code class="literal">user1</code>. Double-clicking this user opens the
        user editor docked at the bottom of the application.
      </p><p>
        In the <code class="literal">User Editor</code>, set the user's name and
        password using the <span class="guilabel">Name</span> and
        <span class="guilabel">Password</span> fields. Assign one role or a
        number of roles to the user by selecting the desired roles from
        the field on the right and then clicking the
        <span class="guibutton">&lt;</span> button. Roles may be revoked by
        moving them in the opposite direction.
      </p><p>
        Right-clicking a user opens a pop-up menu. The items in the menu
        function as described in <a href="wb-adding-roles.html" title="7.5.5.1. Adding Roles">Section 7.5.5.1, “Adding Roles”</a>.
      </p></div></body></html>


path: /wb-html-guitools/wb-importing-sql-script.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.8.1. Importing a Data Definition 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-tutorials.html" title="7.8. Modeling Tutorials"><link rel="prev" href="wb-tutorials.html" title="7.8. Modeling Tutorials"><link rel="next" href="wb-creating-eer-diagram.html" title="7.8.1.1. Adding 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-importing-sql-script"></a>7.8.1. Importing a Data Definition SQL Script</h3></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-creating-eer-diagram.html">7.8.1.1. Adding an EER Diagram</a></span></dt></dl></div><p>
      For this tutorial, use the <code class="literal">sakila</code> database
      script, which you can find by visiting the
      <a href="http://dev.mysql.com/doc/">http://dev.mysql.com/doc/</a> page, selecting the <code class="literal">Other
      Docs</code> tab, and looking in the <code class="literal">Example
      Databases</code> section
    </p><p>
      After downloading the file, extract it to a convenient location.
      Open MySQL Workbench and find the <span class="guimenuitem">Reverse Engineer MySQL
      Create Script</span> menu item by first choosing
      <span class="guimenu">File</span> and then <span class="guisubmenu">Import</span>.
      Find and import the <code class="filename">sakila-schema.sql</code> file.
      This is the script that contains the data definition statements
      for the <code class="literal">sakila</code> database. The file filter for
      the file open dialog window defaults to <code class="literal">*.sql</code>
      so you should be able to view only files with the
      <code class="literal">sql</code> extension.
    </p><p>
      If the file was successfully imported, the application's status
      bar reads, <code class="literal">Import MySQL Create Script done.</code> To
      view the newly imported script, expand the <code class="literal">Physical
      Schemata</code> section by double-clicking the arrow on the
      left of the <code class="literal">Physical Schemata</code> title bar. Select
      the tab labeled <span class="guilabel">sakila</span>.
    </p><p>
      You may also wish to remove the default schema tab,
      <code class="literal">mydb</code>. Select this tab, then click the
      <span class="guibutton">-</span> button on the upper right in the
      <span class="guilabel">Physical Schemata</span> panel.
    </p><p>
      To view all the objects in the <code class="literal">sakila</code> schema,
      you may need to expand the <span class="guilabel">Physical Schemata</span>
      window. Move the mouse pointer anywhere over the gray area that
      defines the lower edge of the <span class="guilabel">Physical
      Schemata</span> window. Hold down the right mouse button and
      move the mouse to adjust the size of the window.
    </p><p>
      After you have expanded the window, all the objects in the
      <code class="literal">sakila</code> database should be visible. Tables
      appear at the top followed by views and then routines. There are
      no routine groups in this schema, but you should see the
      <span class="guilabel">Routine Groups</span> section and an <code class="literal">Add
      Group</code> icon.
    </p><p>
      For a complete description of importing a MySQL create script, see
      <a href="wb-reverse-engineer-create-script.html" title="7.7.9.1. Reverse Engineering Using a Create Script">Section 7.7.9.1, “Reverse Engineering Using a Create Script”</a>.
    </p></div></body></html>


path: /wb-html-guitools/wb-news-5-0-30.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.3.1. Changes in MySQL Workbench 5.0.30 (18 February 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.0.x.html" title="A.3. Changes in Release 5.0"><link rel="prev" href="changes-5.0.x.html" title="A.3. Changes in Release 5.0"><link rel="next" href="wb-news-5-0-29.html" title="A.3.2. Changes in MySQL Workbench 5.0.29 (12 December 2008)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-news-5-0-30"></a>A.3.1. Changes in MySQL Workbench 5.0.30 (18 February 2009)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.0.29.
      </p><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        MySQL Workbench crashed when the mouse wheel was used. If you
        scrolled the <span class="guilabel">Options</span> tab of the
        <span class="guilabel">Table Editor</span>, closed the <span class="guilabel">Table
        Editor</span> and then used the mouse wheel again on the
        <span class="guilabel">MySQL Model</span> page, MySQL Workbench crashed.
       (Bug #42847)</p></li><li><p>
        Introducing a UserType into a model caused the
        <span class="guimenu">File</span>, <span class="guimenu">Export</span>,
        <span class="guimenu">Forward Engineer SQL CREATE Script</span> wizard to
        crash. Further, peforming a <span class="guimenu">Plugins</span>,
        <span class="guimenu">Objects</span>, <span class="guimenu">Copy SQL to
        Clipboard</span> operation also caused MySQL Workbench to crash.
       (Bug #42085)</p></li><li><p>
        The <span class="guilabel">Forward Engineer SQL CREATE Script</span>
        wizard failed to generate a script correctly.
      </p><p>
        This happened when using the <span class="guimenu">File</span>,
        <span class="guimenu">Export</span>, <span class="guimenu">Forward Engineer SQL CREATE
        Script</span> facility. If, in the wizard, <span class="guilabel">Object
        of type MySQL table</span> was selected, and then all tables
        added to the <span class="guilabel">Exclusion Masks</span> pane, before
        moving back the required table to the <span class="guilabel">Objects to
        Process</span> pane, the script was generated for the entire
        database rather than the selected table.
       (Bug #41475)</p></li><li><p>
        When a diagram was renamed, the history displayed:
      </p><pre class="programlisting">Rename 'new name' to 'new name</pre><p>
        It should have instead displayed:
      </p><pre class="programlisting">Rename 'old name' to 'new name'</pre><p>(Bug #41355)</p></li><li><p>
        If a model contained a View that was using a Function, and an
        attempt was made to Synchronize the database, an error was
        generated such as:
      </p><pre class="programlisting">Error 1305: FUNCTION `bleble` does not exist</pre><p>
        A similar error was also generated if the <span class="guilabel">Forward
        Engineer SQL CREATE Script</span> wizard was used.
       (Bug #40846)</p></li><li><p>
        The viewport, which is the combobox in the top right corner of
        Workbench, did not scale to less than 40%. However, resizes
        above 40% worked fine.
       (Bug #39607)</p></li><li><p>
        The <span class="guilabel">Forward Engineer SQL ALTER Script</span>
        wizard produced an erroneous script.
      </p><p>
        If Forward Engineer SQL CREATE Script was used to generate a
        script and this was then used as an input to Forward Engineer
        SQL ALTER Script, without having made any changes to the model,
        then an ALTER script with no changes should be produced.
        However, the ALTER script showed many changes, even though no
        changes had been made to the model.
       (Bug #37709)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-creating-views.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.7.3. Creating Views</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-connection-properties.html" title="7.7.2.3. Connection Properties"><link rel="next" href="wb-views-physical-schemata.html" title="7.7.3.1. Adding Views 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-creating-views"></a>7.7.3. Creating Views</h3></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-views-physical-schemata.html">7.7.3.1. Adding Views to the Physical Schemata</a></span></dt><dt><span class="section"><a href="wb-using-view-tool.html">7.7.3.2. Adding Views to an EER Diagram</a></span></dt><dt><span class="section"><a href="wb-view-editor.html">7.7.3.3. The View Editor</a></span></dt><dt><span class="section"><a href="wb-modifying-view.html">7.7.3.4. Modifying a View Using the Properties Palette</a></span></dt></dl></div><p>
    You can add views to a database either from the <code class="literal">Physical
    Schemata</code> section of the <code class="literal">MySQL Model</code>
    page or from the EER Diagram.
  </p></div></body></html>


path: /wb-html-guitools/wb-sql-editor-overview-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.1. Overview 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-main-tabsheets.html" title="6.7.4. Main Tabsheets"><link rel="next" href="wb-sql-editor-output-tabsheet.html" title="6.7.4.2. Output 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-overview-tabsheet"></a>6.7.4.1. Overview Tabsheet</h4></div></div></div><p>
          This tabsheet provides a live overview of the schema. It
          displays Tables, Views, and Routines for the current schema.
        </p></div></body></html>


path: /wb-html-guitools/wb-tool-specific-toolbar-items.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.5.2.1. Tool-Specific Toolbar Items</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-toolbar.html" title="7.5.2. The Toolbar"><link rel="prev" href="wb-toolbar.html" title="7.5.2. The Toolbar"><link rel="next" href="wb-eer-diagrams-section.html" title="7.5.3. EER Diagrams"></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-tool-specific-toolbar-items"></a>7.5.2.1. Tool-Specific Toolbar Items</h4></div></div></div><p>
      When an EER diagram canvas is selected, the following icons appear
      to the right of the arrow icons:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          The toggle grid icon: Turns the grid on and off
        </p></li><li><p>
          The grid icon: Aligns objects on the canvas with the grid
        </p></li></ul></div><p>
      The toolbar also changes depending upon which tool from the
      vertical toolbar is active. For discussion of these tools, see
      <a href="wb-vertical-toolbar.html" title="7.6.1. The Vertical Toolbar">Section 7.6.1, “The Vertical Toolbar”</a>.
    </p><p>
      If the <code class="literal">Table</code> tool is active, schemata lists,
      engine types, and collations appear on the toolbar. The table
      properties can be modified using the Properties Editor.
    </p><p>
      When an object is selected, the object's properties, such as
      color, can be changed in the Properties Editor.
    </p></div></body></html>


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

Copyright © 1994–2008 Lua.org, PUC-Rio.

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-server-administration-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.1. 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="wb-server-administration.html" title="Chapter 8. Server Administration"><link rel="prev" href="wb-server-administration.html" title="Chapter 8. Server Administration"><link rel="next" href="wb-server-administration-new-server-instance.html" title="8.2. New Server Instance"></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-server-instance"></a>8.1. Server Administration</h2></div></div></div><p>
      This action item enables you to quickly connect to a predefined
      server instance and carry out administration functions on the
      associated server. Clicking this item launches the Server
      Administration dialog, from which you can select the server
      instance to which you wish to connect. A new Admin tab will be
      launched, which displays the Server Status and Configuration.
    </p><p>
      <span class="bold"><strong>Server Administration (icon)</strong></span>
    </p><p>
      If you have already created server instances, you can most quickly
      launch these by clicking the icon for the Server Instance you wish
      to access. A new Admin tab will be launched, which displays Server
      Status and Configuration.
    </p><p>
      For further details, see
      <a href="wb-server-administration-configuration.html" title="8.7. Server Administration and Configuration">Section 8.7, “Server Administration and Configuration”</a>.
    </p></div></body></html>


path: /wb-html-guitools/wb-news-5-0-26.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.3.5. Changes in MySQL Workbench 5.0.26 (16 October 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-27.html" title="A.3.4. Changes in MySQL Workbench 5.0.27 (07 November 2008)"><link rel="next" href="wb-news-5-0-25.html" title="A.3.6. Changes in MySQL Workbench 5.0.25 (12 September 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-26"></a>A.3.5. Changes in MySQL Workbench 5.0.26 (16 October 2008)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.0.25.
      </p><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        When attempting to export a model using the
        <span class="guimenu">File</span>, <span class="guimenu">Export</span>,
        <span class="guimenu">Forward Engineer SQL CREATE Script</span> menu item,
        Workbench crashed on clicking the wizard's
        <span class="guibutton">Finish</span> button.
       (Bug #39578)</p></li><li><p>
        The <span class="guilabel">Copy Insert to Clipboard</span> action
        generated SQL with lowercase keywords. This was not consistent
        with the behavior of the <span class="guilabel">Copy SQL to
        Clipboard</span> action.
       (Bug #39477)</p></li><li><p>
        Renaming a table and then selecting <span class="guimenu">Forward Engineer
        SQL ALTER Script</span> did not result in a
        <code class="literal">RENAME</code> statement. Instead,
        <code class="literal">DROP</code> and <code class="literal">CREATE</code> statements
        were generated.
       (Bug #39256)</p></li><li><p>
        The script generated by the <span class="guimenu">Export</span>,
        <span class="guimenu">Forward Engineer SQL CREATE Script</span> menu item
        contained invalid statements when using two schemata.
       (Bug #39211)</p></li><li><p>
        Exported SQL code containing a trigger that called a procedure
        would fail when an <code class="literal">INSERT</code>
        activated the trigger.
       (Bug #39088)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-data-modeling-open-existing-model.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.1. Open an Existing EER Model</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-data-modeling.html" title="Chapter 7. Data Modeling"><link rel="prev" href="wb-data-modeling.html" title="Chapter 7. Data Modeling"><link rel="next" href="wb-data-modeling-create-new-model.html" title="7.2. Create New EER Model"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="wb-data-modeling-open-existing-model"></a>7.1. Open an Existing EER Model</h2></div></div></div><p>
      Clicking this action item launches a file browser. You can then
      select the model file you wish to load. A new MySQL Model tab will
      then be created, and your model displayed.
    </p><p>
      If you have already created one or more model files, each will
      appear in this panel as an icon. Double-clicking the item of the
      model you wish to load creates a new MySQL Model tab and displays
      your model.
    </p><p>
      If you already have created a connection to a database, it will
      appear in this panel as an icon. Double-clicking the icon directly
      launches an SQL Editor tab, and connects you to the database as
      defined by the connection.
    </p><p>
      To read more about modeling, see
      <a href="wb-model-editor.html" title="7.5. Model Editor">Section 7.5, “Model Editor”</a>.
    </p></div></body></html>


path: /wb-html-guitools/wb-managing-server-instances.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>8.6. Creating and Managing Server Instances</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-server-administration.html" title="Chapter 8. Server Administration"><link rel="prev" href="wb-server-administration-manage-server-instances.html" title="8.5. Manage Server Instances"><link rel="next" href="wb-new-server-instance-wizard.html" title="8.6.1. New Server Instance Wizard"></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-managing-server-instances"></a>8.6. Creating and Managing Server Instances</h2></div></div></div><div class="toc"><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></div><p>
      Server instances can be created and managed from the
      <span class="guilabel">Home</span> page. To create new server instances,
      use one of these methods:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          Click the New Server Instance action item from the Server
          Administration section of the Home window. This launches the
          <span class="guilabel">Create a new server instance</span> wizard. 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></li><li><p>
          Click the Manage Server Instances action item from the Server
          Administration section of the Home window. This launches the
          <span class="guilabel">Manage Server Instances</span> dialog, from
          within which a new server instance can be created. For further
          details, see
          <a href="wb-manage-server-instance-dialog.html" title="8.6.2. Manage Server Instances Dialog">Section 8.6.2, “Manage Server Instances Dialog”</a>.
        </p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-invisible-objects-layers.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.5.11.1. Finding Invisible Objects Using the Layers Palette</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-layers-palette.html" title="7.5.11. The Layers Palette"><link rel="prev" href="wb-layers-palette.html" title="7.5.11. The Layers Palette"><link rel="next" href="wb-properties-palette.html" title="7.5.12. The Properties Palette"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-invisible-objects-layers"></a>7.5.11.1. Finding Invisible Objects Using the Layers Palette</h4></div></div></div><p>
        In some circumstances, you may want to make an object on an EER
        diagram invisible. Select the object and, in the
        <code class="literal">Properties</code> palette, set the
        <code class="literal">visible</code> property to <code class="literal">False</code>.
      </p><p>
        The <code class="literal">Layer</code> palette provides an easy way to
        locate an object, such as a relationship, that has been set to
        <code class="literal">hidden</code>. Open the <code class="literal">Layers</code>
        palette and select the object by double-clicking it. You can
        then edit the object and change its visibility setting to
        <code class="literal">Fully Visible</code>.
      </p></div></body></html>


path: /wb-html-guitools/wb-extending.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Chapter 9. Extending Workbench</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="index.html" title="MySQL Workbench"><link rel="prev" href="wb-manage-server-logs-tab.html" title="8.7.7. The Logs Tab"><link rel="next" href="wb-grt-data-organization.html" title="9.1. GRT and Workbench Data Organization"></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-extending"></a>Chapter 9. Extending Workbench</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="wb-grt-data-organization.html">9.1. GRT and Workbench Data Organization</a></span></dt><dt><span class="section"><a href="wb-modules.html">9.2. Modules</a></span></dt><dt><span class="section"><a href="wb-plugins.html">9.3. Plugins</a></span></dt><dt><span class="section"><a href="wb-mforms.html">9.4. Adding a GUI to a Plugin Using MForms</a></span></dt><dt><span class="section"><a href="wb-scripting-shell.html">9.5. The Workbench Scripting Shell</a></span></dt><dd><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></dd><dt><span class="section"><a href="wb-tutorial-plugins.html">9.6. Tutorial: Writing Plugins</a></span></dt></dl></div><p>
    MySQL Workbench provides an extension and scripting system that enables
    the developer to extend MySQL Workbench capabilities. While the core of
    MySQL Workbench is developed using C++, it is possible to harness this
    core functionality using both the Lua and Python scripting
    languages. MySQL Workbench also provides access to a cross-platform GUI
    library, MForms, which enables the creation of extensions that
    feature a graphical user interface.
  </p><p>
    The extension system enables the following capabilities:
  </p><div class="itemizedlist"><ul type="disc"><li><p>
        Automate common tasks
      </p></li><li><p>
        Extend the Workbench user-interface
      </p></li><li><p>
        Create plugins (code which can be invoked from the Workbench
        menu system)
      </p></li><li><p>
        Manipulate schemata
      </p></li><li><p>
        Create custom Workbench features
      </p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-layer-tool.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.6.1.4. The Layer Tool</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-vertical-toolbar.html" title="7.6.1. The Vertical Toolbar"><link rel="prev" href="wb-eraser-tool.html" title="7.6.1.3. The Eraser Tool"><link rel="next" href="wb-note-tool.html" title="7.6.1.5. The Text Tool"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-layer-tool"></a>7.6.1.4. The Layer Tool</h4></div></div></div><p>
        The layer tool is the rectangular icon with a capital
        <code class="literal">L</code> in the lower left corner. Use the layer
        tool to organize the objects on an EER Diagram canvas. It is
        useful for grouping similar objects. For example, you may use it
        to group all your views.
      </p><p>
        Click the layer tool and use it to draw a rectangle on the
        canvas. Change to the standard mouse pointer tool and pick up
        any objects you would like to place on the newly created layer.
      </p><p>
        To change the size of a layer, first select it by clicking it.
        When a layer is selected, small rectangles appear at each corner
        and in the middle of each side. Adjust the size by dragging any
        of these rectangles.
      </p><p>
        You can also make changes to a layer by selecting the layer and
        changing properties in the <code class="literal">Properties</code> panel.
        Using the <code class="literal">Properties</code> panel is the only way to
        change the name of a layer.
      </p><p>
        To activate the layer tool from the keyboard, use the
        <span><strong class="keycap">L</strong></span> key. For more information about layers, see
        <a href="wb-layers.html" title="7.7.5. Creating Layers">Section 7.7.5, “Creating Layers”</a>.
      </p></div></body></html>


path: /wb-html-guitools/wb-news-5-0-21.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.3.10. Changes in MySQL Workbench 5.0.21 (27 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-22.html" title="A.3.9. Changes in MySQL Workbench 5.0.22 (27 May 2008)"><link rel="next" href="wb-news-5-0-20.html" title="A.3.11. Changes in MySQL Workbench 5.0.20 (26 April 2008)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-news-5-0-21"></a>A.3.10. Changes in MySQL Workbench 5.0.21 (27 April 2008)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.0.20.
      </p><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        The undo operation did not completely undo a relationship
        between two tables. It removed only the line drawn between two
        tables, but did not undo the fields and keys.
       (Bug #36645)</p></li><li><p>
        Double-clicking a column-heading separator in Find results
        caused a crash.
       (Bug #36266)</p></li><li><p>
        The scripts generated by the <span class="guimenu">File</span>,
        <span class="guimenu">Export</span>, <span class="guimenu">Forward Engineer SQL ALTER
        Script</span> and <span class="guimenu">File</span>,
        <span class="guimenu">Export</span>, <span class="guimenu">Forward Engineer SQL CREATE
        Script</span> include unnecessary SQL code.
       (Bug #36170)</p></li><li><p>
        The <span class="guimenu">Copy Connection nn</span> menu item on the
        context menu of a connection does not have a complementary
        <span class="guimenu">Paste Connection</span> menu item. The
        <span class="guimenu">Edit</span> menu has a greyed-out <span class="guimenu">Paste
        Connection</span> menu item.
       (Bug #36166)</p></li><li><p>
        When a schema used <code class="literal">InnoDB</code>, and then was
        switched to use <code class="literal">MyISAM</code>, the script generated
        by <span class="guilabel">Forward Engineer SQL CREATE Script</span> still
        contained <code class="literal">InnoDB</code>-only syntax.
       (Bug #35947)</p></li><li><p>
        <span class="guimenu">Forward Engineer</span> wizard failed to create a
        table, but did not show any error messages.
       (Bug #35874)</p></li><li><p>
        Saving a file restores the column widths of the list view to
        default under <span class="guilabel">Physical Schemata</span>.
       (Bug #35718)</p></li><li><p>
        When making a column a primary key and this column has
        <code class="literal">NULL</code> as default value, this default value is
        not changed. When the table gets synchronized back to the
        database Workbench creates a statement such as:
      </p><pre class="programlisting">ALTER TABLE `test_defhan`.`table1` CHANGE COLUMN `id_table1` `id_table1` INT(11) NOT NULL
DEFAULT NULL, ...</pre><p>
        This leads to an error:
      </p><p>
        <span class="errortext">Error 1067: Invalid default value for
        'id_table1'</span>
       (Bug #32972)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-size.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>5.3. Workbench Application Minimum Window Size</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-workspace.html" title="5.2. Workspace"><link rel="next" href="wb-preferences.html" title="5.4. Workbench Preferences"></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-size"></a>5.3. Workbench Application Minimum Window Size</h2></div></div></div><p>
      As of version 5.2.10, the MySQL Workbench application features a fixed
      minimum window size of 1024x768. You cannot reduce the size of the
      application to less than this resolution.
    </p></div></body></html>


path: /wb-html-guitools/wb-news-5-2-33.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.6. Changes in MySQL Workbench 5.2.33 (11 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-33b.html" title="A.1.5. Changes in MySQL Workbench 5.2.33b (21 March 2011)"><link rel="next" href="wb-news-5-2-32.html" title="A.1.7. Changes in MySQL Workbench 5.2.32 (05 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-33"></a>A.1.6. Changes in MySQL Workbench 5.2.33 (11 March 2011)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.2.32.
      </p><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        It was not possible to forward engineer a model, or synchronize
        it with a live model.
       (Bug #60396, Bug #11850052)</p></li><li><p>
        In the Administrator, when <span class="guimenu">Manage Security</span>
        was selected, an error message was displayed in the status bar.
        It was not then possible to see and therefore manage user
        privileges.
       (Bug #60370, Bug #11840439)</p></li><li><p>
        The ability to synchronize non-model sources was added.
       (Bug #60009, Bug #11766805)</p></li><li><p>
        The query beautifier failed for queries containing subqueries.
       (Bug #58835, Bug #11765832)</p></li><li><p>
        In the <span class="guilabel">Users and Privileges</span> task of the
        Administrator, it was not possible to sort the users
        alphabetically.
       (Bug #56456, Bug #11763710)</p></li><li><p>
        MySQL Workbench would incorrectly report that the MySQL server had
        stopped.
       (Bug #51146, Bug #11758886)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-news-5-0-16.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.3.15. Changes in MySQL Workbench 5.0.16rc (26 March 2008)</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="changes-5.0.x.html" title="A.3. Changes in Release 5.0"><link rel="prev" href="wb-news-5-0-17.html" title="A.3.14. Changes in MySQL Workbench 5.0.17rc (07 April 2008)"><link rel="next" href="wb-news-5-0-15.html" title="A.3.16. Changes in MySQL Workbench 5.0.15rc (17 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-16"></a>A.3.15. Changes in MySQL Workbench 5.0.16rc (26 March 2008)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.0.15rc.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        Options and configuration options that affect models can now be
        set on a model by model basis. Choose <span class="guimenu">Options</span>
        from the <span class="guimenu">Model</span> menu and choose the
        <span class="guilabel">Diagram</span> tab.
       (Bug #34610)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        When double-clicking the row in a column as a primary key, the
        primary key property would be toggled. The editor will now
        permit you to edit the value when you click a data row on the
        table.
       (Bug #35613)</p></li><li><p>
        Opening the <span class="guilabel">Indexes</span> portion of a table
        would generate a unhandled exception error.
       (Bug #35598)</p></li><li><p>
        When disabling global options on an individual model would fail
        to honor the model specific options would be ignored.
       (Bug #35516)</p></li><li><p>
        When placing a 1:n relation, an <code class="literal">index out of
        range</code> error could be raised. This could further result
        in <code class="literal">operation on NULL object: Invalid value</code>
        errors when trying to edit the relation.
       (Bug #35447)</p></li><li><p>
        Setting the value of a numeric column to a negative value was
        not supported.
       (Bug #35442)</p></li><li><p>
        Printing an HTML version of the schema would produce a fatal
        error.
       (Bug #35400)</p></li><li><p>
        The <span class="guibutton">OK</span> and <span class="guibutton">Cancel</span>
        buttons for the <span class="guilabel">Diagram Size</span> dialog would
        not be initialized properly.
       (Bug #34808)</p></li><li><p>
        When using print preview on a diagram, clicking the
        <span class="guibutton">Print</span> button would send a blank page to
        the printer.
       (Bug #34630)</p></li><li><p>
        When copying multiple table definitions from one schema to
        another, only the first table in the selection would be pasted
        into the new schema.
       (Bug #34483)</p></li><li><p>
        The <span class="guilabel">Draw Line Crossing</span> option would fail to
        be recognized correctly. You can also now set this on an
        individual model basis using the <span class="guimenu">Options</span>
        optin in the <span class="guimenu">Model</span> menu.
       (Bug #34248)</p></li><li><p>
        Copying an existing module to the plugins directory would
        trigger a double registration of the modulem, and produce an
        error.
       (Bug #34134)</p></li><li><p>
        When exporting a diagram to PDF, some additional lines would be
        added to the generated PDF.
       (Bug #33586)</p></li><li><p>
        Placing an image on to the canvas could crash the application.
        For images larger than the canvas, the image is automatically
        reduced so that it is properly visible on the canvas for
        editing.
       (Bug #33179)</p></li><li><p>
        A 1:m relation in a diagram would fail to be generated properly
        when exported as a PDF.
       (Bug #32882)</p></li><li><p>
        The Undo and Redo options would not be applied properly when
        making modifications to partition definitions.
       (Bug #32279)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-standard-mouse-pointer.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.6.1.1. The Standard Mouse Pointer</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-vertical-toolbar.html" title="7.6.1. The Vertical Toolbar"><link rel="prev" href="wb-vertical-toolbar.html" title="7.6.1. The Vertical Toolbar"><link rel="next" href="wb-hand-tool.html" title="7.6.1.2. The Hand Tool"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-standard-mouse-pointer"></a>7.6.1.1. The Standard Mouse Pointer</h4></div></div></div><p>
        The standard mouse pointer, located at the top of the vertical
        toolbar, is the default mouse pointer for your operating system.
        Use this tool to revert to the standard mouse pointer after
        using other tools.
      </p><p>
        To revert to the default pointer from the keyboard, use the
        <span><strong class="keycap">Esc</strong></span> key.
      </p></div></body></html>


path: /wb-html-guitools/wb-news-5-0-19.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.3.12. Changes in MySQL Workbench 5.0.19 (15 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-20.html" title="A.3.11. Changes in MySQL Workbench 5.0.20 (26 April 2008)"><link rel="next" href="wb-news-5-0-18.html" title="A.3.13. Changes in MySQL Workbench 5.0.18rc (not released)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-news-5-0-19"></a>A.3.12. Changes in MySQL Workbench 5.0.19 (15 April 2008)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.0.18rc.
      </p><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        The HTML Basic Single Page DBDoc report from the
        <span class="guimenu">Model</span> -&gt; <span class="guimenu">DBDoc</span> -&gt;
        <span class="guimenu">Model Reporting</span> menu option was missing the
        schema and table numbers.
       (Bug #36060)</p></li><li><p>
        <span class="guilabel">Forward Engineer SQL CREATE Script</span> wizard
        generated no output script. Further, no error or warning
        messages appeared to be generated that might explain this.
      </p><p>
        The error message in this case was displayed in the Advanced
        Log, which was not visible to the user. MySQL Workbench was changed
        so that the Advanced Log appeared to the user if it received an
        error message.
       (Bug #34430)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/index.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>MySQL Workbench</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><meta name="description" content="
        This manual documents the MySQL Workbench SE version
        5.2 and the MySQL Workbench OSS version
        5.2.
       
        If you have not yet installed MySQL Workbench OSS please download
        your free copy from the
        download
        site. MySQL Workbench OSS is available for Windows, Mac OS
        X, and Linux.
       
        Document generated on:

        2011-11-30



        (revision: 28180)
       
        For legal information, see the Legal
        Notice.
      "><link rel="start" href="index.html" title="MySQL Workbench"><link rel="next" href="wb-preface.html" title="Preface and Legal Notice"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="workbench"></a>MySQL Workbench</h1></div><div><div class="abstract"><p class="title"><b>Abstract</b></p><p>
        This manual documents the MySQL Workbench SE version
        5.2 and the MySQL Workbench OSS version
        5.2.
      </p><p>
        If you have not yet installed MySQL Workbench OSS please download
        your free copy from the
        <a href="http://dev.mysql.com/downloads/workbench">download
        site</a>. MySQL Workbench OSS is available for Windows, Mac OS
        X, and Linux.
      </p><p>
        Document generated on:

        2011-11-30



        (revision: 28180)
      </p><p>
        For legal information, see the <a href="wb-preface.html#legalnotice">Legal
        Notice</a>.
      </p></div></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="preface"><a href="wb-preface.html">Preface and Legal Notice</a></span></dt><dt><span class="chapter"><a href="wb-intro.html">1. MySQL Workbench Introduction</a></span></dt><dt><span class="chapter"><a href="wb-editions.html">2. MySQL Workbench Editions</a></span></dt><dt><span class="chapter"><a href="wb-installing.html">3. Installing and Launching MySQL Workbench</a></span></dt><dd><dl><dt><span class="section"><a href="wb-requirements-hardware.html">3.1. Hardware Requirements</a></span></dt><dt><span class="section"><a href="wb-requirements-software.html">3.2. Software Requirements</a></span></dt><dt><span class="section"><a href="wb-starting.html">3.3. Starting MySQL Workbench</a></span></dt><dd><dl><dt><span class="section"><a href="wb-installing-windows.html">3.3.1. Installing MySQL Workbench on Windows</a></span></dt><dt><span class="section"><a href="wb-launching-windows.html">3.3.2. Launching MySQL Workbench on Windows</a></span></dt><dt><span class="section"><a href="wb-windows-uninstalling.html">3.3.3. Uninstalling MySQL Workbench on Windows</a></span></dt><dt><span class="section"><a href="wb-installing-linux.html">3.3.4. Installing MySQL Workbench on Linux</a></span></dt><dt><span class="section"><a href="wb-launching-linux.html">3.3.5. Launching MySQL Workbench on Linux</a></span></dt><dt><span class="section"><a href="wb-linux-uninstalling.html">3.3.6. Uninstalling MySQL Workbench on Linux</a></span></dt><dt><span class="section"><a href="wb-installing-mac.html">3.3.7. Installing MySQL Workbench on Mac OS X</a></span></dt><dt><span class="section"><a href="wb-launching-osx.html">3.3.8. Launching MySQL Workbench on Mac OS X</a></span></dt><dt><span class="section"><a href="wb-mac-uninstalling.html">3.3.9. Uninstalling MySQL Workbench on Mac OS X</a></span></dt></dl></dd><dt><span class="section"><a href="wb-launching-activation.html">3.4. Activation Procedure (Commercial Version)</a></span></dt></dl></dd><dt><span class="chapter"><a href="wb-getting-started-tutorial.html">4. Getting Started Tutorial</a></span></dt><dd><dl><dt><span class="section"><a href="wb-getting-started-tutorial-admin.html">4.1. Administering a MySQL Server</a></span></dt><dt><span class="section"><a href="wb-getting-started-tutorial-creating-a-model.html">4.2. Creating a Model</a></span></dt><dt><span class="section"><a href="wb-getting-started-tutorial-adding-data.html">4.3. Adding Data to Your Database</a></span></dt></dl></dd><dt><span class="chapter"><a href="wb-home.html">5. The Home Window</a></span></dt><dd><dl><dt><span class="section"><a href="wb-workbench-central.html">5.1. Workbench Central</a></span></dt><dt><span class="section"><a href="wb-workspace.html">5.2. Workspace</a></span></dt><dt><span class="section"><a href="wb-size.html">5.3. Workbench Application Minimum Window Size</a></span></dt><dt><span class="section"><a href="wb-preferences.html">5.4. Workbench Preferences</a></span></dt><dd><dl><dt><span class="section"><a href="wb-preferences-general.html">5.4.1. The General Tab</a></span></dt><dt><span class="section"><a href="wb-preferences-administrator.html">5.4.2. The Administrator Tab</a></span></dt><dt><span class="section"><a href="wb-preferences-sql-editor.html">5.4.3. The SQL Editor Tab</a></span></dt><dt><span class="section"><a href="wb-preferences-model.html">5.4.4. The Model Tab</a></span></dt><dt><span class="section"><a href="wb-preferences-mysql.html">5.4.5. The MySQL Tab</a></span></dt><dt><span class="section"><a href="wb-preferences-diagram.html">5.4.6. The Diagram Tab</a></span></dt><dt><span class="section"><a href="wb-preferences-appearance.html">5.4.7. The Appearance Tab</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="wb-sql-development.html">6. SQL Development</a></span></dt><dd><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></dd><dt><span class="chapter"><a href="wb-data-modeling.html">7. Data Modeling</a></span></dt><dd><dl><dt><span class="section"><a href="wb-data-modeling-open-existing-model.html">7.1. Open an Existing EER Model</a></span></dt><dt><span class="section"><a href="wb-data-modeling-create-new-model.html">7.2. Create New EER Model</a></span></dt><dt><span class="section"><a href="wb-data-modeling-create-model-from-existing-database.html">7.3. Create EER Model from Existing Database</a></span></dt><dt><span class="section"><a href="wb-data-modeling-create-model-from-sql-script.html">7.4. Create EER Model from SQL Script</a></span></dt><dt><span class="section"><a href="wb-model-editor.html">7.5. Model Editor</a></span></dt><dd><dl><dt><span class="section"><a href="wb-data-modeling-menus.html">7.5.1. Modeling Menus</a></span></dt><dt><span class="section"><a href="wb-toolbar.html">7.5.2. The Toolbar</a></span></dt><dt><span class="section"><a href="wb-eer-diagrams-section.html">7.5.3. EER Diagrams</a></span></dt><dt><span class="section"><a href="wb-view-overview-physical-schemata.html">7.5.4. The Physical Schemata Panel</a></span></dt><dt><span class="section"><a href="wb-model-overview-privileges.html">7.5.5. The Schema Privileges Panel</a></span></dt><dt><span class="section"><a href="wb-views-overview-scripts.html">7.5.6. The SQL Scripts Panel</a></span></dt><dt><span class="section"><a href="wb-views-overview-notes.html">7.5.7. The Model Notes Panel</a></span></dt><dt><span class="section"><a href="wb-history-palette.html">7.5.8. The History Palette</a></span></dt><dt><span class="section"><a href="wb-navigator-panel.html">7.5.9. The Model Navigator Panel</a></span></dt><dt><span class="section"><a href="wb-catalog-palette.html">7.5.10. The Catalog Tree Palette</a></span></dt><dt><span class="section"><a href="wb-layers-palette.html">7.5.11. The Layers Palette</a></span></dt><dt><span class="section"><a href="wb-properties-palette.html">7.5.12. The Properties Palette</a></span></dt></dl></dd><dt><span class="section"><a href="wb-eer-diagram-editor.html">7.6. EER Diagram Editor</a></span></dt><dd><dl><dt><span class="section"><a href="wb-vertical-toolbar.html">7.6.1. The Vertical Toolbar</a></span></dt></dl></dd><dt><span class="section"><a href="wb-working-with-models.html">7.7. Working with Models</a></span></dt><dd><dl><dt><span class="section"><a href="wb-tables.html">7.7.1. Creating Tables</a></span></dt><dt><span class="section"><a href="wb-foreign-key-relationships.html">7.7.2. Creating Foreign Key Relationships</a></span></dt><dt><span class="section"><a href="wb-creating-views.html">7.7.3. Creating Views</a></span></dt><dt><span class="section"><a href="wb-routines-routine-groups.html">7.7.4. Creating Routines and Routine Groups</a></span></dt><dt><span class="section"><a href="wb-layers.html">7.7.5. Creating Layers</a></span></dt><dt><span class="section"><a href="wb-notes.html">7.7.6. Creating Notes</a></span></dt><dt><span class="section"><a href="wb-text-objects.html">7.7.7. Creating Text Objects</a></span></dt><dt><span class="section"><a href="wb-images.html">7.7.8. Creating Images</a></span></dt><dt><span class="section"><a href="wb-reverse-engineering.html">7.7.9. Reverse Engineering</a></span></dt><dt><span class="section"><a href="wb-forward-engineering.html">7.7.10. Forward Engineering</a></span></dt></dl></dd><dt><span class="section"><a href="wb-tutorials.html">7.8. Modeling Tutorials</a></span></dt><dd><dl><dt><span class="section"><a href="wb-importing-sql-script.html">7.8.1. Importing a Data Definition SQL Script</a></span></dt><dt><span class="section"><a href="wb-default-schema.html">7.8.2. Using the Default Schema</a></span></dt><dt><span class="section"><a href="wb-basic-modeling.html">7.8.3. Basic Modeling</a></span></dt><dt><span class="section"><a href="wb-documenting-sakila.html">7.8.4. Documenting the <code class="literal">sakila</code> Database</a></span></dt></dl></dd><dt><span class="section"><a href="wb-printing.html">7.9. Printing</a></span></dt><dd><dl><dt><span class="section"><a href="wb-printing-options.html">7.9.1. Printing Options</a></span></dt></dl></dd><dt><span class="section"><a href="wb-validation-plugins.html">7.10. MySQL Workbench Schema Validation Plugins (Commercial Version)</a></span></dt><dd><dl><dt><span class="section"><a href="wb-general-validation.html">7.10.1. General Validation</a></span></dt><dt><span class="section"><a href="wb-mysql-validation.html">7.10.2. MySQL-Specific Validation</a></span></dt></dl></dd><dt><span class="section"><a href="wb-model-reporting.html">7.11. The DBDoc Model Reporting Dialog Window (Commercial Version)</a></span></dt><dt><span class="section"><a href="dbdoc-templates.html">7.12. Customizing DBDoc Model Reporting Templates</a></span></dt><dd><dl><dt><span class="section"><a href="dbdoc-templates-markers.html">7.12.1. Supported Template Markers</a></span></dt><dt><span class="section"><a href="dbdoc-templates-custom.html">7.12.2. Creating a Custom Template</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="wb-server-administration.html">8. Server Administration</a></span></dt><dd><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></dd><dt><span class="chapter"><a href="wb-extending.html">9. Extending Workbench</a></span></dt><dd><dl><dt><span class="section"><a href="wb-grt-data-organization.html">9.1. GRT and Workbench Data Organization</a></span></dt><dt><span class="section"><a href="wb-modules.html">9.2. Modules</a></span></dt><dt><span class="section"><a href="wb-plugins.html">9.3. Plugins</a></span></dt><dt><span class="section"><a href="wb-mforms.html">9.4. Adding a GUI to a Plugin Using MForms</a></span></dt><dt><span class="section"><a href="wb-scripting-shell.html">9.5. The Workbench Scripting Shell</a></span></dt><dd><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></dd><dt><span class="section"><a href="wb-tutorial-plugins.html">9.6. Tutorial: Writing Plugins</a></span></dt></dl></dd><dt><span class="chapter"><a href="wb-keys.html">10. Keyboard Shortcuts</a></span></dt><dt><span class="chapter"><a href="workbench-faq.html">11. MySQL Workbench FAQ</a></span></dt><dt><span class="appendix"><a href="wb-change-history.html">A. MySQL Workbench Change History</a></span></dt><dd><dl><dt><span class="section"><a href="changes-5.2.x.html">A.1. Changes in Release 5.2</a></span></dt><dd><dl><dt><span class="section"><a href="wb-news-5-2-37.html">A.1.1. Changes in MySQL Workbench 5.2.37 (Not yet released)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-36.html">A.1.2. Changes in MySQL Workbench 5.2.36 (Not yet released)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-35.html">A.1.3. Changes in MySQL Workbench 5.2.35 (23 September 2011)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-34.html">A.1.4. Changes in MySQL Workbench 5.2.34 (26 May 2011)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-33b.html">A.1.5. Changes in MySQL Workbench 5.2.33b (21 March 2011)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-33.html">A.1.6. Changes in MySQL Workbench 5.2.33 (11 March 2011)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-32.html">A.1.7. Changes in MySQL Workbench 5.2.32 (05 March 2011)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-31a.html">A.1.8. Changes in MySQL Workbench 5.2.31a (13 December 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-31.html">A.1.9. Changes in MySQL Workbench 5.2.31 (08 December 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-30.html">A.1.10. Changes in MySQL Workbench 5.2.30 (20 November 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-29.html">A.1.11. Changes in MySQL Workbench 5.2.29 (12 October 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-28.html">A.1.12. Changes in MySQL Workbench 5.2.28 (19 September 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-27.html">A.1.13. Changes in MySQL Workbench 5.2.27 (01 September 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-26.html">A.1.14. Changes in MySQL Workbench 5.2.26 (06 August 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-25.html">A.1.15. Changes in MySQL Workbench 5.2.25 (30 June 2010 General Availability)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-24.html">A.1.16. Changes in MySQL Workbench 5.2.24 (21 June 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-23.html">A.1.17. Changes in MySQL Workbench 5.2.23 (Internal release only)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-22.html">A.1.18. Changes in MySQL Workbench 5.2.22 (02 June 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-21.html">A.1.19. Changes in MySQL Workbench 5.2.21 (12 May 2010 Release Candidate)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-20.html">A.1.20. Changes in MySQL Workbench 5.2.20 (27 April 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-19.html">A.1.21. Changes in MySQL Workbench 5.2.19 (16 April 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-18.html">A.1.22. Changes in MySQL Workbench 5.2.18 (13 April 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-17.html">A.1.23. Changes in MySQL Workbench 5.2.17 (02 April 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-16.html">A.1.24. Changes in MySQL Workbench 5.2.16 (17 February 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-15.html">A.1.25. Changes in MySQL Workbench 5.2.15 (28 January 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-14.html">A.1.26. Changes in MySQL Workbench 5.2.14 (21 January 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-13.html">A.1.27. Changes in MySQL Workbench 5.2.13 (Not released)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-12.html">A.1.28. Changes in MySQL Workbench 5.2.12 (Not released)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-11.html">A.1.29. Changes in MySQL Workbench 5.2.11 (18 December 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-10.html">A.1.30. Changes in MySQL Workbench 5.2.10 (01 December 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-9.html">A.1.31. Changes in MySQL Workbench 5.2.9 (Internal release only)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-8.html">A.1.32. Changes in MySQL Workbench 5.2.8 (18 November 2009 Beta)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-7.html">A.1.33. Changes in MySQL Workbench 5.2.7 (Internal release only)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-6.html">A.1.34. Changes in MySQL Workbench 5.2.6 (21 October 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-5.html">A.1.35. Changes in MySQL Workbench 5.2.5 (Internal Release Only)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-4.html">A.1.36. Changes in MySQL Workbench 5.2.4 (07 October 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-3.html">A.1.37. Changes in MySQL Workbench 5.2.3 (15 September 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-2.html">A.1.38. Changes in MySQL Workbench 5.2.2 (27 July 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-1.html">A.1.39. Changes in MySQL Workbench 5.2.1 (22 May 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-2-0.html">A.1.40. Changes in MySQL Workbench 5.2.0 (30 April 2009 Alpha)</a></span></dt></dl></dd><dt><span class="section"><a href="changes-5.1.x.html">A.2. Changes in Release 5.1</a></span></dt><dd><dl><dt><span class="section"><a href="wb-news-5-1-19.html">A.2.1. Changes in MySQL Workbench 5.1.19 (06 September 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-18.html">A.2.2. Changes in MySQL Workbench 5.1.18 (03 September 2009 General Availability)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-17.html">A.2.3. Changes in MySQL Workbench 5.1.17 (14 August 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-16.html">A.2.4. Changes in MySQL Workbench 5.1.16 (30 June 2009 General Availability)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-15.html">A.2.5. Changes in MySQL Workbench 5.1.15 (26 June 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-14.html">A.2.6. Changes in MySQL Workbench 5.1.14 (19 June 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-13.html">A.2.7. Changes in MySQL Workbench 5.1.13 (12 June 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-12.html">A.2.8. Changes in MySQL Workbench 5.1.12 (27 April 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-11.html">A.2.9. Changes in MySQL Workbench 5.1.11 (Not yet released)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-10.html">A.2.10. Changes in MySQL Workbench 5.1.10 (10 April 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-9.html">A.2.11. Changes in MySQL Workbench 5.1.9 (Not yet released Beta)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-8.html">A.2.12. Changes in MySQL Workbench 5.1.8 (Not yet released)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-7.html">A.2.13. Changes in MySQL Workbench 5.1.7 (Not yet released)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-6.html">A.2.14. Changes in MySQL Workbench 5.1.6 (Not yet released)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-4.html">A.2.15. Changes in MySQL Workbench 5.1.4 (Not yet released)</a></span></dt></dl></dd><dt><span class="section"><a href="changes-5.0.x.html">A.3. Changes in Release 5.0</a></span></dt><dd><dl><dt><span class="section"><a href="wb-news-5-0-30.html">A.3.1. Changes in MySQL Workbench 5.0.30 (18 February 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-29.html">A.3.2. Changes in MySQL Workbench 5.0.29 (12 December 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-28.html">A.3.3. Changes in MySQL Workbench 5.0.28 (06 December 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-27.html">A.3.4. Changes in MySQL Workbench 5.0.27 (07 November 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-26.html">A.3.5. Changes in MySQL Workbench 5.0.26 (16 October 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-25.html">A.3.6. Changes in MySQL Workbench 5.0.25 (12 September 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-24.html">A.3.7. Changes in MySQL Workbench 5.0.24 (12 August 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-23.html">A.3.8. Changes in MySQL Workbench 5.0.23 (25 June 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-22.html">A.3.9. Changes in MySQL Workbench 5.0.22 (27 May 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-21.html">A.3.10. Changes in MySQL Workbench 5.0.21 (27 April 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-20.html">A.3.11. Changes in MySQL Workbench 5.0.20 (26 April 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-19.html">A.3.12. Changes in MySQL Workbench 5.0.19 (15 April 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-18.html">A.3.13. Changes in MySQL Workbench 5.0.18rc (not released)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-17.html">A.3.14. Changes in MySQL Workbench 5.0.17rc (07 April 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-16.html">A.3.15. Changes in MySQL Workbench 5.0.16rc (26 March 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-15.html">A.3.16. Changes in MySQL Workbench 5.0.15rc (17 March 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-14a.html">A.3.17. Changes in MySQL Workbench 5.0.14abeta (28 February 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-14.html">A.3.18. Changes in MySQL Workbench 5.0.14beta (25 February 2008)</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="wb-third-party-licenses.html">B. Third Party Licenses</a></span></dt><dd><dl><dt><span class="section"><a href="license-flat-tab-control.html">B.1. .NET Flat TabControl License</a></span></dt><dt><span class="section"><a href="license-bitstream-vera.html">B.2. Bitstream Vera License</a></span></dt><dt><span class="section"><a href="license-boost.html">B.3. Boost Library License</a></span></dt><dt><span class="section"><a href="license-cairo.html">B.4. Cairo License</a></span></dt><dt><span class="section"><a href="license-ctemplate.html">B.5. CTemplate (Google Template System) License</a></span></dt><dt><span class="section"><a href="license-libcurl.html">B.6. cURL (<code class="literal">libcurl</code>) License</a></span></dt><dt><span class="section"><a href="license-dockpanel.html">B.7. DockPanel Suite License</a></span></dt><dt><span class="section"><a href="license-dojo-toolkit.html">B.8. Dojo Toolkit v1.7.0b1 License</a></span></dt><dt><span class="section"><a href="license-glib-wb.html">B.9. GLib License (for MySQL Workbench)</a></span></dt><dt><span class="section"><a href="license-glitz.html">B.10. Glitz License</a></span></dt><dt><span class="section"><a href="license-gnu-lgpl-2-1.html">B.11. GNU Lesser General Public License Version 2.1, February 1999</a></span></dt><dt><span class="section"><a href="license-html-renderer.html">B.12. HtmlRenderer (System.Drawing.Html)</a></span></dt><dt><span class="section"><a href="license-libxml2.html">B.13. Libxml2 License</a></span></dt><dt><span class="section"><a href="license-libzip.html">B.14. Libzip License</a></span></dt><dt><span class="section"><a href="license-lua.html">B.15. Lua (liblua) License</a></span></dt><dt><span class="section"><a href="license-pcre.html">B.16. PCRE License</a></span></dt><dt><span class="section"><a href="license-pixman.html">B.17. Pixman License</a></span></dt><dt><span class="section"><a href="license-pycrypto.html">B.18. PyCrypto License</a></span></dt><dt><span class="section"><a href="license-python.html">B.19. Python License</a></span></dt><dt><span class="section"><a href="license-scintilla.html">B.20. Scintilla License</a></span></dt><dt><span class="section"><a href="license-scintilla-net.html">B.21. ScintillaNET License</a></span></dt><dt><span class="section"><a href="license-tinyxml.html">B.22. TinyXML License</a></span></dt><dt><span class="section"><a href="license-treeviewadv-net.html">B.23. TreeViewAdv for .NET License</a></span></dt><dt><span class="section"><a href="license-vsqlite.html">B.24. VSQLite++ License</a></span></dt></dl></dd></dl></div></div></body></html>


path: /wb-html-guitools/wb-layers.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.7.5. Creating Layers</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-routine-groups.html" title="7.7.4.2. Routine Groups"><link rel="next" href="wb-using-layer-tool.html" title="7.7.5.1. Adding Layers 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-layers"></a>7.7.5. Creating Layers</h3></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-using-layer-tool.html">7.7.5.1. Adding Layers to an EER Diagram</a></span></dt><dt><span class="section"><a href="wb-modifying-layer.html">7.7.5.2. Modifying a Layer Using the Properties Palette</a></span></dt></dl></div><p>
    You can add layers to a database only from an EER Diagram. Layers
    are used to help organize objects on the canvas. Typically, related
    objects are added to the same layer; for example, you may choose to
    add all your views to one layer.
  </p></div></body></html>


path: /wb-html-guitools/wb-manage-server-accounts-tab.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>8.7.3. The Accounts Tab</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-server-administration-configuration.html" title="8.7. Server Administration and Configuration"><link rel="prev" href="wb-manage-server-configuration-tab.html" title="8.7.2. The Configuration Tab"><link rel="next" href="wb-manage-server-accounts-tab-roles.html" title="8.7.3.1. Administrative Roles"></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-accounts-tab"></a>8.7.3. The Accounts Tab</h3></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-manage-server-accounts-tab-roles.html">8.7.3.1. Administrative Roles</a></span></dt></dl></div><p>
        The Accounts tab has two subtabs:
      </p><div class="itemizedlist"><ul type="disc"><li><p>
            Server Access Management
          </p></li><li><p>
            Schema Privileges
          </p></li></ul></div><p>
        <span class="guilabel">Server Access Management</span> enables you to
        list existing user accounts. You can also add and delete
        accounts. You can allocate administrative roles and also set
        account limits.
      </p><p>
        <span class="guilabel">Schema Privileges</span> enables you to set
        specific privileges on a user basis.
      </p><div class="figure"><a name="wb-manage-server-accounts-tab-screenshot"></a><p class="title"><b>Figure 8.6. Administrator - Accounts Tab</b></p><div class="mediaobject"><img src="images/wb-manage-server-accounts-tab.png" width="1024" height="707" alt="Administrator - Accounts Tab"></div></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
          In the current version of MySQL Workbench, it is not possible to
          manage privileges below the schema level. For example, it is
          not possible to view or manage grants at the table, column, or
          procedure level.
        </p></div></div></body></html>


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


path: /wb-html-guitools/wb-news-5-2-27.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.13. Changes in MySQL Workbench 5.2.27 (01 September 2010)</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="changes-5.2.x.html" title="A.1. Changes in Release 5.2"><link rel="prev" href="wb-news-5-2-28.html" title="A.1.12. Changes in MySQL Workbench 5.2.28 (19 September 2010)"><link rel="next" href="wb-news-5-2-26.html" title="A.1.14. Changes in MySQL Workbench 5.2.26 (06 August 2010)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-news-5-2-27"></a>A.1.13. Changes in MySQL Workbench 5.2.27 (01 September 2010)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.2.26.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        Several changes were made to the <span class="guilabel">Sychronize Model With
        Database</span> wizard:
      </p><div class="itemizedlist"><ul type="circle"><li><p>
            The wizard shows all schemata in a model, regardless of
            whether they exist in the live database.
          </p></li><li><p>
            The wizard shows a list of schemata that exist in the model
            but are missing from the live server, with a note
            recommending the use of the <span class="guilabel">Forward
            Engineering</span> wizard.
          </p></li><li><p>
            The wizard does not auto-select schemata names that are in
            the model but not in the live database.
          </p></li></ul></div><p>(Bug #54748)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        Attempts to restore a backup of selected tables resulted in this
        error:
      </p><pre class="programlisting">File "C:\Program Files\MySQL\MySQL Workbench 5.2 CE\modules\wb_admin_export.py", line
841, in start

    logmsg = "Restoring %s (%s)" % (schema, table)

NameError: global name 'schema' is not defined</pre><p>(Bug #56020)</p></li><li><p>
        Forward engineering a model to a live database caused
        MySQL Workbench to crash.
       (Bug #56009)</p></li><li><p>
        The <span class="guilabel">Dump</span> tab did not display the target
        folder before the dump was performed.
       (Bug #55945)</p></li><li><p>
        MySQL Workbench crashed in the foreign key editor. The Microsoft
        Visual C++ Runtime Library runtime error generated prior to the
        crash was:
      </p><pre class="programlisting">R6025

- pure virtual function call</pre><p>(Bug #55910)</p></li><li><p>
        If the sidebar was placed on the right hand side, using the
        option in Workbench Preferences, this Unexpected Error was
        generated when <span class="guilabel">Add Diagram</span> was
        double-clicked:
      </p><pre class="programlisting">SplitterDistance value is invalid (-52)</pre><p>(Bug #55902)</p></li><li><p>
        In the SQL Editor, executing statements designed for MySQL
        Server 5.5 generated syntax or syntax highlighting errors.
       (Bug #55867, Bug #55891)</p></li><li><p>
        After dropping a schema from the list in the Object Browser, the
        schema that was dropped remained, but with the name of the
        schema that followed it. Refreshing the list of available
        schemata produced an unhandled exception:
      </p><pre class="programlisting">An unhandled exception has occurred:
Invalid node index</pre><p>(Bug #55861)</p></li><li><p>
        Selecting "Dump views" for a backup produced this error:
      </p><pre class="programlisting">Unhandled exception: global name 'views_by_schema' is not defined</pre><p>
        It was necessary to restart the Administrator to enable the dump
        facility again.
       (Bug #55833)</p></li><li><p>
        In the SQL Editor, right-clicking a routine name in the Object
        Browser caused MySQL Workbench to exit unexpectedly.
       (Bug #55822)</p></li><li><p>
        MySQL Workbench crashed when using the
        <span class="guilabel">Partitioning</span> tab of the Table Editor.
       (Bug #55761)</p></li><li><p>
        If a table was copied in the EER Diagram view, and then the
        model was synchronized with the live database, the synchronize
        functionality did not recognize the copied table as a new table
        and overwrote the original table.
       (Bug #55566)</p></li><li><p>
        MySQL Workbench crashed when using the <span class="guilabel">Export recordset to
        an external file</span> command button on the
        <span class="guilabel">result</span> pane of the SQL Editor.
       (Bug #55554)</p></li><li><p>
        Renaming a column with a foreign key resulted in an invalid
        script being generated on forward engineering or synchronization
        with a live database.
       (Bug #55502)</p></li><li><p>
        The second attempt to save a read-only model file produced this
        error:
      </p><pre class="programlisting">Couldn't backup existing file name-of-the-file.mwb: No such file or directory</pre><p>(Bug #55439)</p></li><li><p>
        When a table was being edited in the Table Editor, and its name
        was changed, the name change was not reflected on the Table
        Editor's table tab.
       (Bug #55338)</p></li><li><p>
        It was not possible to add the <code class="literal">LOCK TABLES</code>
        privilege when assigning a new role in the Model Overview
        because that privilege was missing from the available options.
       (Bug #55186)</p></li><li><p>
        The schema collation was not saved after being changed in the
        Table Editor.
       (Bug #55152)</p></li><li><p>
        When an attempt was made to synchronize a model with a live
        database, no schemata were listed as available in the
        <span class="guilabel">Synchronize Model with Database</span> wizard.
        This happened when the name of the schema in the model and the
        schema on the live server differed only in lettercase.
       (Bug #55147)</p></li><li><p>
        When using MySQL Workbench to report a bug, it was not possible to
        attach a file using the <span class="guibutton">Choose File</span>
        button because the button had no effect.
       (Bug #55112)</p></li><li><p>
        Dumping tables or schemata without the <code class="literal">LOCK
        TABLE</code> privilege produced this error:
      </p><pre class="programlisting">mysqldump: Got error: 1044: Access denied for user 'wwroot'@'%' to database db' when
doing LOCK TABLES</pre><p>(Bug #55019)</p></li><li><p>
        Selecting <span class="guimenu">Validate (SQL)</span> from the Model menu
        and then selecting the <span class="guilabel">Validate All</span> option
        reported no errors. Selecting <span class="guimenu">Forward
        Engineer</span> from the <span class="guimenu">Database</span> menu and
        selecting <span class="guilabel">Run Validations</span> also reported no
        errors. However, executing the SQL script resulted in this
        error:
      </p><pre class="programlisting">ERROR: Error 1005: Can't create table 'xxx' (errno:150)</pre><p>(Bug #54985)</p></li><li><p>
        Selecting the <span class="guimenu">Check Duplicated Identifiers
        (Additions)</span> operation from the <span class="guimenu">Validation
        (SQL)</span> submenu of the <span class="guimenu">Model</span> menu
        produced this error message:
      </p><pre class="programlisting">Type mismatch: expected object of type db.Schema, but got workbench.physical.Model</pre><p>(Bug #54968)</p></li><li><p>
        When using the <span class="guilabel">Edit Table Data</span> wizard
        (launched from Home screen), if a database with a single table
        was connected to, after selecting the table, the
        <span class="guibutton">Finish</span> button remained grayed out.
       (Bug #54942)</p></li><li><p>
        At startup, these warnings were generated in the Workbench Scripting Shell:
      </p><pre class="programlisting">Starting Workbench...Registered 147 GRT classes.
WARNING: Could not load wb.mysql.validation.grt.dylib: Invalid module
/Applications/MySQLWorkbench.app/Contents/PlugIns/wb.mysql.validation.grt.dylib

WARNING: Could not load wb.validation.grt.dylib: Invalid module
/Applications/MySQLWorkbench.app/Contents/PlugIns/wb.validation.grt.dylib</pre><p>(Bug #54929)</p></li><li><p>
        When an attempt was made to synchronize a modified exported
        script with the current model, using <span class="guimenu">File</span>,
        <span class="guimenu">Export</span>, <span class="guimenu">Synchronize with SQL Create
        Script</span>, the model was not updated.
       (Bug #54501)</p></li><li><p>
        When the <span class="guilabel">Alter Table</span> dialog for an
        <code class="literal">InnoDB</code> table was displayed in an SQL Editor
        session, the <span class="guilabel">Foreign Key Options Index</span>
        showed <span class="guilabel">INVALID</span> when a foreign key in the
        <span class="guilabel">Foreign Keys</span> tab was clicked.
       (Bug #54471)</p></li><li><p>
        MySQL Workbench caused Windows XP to reboot if launched from
        <span class="guimenu">Start</span>, <span class="guimenu">Programs</span>,
        <span class="guimenu">MySQL</span>, <span class="guimenu">MySQL WorkBench 5.2
        OSS</span>.
      </p><p>
        If a MySQL Workbench model file (<code class="filename">.mwb</code>) was
        opened directly, an error dialog titled <span class="guilabel">Microsoft
        Visual C++ Runtime Library</span> was displayed with the
        message:
      </p><pre class="programlisting">R6034
An application has made an attempt to load the C runtime library incorrectly. Please
contact the application's support team for more information.</pre><p>
        The dialog's only option was <span class="guibutton">OK</span>. After
        clicking <span class="guibutton">OK</span>, two more instances of the
        same dialog were displayed. After clicking
        <span class="guibutton">OK</span> for all three, MySQL Workbench opened with
        the model file displayed.
      </p><p>
        On Windows 7 x64, the same runtime error (R6034) occurred.
       (Bug #52949)</p></li><li><p>
        Opening an SQL Editor connection for a remote server produced
        this error:
      </p><pre class="programlisting">OverviewBE::get_node:invalid node 0.0.0.</pre><p>(Bug #52648)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-sql-editor-query-panel.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>6.7.3. SQL Query Panel</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-sql-editor.html" title="6.7. SQL Editor"><link rel="prev" href="wb-sql-editor-toolbar.html" title="6.7.2. Toolbar"><link rel="next" href="wb-sql-editor-main-tabsheets.html" title="6.7.4. Main Tabsheets"></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-query-panel"></a>6.7.3. SQL Query Panel</h3></div></div></div><p>
        In this area, you can enter SQL statements directly. The
        statements entered can be saved to a file for later use. At any
        point, you can also execute the statements you have entered.
      </p><p>
        To save a snippet of code entered into the SQL Query panel,
        click the <span class="guibutton">Save SQL to Snippets List</span>,
        enter a name, and click <span class="guibutton">OK</span>. The snippet
        can be inserted into the SQL Query panel at any time by
        double-clicking the named snippet in the SQL Snippets Palette.
      </p><div class="figure"><a name="wb-sql-editor-statements-panel-screenshot"></a><p class="title"><b>Figure 6.7. SQL Editor - SQL Query Panel</b></p><div class="mediaobject"><img src="images/wb-sql-editor-statements-panel-screenshot.png" width="798" height="207" alt="SQL Editor - SQL Query Panel"></div></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
          To quickly enter the name of a table, view, or column,
          double-click the item in the Schemata Palette. The item name
          will be inserted into the SQL Query panel.
        </p></div></div></body></html>


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

=================================================================== 
Distribute and use freely; there are no restrictions on further 
dissemination and usage except those imposed by the laws of your 
country of residence.  This software is provided "as is" without 
warranty of fitness for use or suitability for any purpose, express 
or implied. Use at your own risk or not at all. 
=================================================================== 

Incorporating the code into commercial products is permitted; you do 
not have to make source available or contribute your changes back 
(though that would be nice). 

--amk 
(www.amk.ca) 

/********************************************************************\ 
 *  FILE:     rmd160.c 
 *  CONTENTS: A sample C-implementation of the RIPEMD-160 hash-function. 
 *  TARGET:   any computer with an ANSI C compiler 
 *  AUTHOR:   Antoon Bosselaers, Dept. Electrical Eng.-ESAT/COSIC 
 *  DATE:     1 March 1996       VERSION:  1.0 
 ********************************************************************** 
 * Copyright (c) Katholieke Universiteit Leuven 1996, All Rights Reserved 
 * The Katholieke Universiteit Leuven makes no representations concerning 
 * either the merchantability of this software or the suitability of this 
 * software for any particular purpose. It is provided "as is" without 
 * express or implied warranty of any kind. These notices must be retained 
 * in any copies of any part of this documentation and/or software. 
\********************************************************************/ </pre></div></body></html>


path: /wb-html-guitools/wb-manage-server-accounts-tab-roles.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>8.7.3.1. Administrative Roles</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-manage-server-accounts-tab.html" title="8.7.3. The Accounts Tab"><link rel="prev" href="wb-manage-server-accounts-tab.html" title="8.7.3. The Accounts Tab"><link rel="next" href="wb-manage-server-connections-tab.html" title="8.7.4. The Connections Tab"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-manage-server-accounts-tab-roles"></a>8.7.3.1. Administrative Roles</h4></div></div></div><p>
          To aid in assigning privileges to MySQL Server users,
          MySQL Workbench introduces the concept of Administrative Roles.
          Roles are a quick way of granting a set of privileges to a
          user, based on the work the user must carry out on the server.
          It is also possible to assign multiple roles to a user. To
          assign roles, click the User Account you wish to modify, then
          click the <span class="guilabel">Administrative Roles</span> tab. Then
          click the check boxes according to the roles you wish to
          allocate to the user. After you select a role to a user, you
          will see the accumulated privileges in the <span class="guilabel">Global
          Privileges Assigned to User</span> panel. For example, if
          you select the role <code class="literal">BackupAdmin</code>, the
          privileges granted include <code class="literal">EVENT</code>,
          <code class="literal">LOCK TABLES</code>, <code class="literal">SELECT</code>,
          <code class="literal">SHOW DATABASES</code>. If you also select the role
          of <code class="literal">ReplicationAdmin</code>, the list of privileges
          expands to include <code class="literal">REPLICATION CLIENT</code>,
          <code class="literal">REPLICATION SLAVE</code> and
          <code class="literal">SUPER</code>.
        </p><p>
          These roles are available:
        </p><div class="itemizedlist"><ul type="disc"><li><p>
              <span class="bold"><strong>DBA</strong></span>: Grants all
              privileges
            </p></li><li><p>
              <span class="bold"><strong>MaintenanceAdmin</strong></span>: Grants
              privileges to maintain the server
            </p></li><li><p>
              <span class="bold"><strong>ProcessAdmin</strong></span>: Grants
              privileges to monitor and kill user processes
            </p></li><li><p>
              <span class="bold"><strong>UserAdmin</strong></span>: Grants
              privileges to create users and reset passwords
            </p></li><li><p>
              <span class="bold"><strong>SecurityAdmin</strong></span>: Grants
              privileges to manage logins and grant and revoke server
              privileges
            </p></li><li><p>
              <span class="bold"><strong>MonitorAdmin</strong></span>: Grants
              privileges to monitor the server
            </p></li><li><p>
              <span class="bold"><strong>DBManager</strong></span>: Grants
              privileges to manage databases
            </p></li><li><p>
              <span class="bold"><strong>DBDesigner</strong></span>: Grants
              privileges to create and reverse engineer any database
              schema
            </p></li><li><p>
              <span class="bold"><strong>ReplicationAdmin</strong></span>: Grants
              privileges to set up and manage replication
            </p></li><li><p>
              <span class="bold"><strong>BackupAdmin</strong></span>: Grants
              privileges required to back up databases
            </p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-reverse-engineer-create-script.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.7.9.1. Reverse Engineering Using a Create 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-reverse-engineering.html" title="7.7.9. Reverse Engineering"><link rel="prev" href="wb-reverse-engineering.html" title="7.7.9. Reverse Engineering"><link rel="next" href="wb-reverse-engineer-live.html" title="7.7.9.2. Reverse Engineering a Live Database"></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-reverse-engineer-create-script"></a>7.7.9.1. Reverse Engineering Using a Create Script</h4></div></div></div><p>
      To reverse engineer using a create script, choose the
      <span class="guimenu">File</span>, <span class="guisubmenu">Import</span>,
      <span class="guimenuitem">Reverse Engineer MySQL Create Script...</span>
      menu items. This opens a file open dialog box with the default
      file type set to an SQL script file, a file with the extension
      <code class="literal">sql</code>.
    </p><p>
      You can create a data definition (DDL) script by executing the
      <strong class="userinput"><code>mysqldump <em class="replaceable"><code>db_name</code></em>
      <code class="option">--no-data</code> &gt;
      <em class="replaceable"><code>script_file.sql</code></em></code></strong> command.
      Using the <code class="option">--no-data</code> option ensures that the
      script contains only DDL statements. However, if you are working
      with a script that also contains DML statements you need not
      remove them; they will be ignored.
    </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
        If you plan to redesign a database within MySQL Workbench and then
        export the changes, be sure to retain a copy of the original DDL
        script. You will need the original script to create an
        <code class="literal">ALTER</code> script. For more information, see
        <a href="wb-forward-engineering-sql-scripts.html#wb-export-script-alter-schema" title="7.7.10.1.2. Altering a Schema">Section 7.7.10.1.2, “Altering a Schema”</a>.
      </p></div><p>
      Use the <code class="option">--databases</code> option with
      <span><strong class="command">mysqldump</strong></span> if you wish to create the database as
      well as all its objects. If there is no <code class="literal">CREATE DATABASE
      <em class="replaceable"><code>db_name</code></em></code> statement in your
      script file, you must import the database objects into an existing
      schema or, if there is no schema, a new unnamed schema is created.
    </p><p>
      If your script creates a database, MySQL Workbench creates a new
      physical schemata tab on the <code class="literal">MySQL Model</code> page.
    </p><p>
      Any database objects may be imported from a script file in this
      fashion: tables, views, routines, and routine groups. Any indexes,
      keys, and constraints are also imported. Objects imported using an
      SQL script can be manipulated within MySQL Workbench the same as other
      objects.
    </p><p>
      Before exiting, be sure to save the schema. Choose the
      <span class="guimenu">File</span>, <span class="guimenuitem">Save</span> menu item
      and the reverse-engineered database will be saved as a MySQL
      Workbench file with the extension <code class="literal">mwb</code>.
    </p><p>
      See <a href="wb-importing-sql-script.html" title="7.8.1. Importing a Data Definition SQL Script">Section 7.8.1, “Importing a Data Definition SQL Script”</a>, for a tutorial on
      reverse engineering the <code class="literal">sakila</code> database.
    </p></div></body></html>


path: /wb-html-guitools/wb-news-5-1-13.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.2.7. Changes in MySQL Workbench 5.1.13 (12 June 2009)</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="changes-5.1.x.html" title="A.2. Changes in Release 5.1"><link rel="prev" href="wb-news-5-1-14.html" title="A.2.6. Changes in MySQL Workbench 5.1.14 (19 June 2009)"><link rel="next" href="wb-news-5-1-12.html" title="A.2.8. Changes in MySQL Workbench 5.1.12 (27 April 2009)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-news-5-1-13"></a>A.2.7. Changes in MySQL Workbench 5.1.13 (12 June 2009)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.1.12.
      </p><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        When using the <span class="guilabel">Forward Engineer SQL Script</span>
        wizard, the <span class="guilabel">SQL Object Export Filter</span> step
        displayed duplicate items.
       (Bug #45241)</p></li><li><p>
        When using the <span class="guilabel">Generate Catalog Diff Report</span>
        wizard, the Stored Connection information was not automatically
        populated when a previously defined Stored Connection was
        selected.
       (Bug #45234)</p></li><li><p>
        Adding Insert records for a table worked correctly. However,
        there was no way to remove the records once the <span class="guibutton">Open
        Editor</span> facility has been used to add them.
       (Bug #45233)</p></li><li><p>
        On Mac OS X, using the <span class="guilabel">Forward Engineer to
        Database</span>, or <span class="guilabel">Forward Engineer SQL
        Script</span> wizards caused MySQL Workbench to generate this
        error message:
      </p><pre class="programlisting">The application MySQLWorkbench quit unexpectedly after it was relaunched.</pre><p>(Bug #45229)</p></li><li><p>
        When defining a primary key with a user-defined data type, it
        was not possible to set the auto-increment (AI) attribute.
        Clicking the AI check box had no effect.
      </p><p>
        To circumvent this problem it was possible to temporarily change
        the data type of the column to a built-in data type such as
        <code class="literal">INT</code>, set the AI attribute and then change the
        data type back to the desired user-defined data type. The model
        could then be saved. However, if this model was reopened and
        <span class="guimenu">File</span>, <span class="guimenu">Export</span>,
        <span class="guimenu">Forward Engineer SQL CREATE Script</span> used to
        generate a script, MySQL Workbench would crash.
       (Bug #45165)</p></li><li><p>
        MySQL Workbench did not limit foreign key name length. This meant
        that an exported SQL script was invalid and MySQL Server
        generated an error on attempting to import it:
      </p><pre class="programlisting">1059 - ER_TOO_LONG_IDENT</pre><p>(Bug #45139)</p></li><li><p>
        On Mac OS X, if the mouse pointer was used to select an entity
        and then
        <span class="guibutton">Command</span>+<span class="guibutton">Delete</span> was
        pressed before the tooltip appeared, MySQL Workbench crashed when
        the delete was confirmed.
       (Bug #45042)</p></li><li><p>
        Foreign key names must be unique. However, MySQL Workbench default
        generated foreign key names were sometimes identical, causing
        Forward Engineer SQL CREATE Script to fail.
       (Bug #45027)</p></li><li><p>
        Synchronization of the model with an external database failed to
        report errors. This meant there was the possibility of an
        incomplete synchronization, without the developer being
        informed.
       (Bug #45024)</p></li><li><p>
        Changing a relationship's visibility had no effect.
      </p><p>
        If a relationship was right-clicked in the EER diagram,
        <span class="guimenu">Edit Relationship</span> selected, and then the
        <span class="guilabel">Relationship</span> tab selected, the visibility
        radio buttons were displayed. However, if the visibility
        settings were changed there was no effect.
       (Bug #44988)</p></li><li><p>
        On Ubuntu Linux, MySQL Workbench crashed with a segmentation fault
        when an attempt was made to save the model.
       (Bug #44974)</p></li><li><p>
        On the Linux version of MySQL Workbench it was not possible to
        rename a layer by double-clicking it in the
        <span class="guilabel">Layers</span> window (which is typically docked to
        the right hand side of the screen).
      </p><p>
        A layer editor has now been added to the Linux version of
        MySQL Workbench. This can be activated by double-clicking the
        layer's title.
       (Bug #44972)</p></li><li><p>
        It was not possible to rename a table created using
        <span class="guilabel">Add Table</span>, by copying text into its text
        field.
       (Bug #44913)</p></li><li><p>
        In the <span class="guilabel">Flags</span> box, which is located in the
        <span class="guilabel">Column Details</span> panel in the <span class="guilabel">Table
        Editor</span>, the same flags were not listed as available
        for both the <code class="literal">INT</code> and
        <code class="literal">INTEGER</code> data types. <code class="literal">INT</code>
        has both <code class="literal">UNSIGNED</code> and
        <code class="literal">ZEROFILL</code> listed, but these were not listed
        for the column if it was of type <code class="literal">INTEGER</code>.
        Also, the <span class="guilabel">AI</span> check box was not selectable
        for columns defined as <code class="literal">INTEGER</code>.
       (Bug #44872)</p></li><li><p>
        Using the <span class="guilabel">Foreign Keys</span> tab of the
        <span class="guilabel">Table Editor</span>, it was not possible to
        correctly create multiple foreign key relationships.
       (Bug #44701)</p></li><li><p>
        MySQL Workbench appeared not to display table rows in an EER diagram
        for tables that had more than 20 columns.
      </p><p>
        MySQL Workbench now includes the ability to manually resize the
        table, besides automatically limiting the number of columns to a
        user selectable value, by order of appearance, regardless of
        being key columns or not.
       (Bug #44675)</p></li><li><p>
        On Debian Linux (Lenny), after adding a second table and
        selecting AI on the first column element, MySQL Workbench generated
        a segmentation fault.
       (Bug #44612)</p></li><li><p>
        In the <span class="guilabel">Workbench Preferences</span> dialog, on the
        <span class="guilabel">Diagram</span> tab, in the
        <span class="guilabel">Tables</span> panel, the check boxes
        <span class="guilabel">Show Column Types</span> and <span class="guilabel">Show Column
        Flags</span> did not work correctly. Selecting or
        deselecting <span class="guilabel">Show Column Types</span> only had an
        effect when MySQL Workbench was restarted. Selecting <span class="guilabel">Show
        Column Flags</span> had no effect at all, and the flags were
        never displayed.
       (Bug #44586)</p></li><li><p>
        When in the <span class="guilabel">Columns</span> tab of the
        <span class="guilabel">Table Editor</span>, if an attempt was made to
        change a column data type to <code class="literal">INTEGER(n)</code> this
        would have no effect and the column data type would remain
        unchanged. However, if <code class="literal">INT(n)</code> was entered
        this was accepted and the data type changed accordingly.
       (Bug #44552)</p></li><li><p>
        When a new index was created in the <span class="guilabel">Indexes</span>
        tab for a table that already had indexes, the previously
        displayed index field remained selected. This caused concern
        that the newly created index would be on the wrong field.
       (Bug #44532)</p></li><li><p>
        The <span class="guilabel">Forward Engineer SQL Script</span> wizard did
        not permit the SQL script text to be copied using the keyboard
        shortcut. Only the mouse could be used to select and copy the
        text.
       (Bug #44531)</p></li><li><p>
        On Ubuntu Linux, the following MySQL Workbench menu items did not
        work: <span class="guimenu">Page Setup</span>, <span class="guimenu">Print
        Preview</span> and <span class="guimenu">Print</span>.
      </p><p>
        If those menu items were selected, these console messages were
        generated:
      </p><pre class="programlisting">** Message: item_activated: 0xaa44bf0 -&gt; 'builtin:wb.page_setup'
** Message: show_progress_becb not implemented
** Message: unhandled message 4: wb.print.setup finished in 0,00s

** Message: show_progress_becb not implemented
create font Helvetica 0 0 11,000000 (200)** Message: item_activated: 0xa4c9800 -&gt;
'plugin:wb.print.printPreview'
** Message: show_progress_becb not implemented

** (mysql-workbench-bin:11732): WARNING **: Could not open editor shared object
'/usr/lib/mysql-workbench/plugins/'
** Message: unhandled message 4: wb.print.printPreview finished in 0,00s

** Message: show_progress_becb not implemented
** Message: item_activated: 0xa4cec08 -&gt; 'plugin:wb.print.print'
** Message: show_progress_becb not implemented
** Message: unhandled message 4: wb.print.print finished in 0,00s

** Message: show_progress_becb not implemented
create font Helvetica 0 0 11,000000 (300)</pre><p>(Bug #44524)</p></li><li><p>
        When a Routine Group was renamed, this was not immediately
        updated in the EER diagram.
       (Bug #44503)</p></li><li><p>
        When <code class="literal">Workbench:copyToClipboard()</code> was used
        from within a plugin, only garbage characters were copied to the
        Windows clipboard. This affected the operation of plugins.
      </p><p>
        When a plugin attempted to output the string
        “<span class="quote">abcdefghijklmnopqrstuvwxyz0123456789!§$%&amp;/()=</span>”
        a runtime exception was generated.
       (Bug #44461)</p></li><li><p>
        The <span class="guilabel">Forward Engineer SQL Script</span> wizard
        would write over an existing file without prompting the user for
        confirmation.
       (Bug #44437)</p></li><li><p>
        On Mac OS X, an application window's red close button should
        contain a solid circle if the current document is unsaved.
        However, for MySQL Workbench this did not work correctly. Although
        the circle was initially shown, it was not displayed after
        subsequent edits to the model.
       (Bug #44435)</p></li><li><p>
        When attempting to delete an existing EER diagram, MySQL Workbench
        crashed.
      </p><p>
        The origin of the diagram seemed to have no bearing on whether
        the crash occurred because it happened both with diagrams
        created from reverse engineering and those created
        independently.
       (Bug #44407)</p></li><li><p>
        Deleting or cutting a Relation from an EER diagram crashed
        MySQL Workbench.
       (Bug #44340)</p></li><li><p>
        When Relations were deleted using the Foreign Keys tab,
        MySQL Workbench intermittently generated an exception:
      </p><pre class="programlisting">System.AccessViolationException: Attempted to read or write protected memory. This is
often an indication that other memory is corrupt.
   at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method,
Object[] args, Boolean synchronous)
   at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
   at System.Windows.Forms.Control.Invoke(Delegate method)
   at MySQL.GUI.Workbench.Plugins.ObjectEditorPlugin.RefreshFormDataInvoke()
   at MySQL.Grt.DelegateSlot0&lt;void\,void&gt;.cpp_callback()
   at sigc.pointer_functor0&lt;void&gt;.()(pointer_functor0&lt;void&gt;* )
   at sigc.adaptor_functor&lt;sigc::pointer_functor0&lt;void&gt;
&gt;.()(adaptor_functor&lt;sigc::pointer_functor0&lt;void&gt; &gt;* )
   at sigc.internal.slot_call0&lt;sigc::pointer_functor0&lt;void&gt;,void&gt;.call_it(slot_rep* rep)
   at MySQL.Grt.Db.TableEditorBE.remove_fk(NodeId fk)
   at
MySQL.GUI.Workbench.Plugins.DbMysqlTableEditor.deleteSelectedFKsToolStripMenuItem_Click(Ob
ject sender, EventArgs e)
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e,
ToolStripItemEventType met)
   at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType
met)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message&amp; m, MouseButtons button, Int32
clicks)
   at System.Windows.Forms.Control.WndProc(Message&amp; m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message&amp; m)
   at System.Windows.Forms.ToolStrip.WndProc(Message&amp; m)
   at System.Windows.Forms.ToolStripDropDown.WndProc(Message&amp; m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message&amp; m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message&amp; m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam,
IntPtr lparam)</pre><p>(Bug #44326)</p></li><li><p>
        When exiting MySQL Workbench with unsaved changes, you are given the
        choices <span class="guibutton">Save</span>, <span class="guibutton">Don't
        Save</span> and <span class="guibutton">Cancel</span>. When
        <span class="guibutton">Cancel</span> was clicked, MySQL Workbench exited
        without saving, rather than returning to the application without
        making any changes.
      </p><p>
        This only happened when clicking the main application Close
        button, in the upper right corner. It did not happen if the
        application was exited by selecting <span class="guimenu">File</span>,
        <span class="guimenu">Exit</span> from the main menu.
       (Bug #44267)</p></li><li><p>
        The <span class="guimenu">Copy SQL to Clipboard</span> menu item, which
        was normally available when right-clicking a table in
        MySQL Workbench, was not displayed.
       (Bug #44254)</p></li><li><p>
        If the order of columns was changed in the
        <span class="guilabel">Columns</span> tab, this was not reflected in the
        EER diagram.
       (Bug #44240)</p></li><li><p>
        In the table editor the <code class="literal">VARBINARY</code> data type
        was not listed in the list for columns.
       (Bug #44023)</p></li><li><p>
        In the table editor, when a column was added with a data type of
        <code class="literal">TIMESTAMP</code>, and the default value of 0
        entered, MySQL Workbench erroneously added quotation marks around
        the 0. Any generated SQL script therefore contained errors, and
        would subsequently fail.
       (Bug #44006)</p></li><li><p>
        The <span class="guilabel">Forward Engineer SQL Script</span> wizard did
        not emit table INSERT statements in the generated script when
        requested to do so.
       (Bug #43799, Bug #44385)</p></li><li><p>
        When synchronizing a model with a database, using the
        <span class="guilabel">Synchronize Model with Database</span> wizard, the
        data type translation resulted in errors.
       (Bug #42728)</p></li><li><p>
        Omit Schema Qualifiers did not omit schema for foreign keys.
      </p><p>
        When using <span class="guimenu">File</span>, <span class="guimenu">Export</span>,
        <span class="guimenu">Forward Engineer SQL CREATE Script</span> and
        selecting the <span class="guilabel">Omit Schema Qualifiers</span> check
        box, the schema for foreign keys were not omitted.
       (Bug #42328)</p></li><li><p>
        When editing a column's type in the <span class="guilabel">Columns</span>
        tab of the <span class="guilabel">Table Editor</span>, the list for
        selecting the data type displayed <code class="literal">BOOL</code>.
        However, once that had been selected the data type was displayed
        as <code class="literal">BOOLEAN</code>.
      </p><p>
        Further, if a column data type was set by entering
        <code class="literal">INTEGER</code> in the <span class="guilabel">Datatype</span>
        column, it then changed to <code class="literal">INT</code> on pressing
        return.
       (Bug #41934)</p></li><li><p>
        MySQL Workbench frequently crashed with an unknown exception in Wb.h
        at line 1010.
      </p><p>
        This occurred while working on tables within EER diagrams on a
        design consisting of more than 190 tables and 20 EER diagrams.
       (Bug #41325)</p></li><li><p>
        Invisible characters in a reverse engineered script caused
        errors to be generated when the same script was forward
        engineered.
      </p><p>
        The problem was due to the reverse engineered script containing
        a mixture of \n, \r and \r\n line endings. These are now
        normalized to \n in the reverse engneering code. The validation
        process now also checks SQL code objects to ensure valid line
        endings.
       (Bug #41254)</p></li><li><p>
        When working in the <span class="guilabel">Routines</span> tab of the
        <span class="guilabel">Routine Group</span> editor, the
        <span class="guilabel">Routine</span> tab did not appear to save changes
        to routine code.
      </p><p>
        If code was copied from an external application into the
        <span class="guilabel">Routine</span> tab, then the model saved and
        MySQL Workbench exited, then on restarting MySQL Workbench, any changes
        to the routine code were lost.
       (Bug #40885)</p></li><li><p>
        When trying to synchronize a model to a database, tables
        defining some columns as <code class="literal">FLOAT</code> or
        <code class="literal">DOUBLE</code> prevented the synchronization SQL
        script from working.
      </p><p>
        The SQL generated used the syntax <code class="literal">FLOAT(256)</code>
        or <code class="literal">DOUBLE(256)</code> which was rejected by MySQL
        Server 5.0.51a.
      </p><p>
        Editing the generated script manually to use just
        <code class="literal">FLOAT</code> or <code class="literal">DOUBLE</code> worked.
        However, MySQL Workbench then assumed the target table was not
        correctly synchronized, and prompted the user accordingly.
       (Bug #40169)</p></li><li><p>
        When a relationship was fully visible in the EER diagram, if the
        user chose to have it drawn split, or hidden, MySQL Workbench
        behaved as expected. However, if the relationship was hidden,
        and the user chose to have it drawn split, or fully visible
        again, the relationship was not properly redrawn. The user had
        to move either of the tables involved in the relationship to
        have the relationship redrawn.
       (Bug #40015)</p></li><li><p>
        When editing a foreign key in the <span class="guilabel">Foreign
        Keys</span> tab of the Table Editor, and then removing the
        corresponding relationship from the EER Diagram canvas, the
        <span class="guilabel">Foreign Keys</span> tab remained open and
        populated, instead of being cleared and closed.
       (Bug #39478)</p></li><li><p>
        When tables with relationship connectors were dragged or copied
        from one EER diagram to another, the connectors were not always
        drawn.
       (Bug #38545)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-model-editor.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.5. Model Editor</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-data-modeling.html" title="Chapter 7. Data Modeling"><link rel="prev" href="wb-data-modeling-create-model-from-sql-script.html" title="7.4. Create EER Model from SQL Script"><link rel="next" href="wb-data-modeling-menus.html" title="7.5.1. Modeling Menus"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="wb-model-editor"></a>7.5. Model Editor</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-data-modeling-menus.html">7.5.1. Modeling Menus</a></span></dt><dt><span class="section"><a href="wb-toolbar.html">7.5.2. The Toolbar</a></span></dt><dt><span class="section"><a href="wb-eer-diagrams-section.html">7.5.3. EER Diagrams</a></span></dt><dt><span class="section"><a href="wb-view-overview-physical-schemata.html">7.5.4. The Physical Schemata Panel</a></span></dt><dt><span class="section"><a href="wb-model-overview-privileges.html">7.5.5. The Schema Privileges Panel</a></span></dt><dt><span class="section"><a href="wb-views-overview-scripts.html">7.5.6. The SQL Scripts Panel</a></span></dt><dt><span class="section"><a href="wb-views-overview-notes.html">7.5.7. The Model Notes Panel</a></span></dt><dt><span class="section"><a href="wb-history-palette.html">7.5.8. The History Palette</a></span></dt><dt><span class="section"><a href="wb-navigator-panel.html">7.5.9. The Model Navigator Panel</a></span></dt><dt><span class="section"><a href="wb-catalog-palette.html">7.5.10. The Catalog Tree Palette</a></span></dt><dt><span class="section"><a href="wb-layers-palette.html">7.5.11. The Layers Palette</a></span></dt><dt><span class="section"><a href="wb-properties-palette.html">7.5.12. The Properties Palette</a></span></dt></dl></div><p>
    When the Model Editor is executed from the Home window, MySQL Workbench
    displays the MySQL Model page. The MySQL Model page has three main
    panels, as shown in the following screenshot: Description Editor,
    User Types List/History panel, and Model Overview.
  </p><div class="figure"><a name="wb-mysql-model-page-image"></a><p class="title"><b>Figure 7.1. The <code class="literal">MySQL Model</code> Page</b></p><div class="mediaobject"><img src="images/wb-mysql-model-page.png" width="1024" height="708" alt="The MySQL Model Page"></div></div><p>
    The Description Editor and User Types List/History panel are
    contained within the Sidebar. The Sidebar is located on the left by
    default, but can be relocated to the right using a setting in the
    Workbench Preferences dialog.
  </p><p>
    The Model Overview panel has several sections:
  </p><div class="itemizedlist"><ul type="disc"><li><p>
        EER Diagrams
      </p></li><li><p>
        Physical Schemata
      </p></li><li><p>
        Schema Privileges
      </p></li><li><p>
        SQL Scripts
      </p></li><li><p>
        Model Notes
      </p></li></ul></div><p>
    For each of these sections, add objects to a project by clicking the
    appropriate add-object icon. You may also rename, edit, cut, copy,
    or delete objects on this page by right-clicking to open a pop-up
    menu.
  </p><p>
    The following sections further discuss the MySQL Model page.
  </p></div></body></html>


path: /wb-html-guitools/wb-properties-palette.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.5.12. The Properties Palette</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-model-editor.html" title="7.5. Model Editor"><link rel="prev" href="wb-invisible-objects-layers.html" title="7.5.11.1. Finding Invisible Objects Using the Layers Palette"><link rel="next" href="wb-eer-diagram-editor.html" title="7.6. EER Diagram Editor"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-properties-palette"></a>7.5.12. The Properties Palette</h3></div></div></div><p>
      The <code class="literal">Properties</code> palette is used to display and
      edit the properties of objects on an EER diagram. It is especially
      useful for editing display objects such as layers and notes.
    </p><p>
      All objects except connections have the following properties
      except as noted:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <code class="literal">color</code>: The color accent of the object,
          displayed as a hexadecimal value. Change the color of the
          object by changing this value. Only characters that are legal
          for hexadecimal values may be entered. You can also change the
          color by clicking the <span class="guibutton">...</span> button to
          open a color changer dialog box.
        </p></li><li><p>
          <code class="literal">description</code>: Applicable to layers only. A
          means of documenting the purpose of a layer.
        </p></li><li><p>
          <code class="literal">expanded</code>: This attribute applies to objects
          such as tables that can be expanded to show columns, indexes,
          and triggers.
        </p></li><li><p>
          <code class="literal">height</code>: The height of the object. Depending
          upon the object, this property may be read only or read/write.
        </p></li><li><p>
          <code class="literal">left</code>: The number of pixels from the object
          to the left side of the canvas.
        </p></li><li><p>
          <code class="literal">locked</code>: Whether the object is locked. The
          value for this attribute is either <code class="literal">true</code> or
          <code class="literal">false</code>.
        </p></li><li><p>
          <code class="literal">manualSizing</code>: Whether the object has been
          manually sized. The value for this attribute is either
          <code class="literal">true</code> or <code class="literal">false</code>.
        </p></li><li><p>
          <code class="literal">name</code>: The name of the object.
        </p></li><li><p>
          <code class="literal">top</code>: The number of pixels from the object
          to the top of the canvas.
        </p></li><li><p>
          <code class="literal">visible</code>: Whether the object shows up on the
          canvas. Use <code class="literal">‘1’</code> for true and
          <code class="literal">‘0’</code> for false. It is currently
          used only for relationships.
        </p></li><li><p>
          <code class="literal">width</code>: The width of the object. Depending
          upon the object, this property may be read only or read/write.
        </p></li></ul></div><p>
      
    </p><p>
      Tables have the following additional properties:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <code class="literal">indexesExpanded</code>: Whether indexes are
          displayed when a table is placed on the canvas. Use
          <code class="literal">‘1’</code> for true and
          <code class="literal">‘0’</code> for false.
        </p></li><li><p>
          <code class="literal">triggersExpanded</code>: Whether triggers are
          displayed when a table is placed on the canvas. Use
          <code class="literal">‘1’</code> for true and
          <code class="literal">‘0’</code> for false.
        </p></li></ul></div><p>
      For a discussion of connection properties, see
      <a href="wb-connection-properties.html" title="7.7.2.3. Connection Properties">Section 7.7.2.3, “Connection Properties”</a>.
    </p></div></body></html>


path: /wb-html-guitools/changes-5.0.x.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.3. Changes in Release 5.0</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-change-history.html" title="Appendix A. MySQL Workbench Change History"><link rel="prev" href="wb-news-5-1-4.html" title="A.2.15. Changes in MySQL Workbench 5.1.4 (Not yet released)"><link rel="next" href="wb-news-5-0-30.html" title="A.3.1. Changes in MySQL Workbench 5.0.30 (18 February 2009)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="changes-5.0.x"></a>A.3. Changes in Release 5.0</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-news-5-0-30.html">A.3.1. Changes in MySQL Workbench 5.0.30 (18 February 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-29.html">A.3.2. Changes in MySQL Workbench 5.0.29 (12 December 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-28.html">A.3.3. Changes in MySQL Workbench 5.0.28 (06 December 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-27.html">A.3.4. Changes in MySQL Workbench 5.0.27 (07 November 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-26.html">A.3.5. Changes in MySQL Workbench 5.0.26 (16 October 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-25.html">A.3.6. Changes in MySQL Workbench 5.0.25 (12 September 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-24.html">A.3.7. Changes in MySQL Workbench 5.0.24 (12 August 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-23.html">A.3.8. Changes in MySQL Workbench 5.0.23 (25 June 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-22.html">A.3.9. Changes in MySQL Workbench 5.0.22 (27 May 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-21.html">A.3.10. Changes in MySQL Workbench 5.0.21 (27 April 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-20.html">A.3.11. Changes in MySQL Workbench 5.0.20 (26 April 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-19.html">A.3.12. Changes in MySQL Workbench 5.0.19 (15 April 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-18.html">A.3.13. Changes in MySQL Workbench 5.0.18rc (not released)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-17.html">A.3.14. Changes in MySQL Workbench 5.0.17rc (07 April 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-16.html">A.3.15. Changes in MySQL Workbench 5.0.16rc (26 March 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-15.html">A.3.16. Changes in MySQL Workbench 5.0.15rc (17 March 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-14a.html">A.3.17. Changes in MySQL Workbench 5.0.14abeta (28 February 2008)</a></span></dt><dt><span class="section"><a href="wb-news-5-0-14.html">A.3.18. Changes in MySQL Workbench 5.0.14beta (25 February 2008)</a></span></dt></dl></div></div></body></html>


path: /wb-html-guitools/wb-manage-server-startup-tab.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>8.7.1. The Startup Tab</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-server-administration-configuration.html" title="8.7. Server Administration and Configuration"><link rel="prev" href="wb-server-administration-configuration.html" title="8.7. Server Administration and Configuration"><link rel="next" href="wb-manage-server-configuration-tab.html" title="8.7.2. The Configuration Tab"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-manage-server-startup-tab"></a>8.7.1. The Startup Tab</h3></div></div></div><p>
        The Startup tab has several purposes:
      </p><div class="itemizedlist"><ul type="disc"><li><p>
            To display database server status
          </p></li><li><p>
            To start up and shut down the server
          </p></li><li><p>
            To display the Startup Message log
          </p></li><li><p>
            To select whether the server starts when the system starts
          </p></li></ul></div><div class="figure"><a name="wb-manage-server-startup-tab-screenshot"></a><p class="title"><b>Figure 8.4. Administrator - Startup Tab</b></p><div class="mediaobject"><img src="images/wb-manage-server-startup-tab.png" width="1024" height="707" alt="Administrator - Startup Tab"></div></div></div></body></html>


path: /wb-html-guitools/changes-5.1.x.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.2. Changes in Release 5.1</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-change-history.html" title="Appendix A. MySQL Workbench Change History"><link rel="prev" href="wb-news-5-2-0.html" title="A.1.40. Changes in MySQL Workbench 5.2.0 (30 April 2009 Alpha)"><link rel="next" href="wb-news-5-1-19.html" title="A.2.1. Changes in MySQL Workbench 5.1.19 (06 September 2010)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="changes-5.1.x"></a>A.2. Changes in Release 5.1</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-news-5-1-19.html">A.2.1. Changes in MySQL Workbench 5.1.19 (06 September 2010)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-18.html">A.2.2. Changes in MySQL Workbench 5.1.18 (03 September 2009 General Availability)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-17.html">A.2.3. Changes in MySQL Workbench 5.1.17 (14 August 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-16.html">A.2.4. Changes in MySQL Workbench 5.1.16 (30 June 2009 General Availability)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-15.html">A.2.5. Changes in MySQL Workbench 5.1.15 (26 June 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-14.html">A.2.6. Changes in MySQL Workbench 5.1.14 (19 June 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-13.html">A.2.7. Changes in MySQL Workbench 5.1.13 (12 June 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-12.html">A.2.8. Changes in MySQL Workbench 5.1.12 (27 April 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-11.html">A.2.9. Changes in MySQL Workbench 5.1.11 (Not yet released)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-10.html">A.2.10. Changes in MySQL Workbench 5.1.10 (10 April 2009)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-9.html">A.2.11. Changes in MySQL Workbench 5.1.9 (Not yet released Beta)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-8.html">A.2.12. Changes in MySQL Workbench 5.1.8 (Not yet released)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-7.html">A.2.13. Changes in MySQL Workbench 5.1.7 (Not yet released)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-6.html">A.2.14. Changes in MySQL Workbench 5.1.6 (Not yet released)</a></span></dt><dt><span class="section"><a href="wb-news-5-1-4.html">A.2.15. Changes in MySQL Workbench 5.1.4 (Not yet released)</a></span></dt></dl></div></div></body></html>


path: /wb-html-guitools/wb-manage-server-data-dump-tab.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>8.7.6. The Data Dump Tab</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-server-administration-configuration.html" title="8.7. Server Administration and Configuration"><link rel="prev" href="wb-manage-server-variables-tab.html" title="8.7.5. The Variables Tab"><link rel="next" href="wb-manage-server-export-to-disk.html" title="8.7.6.1. Export to Disk"></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-data-dump-tab"></a>8.7.6. The Data Dump Tab</h3></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-manage-server-export-to-disk.html">8.7.6.1. Export to Disk</a></span></dt><dt><span class="section"><a href="wb-manage-server-import-from-disk.html">8.7.6.2. Import from Disk</a></span></dt><dt><span class="section"><a href="wb-manage-server-advanced-options.html">8.7.6.3. Advanced Export Options</a></span></dt></dl></div><p>
        The Import/Export Server Data tab enables you to create a dump
        file, or restore data from a dump file. Clicking the
        <span class="guilabel">Import/Export Server Data</span> action item
        launches a new Admin page, at the Data Dump tab.
      </p><p>
        Within the Data Dump tab are three further tabbed windows:
      </p><div class="itemizedlist"><ul type="disc"><li><p>
            Export to Disk
          </p></li><li><p>
            Import from Disk
          </p></li><li><p>
            Advanced Options
          </p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-reverse-engineer-live.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.7.9.2. Reverse Engineering a Live Database</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-reverse-engineering.html" title="7.7.9. Reverse Engineering"><link rel="prev" href="wb-reverse-engineer-create-script.html" title="7.7.9.1. Reverse Engineering Using a Create Script"><link rel="next" href="wb-forward-engineering.html" title="7.7.10. Forward 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-reverse-engineer-live"></a>7.7.9.2. Reverse Engineering a Live Database</h4></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-reverse-engineer-live.html#wb-errors-reverse-engineering">7.7.9.2.1. Errors During Reverse Engineering</a></span></dt></dl></div><p>
      To reverse engineer a live database, choose the
      <span class="guimenu">Database</span>, <span class="guimenuitem">Reverse
      Engineer...</span> menu item from the main menu. This opens
      the Reverse Engineer Database wizard.
    </p><div class="figure"><a name="wb-reverse-engineer-database-wizard"></a><p class="title"><b>Figure 7.14. Reverse Engineer Database Wizard</b></p><div class="mediaobject"><img src="images/wb-reverse-engineer-database-wizard.png" width="798" height="598" alt="Reverse Engineer Database Wizard"></div></div><p>
      The first page of the wizard enables you to set up a connection to
      the live database you wish to reverse engineer. You can set up a
      new connection or select a previously created stored connection.
      Typical information required for the connection includes host
      name, user name and password.
    </p><p>
      After this information has been entered, or you have selected a
      stored connection, click the <span class="guibutton">Next</span> button to
      proceed to the next page.
    </p><div class="figure"><a name="wb-reverse-engineer-database-wizard-connect-dbms"></a><p class="title"><b>Figure 7.15. Connect to DBMS</b></p><div class="mediaobject"><img src="images/wb-reverse-engineer-database-wizard-connect-dbms.png" width="798" height="598" alt="Connect to DBMS"></div></div><p>
      Review the displayed information to make sure that the connection
      did not generate errors, then click <span class="guibutton">Next</span>.
    </p><p>
      The next page displays the schemata available on the server. Click
      the check box or check boxes for any schemata you wish to process.
    </p><div class="figure"><a name="wb-reverse-engineer-database-wizard-select-schemata"></a><p class="title"><b>Figure 7.16. Select Schemata</b></p><div class="mediaobject"><img src="images/wb-reverse-engineer-database-wizard-select-schemata.png" width="798" height="598" alt="Select Schemata"></div></div><p>
      After you have selected the desired schemata, click the
      <span class="guibutton">Next</span> button to continue.
    </p><p>
      The wizard then displays the tasks it carried out and summarizes
      the results of the operation.
    </p><div class="figure"><a name="wb-reverse-engineer-database-wizard-fetch-object-info"></a><p class="title"><b>Figure 7.17. Retrieve Object Information</b></p><div class="mediaobject"><img src="images/wb-reverse-engineer-database-wizard-fetch-object-info.png" width="798" height="598" alt="Retrieve Object Information"></div></div><p>
      Review the results before clicking <span class="guibutton">Next</span> to
      continue.
    </p><p>
      The next page is the <code class="literal">Select Objects</code> page. It
      has a section for each object type present in the schema (tables,
      views, routines, and so forth). This page is of special interest
      if you do not wish to import all the objects from the existing
      database. It gives you the option of filtering which objects are
      imported. Each section has a <span class="guibutton">Show Filter</span>
      button. Click this button if you do not want to import all the
      objects of a specific type.
    </p><div class="figure"><a name="wb-reverse-engineer-database-wizard-select-objects"></a><p class="title"><b>Figure 7.18. Select Objects</b></p><div class="mediaobject"><img src="images/wb-reverse-engineer-database-wizard-select-objects.png" width="798" height="598" alt="Select Objects"></div></div><p>
      For the <span class="guilabel">Import MySQL Table Objects</span> section,
      if you click the <span class="guibutton">Show Filter</span> button, the
      following page is displayed.
    </p><div class="figure"><a name="wb-reverse-engineer-database-wizard-show-filter"></a><p class="title"><b>Figure 7.19. Show Filter</b></p><div class="mediaobject"><img src="images/wb-reverse-engineer-database-wizard-show-filter.png" width="798" height="598" alt="Show Filter"></div></div><p>
      This page enables you to select specific tables for import. Having
      selected the desired tables, you can optionally hide the filter by
      clicking the <span class="guibutton">Hide Filter</span> button.
    </p><p>
      The other sections, such as <span class="guilabel">MySQL Routine
      Objects</span>, have similar filters available.
    </p><p>
      Click <span class="guibutton">Execute</span> to continue to the next page.
    </p><p>
      The wizard then imports objects, displaying the tasks that have
      been carried out and whether the operation was successful. If
      errors were generated, you can click the <span class="guibutton">Show
      Logs</span> button to see the nature of the errors.
    </p><div class="figure"><a name="wb-reverse-engineer-database-wizard-progress"></a><p class="title"><b>Figure 7.20. Progress</b></p><div class="mediaobject"><img src="images/wb-reverse-engineer-database-wizard-progress.png" width="798" height="598" alt="Progress"></div></div><p>
      Click <span class="guibutton">Next</span> to continue to the next page.
    </p><p>
      The final page of the wizard provides a summary of the reverse
      engineered objects.
    </p><div class="figure"><a name="wb-reverse-engineer-database-wizard-results"></a><p class="title"><b>Figure 7.21. Results</b></p><div class="mediaobject"><img src="images/wb-reverse-engineer-database-wizard-results.png" width="798" height="598" alt="Results"></div></div><p>
      Click <span class="guibutton">Finish</span> to exit the wizard.
    </p><p>
      Before exiting MySQL Workbench be sure to save the schema. Choose the
      <span class="guimenu">File</span>, <span class="guimenuitem">Save</span> menu item
      to save the reverse-engineered database as a MySQL Workbench file
      with the extension <code class="literal">mwb</code>.
    </p><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="wb-errors-reverse-engineering"></a>7.7.9.2.1. Errors During Reverse Engineering</h5></div></div></div><p>
        During reverse engineering, the application checks for tables
        and views that duplicate existing names and disallows duplicate
        names if necessary. If you attempt to import an object that
        duplicates the name of an existing object you will be notified
        with an error message. To see any errors that have occurred
        during reverse engineering, you can click the button
        <span class="guibutton">Show Logs</span>. This will create a panel
        containing a list of messages, including any error messages than
        may have been generated. Click the <span class="guibutton">Hide
        Logs</span> button to close the panel.
      </p><div class="figure"><a name="wb-reverse-engineer-database-wizard-logs"></a><p class="title"><b>Figure 7.22. Message Log</b></p><div class="mediaobject"><img src="images/wb-reverse-engineer-database-wizard-logs.png" width="800" height="600" alt="Message Log"></div></div><p>
        If you wish to import an object with the same name as an
        existing object, rename the existing object before reverse
        engineering.
      </p><p>
        If you import objects from more than one schema, there will be a
        tab in the <code class="literal">Physical Schemata</code> section of the
        <code class="literal">MySQL Model</code> page for each schema imported.
      </p><p>
        You cannot reverse engineer a live database that has the same
        name as an existing schema. If you wish to do this, first rename
        the existing schema.
      </p></div></div></body></html>


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

Use of any of this software is governed by the terms of the license below:

COPYRIGHT AND PERMISSION NOTICE

Copyright (c) 1996 - 2009, Daniel Stenberg, &lt;daniel@haxx.se&gt;.
All rights reserved.

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

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 OF THIRD PARTY 
RIGHTS. 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.

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


path: /wb-html-guitools/wb-starting.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>3.3. Starting 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-installing.html" title="Chapter 3. Installing and Launching MySQL Workbench"><link rel="prev" href="wb-requirements-software.html" title="3.2. Software Requirements"><link rel="next" href="wb-installing-windows.html" title="3.3.1. Installing MySQL Workbench on Windows"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="wb-starting"></a>3.3. Starting MySQL Workbench</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-installing-windows.html">3.3.1. Installing MySQL Workbench on Windows</a></span></dt><dt><span class="section"><a href="wb-launching-windows.html">3.3.2. Launching MySQL Workbench on Windows</a></span></dt><dt><span class="section"><a href="wb-windows-uninstalling.html">3.3.3. Uninstalling MySQL Workbench on Windows</a></span></dt><dt><span class="section"><a href="wb-installing-linux.html">3.3.4. Installing MySQL Workbench on Linux</a></span></dt><dt><span class="section"><a href="wb-launching-linux.html">3.3.5. Launching MySQL Workbench on Linux</a></span></dt><dt><span class="section"><a href="wb-linux-uninstalling.html">3.3.6. Uninstalling MySQL Workbench on Linux</a></span></dt><dt><span class="section"><a href="wb-installing-mac.html">3.3.7. Installing MySQL Workbench on Mac OS X</a></span></dt><dt><span class="section"><a href="wb-launching-osx.html">3.3.8. Launching MySQL Workbench on Mac OS X</a></span></dt><dt><span class="section"><a href="wb-mac-uninstalling.html">3.3.9. Uninstalling MySQL Workbench on Mac OS X</a></span></dt></dl></div><p>
      The procedure for launching MySQL Workbench depends on the platform.
      Generally, there are two ways to launch MySQL Workbench: either from
      the command line or from the graphical user interface of the host
      operating system. Using the command-line launching facility is
      useful when you want to customize some aspects of the way
      MySQL Workbench operates. The following sections describe how to
      launch MySQL Workbench for each of the supported platforms.
    </p><p>
      In addition to platform-specific command-line options, MySQL Workbench
      has the following command-line options:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <code class="option">--admin <em class="replaceable"><code>instance</code></em></code>:
          Load the server instance specified.
        </p></li><li><p>
          <code class="option">--query
          <em class="replaceable"><code>connection</code></em></code>: Load the
          connection specified.
        </p></li><li><p>
          <code class="option">--model <em class="replaceable"><code>modelfile</code></em></code>:
          Load the model specified.
        </p></li><li><p>
          <code class="option">--script <em class="replaceable"><code>script</code></em></code>:
          Run the script specified.
        </p></li><li><p>
          <code class="option">--run <em class="replaceable"><code>code</code></em></code>: Run
          the code snippet specified.
        </p></li><li><p>
          <code class="option">--quit-when-done</code>: Quits MySQL Workbench after
          <code class="option">--script</code> or <code class="option">--run</code> finishes.
        </p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-news-5-0-27.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.3.4. Changes in MySQL Workbench 5.0.27 (07 November 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-28.html" title="A.3.3. Changes in MySQL Workbench 5.0.28 (06 December 2008)"><link rel="next" href="wb-news-5-0-26.html" title="A.3.5. Changes in MySQL Workbench 5.0.26 (16 October 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-27"></a>A.3.4. Changes in MySQL Workbench 5.0.27 (07 November 2008)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.0.26.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        There was a problem where relationships that were hidden could
        then not be selected to bring up their relationship editor.
        Relationships can now be selected as objects in the Layer
        window. Once selected, the relationship's
        <code class="literal">visible</code> property can be set to
        <code class="literal">True</code> in the Properties window, thus making
        the relationship visible again.
       (Bug #40167)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        When a stored routine was edited, the edit cursor jumped back to
        the start of the page unless typing was constant.
       (Bug #40426)</p></li><li><p>
        When using the <span class="guimenu">Copy Insert to Clipboard</span> menu
        item the generated SQL code was incorrect. The “<span class="quote">S</span>”
        was missing from “<span class="quote">VALUES</span>” and the data was not
        included. This resulted in SQL code such as:
      </p><pre class="programlisting">INSERT INTO `table1` (`table1_id`, `descr`) VALUE ();</pre><p>(Bug #40041)</p></li><li><p>
        If a trigger was renamed, and the design then synched with a
        database instance, the generated SQL created a trigger with the
        new name and then dropped the trigger with the old name. This
        resulted in this error:
      </p><pre class="programlisting">Error 1235: This version of MySQL doesn't yet support
'multiple triggers with the same action time and event for one table'</pre><p>(Bug #39989)</p></li><li><p>
        The <span class="guimenu">Copy SQL to Clipboard</span> action (right-click
        menu on table) did not use Windows-compatible line endings.
       (Bug #39476)</p></li><li><p>
        When a column had a data type <code class="literal">BOOLEAN</code> and it
        was exported using <span class="guimenu">Forward Engineer SQL
        ALTER</span>, the exported type was
        <code class="literal">BOOLEAN(2)</code> instead of
        <code class="literal">BOOLEAN</code>.
       (Bug #39257)</p></li><li><p>
        Workbench application performance was poor, with slow loading
        times and excessive memory usage.
       (Bug #38439)</p></li><li><p>
        When a DBDesigner model with 333 tables was imported into
        Workbench the RAM usage went up to approximately 1GB. Workbench
        then crashed with this exception:
      </p><pre class="programlisting">  Error creating cairo context: out of memory</pre><p>(Bug #37178)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-history-palette.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.5.8. The History Palette</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-model-editor.html" title="7.5. Model Editor"><link rel="prev" href="wb-views-overview-notes.html" title="7.5.7. The Model Notes Panel"><link rel="next" href="wb-navigator-panel.html" title="7.5.9. The Model Navigator 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-history-palette"></a>7.5.8. The History Palette</h3></div></div></div><p>
      Use the <code class="literal">History</code> palette to review the actions
      that you have taken. Left-clicking an entry opens a pop-up menu
      with the item, <span class="guimenuitem">Copy History Entries to
      Clipboard</span>. Choose this item to select a single
      entry. You can select multiple contiguous entries by pressing the
      <span><strong class="keycap">Shift</strong></span> key and clicking the entries you wish to
      copy. Select noncontiguous entries by using the
      <span><strong class="keycap">Control</strong></span> key.
    </p><p>
      Only actions that alter the MySQL model or change an EER diagram
      are captured by the <code class="literal">History</code> palette.
    </p></div></body></html>


path: /wb-html-guitools/wb-views-overview-scripts.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.5.6. The SQL Scripts Panel</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-model-editor.html" title="7.5. Model Editor"><link rel="prev" href="wb-adding-users.html" title="7.5.5.2. Adding Users"><link rel="next" href="wb-views-overview-notes.html" title="7.5.7. The Model Notes 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-views-overview-scripts"></a>7.5.6. The SQL Scripts Panel</h3></div></div></div><p>
      Use the <code class="literal">SQL Scripts</code> panel to load and modify
      SQL scripts. If you created your project from an SQL script and
      plan to create an <code class="literal">ALTER</code> script, you may want to
      add the original script here, since it will be needed to create an
      <code class="literal">ALTER</code> script. For more information, see
      <a href="wb-forward-engineering-sql-scripts.html#wb-export-script-alter-schema" title="7.7.10.1.2. Altering a Schema">Section 7.7.10.1.2, “Altering a Schema”</a>.
    </p></div></body></html>


path: /wb-html-guitools/wb-news-5-2-26.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.14. Changes in MySQL Workbench 5.2.26 (06 August 2010)</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="changes-5.2.x.html" title="A.1. Changes in Release 5.2"><link rel="prev" href="wb-news-5-2-27.html" title="A.1.13. Changes in MySQL Workbench 5.2.27 (01 September 2010)"><link rel="next" href="wb-news-5-2-25.html" title="A.1.15. Changes in MySQL Workbench 5.2.25 (30 June 2010 General Availability)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-news-5-2-26"></a>A.1.14. Changes in MySQL Workbench 5.2.26 (06 August 2010)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.2.25.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        When using the MySQL Workbench table properties to add a foreign
        key, the size of a new foreign key field will now update to
        match the size of the corresponding primary key.
       (Bug #55083, Bug #11762482)</p></li><li><p>
        Added the default value of <code class="literal">CURRENT_TIMESTAMP ON UPDATE
        CURRENT_TIMESTAMP</code> to context menu of column editor for
        <code class="literal">TIMESTAMP</code> columns.
       (Bug #54987)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        On the Home screen, the saved connections previously listed in
        the Workspace were no longer visible.
       (Bug #55484)</p></li><li><p>
        When a model was synchronized with a live database,
        <code class="literal">CHAR(<em class="replaceable"><code>N</code></em>)</code> columns
        were always synchronized as <code class="literal">CHAR(1)</code>.
       (Bug #55334)</p></li><li><p>
        Importing a DBDesigner model caused MySQL Workbench to crash.
       (Bug #55300)</p></li><li><p>
        In the <span class="guilabel">Synchronize Model with Database</span>
        wizard, the list of schemata was not drawn correctly on the
        <span class="guilabel">Select Schemata</span> page, if
        <span class="guibutton">Back</span> was clicked from the <span class="guilabel">Fetch
        Object Info</span> page.
       (Bug #55174)</p></li><li><p>
        Complex queries with multiple newlines did not fit well in the
        <span class="guilabel">Action</span> column of the
        <span class="guilabel">Output</span> tab of the SQL Editor. This
        prevented any query error messages from being read.
       (Bug #55117)</p></li><li><p>
        In the <span class="guilabel">Reverse Engineer Database</span> wizard,
        using a pattern mask to filter tables being imported caused a
        subsequent MySQL Workbench crash.
       (Bug #55076)</p></li><li><p>
        In the Administrator, if the MySQL server configuration file was
        modified to enable <code class="literal">skip-innodb</code>, and the
        server was restarted, <code class="literal">InnoDB</code> was still
        active.
       (Bug #55030)</p></li><li><p>
        On the <span class="guilabel">Snippets</span> tab, the tooltip for the
        <span class="guilabel">Insert selected snippet to cursor position in the
        active SQL editor</span> button contained the misspelling
        “<span class="quote">seleced</span>”.
       (Bug #55026)</p></li><li><p>
        The <span class="guilabel">Configuration</span> section of the
        MySQL Workbench Administrator did not copy configuration variables
        from the <code class="filename">my.cnf</code> file that contained an
        underscore character.
       (Bug #54933)</p></li><li><p>
        MySQL Workbench crashed if minimized while loading a model.
       (Bug #54918)</p></li><li><p>
        In the <span class="guilabel">Overview</span> tab of the SQL Editor, if
        there was a large number of schemata, using the arrow buttons in
        the interface to scroll through them caused MySQL Workbench to
        crash, usually on the last schema in the list.
       (Bug #54891)</p></li><li><p>
        When using the SQL Editor and issuing a query containing
        <code class="literal">SQL_CALC_FOUND_ROWS</code> and a subsequent
        <code class="literal">FOUND_ROWS()</code> query,
        <code class="literal">FOUND_ROWS()</code> returned zero instead of the
        number of matching rows without a <code class="literal">LIMIT</code>
        applied.
       (Bug #54868)</p></li><li><p>
        MySQL Workbench would not compile on RHEL 5. This was due to the
        calls to the function <code class="literal">set_opacity</code> in
        <code class="filename">library/form/gtk/src/lf_utilities.cpp</code> (line
        661) and <code class="filename">library/forms/gtk/src/lf_popup.cpp</code>
        (line 64). The <code class="literal">set_opacity</code> function was not
        available in GTK 2.10.
       (Bug #54844)</p></li><li><p>
        Multi-statement syntax did not work in the SQL Editor. If the
        delimiter was set to a character other than the default
        semicolon, the SQL Editor should still have recognized semicolon
        as a valid delimiter for multi-statements, but it did not.
       (Bug #54831)</p></li><li><p>
        In the SQL Editor, if a column's comment contained a Chinese
        word, then in the Object Browser, if the context-sensitive menu
        item <span class="guimenu">Send to SQL Editor</span>, <span class="guimenu">Create
        Statement</span> was selected, incomplete script code was
        sent to the SQL Query tab.
       (Bug #54822)</p></li><li><p>
        When a model was forward engineered to a database, insert
        statements associated with binary data were not present in the
        generated code. As a result, binary data was not forwarded to
        the database.
       (Bug #54680)</p></li><li><p>
        In an EER Diagram, the circles at each end of a relationship
        line were drawn in different sizes.
       (Bug #54663)</p></li><li><p>
        When forward engineering an SQL ALTER script, the generated code
        attempted to recreate all foreign keys.
       (Bug #54363)</p></li><li><p>
        In forward engineering a model to a database, the
        <code class="literal">PRIMARY</code> index was not reordered correctly
        when columns were reordered.
       (Bug #54176)</p></li><li><p>
        When using <span><strong class="command">su -user</strong></span> instead of
        <span><strong class="command">sudo</strong></span>, rather than requesting the password of
        the user for invoking the <span><strong class="command">su</strong></span> command,
        MySQL Workbench requested the <code class="literal">root</code> password and
        attempted to invoke the <span><strong class="command">sudo</strong></span> command.
       (Bug #53740)</p></li><li><p>
        When zooming in and out of the EER Diagram view, MySQL Workbench
        generated an unknown error.
       (Bug #52829, Bug #55390)</p></li><li><p>
        When connecting to a server, MySQL Workbench prompted for a
        password, even if one had not been set for that account.
       (Bug #52826)</p></li><li><p>
        After creating a server instance and double-clicking it on the
        Home screen, the Administrator took an excessively long time to
        load (over 10 minutes).
       (Bug #52530)</p></li><li><p>
        MySQL Workbench crashed when executing <code class="literal">LOAD DATA LOCAL
        INFILE</code> as a query in the SQL Editor.
       (Bug #49694)</p></li><li><p>
        If the Start Server button was clicked twice in MySQL Workbench, the
        server would stop.
       (Bug #49588)</p></li><li><p>
        In the list view of the physical schemata, clicking a list
        column heading failed to sort the items by that column.
       (Bug #38863)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-manage-db-connections-socket.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>6.6.3. Local Socket/Pipe 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-standard.html" title="6.6.2. Standard TCP/IP Connection"><link rel="next" href="wb-manage-db-connections-ssh.html" title="6.6.4. Standard TCP/IP over SSH 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-socket"></a>6.6.3. Local Socket/Pipe Connection</h3></div></div></div><p>
      This connection method enables MySQL Workbench to connect to MySQL
      Server using a socket file (on Unix) or a named pipe (on Windows).
    </p><p>
      <span class="bold"><strong>Parameters</strong></span>
    </p><p>
      The unique field here is <span class="guilabel">Socket/Pipe Path</span>.
      Enter the name of the socket or pipe here. If the field is left
      blank, the default socket or pipe name is used. On Unix, the
      default socket name is <code class="literal">/tmp/mysql.sock</code>. On
      Microsft Windows, the default pipe name is
      <code class="literal">MySQL</code>.
    </p><p>
      This option can be seen in the following screenshot.
    </p><div class="figure"><a name="wb-manage-db-connections-socket-parameters"></a><p class="title"><b>Figure 6.3. Manage DB Connections - Socket/Pipe Parameters</b></p><div class="mediaobject"><img src="images/wb-manage-db-connections-socket-parameters.png" width="898" height="498" alt="Manage DB Connections - Socket/Pipe
          Parameters"></div></div><p>
      <span class="bold"><strong>Advanced</strong></span>
    </p><p>
      The only option available in this tab is <span class="guilabel">Use ANSI
      quoutes to quote identifiers</span>. This option was discussed
      in <a href="wb-manage-db-connections-standard.html" title="6.6.2. Standard TCP/IP Connection">Section 6.6.2, “Standard TCP/IP Connection”</a>.
    </p></div></body></html>


path: /wb-html-guitools/wb-manage-db-connections-vault.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>6.6.1. The Password Storage Vault</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.html" title="6.6. Manage DB Connections Dialog"><link rel="next" href="wb-manage-db-connections-standard.html" title="6.6.2. Standard TCP/IP 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-vault"></a>6.6.1. The Password Storage Vault</h3></div></div></div><p>
      The vault provides a convenient secure storage for passwords used
      to access MySQL servers. By using the vault, you need not enter
      credentials every time MySQL Workbench attempts to connect to a
      server. The vault is implemented differently on each platform:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <span class="bold"><strong>Windows</strong></span>: The vault is an
          encrypted file in the MySQL Workbench <code class="filename">data</code>
          directory. This is where <code class="filename">connections.xml</code>
          and related files are located. The file is encrypted using a
          Windows API which performs the encryption based on the current
          user, so only the current user can decrypt it. As a result it
          is not possible to decrypt the file on any other computer. It
          is possible to delete the file, in which case all stored
          passwords are lost, but MySQL Workbench will otherwise perform as
          expected. You then must re-enter passwords as required.
        </p></li><li><p>
          <span class="bold"><strong>Mac OS X</strong></span>: The vault is
          implemented using the Mac OS X Secure Keychain. The keychain
          contents can be viewed using the <code class="filename">Keychain
          Access.app</code> utility.
        </p></li><li><p>
          <span class="bold"><strong>Linux</strong></span>: The vault works by
          storing passwords using the <code class="literal">gnome-keyring</code>
          daemon, which must be running for password persistency to
          work. The daemon is automatically started in GNOME desktops,
          but normally is not in KDE and others. The
          <code class="literal">gnome-keyring</code> daemon can be used for
          password storage in MySQL Workbench on non-GNOME platforms, but
          must be started manually.
        </p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-view-menu.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.5.1.3. The View Menu</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-data-modeling-menus.html" title="7.5.1. Modeling Menus"><link rel="prev" href="wb-edit-menu.html" title="7.5.1.2. The Edit Menu"><link rel="next" href="wb-arrange-menu.html" title="7.5.1.4. The Arrange Menu"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-view-menu"></a>7.5.1.3. The View Menu</h4></div></div></div><p>
      The <span class="guimenu">View</span> menu has these items:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <span class="guimenuitem">Home</span>: Selects the Home window
        </p></li><li><p>
          <span class="guimenuitem">Windows</span>: A submenu with items that
          provide a means for opening the windows associated with them:
        </p><div class="itemizedlist"><ul type="circle"><li><p>
              <span class="guimenuitem">Model Navigator</span>: Opens the
              <code class="literal">Model Navigator</code> palette
            </p></li><li><p>
              <span class="guimenuitem">Catalog</span>: Opens the
              <code class="literal">Catalog</code> palette
            </p></li><li><p>
              <span class="guimenuitem">Layers</span>: Opens the
              <code class="literal">Layers</code> palette
            </p></li><li><p>
              <span class="guimenuitem">User Datatypes</span>: Opens the
              <code class="literal">User Datatypes</code> palette
            </p></li><li><p>
              <span class="guimenuitem">Object description</span>: Opens the
              <code class="literal">Description</code> palette
            </p></li><li><p>
              <span class="guimenuitem">Object properties</span>: Opens the
              <code class="literal">Properties</code> palette
            </p></li><li><p>
              <span class="guimenuitem">Undo History</span>: Opens the
              <code class="literal">History</code> palette
            </p></li></ul></div></li><li><p>
          <span class="guimenu">Advanced</span>
        </p><div class="itemizedlist"><ul type="circle"><li><p>
              <span class="guimenuitem">Output Window</span>: Displays the
              console output. The keyboard shortcut for this menu item
              is <span><strong class="keycap">Control+F2</strong></span>.
            </p></li><li><p>
              <span class="guimenuitem">GRT Shell</span>: Opens the GRT shell.
              For more information about the GRT shell, see
              <a href="wb-scripting-shell.html" title="9.5. The Workbench Scripting Shell">Section 9.5, “The Workbench Scripting Shell”</a>. The keyboard
              shortcut for this menu item is
              <span><strong class="keycap">Control+F3</strong></span>.
            </p></li></ul></div></li><li><p>
          <span class="guimenuitem">Reset Window Layout</span>: Resets all
          windows to their default layout
        </p></li><li><p>
          <span class="guimenuitem">Zoom 100%</span>: The default level of
          detail of an EER diagram
        </p></li><li><p>
          <span class="guimenuitem">Zoom In</span>: Zooms in on an EER
          diagram.
        </p></li><li><p>
          <span class="guimenuitem">Zoom Out</span>: Zooms out from an EER
          diagram.
        </p><p>
          The ability to zoom in on an EER diagram is also available
          using the slider tool in the <code class="literal">Model
          Navigator</code> palette. See
          <a href="wb-navigator-panel.html" title="7.5.9. The Model Navigator Panel">Section 7.5.9, “The Model Navigator Panel”</a>.
        </p></li><li><p>
          <span class="guimenuitem">Set Marker</span>: Bookmarks an object.
          From the keyboard, select the object you wish to bookmark,
          then use the key combination <span><strong class="keycap">Control+Shift</strong></span>
          and the number of the marker (1 through 9). You may create up
          to nine markers.
        </p></li><li><p>
          <span class="guimenuitem">Go To Marker</span>: Returns to a marker.
          From the keyboard, use the <span><strong class="keycap">Control</strong></span> key and
          the number of the marker.
        </p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-news-5-1-12.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.2.8. Changes in MySQL Workbench 5.1.12 (27 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-13.html" title="A.2.7. Changes in MySQL Workbench 5.1.13 (12 June 2009)"><link rel="next" href="wb-news-5-1-11.html" title="A.2.9. Changes in MySQL Workbench 5.1.11 (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-12"></a>A.2.8. Changes in MySQL Workbench 5.1.12 (27 April 2009)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.1.11.
      </p><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        In the <span class="guilabel">Foreign Key</span> tab of the Relationship
        Editor, the two buttons labeled <span class="guibutton">Edit
        Table...</span> were inactive. Clicking them had no effect.
       (Bug #45391)</p></li><li><p>
        When running on Ubuntu Linux the edit window in MySQL Workbench was
        not expanded horizontally by default.
      </p><p>
        When editing existing routines, the horizontal scroll-bar
        covered 100% of the visible area, no matter how long any of the
        rows are. This meant that if a row expanded outside the visible
        area, it was not possible to scroll sideways to see the rest of
        the row. All of the row was there, but the right part was not
        visible.
       (Bug #44296)</p></li><li><p>
        It was not possible to change the Default Collation for any
        schema.
       (Bug #44220)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/license-scintilla.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>B.20. Scintilla 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-python.html" title="B.19. Python License"><link rel="next" href="license-scintilla-net.html" title="B.21. ScintillaNET License"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="license-scintilla"></a>B.20. Scintilla License</h2></div></div></div><p>
    The following software may be included in this product:
  </p><pre class="programlisting">Scintilla 

License for Scintilla and SciTE

Copyright 1998-2003 by Neil Hodgson &lt;neilh@scintilla.org&gt;

All Rights Reserved 

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

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

Scintilla includes some files copyright Adobe Systems Incorporated:

Copyright (c) 2007 Adobe Systems Incorporated

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.

----

Scintilla includes some files copyright Apple Computer, Inc.:

Disclaimer:  IMPORTANT:  This Apple software is supplied to you by Apple
Computer, Inc. ("Apple") in consideration of your agreement to the following
terms, and your use, installation, modification or redistribution of this
Apple software constitutes acceptance of these terms.  If you do not agree
with these terms, please do not use, install, modify or redistribute this
Apple software.

In consideration of your agreement to abide by the following terms, and
subject to these terms, Apple grants you a personal, non-exclusive license,
under Apple's copyrights in this original Apple software (the "Apple
Software"), to use, reproduce, modify and redistribute the Apple Software,
with or without modifications, in source and/or binary forms; provided that
if you redistribute the Apple Software in its entirety and without
modifications, you must retain this notice and the following text and
disclaimers in all such redistributions of the Apple Software.  Neither the
name, trademarks, service marks or logos of Apple Computer, Inc. may be used
to endorse or promote products derived from the Apple Software without
specific prior written permission from Apple.  Except as expressly stated in
this notice, no other rights or licenses, express or implied, are granted by
Apple herein, including but not limited to any patent rights that may be
infringed by your derivative works or by other works in which the Apple
Software may be incorporated.

The Apple Software is provided by Apple on an "AS IS" basis.  APPLE MAKES NO
WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE, REGARDING THE APPLE SOFTWARE OR ITS USE AND OPERATION ALONE OR IN
COMBINATION WITH YOUR PRODUCTS.

IN NO EVENT SHALL APPLE BE LIABLE FOR ANY SPECIAL, INDIRECT, INCIDENTAL OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) ARISING IN ANY WAY OUT OF THE USE, REPRODUCTION, MODIFICATION
AND/OR DISTRIBUTION OF THE APPLE SOFTWARE, HOWEVER CAUSED AND WHETHER UNDER
THEORY OF CONTRACT, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY OR
OTHERWISE, EVEN IF APPLE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Copyright (c) 2002 Apple Computer, Inc., All Rights Reserved 
</pre></div></body></html>


path: /wb-html-guitools/wb-forward-engineering-sql-scripts.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.1. Forward Engineering Using an 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-forward-engineering.html" title="7.7.10. Forward Engineering"><link rel="prev" href="wb-forward-engineering.html" title="7.7.10. Forward Engineering"><link rel="next" href="wb-forward-engineering-live-server.html" title="7.7.10.2. Forward Engineering to a Live Server"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-forward-engineering-sql-scripts"></a>7.7.10.1. Forward Engineering Using an SQL Script</h4></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-forward-engineering-sql-scripts.html#wb-export-script-create-sql">7.7.10.1.1. Creating a Schema</a></span></dt><dt><span class="section"><a href="wb-forward-engineering-sql-scripts.html#wb-export-script-alter-schema">7.7.10.1.2. Altering a Schema</a></span></dt></dl></div><p>
      To create a script of your database model, choose the
      <span class="guisubmenu">Export</span> item from the
      <span class="guimenu">File</span> menu. You may export a script to alter an
      existing database or create a new database. The script to create a
      database is similar to the one created using the
      <span><strong class="command">mysqldump <em class="replaceable"><code>db_name</code></em></strong></span>
      command.
    </p><p>
      If you choose to create a database, there are several export
      options available.
    </p><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="wb-export-script-create-sql"></a>7.7.10.1.1. Creating a Schema</h5></div></div></div><p>
        Select the <span class="guimenu">File</span>,
        <span class="guisubmenu">Export</span>, <span class="guimenuitem">Forward Engineer
        SQL CREATE Script</span> menu item to start the Forward
        Engineer SQL Script wizard. The following figure shows the first
        page of the wizard.
      </p><div class="figure"><a name="wb-forward-engineer-sql-script-wizard-export-options"></a><p class="title"><b>Figure 7.23. SQL Export Options</b></p><div class="mediaobject"><img src="images/wb-forward-engineer-sql-script-wizard-export-options.png" width="798" height="598" alt="SQL Export Options"></div></div><p>
        The SQL Export Options displays the following facilities:
      </p><div class="itemizedlist"><ul type="disc"><li><p>
            <code class="literal">Output SQL Script File</code>
          </p><p>
            To specify the output file name, enter it into the
            <span class="guilabel">Output SQL Script File</span> field, or use
            the <span class="guibutton">Browse</span> button to select a file.
            If this field is left blank, you will be able to view the
            generated script, but it will not be saved to a file.
          </p></li><li><p>
            <code class="literal">Generate DROP Statements Before Each CREATE
            Statement</code>
          </p><p>
            Select this option to generate a statement to drop each
            object before the statement that creates it. This ensures
            that any existing instance of each object is removed when
            the output is executed.
          </p></li><li><p>
            <code class="literal">Omit Schema Qualifier in Object Names</code>
          </p><p>
            Select this option to generate unqualified object names in
            SQL statements.
          </p></li><li><p>
            <code class="literal">Generate Separate CREATE INDEX Statements</code>
          </p><p>
            Select this option to create separate statements for index
            creation instead of including index definitions in
            <code class="literal">CREATE TABLE</code> statements.
          </p></li><li><p>
            <code class="literal">Add SHOW WARNINGS after every DDL
            statement</code>
          </p><p>
            Select this option to add <code class="literal">SHOW WARNINGS</code>
            statements to the output. This causes display of any
            warnings generated when the output is executed, which may be
            useful for debugging.
          </p></li><li><p>
            <code class="literal">Do Not Create Users. Only Export
            Privileges</code>
          </p><p>
            Select this option to update the privileges of existing
            users, as opposed to creating new users. Exporting
            privileges for nonexistent users will result in errors when
            you execute the <code class="literal">CREATE</code> script. Exporting
            users that already exist will also result in an error.
          </p></li><li><p>
            <code class="literal">Generate INSERT Statements for Tables</code>
          </p><p>
            Select this option if you have added any rows to a table.
            For more information about inserting rows, see
            <a href="wb-table-editor.html#wb-table-editor-inserts-tab" title="7.7.1.3.9. The Inserts Tab">Section 7.7.1.3.9, “The Inserts Tab”</a>.
          </p></li></ul></div><p>
        Clicking <span class="guibutton">Next</span> takes you to the
        <span class="guilabel">SQL Object Export Filter</span> page where you
        select the objects you wish to export.
      </p><div class="figure"><a name="wb-forward-engineer-sql-script-wizard-filter"></a><p class="title"><b>Figure 7.24. SQL Object Export Filter</b></p><div class="mediaobject"><img src="images/wb-forward-engineer-sql-script-wizard-filter.png" width="800" height="600" alt="SQL Object Export Filter"></div></div><p>
        Precise control over the objects to export can be fine tuned by
        clicking the <span class="guibutton">Show Filter</span> button. After
        the objects to export have been selected, it is possible to
        reduce the expanded panel by clicking the same button, now
        labeled <span class="guibutton">Hide Filter</span>.
      </p><p>
        After selecting the objects to export, click the
        <span class="guibutton">Next</span> button to review the script that has
        been generated.
      </p><div class="figure"><a name="wb-forward-engineer-sql-script-wizard-review-script"></a><p class="title"><b>Figure 7.25. Review Generated Script</b></p><div class="mediaobject"><img src="images/wb-forward-engineer-sql-script-wizard-review-script.png" width="800" height="600" alt="Review Generated Script"></div></div><p>
        You may return to the previous page using the
        <span class="guibutton">Back</span> button.
      </p><p>
        The <span class="guibutton">Finish</span> button saves the script file
        and exits. You can then use the saved script to create a
        database.
      </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="wb-export-script-alter-schema"></a>7.7.10.1.2. Altering a Schema</h5></div></div></div><p>
        The menu item for altering a schema, <span class="guimenuitem">Forward
        Engineer SQL ALTER Script...</span>, is used for updating
        a database that has been redesigned within MySQL Workbench.
        Typically, this option is used when the SQL script of a database
        has been imported into MySQL Workbench and changed, and then you
        want to create a script that can be run against the database to
        alter it to reflect the adjusted model. For instructions on
        importing a DDL script, see
        <a href="wb-reverse-engineer-create-script.html" title="7.7.9.1. Reverse Engineering Using a Create Script">Section 7.7.9.1, “Reverse Engineering Using a Create Script”</a>.
      </p><p>
        Select the <span class="guimenu">File</span>,
        <span class="guisubmenu">Export</span>, <span class="guimenuitem">Forward Engineer
        SQL ALTER Script</span> menu item to start the Forward
        Engineer an ALTER Script wizard. You will be presented with the
        first page showing the available options.
      </p><div class="figure"><a name="wb-forward-engineer-sql-alter-script-wizard-options"></a><p class="title"><b>Figure 7.26. Options</b></p><div class="mediaobject"><img src="images/wb-forward-engineer-sql-alter-script-wizard-options.png" width="800" height="600" alt="Options"></div></div><p>
        This first page enables you to select an SQL script and compare
        it with the model currently in MySQL Workbench. The difference
        between the two models will be used to create an alter script
        that can be used to modify the target schema to match the model
        held in MySQL Workbench. To view the script generated, rather than
        saving it to a file, leave the <span class="guilabel">Output File</span>
        field empty.
      </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
          The script selected as the Input File must use full schema
          qualifiers, such as
          <em class="replaceable"><code>schema_name.table_name</code></em>. Otherwise,
          MySQL Workbench cannot generate a useable alter script.
        </p></div><p>
        Clicking <span class="guibutton">Next</span> brings you to the
        <span class="guilabel">Review SQL Script</span> page.
      </p><div class="figure"><a name="wb-forward-engineer-sql-alter-script-wizard-script"></a><p class="title"><b>Figure 7.27. Script</b></p><div class="mediaobject"><img src="images/wb-forward-engineer-sql-alter-script-wizard-script.png" width="800" height="600" alt="Script"></div></div><p>
        Here you can review and change the alter script that will be
        generated. Make any changes you wish and, if you are happy with
        the changes, save the <code class="literal">ALTER</code> script to file
        using the <span class="guibutton">Save to File...</span> button. You can
        also click the <span class="guibutton">Execute</span> button to tell
        MySQL Workbench to write the script to the previously specified
        output file.
      </p><p>
        The generated script can then be used to update the database.
      </p></div></div></body></html>


path: /wb-html-guitools/wb-news-5-1-7.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.2.13. Changes in MySQL Workbench 5.1.7 (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-8.html" title="A.2.12. Changes in MySQL Workbench 5.1.8 (Not yet released)"><link rel="next" href="wb-news-5-1-6.html" title="A.2.14. Changes in MySQL Workbench 5.1.6 (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-7"></a>A.2.13. Changes in MySQL Workbench 5.1.7 (Not yet released)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.1.6.
      </p><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        MySQL Workbench 5.1.7 for Mac OS X crashed at startup. It was
        looking for <code class="filename">libmysqlclient.15</code>, which was
        not found in <code class="filename">/usr/local/mysql/lib</code>. The
        error generated was:
      </p><pre class="programlisting">Process:         MySQLWorkbench [14915]
Path:            /Applications/MySQLWorkbench.app/Contents/MacOS/MySQLWorkbench
Identifier:      com.sun.MySQLWorkbench
Version:         ??? (???)
Code Type:       X86 (Native)
Parent Process:  launchd [95]

Date/Time:       2009-02-02 18:53:52.120 +0100
OS Version:      Mac OS X 10.5.6 (9G55)
Report Version:  6

Exception Type:  EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread:  0

Dyld Error Message:
  Library not loaded: /usr/local/mysql/lib/libmysqlclient.15.dylib
  Referenced from: /Applications/MySQLWorkbench.app/Contents/MacOS/MySQLWorkbench
  Reason: image not found</pre><p>
        Note that MySQL was installed, but the specific version of
        client library required was not present.
       (Bug #42550)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-preferences-sql-editor.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>5.4.3. The SQL Editor 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-administrator.html" title="5.4.2. The Administrator Tab"><link rel="next" href="wb-preferences-model.html" title="5.4.4. The Model 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-sql-editor"></a>5.4.3. The SQL Editor Tab</h3></div></div></div><p>
      This section provides configuration options that affect the SQL
      Editor functionality in MySQL Workbench.
    </p><p>
      There are three main groups of parameters that can be set here:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          SQL properties
        </p></li><li><p>
          Query Editor
        </p></li><li><p>
          Query Results
        </p></li></ul></div><p>
      <span class="bold"><strong>SQL Properties</strong></span>
    </p><p>
      SQL properties that can be set include the
      <code class="literal">SQL_MODE</code>, case sensitivity of identifiers, and
      the SQL delimiter used.
    </p><p>
      The document property <code class="literal">SqlMode</code> defines
      <code class="literal">SQL_MODE</code> for all operations affecting SQL
      parsing at the document scope. The purpose of this option is to
      preserve the consistency of SQL statements within the document.
    </p><p>
      The property has the following functions:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          Sets the <code class="literal">SQL_MODE</code> DBMS session variable to
          the value stored in the <code class="literal">SqlMode</code> property of
          the document when performing reverse engineering, forward
          engineering, or synchronization operations.
        </p></li><li><p>
          Honors the <code class="literal">SQL_MODE</code> values defined in
          <code class="literal">SqlMode</code> so that SQL parsing is correct.
        </p></li></ul></div><p>
      Only a subset of all possible <code class="literal">SQL_MODE</code> values
      affect the MySQL Workbench SQL parser. These values are:
      <code class="literal">ANSI_QUOTES</code>,
      <code class="literal">HIGH_NOT_PRECEDENCE</code>,
      <code class="literal">IGNORE_SPACE</code>,
      <code class="literal">NO_BACKSLASH_ESCAPES</code>,
      <code class="literal">PIPES_AS_CONCAT</code>. Other values do not affect the
      MySQL Workbench SQL parser and are ignored.
    </p><p>
      If the value of <code class="literal">SqlMode</code> is not set, the default
      value of the <code class="literal">SQL_MODE</code> session variable defined
      by the server stays unchanged during operations with the server.
      However, the MySQL Workbench SQL parser behaves as if
      <code class="literal">SQL_MODE</code> is also not set. This may potentially
      lead to inconsistencies in parsing of SQL statements stored in the
      document. If you choose to not set the <code class="literal">SqlMode</code>
      property, ensure that the default <code class="literal">SQL_MODE</code>
      variable defined by the server does not contain any values from
      the following list: <code class="literal">ANSI_QUOTES</code>,
      <code class="literal">HIGH_NOT_PRECEDENCE</code>,
      <code class="literal">IGNORE_SPACE</code>,
      <code class="literal">NO_BACKSLASH_ESCAPES</code>,
      <code class="literal">PIPES_AS_CONCAT</code>.
    </p><p>
      The <code class="literal">SqlMode</code> property is defined in two
      locations: globally and at document scope. MySQL Workbench uses the
      global property to initialize the document property for each new
      document created. For each document, the property value defined at
      document scope always has higher priority over the one defined
      globally.
    </p><p>
      <span class="bold"><strong>Query Editor</strong></span>
    </p><p>
      The query editor properties that can be set include the following:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <span class="guilabel">Show Live Schema Overview</span>: This option
          enables a simplification of the user interface by removing the
          Overview tab from the SQL Editor. This is extremely useful if
          schemata have a large number of tables, or a model has a large
          number of schemata. In each of these cases, load times would
          be greatly increased as the tables and schemata are enumerated
          and drawn.
        </p></li><li><p>
          <span class="guilabel">Show Schema Contents in Schema Tree</span>:
          Enumerating, populating, and drawing large numbers of items
          can significantly increase loading times. For this reason,
          this facility can be switched off for models containing large
          numbers of schemata and tables.
        </p></li><li><p>
          <span class="guilabel">Show Metadata Schemata</span>: By default
          metadata schemata are not displayed. To display them, for
          example to troubleshoot or check metadata information, select
          this option.
        </p></li><li><p>
          <span class="guilabel">Continue on SQL Script Error</span>: Should an
          error occur while executing a script, this option causes
          execution to continue for the remainder of the script.
        </p></li><li><p>
          <span class="guilabel">Forbid UPDATE and DELETE statements without a WHERE
          clause</span>: This option enables the
          <code class="literal">SQL_SAFE_UPDATES</code> option for the sesson,
          preventing <code class="literal">UPDATE</code> and
          <code class="literal">DELETE</code> statements from being executed if a
          <code class="literal">WHERE</code> clause is not present. This can avoid
          potentially dangerous situations where a statement could
          accidentally update or delete all rows in a table.
        </p></li><li><p>
          <span class="guilabel">Max syntax error count</span>: Large complex
          scripts can contain many errors. Further, a syntax error early
          on can lead to many subsequent syntax errors. For these
          reasons, it is possible to limit the number of errors
          displayed using this option. The default is 100 error
          messages.
        </p></li><li><p>
          <span class="guilabel">Progress status update interval</span>: When
          executing long running queries over a slow connection, you may
          need to increase this value to prevent excess load on the
          connection.
        </p></li><li><p>
          <span class="guilabel">DBMS connection keep-alive interval</span>: When
          executing long running queries over a slow connection, you may
          need to increase this value to prevent the connection being
          lost.
        </p></li></ul></div><p>
      <span class="bold"><strong>Query Results</strong></span>
    </p><p>
      The query results properties that can be set include the
      following:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <span class="guilabel">Limit Rows</span>: Queries can sometimes return
          an excessive number of rows, which can heavily load the
          connection, and take time to display in MySQL Workbench. To
          prevent this, you can set a more moderate value here.
        </p></li><li><p>
          <span class="guilabel">Limit Rows Count</span>: Specify the maximum
          number of result rows to return.
        </p></li><li><p>
          <span class="guilabel">Max. Field Value Length to Display</span>: To
          avoid display problems due to excessive field length, it is
          possible to set the maximum field length to display (in
          bytes).
        </p></li><li><p>
          <span class="guilabel">Treat BINARY/VARBINARY as non-binary character
          string</span>: Binary byte string values are not displayed
          by default in the results grid, but are instead marked as
          <code class="literal">BLOB</code> values. These can then be viewed or
          edited with the <code class="literal">BLOB</code> editor. Nonbinary
          character string values are displayed in the results grid, and
          can be edited in the grid cell or using the
          <code class="literal">BLOB</code> editor.
        </p><p>
          If this option is turned on, data truncation may result:
          Binary byte string values may contain null bytes as part of
          their valid data, whereas for nonbinary character strings, a
          null byte terminates the string.
        </p></li><li><p>
          <span class="guilabel">Enable Data Changes Commit Wizard</span>: In the
          SQL Editor, if you edit table data and then click the
          <span class="guibutton">Applying changes to data</span> button,
          MySQL Workbench launches a wizard to step you through applying
          your changes. This gives you a chance to review the SQL that
          will be applied to the live server to make the requested
          changes. If this option is deselected, the changes will be
          applied to the server without the wizard being displayed and
          without giving you a chance to review the changes that will be
          made.
        </p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-getting-started-tutorial-adding-data.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>4.3. Adding Data to Your Database</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-getting-started-tutorial.html" title="Chapter 4. Getting Started Tutorial"><link rel="prev" href="wb-getting-started-tutorial-creating-a-model.html" title="4.2. Creating a Model"><link rel="next" href="wb-home.html" title="Chapter 5. The Home Window"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="wb-getting-started-tutorial-adding-data"></a>4.3. Adding Data to Your Database</h2></div></div></div><p>
      In the previous section, you created a model, schema, and table.
      You also forward engineered your model to the live server. In this
      section, you will see how you can use MySQL Workbench to add data into
      your database on the live server.
    </p><div class="orderedlist"><ol type="1"><li><p>
          On the Home window, click the link <span class="guilabel">Edit Table
          Data</span> in the SQL Development area of the Workspace.
          This launches <span class="guilabel">Edit Table Data</span> wizard.
        </p><div class="figure"><a name="wb-getting-started-tutorial-edit-table-data"></a><p class="title"><b>Figure 4.19. Getting Started Tutorial - Edit Table Data</b></p><div class="mediaobject"><img src="images/wb-getting-started-tutorial-edit-table-data.png" width="1024" height="719" alt="Getting Started Tutorial - Edit Table
              Data"></div></div></li><li><p>
          In the wizard, select the “<span class="quote">Big Iron Server</span>”
          connection from the stored connection list. Click
          <span class="guibutton">Next</span>.
        </p></li><li><p>
          Select the schema, <code class="literal">dvd_collection</code>. Select
          the table to edit, <code class="literal">movies</code>. Click
          <span class="guibutton">Finish</span>.
        </p></li><li><p>
          You will see a data grid. This is where you can enter the data
          for your database. Remember that the
          <code class="literal">movie_id</code> was set to be autoincrement, so
          you need not enter values directly for this column. In the
          data grid, enter the movie information shown in the following
          table.
        </p><div class="informaltable"><table border="1"><colgroup><col><col></colgroup><thead><tr><th>title</th><th>release_date</th></tr></thead><tbody><tr><td>Gone with the Wind</td><td>1939-04-17</td></tr><tr><td>The Hound of the Baskervilles</td><td>1939-03-31</td></tr><tr><td>The Matrix</td><td>1999-06-11</td></tr><tr><td>Above the Law</td><td>1988-04-08</td></tr></tbody></table></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
            Do not modify any values in the <code class="literal">movie_id</code>
            column.
          </p></div></li><li><p>
          Now click the <span class="guibutton">Apply changes to data
          source</span> button in the toolbar located in the bottom
          right corner. A list of SQL statements will be displayed.
          Confirm that you understand the operations to be carried out.
          Click <span class="guibutton">Apply SQL</span> to apply these changes
          to the live server.
        </p></li><li><p>
          Confirm that the script was executed correctly, then click
          <span class="guibutton">Finish</span>.
        </p></li><li><p>
          View the data grid again and observe that the autoincrement
          values have been generated.
        </p><div class="figure"><a name="wb-getting-started-tutorial-edit-data"></a><p class="title"><b>Figure 4.20. Getting Started Tutorial - Edit Data</b></p><div class="mediaobject"><img src="images/wb-getting-started-tutorial-edit-data.png" width="1024" height="719" alt="Getting Started Tutorial - Edit
              Data"></div></div></li><li><p>
          Now you will check that the data really has been applied to
          the live server. Launch the MySQL Command Line Client. Enter
          <code class="literal">SELECT * FROM movies;</code> to see the data just
          entered.
        </p></li><li><p>
          You can also carry out a similar check from within
          MySQL Workbench. Click on the Home window tab.
        </p></li><li><p>
          Click the link <span class="guilabel">Open Connection to start
          Querying</span> in the SQL Development section of the
          Workspace. This will launch the <span class="guilabel">Connect to
          Database</span> dialog. Select “<span class="quote">Big Iron
          Server</span>” from the list. Click <span class="guibutton">OK</span>.
        </p></li><li><p>
          A new SQL Editor tab will be displayed. In the SQL Statements
          area, enter the following code:
        </p><pre class="programlisting">USE dvd_collection;
SELECT * FROM movies;</pre></li><li><p>
          Now click the <span class="guibutton">Execute SQL Script in Connected
          Server</span> toolbar button. This resembles a small
          lightning bolt. The SQL Editor will display a new Result tab
          contain the result of executing the SQL statements.
        </p><div class="figure"><a name="wb-getting-started-tutorial-results"></a><p class="title"><b>Figure 4.21. Getting Started Tutorial - Results</b></p><div class="mediaobject"><img src="images/wb-getting-started-tutorial-results.png" width="1024" height="719" alt="Getting Started Tutorial -
              Results"></div></div></li></ol></div><p>
      In this section of the tutorial, you have learned how to add data
      to your database, and also how to execute SQL statements using
      MySQL Workbench.
    </p></div></body></html>


path: /wb-html-guitools/wb-toolbar.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.5.2. The 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-model-editor.html" title="7.5. Model Editor"><link rel="prev" href="wb-help-menu.html" title="7.5.1.10. The Help Menu"><link rel="next" href="wb-tool-specific-toolbar-items.html" title="7.5.2.1. Tool-Specific Toolbar Items"></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-toolbar"></a>7.5.2. The Toolbar</h3></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-tool-specific-toolbar-items.html">7.5.2.1. Tool-Specific Toolbar Items</a></span></dt></dl></div><p>
    The MySQL Workbench toolbar is located immediately below the menu bar.
    Click the tools in the toolbar to perform the following actions:
  </p><div class="itemizedlist"><ul type="disc"><li><p>
        The new document icon: Creates a new document
      </p></li><li><p>
        The folder icon: Opens a MySQL Workbench file
        (<code class="filename">mwb</code> extension)
      </p></li><li><p>
        The save icon: Saves the current MySQL Workbench project
      </p></li><li><p>
        The right and left arrows: The left arrow performs an
        “<span class="quote">Undo</span>” operation. The right arrow performs a
        “<span class="quote">Redo</span>” operation.
      </p></li></ul></div><p>
    Other tools appear on the toolbar depending upon the context.
  </p></div></body></html>


path: /wb-html-guitools/wb-overview-schema-objects.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.5.4.1. The Schema Objects Panel</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-view-overview-physical-schemata.html" title="7.5.4. The Physical Schemata Panel"><link rel="prev" href="wb-view-overview-physical-schemata.html" title="7.5.4. The Physical Schemata Panel"><link rel="next" href="wb-model-overview-privileges.html" title="7.5.5. The Schema Privileges Panel"></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-overview-schema-objects"></a>7.5.4.1. The Schema Objects Panel</h4></div></div></div><p>
        The <code class="literal">Physical Schemata</code> panel has the following
        sections:
      </p><div class="itemizedlist"><ul type="disc"><li><p>
            Tables
          </p></li><li><p>
            Views
          </p></li><li><p>
            Routines
          </p></li><li><p>
            Routine Groups
          </p></li></ul></div><p>
        Each section contains the specified database objects and an icon
        used for creating additional objects.
      </p><p>
        Any database objects added to an EER diagram canvas also show up
        in the <code class="literal">Physical Schemata</code> section. For
        information about adding objects to an EER diagram canvas, see
        <a href="wb-eer-diagram-editor.html" title="7.6. EER Diagram Editor">Section 7.6, “EER Diagram Editor”</a>.
      </p></div></body></html>


path: /wb-html-guitools/license-tinyxml.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>B.22. TinyXML License</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-third-party-licenses.html" title="Appendix B. Third Party Licenses"><link rel="prev" href="license-scintilla-net.html" title="B.21. ScintillaNET License"><link rel="next" href="license-treeviewadv-net.html" title="B.23. TreeViewAdv for .NET 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-tinyxml"></a>B.22. TinyXML License</h2></div></div></div><p>
    The following software may be included in this product:
  </p><p>
    TinyXML
  </p><pre class="programlisting">TinyXML is released under the zlib license: 

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

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

1. The origin of this software must not be misrepresented; you must 
not claim that you wrote the original software. If you use this 
software in a product, an acknowledgment in the product documentation 
would be appreciated but is not required. 

2. Altered source versions must be plainly marked as such, and 
must not be misrepresented as being the original software. 

3. This notice may not be removed or altered from any source 
distribution. </pre></div></body></html>


path: /wb-html-guitools/wb-news-5-2-21.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.19. Changes in MySQL Workbench 5.2.21 (12 May 2010 Release Candidate)</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-22.html" title="A.1.18. Changes in MySQL Workbench 5.2.22 (02 June 2010)"><link rel="next" href="wb-news-5-2-20.html" title="A.1.20. Changes in MySQL Workbench 5.2.20 (27 April 2010)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-news-5-2-21"></a>A.1.19. Changes in MySQL Workbench 5.2.21 (12 May 2010 Release Candidate)</h3></div></div></div><p>
        First release candidate. This section documents all changes and
        bug fixes applied since the release of 5.2.20.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        MySQL Workbench now features a check that compares the
        <code class="literal">mysqldump</code> version on the client and server
        machines.
       (Bug #52689)</p></li><li><p>
        MySQL Workbench now includes the following menu items and keyboard
        shortcuts:
      </p><div class="itemizedlist"><ul type="circle"><li><p>
            <span class="guimenuitem">Execute Current Statement</span>,
            <span><strong class="keycap">Control+Enter</strong></span>
          </p></li><li><p>
            <span class="guimenuitem">Execute (All or Selection)</span>,
            <span><strong class="keycap">Control+Shift+Enter</strong></span>
          </p></li><li><p>
            <span class="guimenuitem">Explain Current Statement</span>,
            <span><strong class="keycap">Control+Alt+Enter</strong></span>
          </p></li><li><p>
            <span class="guimenuitem">Explain (All or Selection)</span>,
            <span><strong class="keycap">Control+Alt+Shift+Enter</strong></span>
          </p></li></ul></div><p>
        The Stop toolbar button and menu item now are automatically
        enabled and disabled.
       (Bug #50911)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        Proceeding through the <span class="guilabel">Edit Table Data</span>
        wizard (launched by the <span class="guilabel">Edit Table Data</span>
        action item on the Home screen) and clicking
        <span class="guibutton">Finish</span> to complete the wizard caused
        MySQL Workbench to crash.
       (Bug #53511)</p></li><li><p>
        When forward engineering a model to a database, not all tables
        were created on the live database.
       (Bug #53506)</p></li><li><p>
        Russian characters were not displayed correctly in the
        <span class="guilabel">SQL Query</span> tab of the SQL Editor.
       (Bug #53408)</p></li><li><p>
        It was not possible to give the index name and foreign key name
        of a column different names. Now renaming an index in
        MySQL Workbench does not automatically rename a corresponding
        foreign key. Renaming a foreign key automatically renames the
        associated index only if the names still match at the time the
        foreign key is renamed.
       (Bug #53370)</p></li><li><p>
        The <span class="guilabel">Edit SQL Script</span> action item on the Home
        screen failed to load and execute the script.
       (Bug #53359)</p></li><li><p>
        If a socket/pipe connection method was used, and the password
        was stored in the keychain, MySQL Workbench could not connect to the
        server.
       (Bug #53355)</p></li><li><p>
        On Mac OS X, the overlay text for <code class="literal">NULL</code> and
        <code class="literal">BLOB</code> fields was missing from the results grid
        in the SQL editor. This meant that those fields appeared empty
        if a query was executed that returned a <code class="literal">BLOB</code>,
        such as <code class="literal">SELECT SHA1('hello');</code>.
       (Bug #53335)</p></li><li><p>
        Changing the fonts in the <span class="guilabel">Workbench
        Preferences</span> dialog had no effect on the appearance of
        MySQL Workbench.
       (Bug #53321, Bug #49832)</p></li><li><p>
        In the SQL Editor, if some script text was highlighted, when
        <span><strong class="keycap">Control+S</strong></span> was pressed to save the script to a
        file, only the highlighted text was saved.
       (Bug #53275)</p></li><li><p>
        An error was generated when a server was selected from the
        <span class="guilabel">Import/Export MySQL Data</span> dialog, displayed
        after clicking the <span class="guilabel">Manage Import/Export</span>
        action item on the Home screen.
       (Bug #53271)</p></li><li><p>
        In the modeler, if a table was double-clicked to open it in the
        Table Editor, and then, without closing the Table Editor,
        another table was double-clicked to open it, the Table Editor
        was rendered as a blank panel.
       (Bug #53250, Bug #53347)</p></li><li><p>
        MySQL Workbench crashed after using the <span class="guilabel">Edit SQL
        Script</span> action item from the Home screen. In the
        <span class="guilabel">Edit SQL Script</span> wizard, a connection was
        chosen that did not use a stored password, and then a script
        selected and the <span class="guibutton">Finish</span> button clicked to
        exit the wizard. MySQL Workbench subsequently crashed when the
        requested password was entered into the dialog and the
        <span class="guibutton">OK</span> clicked.
       (Bug #53247)</p></li><li><p>
        In the SQL Editor, if a <code class="literal">BLOB</code> field containing
        an image was loaded into the Viewer, the image was not
        displayed.
       (Bug #53245)</p></li><li><p>
        In the <span class="guilabel">Administrator</span> tab of the
        <span class="guilabel">Workbench Preferences</span> dialog, the
        description to the right of the text field <span class="guilabel">Path to
        mysql Tool</span> was incorrect.
       (Bug #53201)</p></li><li><p>
        MySQL Workbench permitted the creation of invalid foreign keys that
        referenced a column that did not use a <code class="literal">PRIMARY
        KEY</code> or <code class="literal">UNIQUE</code> key declaration.
        MySQL Workbench now filters the list of columns permitted for a
        referenced foreign key, so that only primary key and indexed
        columns are listed.
       (Bug #53136)</p></li><li><p>
        In the <span class="guilabel">Alter Table</span> dialog of the SQL
        Editor, it was not possible to create new Foreign Keys.
       (Bug #53134)</p></li><li><p>
        If a model was saved using a file name that contained
        non-English characters, it could not be reopened from the list
        of existing models on the Home screen.
       (Bug #53110)</p></li><li><p>
        In the SQL Editor, if multiple Query tabs were opened so that
        they used more than the available screen width, it was not
        possible to move to the tabs that were not visible. MySQL Workbench
        now includes scroll buttons should the number of tabs exceed the
        screen width. The scroll buttons make it possible to access
        non-visible tabs.
       (Bug #53070)</p></li><li><p>
        If a model was forward engineered to a database, renamed, and
        then forward engineered again, the SQL that was generated was
        erroneous.
       (Bug #53068)</p></li><li><p>
        In the <span class="guilabel">Inserts</span> tab of the Table Editor, if
        characters were entered into an integer column, MySQL Workbench
        crashed when a new column was selected.
       (Bug #53066)</p></li><li><p>
        If a table was copied in the modeler, the copy of the table was
        renamed. However, foreign key relationships contained within the
        table were not renamed.
       (Bug #53020)</p></li><li><p>
        In the <span class="guilabel">Alter Table</span> dialog of the SQL
        Editor, if two triggers were created, the second with a bad
        command, and the error corrected, then when changes were
        applied, the generated code was incorrect, dropping both
        triggers.
       (Bug #52997)</p></li><li><p>
        It was not possible to increase the font size of text in the SQL
        Editor. MySQL Workbench has been changed so that fonts set in the
        <span class="guilabel">Workbench Preferences</span> dialog now also
        affect the SQL Editor.
       (Bug #52968)</p></li><li><p>
        It was not possible to delete a trigger from the
        <span class="guilabel">Triggers</span> tab in the <span class="guilabel">Alter
        Table</span> dialog. Even though the trigger code was
        selected and deleted, and then <span class="guibutton">Apply</span>
        clicked, the code that was generated did not drop the deleted
        trigger as expected.
       (Bug #52955)</p></li><li><p>
        Synchronize to live database failed when the model contained
        triggers.
       (Bug #52939)</p></li><li><p>
        In the SQL Editor, when the <span class="guimenu">Alter Table</span>
        context-sensitive menu option was used on a table and changes
        were made, it was not possible to save them because the dialog
        reported that no changes to the object had been detected.
       (Bug #52786)</p></li><li><p>
        In the SQL Editor, if the table data was edited, attempts to
        apply the changes did nothing.
       (Bug #52705)</p></li><li><p>
        Selecting <span class="guimenu">Plugins</span>,
        <span class="guimenu">Utilities</span>, <span class="guimenu">Test filters</span>
        produced an unexpected error:
      </p><pre class="programlisting">Error calling WbAdmin.openFilterDebugger</pre><p>
        The Filters Debugger facility can now be accessed in the
        <span class="guilabel">Manage Server Instances</span> dialog. It is
        located on the Server Stats sub-tab of the Server Profile tab.
       (Bug #52655)</p></li><li><p>
        In the SQL Editor the Find and Replace facility did not appear
        to function.
       (Bug #52251)</p></li><li><p>
        Changes to EER Diagram page size using <span class="guimenu">File</span>,
        <span class="guimenu">Page Setup</span> were not reflected in the model
        navigator.
       (Bug #52077)</p></li><li><p>
        When editing table data in the SQL Editor, the table would
        refresh after data was edited in the first column. This meant it
        was necessary to then scroll to the bottom of the table data to
        continue editing the record.
       (Bug #51965)</p></li><li><p>
        Any columns that contained a comment were marked for change when
        synchronizing the model with the live database.
       (Bug #51765)</p></li><li><p>
        Diagram names containing an ampersand were not displayed
        correctly in the Model Overview.
       (Bug #51617)</p></li><li><p>
        The default Export Directory Path in the <span class="guilabel">Workbench
        Preferences</span> dialog was given as
        <code class="filename"><em class="replaceable"><code>DriveLetter</code></em>:\<em class="replaceable"><code>MyDocumentsPath</code></em>/dumps</code>.
        This mixed the <code class="literal">'/'</code> and <code class="literal">'\'</code>
        directory separators.
      </p><p>
        Further, the preferred Export Directory Path set in the
        <span class="guilabel">Workbench Preferences</span> dialog was not
        reflected in the Export to Disk section of the <span class="guilabel">Data
        Dump</span> facility in the Administrator.
       (Bug #51519)</p></li><li><p>
        In the <span class="guilabel">Alter Table</span> dialog of the SQL
        Editor, there was no effective way of altering a foreign key.
        Also, the Column and Referenced Column were not updated when a
        foreign key was created in the Foreign Keys tab.
       (Bug #51124, Bug #51262)</p></li><li><p>
        In trigger code, triggers using the alias <code class="literal">new</code>
        were correctly colored by the syntax highlighter, but triggers
        using the alias <code class="literal">old</code> were not.
       (Bug #51061)</p></li><li><p>
        When an EER Diagram layout was set to span multiple pages and
        then printed, the diagram was printed so small as to be
        illegible.
       (Bug #51032)</p></li><li><p>
        When MySQL Workbench was maximized, it did not fit correctly onto
        the screen and the title bar was not displayed.
       (Bug #50975)</p></li><li><p>
        If the name of a table was changed in the <span class="guilabel">Alter
        Table</span> dialog and <span class="guibutton">Apply</span> was
        clicked, the message “<span class="quote">no changes to object were
        detected</span>” was received, even though a change had been
        made.
       (Bug #50894)</p></li><li><p>
        In the EER Diagram view, changing the page orientation to
        landscape using <span class="guimenu">File</span>, <span class="guimenu">Page
        Setup</span> caused multiple problems in MySQL Workbench. The
        Navigator orientation did not change, the diagram did not print
        at the correct size, and MySQL Workbench eventually crashed.
       (Bug #50861)</p></li><li><p>
        When the SQL Editor was launched, MySQL Workbench became overloaded,
        due to a large number of tables (10,000+) in the schema.
        MySQL Workbench now includes two new options in the
        <span class="guilabel">Workbench Preferences</span> dialog:
        <span class="guilabel">Disable Live Schema Overview</span> and
        <span class="guilabel">Show Schema Names Only in Catalog List</span>.
        This enables the application to be configured to handle schemata
        with large numbers of tables.
       (Bug #50701)</p></li><li><p>
        The Relationship and Layer editors did not close if the object
        they were editing was deleted. MySQL Workbench now supports
        auto-closing of all open editors, should the object being edited
        be deleted.
       (Bug #50681)</p></li><li><p>
        If a PDF is generated of the EER Diagram and the resulting PDF
        file is viewed in Acrobat Reader, MySQL Workbench crashed if an
        attempt was made to reprint the diagram (overwriting the file
        that was currently opened in Acrobat Reader).
       (Bug #50408)</p></li><li><p>
        In the <span class="guilabel">User Defined Types</span> dialog (launched
        using the main menu item <span class="guimenu">Model</span>, <span class="guimenu">User
        Defined Types</span>), selection of the
        <code class="literal">UNSIGNED</code> or <code class="literal">ZEROFILL</code> check
        boxes was not reflected in SQL code generated by the
        <span class="guilabel">Forward Engineer SQL Script</span> wizard.
       (Bug #50323)</p></li><li><p>
        If some changes were made in the Table Editor, and the editor
        was still in edit mode, the active changes in the Table Editor
        were not saved when the model was saved.
       (Bug #50006)</p></li><li><p>
        Using the <span class="guilabel">Compare and Report Differences in
        Catalogs</span> wizard caused MySQL Workbench to crash.
       (Bug #49561)</p></li><li><p>
        Find was always enabled, even in contexts where it had no useful
        functionality.
       (Bug #49293)</p></li><li><p>
        MySQL Workbench permitted setting the auto-increment check box for
        multiple columns in the Table Editor.
       (Bug #49278)</p></li><li><p>
        In the <span class="guilabel">Select Changes to Apply</span> page of the
        <span class="guilabel">Synchronize Model with Database</span> wizard, if
        a schema was selected and then any of the <span class="guibutton">Update
        Model</span>, <span class="guibutton">Ignore</span>, or
        <span class="guibutton">Update Source</span> buttons was clicked, this
        change was not applied to child objects of the schema.
       (Bug #45454)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-data-modeling-create-model-from-existing-database.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.3. Create EER Model from Existing Database</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-data-modeling.html" title="Chapter 7. Data Modeling"><link rel="prev" href="wb-data-modeling-create-new-model.html" title="7.2. Create New EER Model"><link rel="next" href="wb-data-modeling-create-model-from-sql-script.html" title="7.4. Create EER Model from 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-data-modeling-create-model-from-existing-database"></a>7.3. Create EER Model from Existing Database</h2></div></div></div><p>
      This action item enables you to create an EER Model from an
      existing live database. Clicking this action item launches the
      Reverse Engineer Database. This is a multi-stage wizard that
      enables you to select a connection to a live server, and select
      the schema and objects you wish to reverse engineer into your new
      model. This is a convenient way to see how an existing database is
      structured.
    </p><p>
      For further information about reverse engineering, see
      <a href="wb-reverse-engineer-live.html" title="7.7.9.2. Reverse Engineering a Live Database">Section 7.7.9.2, “Reverse Engineering a Live Database”</a>.
    </p></div></body></html>


path: /wb-html-guitools/wb-working-with-models.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.7. Working with Models</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-reference-relationship-tools.html" title="7.6.1.10. The Relationship Tools"><link rel="next" href="wb-tables.html" title="7.7.1. Creating Tables"></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-working-with-models"></a>7.7. Working with Models</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-tables.html">7.7.1. Creating Tables</a></span></dt><dt><span class="section"><a href="wb-foreign-key-relationships.html">7.7.2. Creating Foreign Key Relationships</a></span></dt><dt><span class="section"><a href="wb-creating-views.html">7.7.3. Creating Views</a></span></dt><dt><span class="section"><a href="wb-routines-routine-groups.html">7.7.4. Creating Routines and Routine Groups</a></span></dt><dt><span class="section"><a href="wb-layers.html">7.7.5. Creating Layers</a></span></dt><dt><span class="section"><a href="wb-notes.html">7.7.6. Creating Notes</a></span></dt><dt><span class="section"><a href="wb-text-objects.html">7.7.7. Creating Text Objects</a></span></dt><dt><span class="section"><a href="wb-images.html">7.7.8. Creating Images</a></span></dt><dt><span class="section"><a href="wb-reverse-engineering.html">7.7.9. Reverse Engineering</a></span></dt><dt><span class="section"><a href="wb-forward-engineering.html">7.7.10. Forward Engineering</a></span></dt></dl></div></div></body></html>


path: /wb-html-guitools/wb-sql-editor-main-menu.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>6.7.1. Main Menu</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-sql-editor.html" title="6.7. SQL Editor"><link rel="prev" href="wb-sql-editor.html" title="6.7. SQL Editor"><link rel="next" href="wb-sql-editor-toolbar.html" title="6.7.2. Toolbar"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-sql-editor-main-menu"></a>6.7.1. Main Menu</h3></div></div></div><p>
        When an SQL Editor tab is selected, the most important items on
        the main menu bar are the <span class="guimenu">Query</span> and
        <span class="guimenu">Edit</span> menus.
      </p><p>
        <span class="bold"><strong>Query Menu</strong></span>
      </p><p>
        The <span class="guimenu">Query</span> menu features the following items:
      </p><div class="itemizedlist"><ul type="disc"><li><p>
            <span class="guimenuitem">Execute (All or Selection)</span>:
            Executes all statements in the SQL Query area, or only the
            selected statements.
          </p></li><li><p>
            <span class="guimenuitem">Execute Current Statement</span>:
            Executes the current SQL statement.
          </p></li><li><p>
            <span class="guimenuitem">Explain (All or Selection)</span>:
            Describes all statements, or the selected statement.
          </p></li><li><p>
            <span class="guimenuitem">Explain Current Statement</span>:
            Describes the current statement.
          </p></li><li><p>
            <span class="guimenuitem">Stop</span>: Stops executing the
            currently running script.
          </p></li><li><p>
            <span class="guimenuitem">Reconnect to Server</span>: Reconnects
            to the MySQL server.
          </p></li><li><p>
            <span class="guimenuitem">New Tab</span>: Creates a duplicate of
            the current SQL Editor tab.
          </p></li><li><p>
            <span class="guimenuitem">Commit Transaction</span>: Commits a
            database transaction.
          </p></li><li><p>
            <span class="guimenuitem">Rollback Transaction</span>: Rolls back
            a database transaction.
          </p></li><li><p>
            <span class="guimenuitem">Refresh</span>: Synchronizes with the
            live server and refreshes views such as the live Overview
            tabsheet.
          </p></li><li><p>
            <span class="guimenuitem">Commit Result Edits</span>: Commits any
            changes you have made to the server.
          </p></li><li><p>
            <span class="guimenuitem">Discard Result Edits</span>: Discards
            any changes you have made.
          </p></li><li><p>
            <span class="guimenuitem">Export Results</span>: Exports result
            sets to a file. Selecting this option displays the
            <span class="guilabel">Export Query Results to File</span> dialog.
            The dialog enables you to select which result set you wish
            to export, the file format (CSV, HTML, XML), and the name
            and location of the output file. Then click
            <span class="guibutton">Export</span> to export the data.
          </p></li></ul></div><p>
        <span class="bold"><strong>Edit Menu</strong></span>
      </p><p>
        The <span class="guimenu">Edit</span> menu features the
        <span class="guisubmenu">Format</span> submenu. The
        <span class="guisubmenu">Format</span> submenu includes the following
        menu items that are of importance when in SQL Editor mode:
      </p><div class="itemizedlist"><ul type="disc"><li><p>
            <span class="guimenuitem">Beautify Query</span>: Reformats the
            query selected in the query tab and lays it out in nicely
            indented fashion.
          </p></li><li><p>
            <span class="guimenuitem">UPCASE Keywords</span>: Converts
            keywords to uppercase in the currently selected query in the
            query tab.
          </p></li><li><p>
            <span class="guimenuitem">lowercase Keywords</span>: Converts
            keywords to lowercase in the currently selected query in the
            query tab.
          </p></li><li><p>
            <span class="guimenuitem">Indent Lines</span>: Indents the lines
            selected in the query tab.
          </p></li><li><p>
            <span class="guimenuitem">Unindent Lines</span>: Unindents the
            lines selected in the query tab.
          </p></li><li><p>
            <span class="guimenuitem">Un/Comment Selection</span>: Comments
            the lines currently selected in the query tab. If the lines
            are already commented, this operation removes the comments.
          </p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-launching-windows.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>3.3.2. Launching MySQL Workbench on Windows</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-starting.html" title="3.3. Starting MySQL Workbench"><link rel="prev" href="wb-installing-windows.html" title="3.3.1. Installing MySQL Workbench on Windows"><link rel="next" href="wb-windows-uninstalling.html" title="3.3.3. Uninstalling MySQL Workbench on Windows"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-launching-windows"></a>3.3.2. Launching MySQL Workbench on Windows</h3></div></div></div><p>
        To start MySQL Workbench on Windows, select
        <span class="guimenu">Start</span>, <span class="guimenuitem">Programs</span>,
        <span class="guimenuitem">MySQL</span>, then select MySQL Workbench.
      </p><p>
        Alternatively, start MySQL Workbench from the command line. To view
        the available command-line options, issue the command
        <span><strong class="command">MySQLWorkbench -help | more</strong></span> from the
        MySQL Workbench installation directory. You will see the following
        output:
      </p><pre class="programlisting">MySQL Workbench 5.2.34 SE. (C) 2006-2011 by Oracle Corporation.
All rights reserved.

Usage: MySQLWorkbench [options] [model file]

Options
 -admin instance .... Open an admin tab to the named server instance at startup
 -open filename ..... Open the given filename at startup
 -query server ...... Open a DB query tab to the named server connection at startup
 -run script ........ Executes the given Workbench script at startup
 -run-python script . Executes the given Workbench Python script at startup
 -run-lua script .... Executes the given Workbench Lua script at startup
 -script scriptfile . Executes the given Workbench script file at startup
 -quit-when-done .... Quits Workbench once the given script finishes executing
 -swrendering ....... Force the canvas to use software rendering instead of OpenGL
 -nologo ............ Do not display the splash screen
 -log ............... Instruction to save messages (other debug info) to file
 -verbose (-v) ...... Print verbose output in the GRT Shell
 -version ........... Print the version information
 -grtversion ........ Print the GRT version information
 -help (-h) ......... Print this output</pre><p>
        The MySQL Workbench help output includes a version number, a usage
        message, and the option descriptions. Use the
        <code class="option">-swrendering</code> option if your video card does not
        support OpenGL 1.5. The <code class="option">-version</code> option can be
        used to display the MySQL Workbench version number. The
        <code class="option">-grtversion</code> can be used to display the GRT
        (Generic RunTime) shell version number. The other options are
        self-explanatory.
      </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
          When using the <code class="option">-help</code> and
          <code class="option">-version</code>, command-line options that display
          output to a console window, be sure that you pipe the output
          through the <span><strong class="command">more</strong></span> command. Otherwise,
          nothing will be displayed.
        </p></div></div></body></html>


path: /wb-html-guitools/wb-preferences-model.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>5.4.4. The Model 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-sql-editor.html" title="5.4.3. The SQL Editor Tab"><link rel="next" href="wb-preferences-mysql.html" title="5.4.5. The MySQL 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-model"></a>5.4.4. The Model Tab</h3></div></div></div><p>
      This section provides configuration options that affect the
      Modeling functionality in MySQL Workbench.
    </p><p>
      Use the <span class="guilabel">When Deleting Physical Model Figures in
      Diagram</span> section to determine the behavior when deleting
      objects from the EER diagram canvas. Choose <code class="literal">Ask</code>
      and whenever you delete an object, you will be asked whether you
      wish to remove the object from an EER diagram only or also from
      the catalog. The <code class="literal">Keep Database Object in
      Catalog</code> is the safest option. You also have the option
      of deleting the object from both the EER diagram and the catalog.
    </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
        If you choose the <code class="literal">Ask</code> option, a confirmation
        dialog box opens only when you are deleting an object from an
        EER Diagram. When deleting in the MySQL Model view, there is
        <span class="bold"><strong>no</strong></span> confirmation dialog window
        and the delete action always removes the object from the
        catalog.
      </p></div><p>
      There are a variety of ways to delete an object from an EER
      canvas: using the <code class="literal">eraser</code> tool; choosing a
      pop-up menu item; using the delete key; and by choosing the delete
      option from the <span class="guimenu">Edit</span> menu. In each case, the
      action performed by the delete key is determined by the option
      chosen from the <span class="guilabel">When Deleting Physical Model Figures in
      Diagram</span> section.
    </p><p>
      Use the Model tab to set the default value for various object
      names and the primary key data type. The following table shows the
      object names and their default values.
    </p><div class="informaltable"><table border="1"><colgroup><col><col></colgroup><thead><tr><th>Object Name</th><th>Default Value</th></tr></thead><tbody><tr><td><code class="literal">Primary Key Column Name</code></td><td><code class="literal">id%table%</code></td></tr><tr><td><code class="literal">Primary Key Column Type</code></td><td><code class="literal">INT</code></td></tr><tr><td><code class="literal">Column Name</code></td><td><code class="literal">%table%col</code></td></tr><tr><td><code class="literal">Column Type</code></td><td><code class="literal">VARCHAR(45)</code></td></tr><tr><td><code class="literal">Foreign Key Name</code></td><td><code class="literal">fk%stable_%dtable%</code></td></tr><tr><td><code class="literal">Foreign Key Column Name</code></td><td><code class="literal">%table%_%column%</code></td></tr><tr><td><code class="literal">ON UPDATE</code></td><td><code class="literal">NO ACTION</code></td></tr><tr><td><code class="literal">ON DELETE</code></td><td><code class="literal">NO ACTION</code></td></tr><tr><td><code class="literal">Associative Table Name</code></td><td><code class="literal">%stable%_has_%dtable%</code></td></tr></tbody></table></div><p>
      The <code class="literal">Primary Key Column Name</code> <code class="literal">Primary
      Key Column Type</code>, <code class="literal">Column Name</code>, and
      <code class="literal">Column Type</code> values are the defaults used by the
      table editor. The others are the default names used when using the
      relationship tools on an EER diagram.
    </p><p>
      Within object values items enclosed by percentage signs are
      variables. Their meanings are as follows:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <code class="literal">%table%</code>: The table associated with the
          object
        </p></li><li><p>
          <code class="literal">%stable%</code>: The source table associated with
          the object
        </p></li><li><p>
          <code class="literal">%dtable%</code>: The destination table associated
          with the object
        </p></li><li><p>
          <code class="literal">%column%</code>: The column associated with the
          object
        </p></li></ul></div><p>
      Legitimate values for the foreign key update or delete rules are:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <code class="literal">RESTRICT</code>
        </p></li><li><p>
          <code class="literal">CASCADE</code>
        </p></li><li><p>
          <code class="literal">SET NULL</code>
        </p></li><li><p>
          <code class="literal">NO ACTION</code> (default)
        </p></li></ul></div><p>
      For more information about these actions, 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></div></body></html>


path: /wb-html-guitools/wb-connection-properties.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.3. Connection Properties</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-editor.html" title="7.7.2.2. The Relationship Editor"><link rel="next" href="wb-creating-views.html" title="7.7.3. Creating Views"></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-connection-properties"></a>7.7.2.3. Connection Properties</h4></div></div></div><p>
      Right-click a connection to select it. When a connection is
      selected, it is highlighted and its properties are displayed in
      the properties palette. Connection properties are quite different
      from the properties of other objects. The following list describes
      them:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <code class="literal">caption</code>: The name of the connection. By
          default, the name is the name of the foreign key and the
          property is centered above the connection line.
        </p></li><li><p>
          <code class="literal">captionXOffs</code>: The X offset of the caption.
        </p></li><li><p>
          <code class="literal">captionYOffs</code>: The Y offset of the caption.
        </p></li><li><p>
          <code class="literal">comment</code>: The comment associated with the
          relationship.
        </p></li><li><p>
          <code class="literal">drawSplit</code>: Whether to show the relationship
          as a continuous line.
        </p></li><li><p>
          <code class="literal">endCaptionXOffs</code>: The X termination point of
          the caption offset.
        </p></li><li><p>
          <code class="literal">endCaptionYOffs</code>: The Y termination point of
          the caption offset.
        </p></li><li><p>
          <code class="literal">extraCaption</code>: A secondary caption. By
          default, this extra caption is centered beneath the connection
          line.
        </p></li><li><p>
          <code class="literal">extraCaptionXOffs</code>: The X offset of the
          secondary caption.
        </p></li><li><p>
          <code class="literal">extraCaptionYOffs</code>: The Y offset of the
          secondary caption.
        </p></li><li><p>
          <code class="literal">mandatory</code>: Whether the entities are
          mandatory. For more information, see
          <a href="wb-relationship-editor.html" title="7.7.2.2. The Relationship Editor">Section 7.7.2.2, “The Relationship Editor”</a>.
        </p></li><li><p>
          <code class="literal">many</code>: False if the relationship is a
          one-to-one relationship.
        </p></li><li><p>
          <code class="literal">middleSegmentOffset</code>: The offset of the
          middle section of the connector.
        </p></li><li><p>
          <code class="literal">modelOnly</code>: Set when the connection will not
          be propagated to the DDL. It is just a logical connection
          drawn on a diagram. This is used, for example, when drawing
          <code class="literal">MyISAM</code> tables with a visual relationship,
          but with no foreign keys.
        </p></li><li><p>
          <code class="literal">name</code>: The name used to identify the
          connection on the EER Diagram canvas. Note that this is
          <span class="bold"><strong>not</strong></span> the name of the foreign
          key.
        </p></li><li><p>
          <code class="literal">referredMandatory</code>: Whether the referred
          entity is mandatory.
        </p></li><li><p>
          <code class="literal">startCaptionXOffs</code>: The start of the X
          offset of the caption.
        </p></li><li><p>
          <code class="literal">startCaptionYOffs</code>: The start of the Y
          offset of the caption.
        </p></li></ul></div><p>
      In most cases, you can change the properties of a relationship
      using the relationship editor rather than the
      <code class="literal">Properties</code> palette.
    </p><p>
      If you make a relationship invisible by hiding it using the
      relationship editor's <span class="guilabel">Visibility Settings</span>,
      and then close the relationship editor, you will no longer be able
      to select the relationship to bring up its relationship editor. To
      make the relationship visible again, you must expand the table
      object relating to the relationship in the
      <span class="guilabel">Layers</span> palette and select the relationship
      object. To edit the selected object, right-click it, then select
      <span class="guimenuitem">Edit Object</span>. You can then set the
      <span class="guilabel">Visibility Settings</span> to <span class="guilabel">Fully
      Visible</span>. The relationship will then be visible in the
      <span class="guilabel">EER Diagram</span> window.
    </p></div></body></html>


path: /wb-html-guitools/wb-news-5-2-31.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.9. Changes in MySQL Workbench 5.2.31 (08 December 2010)</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="changes-5.2.x.html" title="A.1. Changes in Release 5.2"><link rel="prev" href="wb-news-5-2-31a.html" title="A.1.8. Changes in MySQL Workbench 5.2.31a (13 December 2010)"><link rel="next" href="wb-news-5-2-30.html" title="A.1.10. Changes in MySQL Workbench 5.2.30 (20 November 2010)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-news-5-2-31"></a>A.1.9. Changes in MySQL Workbench 5.2.31 (08 December 2010)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.2.30.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        <span class="guimenu">Edit</span>, <span class="guimenu">Format</span>,
        <span class="guimenu">Un/Comment Selection</span> was added.
       (Bug #55278, Bug #11762657)</p></li><li><p>
        The query execution time was added to the query result status
        bar.
       (Bug #53509, Bug #11761054)</p></li><li><p>
        MySQL Workbench has been changed so that holding the spacebar while
        in the EER Diagram view temporarily changes the cursor to the
        hand tool. When the spacebar is released the cursor reverts to
        the tool that was selected prior to the spacebar having been
        pressed.
       (Bug #52331)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        Typing into the Workbench Scripting Shell resulted in an Unexpected Error:
      </p><pre class="programlisting">MySQL Workbench has encountered a problem.

Attempted to read or write protected memory. This is often an indication that other
memory is corrupt.</pre><p>(Bug #58832)</p></li><li><p>
        These query beautifier problems were corrected:
      </p><div class="itemizedlist"><ul type="circle"><li><p>
            When the beautifier was used on a query that performed a
            join with the <code class="literal">USING</code> keyword, the table
            name was concatenated with that keyword.
          </p></li><li><p>
            The beautifier did not recognize the optional
            <code class="literal">AS</code> keyword in table references. When
            <code class="literal">AS</code> was used with a table alias, the
            beautifier concatenated that keyword and the alias, which
            caused any references to the original alias to fail.
          </p></li><li><p>
            Using the beautifier on a query containing
            <code class="literal">USING</code> resulted in an invalid query being
            generated. This was due to missing spaces around
            <code class="literal">USING</code>.
          </p></li><li><p>
            Using the beautifier on a query resulted in an unhandled
            exception.
          </p></li><li><p>
            If a query was partially selected, and then the beautifier
            was run, the results were unpredictable. Problems included
            exceptions, duplicated tokens, and incorrect indentation.
          </p></li><li><p>
            When the beautifier was run on code containing several
            statements, the code was incorrectly formatted.
          </p></li><li><p>
            A query containing a <code class="literal">CASE</code> keyword was not
            handled correctly.
          </p></li><li><p>
            The beautifier converted certain tokens to uppercase that
            should not have been converted.
          </p></li><li><p>
            When attempting to beautify a <code class="literal">CREATE
            INDEX</code> query, the beautifier removed part of the
            query.
          </p></li><li><p>
            If a query was written in the <span class="guilabel">SQL Query</span>
            tab, and then highlighted using the cursor, the beautifier
            failed with an unhandled exception on calls to beautify,
            uppercase, or lowercase functions.
          </p></li><li><p>
            Using the beautifier on a <code class="literal">CREATE TABLE</code>
            statement resulted in an unhandled exception.
          </p></li></ul></div><p>(Bug #58598, Bug #58569, Bug #58347, Bug #58565, Bug #58359, Bug #58367, Bug #58361, Bug #58360, Bug #58357, Bug #58358, Bug #58356)</p></li><li><p>
        In the Administrator, monitoring of a remote server did not
        work.
       (Bug #58586)</p></li><li><p>
        In the Administrator, starting or stopping the monitored server
        produced this error message:
      </p><pre class="programlisting">Could not stop/start server: expected a character buffer object</pre><p>(Bug #58400)</p></li><li><p>
        When exporting a record set using the <span class="guilabel">SQL INSERT
        statements</span> file format, a number of issues were
        found:
      </p><div class="itemizedlist"><ul type="circle"><li><p>
            The first line contained the executed
            <code class="literal">SELECT</code> statement as a comment but the
            <code class="literal">LIMIT</code> syntax was located in a new line.
            This resulted in the <code class="literal">LIMIT</code> part of the
            statement not being commented out.
          </p></li><li><p>
            Strings following the <code class="literal">VALUES</code> keyword were
            not quoted.
          </p></li><li><p>
            The <code class="literal">INSERT</code> statements contained the text
            “<span class="quote">table</span>” in place of the actual table name.
          </p></li><li><p>
            Existing files were overwritten without prompting the user.
          </p></li></ul></div><p>(Bug #58377, Bug #56950)</p></li><li><p>
        In the SQL Editor, selecting the default database where the
        server contained only a single database had no effect. To avoid
        a “<span class="quote">No database selected</span>” error, the database had to
        be selected in a script using the <code class="literal">USE</code>
        statement.
       (Bug #58274)</p></li><li><p>
        Autotools were required to be installed locally to build
        MySQL Workbench from source.
       (Bug #58263)</p></li><li><p>
        The MySQL Workbench tarball contained cached Autotools information.
       (Bug #58261)</p></li><li><p>
        In the SQL Editor, right-clicking a table name and selecting
        <span class="guimenu">Alter table</span> did not launch the
        <span class="guilabel">Alter table</span> dialog as expected. This
        happened if the table name utilized mixed case letters.
       (Bug #58223)</p></li><li><p>
        Results for queries on rows that contained a null byte (\0) were
        truncated at the null byte character when displayed in the SQL
        Editor results pane.
       (Bug #58099)</p></li><li><p>
        In the SQL Editor, when entering a hex value into an
        <code class="literal">INTEGER</code> column, the hex value was
        automatically quoted as a string, causing it to be evaluated to
        0.
       (Bug #58045)</p></li><li><p>
        In the <span class="guilabel">Server Access Management</span> tab of the
        Administrator no user accounts were displayed. Further,
        attempting to create a new account resulted in an exception.
       (Bug #57941)</p></li><li><p>
        In the <span class="guilabel">Reverse Engineer SQL Script</span> wizard,
        on the <span class="guilabel">Input and Options</span> page, the button
        to select the SQL script file had the text “<span class="quote">Brow</span>”
        instead of “<span class="quote">Browse</span>”.
       (Bug #57929)</p></li><li><p>
        The commands to arrange objects were not enabled in the EER
        Diagram view. This rendered it impossible to move objects to the
        back or bring them to the front.
       (Bug #57907)</p></li><li><p>
        When setting the data type of a column to
        <code class="literal">DOUBLE</code> with precision specified, the data
        type reverted to <code class="literal">DOUBLE</code> without the desired
        precision specifiers. This happened in both the Table Editor and
        the SQL Editor.
       (Bug #57865)</p></li><li><p>
        In the <span class="guilabel">Columns</span> tab of the Table Editor,
        double-clicking to edit or add a new column caused the window to
        scroll to the top.
       (Bug #57793)</p></li><li><p>
        An error message contained a spelling mistake:
      </p><pre class="programlisting">Line 437 of .\backend\wbprivate\workbench\wb_context_ui_home.cpp:
std::string msg = strfmt("Error in sercurityManager module: %s",err.what());</pre><p>(Bug #57684)</p></li><li><p>
        In the <span class="guilabel">SQL Editor</span> tab of the
        <span class="guilabel">Workbench Preferences</span> dialog, if the
        <span class="guibutton">OK</span> button was not clicked centrally, it
        was possible to accidentally select or deselect one of the
        options <span class="guilabel">Treat BINARY/VARBINARY as nonbinary character
        string</span> or <span class="guilabel">Enable Data Changes Commit
        Wizard</span>.
       (Bug #57669)</p></li><li><p>
        For a column of type <code class="literal">TIMESTAMP</code>, the menu
        items <span class="guimenu">Default CURRENT_TIMESTAMP</span> and
        <span class="guimenu">Default CURRENT_TIMESTAMP ON UPDATE
        CURRENT_TIMESTAMP</span> in the context-sensitive menu of the
        <span class="guilabel">Columns</span> tab of the Table Editor were grayed
        out. This occurred where a preceding column of type
        <code class="literal">TIMESTAMP</code> was allocated an explicit default
        value. MySQL Workbench should not have prevented setting a value
        using the context-sensitive menu for the second defined column
        in this case.
       (Bug #57665)</p></li><li><p>
        A script file that was converted to the <code class="literal">cp850</code>
        character set was truncated on loading into the SQL Editor.
       (Bug #57636)</p></li><li><p>
        The forward engineering process generated SQL code that quoted
        boolean values, causing incorrect cast values. When a table
        contained the logical <code class="literal">BOOLEAN</code> type for a
        field it was converted to <code class="literal">TINYINT(1)</code> as
        expected. However, the values that were supplied for any inserts
        were quoted, as in this example:
      </p><pre class="programlisting">INSERT INTO mytable (id,flag) VALUES (NULL,'TRUE');</pre><p>(Bug #57545)</p></li><li><p>
        The SQL Editor generated these errors if a query ran longer than
        30 seconds:
      </p><pre class="programlisting">Error Code: 2013  Lost connection to MySQL server during query
Error Code: 2006  MySQL server has gone away</pre><p>(Bug #57449)</p></li><li><p>
        Clicking the <span class="guilabel">Configuration</span> tab in the
        Administrator produced this error:
      </p><pre class="programlisting">Error Opening Configuration File
Exception: Internal error. File data passed is not in expected format. This is a bug, we
would appreciate if you file a bug report at http://bugs.mysql.com.</pre><p>(Bug #57418)</p></li><li><p>
        <code class="literal">ENUM</code> values entered into the Inserts Editor
        were not automatically quoted.
       (Bug #57399)</p></li><li><p>
        On the <span class="guilabel">Select Object</span> page of the
        <span class="guilabel">Reverse Engineer Database</span> dialog, the
        panels displayed when <span class="guilabel">Show Filter</span> was
        clicked did not resize correctly when <span class="guibutton">Hide
        Filter</span> was clicked.
       (Bug #57376)</p></li><li><p>
        Forward engineering a model failed with a duplicate column name
        error when the EER diagram contained a view consisting of tables
        joined using the <code class="literal">JOIN</code> ...
        <code class="literal">USING</code> syntax.
       (Bug #57329)</p></li><li><p>
        In the Administrator, attempting to add an account with a login
        name longer than 16 characters resulted in an exception.
       (Bug #57300)</p></li><li><p>
        The MySQL configuration file could not be accessed during
        MySQL Workbench installation.
       (Bug #56987)</p></li><li><p>
        When the MySQL service was set to manual in MySQL Workbench, the
        service was displayed as running in the server status panel,
        even though the service had not yet been started.
       (Bug #56919)</p></li><li><p>
        When creating a new server instance, this error occurred when
        testing the settings:
      </p><pre class="programlisting">Operation failed: File  doesn't exist</pre><p>(Bug #56911)</p></li><li><p>
        <span class="guimenu">Find</span> and <span class="guimenu">Find and replace</span>
        did not work in the <span class="guilabel">SQL Query</span> tab.
       (Bug #56898)</p></li><li><p>
        Backups dumped to a project folder (file per table) were
        restored in no particular order. This made it difficult to
        resume a problematic restore at a specific point.
       (Bug #56897)</p></li><li><p>
        Creating a many-to-many relationship between two tables resulted
        in only one index being generated.
       (Bug #56613)</p></li><li><p>
        MySQL Workbench crashed when a snippet in the snippet list was
        right-clicked.
       (Bug #56588)</p></li><li><p>
        When saving over a read-only file, MySQL Workbench changed the file
        permissions to read/write.
       (Bug #56403)</p></li><li><p>
        In the Role Editor, the “<span class="quote">Drag object from the catalog tree
        to assign privileges</span>” text label was out of date. The
        label should have read “<span class="quote">Drag objects from Physical
        Schemata section to assign privileges</span>”.
       (Bug #56321)</p></li><li><p>
        If the Table Editor was resized, it returned to the default size
        when switching between tables to be edited.
       (Bug #56314)</p></li><li><p>
        After the computer woke from the sleep state, MySQL Workbench
        attempted to reconnect to a connection that had previously been
        closed in the SQL Editor.
       (Bug #56302)</p></li><li><p>
        In the <span class="guilabel">Reverse Engineer Database</span> wizard,
        the ability to select the default schema on the
        <span class="guilabel">Connection Options</span> page was superfluous.
       (Bug #56179)</p></li><li><p>
        In the <span class="guilabel">Connections</span> tab of the
        Administrator, scrolling did not work correctly with large
        numbers of connections.
       (Bug #56144)</p></li><li><p>
        When multiple tabs were open in the Administrator, with each
        connected to a different server, and with export of a database
        was set up in each, running an export operation resulted in
        errors. This occurred because MySQL Workbench attempted to export a
        database selected in a tab other than the currently selected
        one.
       (Bug #56113)</p></li><li><p>
        Deleting routine groups from the EER Diagram view did not delete
        routines.
       (Bug #56084)</p></li><li><p>
        If a MWB file was double-clicked to open, but MySQL Workbench was
        already running, a new instance of MySQL Workbench was launched,
        rather than opening the file in a new tab in the currently
        running instance.
       (Bug #56067)</p></li><li><p>
        In the SQL Editor, in the <span class="guilabel">Foreign Key</span> tab
        of the <span class="guilabel">new-table</span> dialog, it was not
        possible to select any of the foreign key check boxes.
       (Bug #56024)</p></li><li><p>
        When objects were double-clicked in the Diagram view, the
        correct tab was not always switched to in the Object Editor. The
        Description Editor did however switch to the correct object.
       (Bug #55994)</p></li><li><p>
        Close tab functionality failed intermittently. This occurred for
        attempts to close the tab directly or when using the
        <span class="guimenu">File</span>, <span class="guimenu">Close tab</span> menu item.
       (Bug #55901)</p></li><li><p>
        In the SQL Editor, an out of memory exception occurred when
        exporting a large record set in the CSV file format.
       (Bug #55889)</p></li><li><p>
        In the sidebar of the SQL Editor, when a default schema was
        selected, other schemas listed in the sidebar were not
        displayed.
       (Bug #55864)</p></li><li><p>
        In the Administrator, most columns were not sortable. For
        example, in the Connections tab, it was not possible to sort
        connections based on clicking the columns id, User, Host, DB,
        Command, Time, State, Info.
       (Bug #55813)</p></li><li><p>
        When an EER diagram that was in the background was closed, it
        was not possible to reopen it.
       (Bug #55767)</p></li><li><p>
        If the relationship editor was already open, it was not possible
        to open it for another relationship without closing it first.
       (Bug #55708)</p></li><li><p>
        The <code class="literal">PYTHONPATH</code> environment variable from
        other Python installations interfered with MySQL Workbench. At
        startup, the error “<span class="quote">cannot open SSH Tunnel Manager</span>”
        appeared. Further, it was not possible to use the MySQL Workbench
        administrative functions.
       (Bug #55674)</p></li><li><p>
        In the <span class="guilabel">Column</span> tab of the Table Editor, it
        was possible to set <code class="literal">NULL</code> as the default value
        for a column that had been specified as <code class="literal">NOT
        NULL</code>.
       (Bug #55456)</p></li><li><p>
        In the SQL Editor, it was not possible to create a foreign key
        relationship between two tables.
       (Bug #55399)</p></li><li><p>
        In the Table Editor, if a data type was selected for a column,
        this was immediately reflected on the EER Diagram view. However,
        if the selection was reverted by pressing
        <span><strong class="keycap">Control+Z</strong></span>, the EER Diagram was not updated to
        reflect this, and continued to display the original data type.
       (Bug #55348)</p></li><li><p>
        In the EER Diagram view, a copied object could not be pasted, if
        the object had previously been pasted and then edited.
       (Bug #55336)</p></li><li><p>
        In the User Defined Data Types Editor, clicking the button to
        edit the argument list caused the <span class="guilabel">Argument List
        Editor</span> dialog to be drawn beneath the current dialog.
        As the dialog with focus could not be accessed, this meant it
        was not possible to proceed with editing and MySQL Workbench had to
        be closed.
       (Bug #55242)</p></li><li><p>
        The <span class="guilabel">Modified</span> time displayed in the
        <span class="guilabel">Model Overview</span> was incorrectly set to the
        current time.
       (Bug #55237)</p></li><li><p>
        Selecting a <span class="guilabel">Refresh</span> or <span class="guilabel">Refresh
        all</span> button or menu item caused the list of tables and
        views in the sidebar to become empty.
       (Bug #55214)</p></li><li><p>
        In the <span class="guilabel">Configuration</span> tab of the
        Administrator it was not possible to enable or disable the
        <code class="literal">local_infile</code> (<code class="literal">LOAD DATA
        LOCAL</code>) option.
       (Bug #55031)</p></li><li><p>
        It was not possible to select and copy messages in the Output
        window of MySQL Workbench. When messages were displayed it was no
        longer possible to right-click them and select either the
        <span class="guimenu">Copy Selected Messages to Clipboard</span> or the
        <span class="guimenu">Clear Output Windows</span> menu items.
       (Bug #54983)</p></li><li><p>
        In the Model Overview, if a diagram had a title that wrapped to
        two lines or more, the second line was truncated due to lack of
        space in the panel. Now MySQL Workbench includes a scrollbar should
        the diagram titles not fit within the standard panel.
       (Bug #54952)</p></li><li><p>
        Generated <code class="literal">INSERT</code> statements did not include
        quote characters for <code class="literal">TEXT</code> or
        <code class="literal">DATE</code> columns.
       (Bug #54910)</p></li><li><p>
        In the SQL Editor, when viewing table data where the number of
        columns was such that some columns were offscreen, if the
        <span><strong class="keycap">End</strong></span> key was pressed to go to the last column in
        the row, the data grid did not scroll accordingly, so the column
        containing the cursor was not visible without manually
        scrolling.
       (Bug #54753)</p></li><li><p>
        In the Diagram view switching between tables caused erroneous
        carriage returns to be added to the DDL code in the Triggers
        tab.
       (Bug #54411)</p></li><li><p>
        The error message displayed when the
        <span><strong class="command">mysqldump</strong></span> version needed updating was not
        informative enough.
       (Bug #54209)</p></li><li><p>
        In the Administrator, system health displayed NO DATA.
       (Bug #52151)</p></li><li><p>
        Formatting of view code entered in the View Editor was not
        retained after synchronization of the model with the server.
       (Bug #52004)</p></li><li><p>
        It was not possible to add a comment for a Layer using the
        Object Editor. MySQL Workbench has been updated so that it is
        possible to add a comment for a layer using the Object Editor.
       (Bug #50668)</p></li><li><p>
        When using the Administrator, the CPU utilization jumped to 50%.
       (Bug #50578)</p></li><li><p>
        After printing, the status message displayed included incorrect
        capitalization. “<span class="quote">Print Diagram done</span>” should have
        been displayed as “<span class="quote">Print diagram done</span>”.
       (Bug #50035)</p></li><li><p>
        The schema editor decreased in size by several pixels each time
        a new schema was edited.
       (Bug #49425)</p></li><li><p>
        The SQL Editor did not display the execution times for queries.
       (Bug #49390)</p></li><li><p>
        MySQL Workbench permitted an <code class="literal">AUTO_INCREMENT</code>
        column to be assigned a default value in the Table Editor,
        resulting in invalid DDL being generated.
       (Bug #49279)</p></li><li><p>
        The menu option <span class="guimenu">View</span>,
        <span class="guimenu">Windows</span>, <span class="guimenu"><em class="replaceable"><code>menu
        item</code></em></span> did not appear to have any useful
        function.
       (Bug #49056)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-sql-editor.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>6.7. SQL 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-sql-development.html" title="Chapter 6. SQL Development"><link rel="prev" href="wb-manage-db-connections-ssh.html" title="6.6.4. Standard TCP/IP over SSH Connection"><link rel="next" href="wb-sql-editor-main-menu.html" title="6.7.1. Main Menu"></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-editor"></a>6.7. SQL Editor</h2></div></div></div><div class="toc"><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></div><p>
      MySQL Workbench 5.2 introduced the SQL Editor facility. The SQL Editor
      can be launched using various action items on the Home window. It
      can also be launched by selecting <span class="guimenu">Database</span>,
      <span class="guimenuitem">Query Database</span> from the main menu, or
      by using the keyboard shortcut <span><strong class="keycap">Control+U</strong></span> on
      Windows, or <span><strong class="keycap">Command+U</strong></span> on Mac OS X. At this point,
      you will be asked to either select a stored connection or enter
      the details for a new connection. After a connection has been made
      to the server, a new tab called <span class="guilabel">SQL Editor
      <em class="replaceable"><code>(schema)</code></em></span> is displayed.
    </p><div class="figure"><a name="wb-sql-editor-screenshot"></a><p class="title"><b>Figure 6.5. SQL Editor</b></p><div class="mediaobject"><img src="images/wb-sql-editor-screenshot.png" width="1024" height="708" alt="SQL Editor"></div></div><p>
      The SQL Editor user interface has these main elements:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          Main Menu
        </p></li><li><p>
          Toolbar
        </p></li><li><p>
          SQL Query Panel
        </p></li><li><p>
          Main Tabsheets (Overview, Output, History, Snippets, Results)
        </p></li><li><p>
          Sidebar
        </p></li></ul></div><p>
      The following sections describe each of these elements.
    </p></div></body></html>


path: /wb-html-guitools/wb-modifying-view.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.7.3.4. Modifying a View Using the Properties Palette</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-creating-views.html" title="7.7.3. Creating Views"><link rel="prev" href="wb-view-editor.html" title="7.7.3.3. The View Editor"><link rel="next" href="wb-routines-routine-groups.html" title="7.7.4. Creating Routines and Routine Groups"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-modifying-view"></a>7.7.3.4. Modifying a View Using the Properties Palette</h4></div></div></div><p>
      When you select a view on the EER Diagram canvas, its properties
      are displayed in the <code class="literal">Properties</code> palette. Most
      of the properties accessible from the
      <code class="literal">Properties</code> palette apply to the appearance of a
      view on the EER Diagram canvas.
    </p><p>
      For a list of properties accessible through the
      <code class="literal">Properties</code> palette, see
      <a href="wb-properties-palette.html" title="7.5.12. The Properties Palette">Section 7.5.12, “The Properties Palette”</a>.
    </p></div></body></html>


path: /wb-html-guitools/wb-community-menu.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.5.1.9. The Community Menu</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-data-modeling-menus.html" title="7.5.1. Modeling Menus"><link rel="prev" href="wb-scripting-menu.html" title="7.5.1.8. The Scripting Menu"><link rel="next" href="wb-help-menu.html" title="7.5.1.10. The Help Menu"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-community-menu"></a>7.5.1.9. The Community Menu</h4></div></div></div><p>
      The <span class="guimenuitem">Community</span> menu has the following
      items. Use them to go online and learn more about MySQL Workbench.
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <span class="guimenuitem">Workbench Blog</span>
        </p></li><li><p>
          <span class="guimenuitem">FAQs About Workbench</span>
        </p></li><li><p>
          <span class="guimenuitem">Learn How To Code For Workbench</span>
        </p></li><li><p>
          <span class="guimenuitem">Discuss Workbench Topics</span>
        </p></li><li><p>
          <span class="guimenuitem">Contribute To Workbench</span>
        </p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-requirements-software.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>3.2. Software 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-requirements-hardware.html" title="3.1. Hardware Requirements"><link rel="next" href="wb-starting.html" title="3.3. Starting MySQL Workbench"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="wb-requirements-software"></a>3.2. Software Requirements</h2></div></div></div><p>
      The following operating systems are officially supported:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          Apple Mac OS X v10.6.1+ (32-bit/64-bit)
        </p></li><li><p>
          Fedora 15 (32-bit/64-bit)
        </p></li><li><p>
          Microsoft Windows 7 (32-bit/64-bit)
        </p></li><li><p>
          Oracle Linux 6 (32-bit/64-bit)
        </p></li><li><p>
          Ubuntu 10.04 LTS (32-bit/64-bit)
        </p></li><li><p>
          Ubuntu 11.04 (32-bit/64-bit)
        </p></li></ul></div><p>
      MySQL Workbench also has the following general requirements:
    </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
        On startup, the application checks the OpenGL version and
        chooses between software and hardware rendering. To determine
        which rendering method is being used, open the
        <span class="guimenu">Help</span> menu and choose the <span class="guimenuitem">System
        Info</span> item.
      </p></div><p>
      Requirements for Linux:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          The requirements for Linux are embedded within their
          respective packages. Use the platform specific tool (for
          example, yum or apt) to install the package and their
          dependencies.
        </p></li></ul></div><p>
      Requirements for Microsoft Windows:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          Microsoft .NET 4.0 Framework
        </p></li><li><p>
          Microsoft Visual C++ 2010 Redistributable Package (x86)
        </p></li></ul></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><div class="admon-title">Note</div><p>
        For convenience, the Windows libraries are available as the
        download “<span class="quote">Dependencies for Compiling in Windows</span>”.
      </p></div></div></body></html>


path: /wb-html-guitools/wb-news-5-0-18.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.3.13. Changes in MySQL Workbench 5.0.18rc (not released)</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="changes-5.0.x.html" title="A.3. Changes in Release 5.0"><link rel="prev" href="wb-news-5-0-19.html" title="A.3.12. Changes in MySQL Workbench 5.0.19 (15 April 2008)"><link rel="next" href="wb-news-5-0-17.html" title="A.3.14. Changes in MySQL Workbench 5.0.17rc (07 April 2008)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-news-5-0-18"></a>A.3.13. Changes in MySQL Workbench 5.0.18rc (not released)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.0.17rc.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        Foreign key labels could not be hidden, and displayed labels
        were not centered. There are now options to hide all connection
        captions, and to center captions.
       (Bug #30902)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        In the table editor, setting the input focus by clicking the
        mouse did not work.
       (Bug #35969)</p></li><li><p>
        The Reference Column dropdown used during foreign key creation
        was slow to display.
       (Bug #35948)</p></li><li><p>
        In the table editors foreign key Tab, when a column for the
        foreign key is checked (right pane), the Referenced Column
        dropdown opens. Pressing Escape at this point caused a crash.
       (Bug #35926)</p></li><li><p>
        After changing the Row Format option, closing the table editor
        and opening a new document caused a crash.
       (Bug #35925)</p></li><li><p>
        If a table in an EER Diagram was double-clicked in an attempt to
        open it for editing in the Table Editor, this error was
        generated:
      </p><pre class="programlisting">Cannot load selected plugin(.\db.mysql.editors.wbp.fe.dll::DbMysqlTableEditor)</pre><p>(Bug #35897)</p></li><li><p>
        Synchronizing the data model with a live database from the
        <span class="guilabel">SQL Diff Tree</span> dialog resulted in a crash.
       (Bug #35884)</p></li><li><p>
        Creating a Schema Diff Report from the local model to a live
        database caused a crash.
       (Bug #35878)</p></li><li><p>
        The Pack Keys option could not be saved.
       (Bug #35872)</p></li><li><p>
        Some menus or submenus had items enabled when the corresponding
        features were disabled.
       (Bug #35870)</p></li><li><p>
        The Connection Caption option did not work properly.
       (Bug #35859)</p></li><li><p>
        The status of a connection line in a table diagram was not
        updated when a foreign key relationship between tables was
        changed.
       (Bug #35800)</p></li><li><p>
        The <span class="guimenu">File</span> -&gt; <span class="guimenu">Export</span>
        -&gt; <span class="guimenu">Export as PNG</span> menu item was enabled
        under some circumstances in which it should have been disabled.
       (Bug #35746)</p></li><li><p>
        Scrolling was slow for table models with large numbers of
        tables.
       (Bug #35655)</p></li><li><p>
        Pressing <span><strong class="keycap">Control+Z</strong></span> to undo the last change in
        an SQL Script text box deleted the entire script.
       (Bug #35649)</p></li><li><p>
        Workbench is unable to read files such as Workbench Model Files
        from a non-English directory.
       (Bug #35547)</p></li><li><p>
        Workbench permitted table comments to be entered longer than the
        maximum length of 60 characters.
       (Bug #34507)</p></li><li><p>
        A crash could occur during foreign key creation.
       (Bug #33545)</p></li><li><p>
        Autoplacing for display of complex schemas has been improved.
       (Bug #32888)</p></li><li><p>
        Typing <code class="literal">q</code> in the GRT Shell caused a crash.
       (Bug #32755)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-preferences-mysql.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>5.4.5. The MySQL 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-model.html" title="5.4.4. The Model Tab"><link rel="next" href="wb-preferences-diagram.html" title="5.4.6. The Diagram 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-mysql"></a>5.4.5. The MySQL Tab</h3></div></div></div><p>
      This enables you to set the default table storage engine.
    </p></div></body></html>


path: /wb-html-guitools/wb-notes-physical-schemata.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.7.6.1. Adding Notes</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-notes.html" title="7.7.6. Creating Notes"><link rel="prev" href="wb-notes.html" title="7.7.6. Creating Notes"><link rel="next" href="wb-note-editor.html" title="7.7.6.2. The Note 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-notes-physical-schemata"></a>7.7.6.1. Adding Notes</h4></div></div></div><p>
      Double-clicking the <code class="literal">Add Note</code> icon in the
      <code class="literal">Model Notes</code> section of the <code class="literal">MySQL
      Model</code> page adds a note with the default name of
      <code class="literal">note1</code>. If a note with this name already exists,
      the new note is named <code class="literal">note2</code>.
    </p><p>
      Adding a new note automatically opens the note editor docked at
      the bottom of the application. For information about using the
      note editor, see <a href="wb-note-editor.html" title="7.7.6.2. The Note Editor">Section 7.7.6.2, “The Note Editor”</a>.
    </p><p>
      Right-clicking a note opens a pop-up menu with the following
      items:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <span class="guimenuitem">Rename</span>
        </p></li><li><p>
          <span class="guimenuitem">Cut
          '<em class="replaceable"><code>note_name</code></em>'</span>
        </p></li><li><p>
          <span class="guimenuitem">Copy
          '<em class="replaceable"><code>note_name</code></em>'</span>
        </p></li><li><p>
          <span class="guimenuitem">Delete
          '<em class="replaceable"><code>note_name</code></em>'</span>
        </p></li></ul></div><p>
      The <span class="guimenuitem">Edit Note...</span> item opens the note
      editor. For information about using the note editor, see
      <a href="wb-note-editor.html" title="7.7.6.2. The Note Editor">Section 7.7.6.2, “The Note Editor”</a>.
    </p><p>
      The cut and copy items are useful for copying notes between
      different schemata.
    </p><p>
      Notes can be added only on the <code class="literal">MySQL Model</code>
      page.
    </p></div></body></html>


path: /wb-html-guitools/wb-news-5-2-22.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.18. Changes in MySQL Workbench 5.2.22 (02 June 2010)</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="changes-5.2.x.html" title="A.1. Changes in Release 5.2"><link rel="prev" href="wb-news-5-2-23.html" title="A.1.17. Changes in MySQL Workbench 5.2.23 (Internal release only)"><link rel="next" href="wb-news-5-2-21.html" title="A.1.19. Changes in MySQL Workbench 5.2.21 (12 May 2010 Release Candidate)"></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-22"></a>A.1.18. Changes in MySQL Workbench 5.2.22 (02 June 2010)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.2.21.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        On Linux, MySQL Workbench automatically added a
        <code class="filename">.sql</code> extension, where an extension was not
        specified, to any script file saved from the SQL Editor.
        MySQL Workbench now does not automatically add a
        <code class="filename">.sql</code> extension on Linux. However, on
        Windows, the file extension is added if one is not specified.
       (Bug #53731)</p></li><li><p>
        MySQL Workbench now indicates that changes need to be saved using
        only an asterisk in the Model Overview tab, rather than this
        being reflected on individual EER Diagrams.
       (Bug #53042)</p></li><li><p>
        The SQL Editor now includes a new <span class="guimenu">Set as Default
        Schema</span> context menu item. This is applicable to schema
        nodes in the <span class="guilabel">Object Browser</span> and the
        <span class="guilabel">Overview</span> panel of the Query Editor.
        Previously the only way to change the default schema was to
        select the schema from the schema selector list located at the
        top of the Object Browser.
       (Bug #51479)</p></li><li><p>
        MySQL Workbench now supports creating a new tab in tabbed interfaces
        by using <span><strong class="keycap">Control+T</strong></span> on Windows and
        <span><strong class="keycap">Command+T</strong></span> on Mac OS X.
       (Bug #48798)</p></li><li><p>
        MySQL Workbench now supports entering of expressions such as
        <code class="literal">DEFAULT</code> or
        <code class="literal">CURRENT_TIMESTAMP</code> into the inserts editor.
        The expression needs to be preceded by <code class="literal">\func</code>.
        See <a href="wb-sql-editor-live-editing-tabsheets.html" title="6.7.4.6. Live Editing Tabsheets">Section 6.7.4.6, “Live Editing Tabsheets”</a>.
       (Bug #36206)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        If a property value was changed in the <span class="guilabel">Workbench
        Preferences</span> dialog, and <span class="guibutton">OK</span> was
        clicked, or a new tab was clicked before the cursor was moved
        away from the value being changed, the change was silently
        reverted.
       (Bug #54060)</p></li><li><p>
        If the <span class="guilabel">Manage Server Instances</span> dialog was
        launched, and either the <span class="guibutton">New</span> or
        <span class="guibutton">Delete</span> button was clicked, and then the
        dialog was closed, MySQL Workbench crashed if the <span class="guilabel">New
        Server Instance</span> action item was then clicked on the
        Home screen.
       (Bug #54028)</p></li><li><p>
        The Gnome keyring package was a dependency of MySQL Workbench. It
        was undesirable to require its installation on KDE-based
        systems.
       (Bug #54010)</p></li><li><p>
        MySQL Workbench did not size its application window correctly on
        screen sizes with a 16/9 aspect ratio.
       (Bug #53984, Bug #11761483)</p></li><li><p>
        When MySQL Workbench was launched, an overlay was displayed. In the
        application bar, the dialog prompting for the keyring password
        was waiting for input, but it was not possible to enter the
        password because the overlay hid the dialog.
       (Bug #53974)</p></li><li><p>
        On the Model Overview page, when a new user object was created
        with Add User in the Schema privileges section, it was not
        possible to change any of the user object's attributes. For
        example, if the name of the object was changed, it would then
        change back to its original setting.
       (Bug #53946)</p></li><li><p>
        In the EER Diagram view, heavy flicker resulted if the cursor
        was hovered over relationship lines or tables.
       (Bug #53941)</p></li><li><p>
        When a table containing triggers was loaded into the
        <span class="guilabel">Alter Table</span> dialog of SQL Editor, clicking
        the <span class="guilabel">Triggers</span> tab showed an empty trigger,
        rather than the correct trigger code.
       (Bug #53940)</p></li><li><p>
        In the SQL Editor, performing a query on a remote server
        returned <code class="literal">BLOB</code> values for columns that were
        not of type <code class="literal">BLOB</code>.
      </p><p>
        Because binary byte strings tend to contain null bytes in their
        values, for safety reasons they were not displayed in the
        results grid. They could only be viewed or edited by means of
        the <code class="literal">BLOB</code> editor to avoid data truncation.
      </p><p>
        MySQL Workbench now includes a new global option that has been added
        to the <span class="guilabel">SQL Editor</span> tab of the
        <span class="guilabel">Workbench Preferences</span> dialog. The option is
        <span class="guilabel">Treat BINARY/VARBINARY as non-binary character
        string</span>. By default, it is not selected.
       (Bug #53920)</p></li><li><p>
        Attempting to copy objects from an existing diagram to a new
        diagram resulted in this error:
      </p><pre class="programlisting">OverviewBE::get_node: invalid node 1.0.0.22</pre><p>(Bug #53914)</p></li><li><p>
        In the SQL Editor, the context-sensitive menu options
        <span class="guimenu">Copy to Clipboard</span> and <span class="guimenu">Send to SQL
        Editor</span> both failed to work. This applied to both
        copying in the <span class="guilabel">Object Browser</span> and in the
        <span class="guilabel">Overview</span> tab.
       (Bug #53903)</p></li><li><p>
        In the SQL Editor, deleting a snippet from the snippet list
        using the toolbar button caused the first snippet to be deleted,
        regardless of which snippet was selected.
       (Bug #53860)</p></li><li><p>
        When forward engineering a schema to a database with the
        <span class="guilabel">DROP Objects Before Each CREATE Object</span>
        option selected, the <code class="literal">DROP</code> statement used a
        delimiter before it had been declared.
       (Bug #53853)</p></li><li><p>
        In the SQL Editor, if code was entered into the SQL Query tab,
        and then the application exited, MySQL Workbench did not prompt the
        user regarding unsaved changes, so they were lost.
       (Bug #53848)</p></li><li><p>
        In the SQL Editor, when renaming views or routines using the
        live editor, the generated <code class="literal">ALTER</code> script
        contained only <code class="literal">DROP</code> statements and not
        <code class="literal">CREATE</code> statements.
       (Bug #53847)</p></li><li><p>
        In the SQL Editor, when attempting to change an index from
        <code class="literal">INDEX</code> to <code class="literal">UNIQUE</code> using the
        <span class="guilabel">Alter Table</span> dialog, no changes were
        applied, and this error message was generated:
      </p><pre class="programlisting">No changes to object were detected</pre><p>(Bug #53787)</p></li><li><p>
        In the <span class="guilabel">Create Schema</span> dialog of the SQL
        Editor, when a new schema name was entered, and changes applied,
        the schema name appeared to revert to the default name
        <code class="literal">new_schema</code>, rather than being changed to the
        newly specified name. This only happened on Mac OS X.
       (Bug #53764)</p></li><li><p>
        In the SQL Editor, if two procedures were defined in a script,
        each proceded with a suitable <code class="literal">DROP</code> statement,
        then when the script was executed and the procedures already
        existed, a “<span class="quote">procedure already defined</span>” error
        occurred. It appeared that the second <code class="literal">DROP</code>
        statement was being ignored. This problem happened if the line
        preceding the second <code class="literal">DROP</code> statement was
        terminated with a space.
       (Bug #53760)</p></li><li><p>
        With multiple tabs open in the SQL Editor, if the script in each
        tab was saved to a file in turn, the script was actually saved
        over the previously saved script, resulting in the loss of that
        script.
       (Bug #53733)</p></li><li><p>
        If multiple SQL Query tabs were opened in the SQL Editor, when a
        snippet was saved to the snippet list, the snippet saved would
        always be from the last opened <span class="guilabel">SQL Query</span>
        tab (the furthest to the right), rather than the currently
        selected tab.
       (Bug #53713)</p></li><li><p>
        In the <span class="guilabel">Columns</span> tab of the Table Editor,
        automatic data type completion did not occur if the type was
        entered in lowercase. MySQL Workbench now completes the data type
        regardless of lettercase.
       (Bug #53710)</p></li><li><p>
        Compiling MySQL Workbench from source failed with these errors:
      </p><pre class="programlisting">
...
-I../../library/dbc/src -I../../library/vsqlite++/include  -D_FORTIFY_SOURCE=2   -O2
-fno-strict-aliasing -fwrapv -march=x86-64 -gdwarf-2 -g2  -Wextra -Wall -Wno-unused
-Wno-deprecated -ggdb3 -DENABLE_DEBUG   -MT canvas_floater.o -MD -MP -MF
.deps/canvas_floater.Tpo -c -o canvas_floater.o `test -f 'model/canvas_floater.cpp' ||
echo './'`model/canvas_floater.cpp
model/canvas_floater.cpp: In constructor 'wb::Floater::Floater(mdc::Layer*, const
std::string&amp;)':
model/canvas_floater.cpp:65:59: error: cannot call constructor 'mdc::Color::Color'
directly
model/canvas_floater.cpp:65:59: error:   for a function-style cast, remove the redundant
'::Color'
make[3]: *** [canvas_floater.o] Error 1
make[3]: Leaving directory
`/home/users/Arvenil/rpm/BUILD/mysql-workbench-oss-5.2.21/backend/wbprivate'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/home/users/Arvenil/rpm/BUILD/mysql-workbench-oss-5.2.21/backend'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/users/Arvenil/rpm/BUILD/mysql-workbench-oss-5.2.21'
make: *** [all] Error 2
</pre><p>(Bug #53687)</p></li><li><p>
        In the <span class="guilabel">Data Dump</span> tab of the Administrator,
        the <span class="guilabel">Options</span> panel was not rendered
        correctly.
       (Bug #53681)</p></li><li><p>
        In the SQL Editor, if a query was executed and then interrupted,
        MySQL Workbench hung.
       (Bug #53652)</p></li><li><p>
        If a query was entered in the SQL Query tab, and then
        <span><strong class="keycap">Command+Enter</strong></span> was immediately pressed to
        execute the query, the query failed. This only happened on Mac
        OS X.
       (Bug #53650)</p></li><li><p>
        In the <span class="guilabel">Create New Server Instance Profile</span>
        wizard, on the <span class="guilabel">Operating System</span> page the
        <span class="guilabel">MySQL Installation Type</span> list was not
        populated correctly. Although all items were initially correctly
        displayed, if the <span class="guibutton">Back</span> button was
        clicked, and then <span class="guibutton">Next</span> clicked to return
        to the page, all the items in the list were duplicated. Each
        time this process was repeated the original list items would
        again be duplicated.
       (Bug #53649)</p></li><li><p>
        On the Home screen, the MySQL Team Blog and Workbench Team Blog
        icons linked to the same page. Further, the MySQL News Letter
        icon linked to the MySQL Developer forum.
       (Bug #53628)</p></li><li><p>
        In the <span class="guilabel">SSH Shell Connection</span> panel of the
        <span class="guilabel">Manage Server Instances</span> dialog, if any port
        other than 22 was specified, it was subsequently ignored.
       (Bug #53623)</p></li><li><p>
        The MySQL configuration file was corrupted by the Administrator
        when changes were applied, if the configuration file was not
        terminated with a new line.
       (Bug #53620)</p></li><li><p>
        In the SQL Editor, the toolbar items on the
        <span class="guilabel">Snippets</span> tab to replace and insert snippets
        had no effect when clicked.
       (Bug #53610)</p></li><li><p>
        Specifying a new font for the SQL Editor's SQL Query tab
        contents had no affect on appearance.
       (Bug #53605)</p></li><li><p>
        In the <span class="guilabel">Data Dump</span> section of the
        Administrator, this error occurred when an export was generated:
      </p><pre class="programlisting">mysqldump: Error 2020: Got packet bigger than 'max_allowed_packet' bytes when dumping
table 'xxx' at row: 1</pre><p>
        This happened only for larger tables.
       (Bug #53599)</p></li><li><p>
        MySQL Workbench crashed when attempting to connect to a Linux server
        using an SSH connection.
       (Bug #53476)</p></li><li><p>
        When a model containing a stored procedure was forward
        engineered to a script, the script contained invalid SQL code.
        This happened when the <span class="guilabel">DROP Objects Before Each CREATE
        Statement</span> and <span class="guilabel">Export MySQL Routine
        Objects</span> options were selected. Problems with the SQL
        code included a delimiter being used before its definition and
        also <code class="literal">DROP</code> statements not being terminated.
       (Bug #53467)</p></li><li><p>
        MySQL Workbench crashed on selection of the
        <span class="guimenu">Model</span>, <span class="guimenu">Create Diagram from Catalog
        Objects</span> menu item.
       (Bug #53454)</p></li><li><p>
        It was not possible to edit schema properties in the schema
        editor, such as name and default collation.
       (Bug #53438)</p></li><li><p>
        When a model containing a table using a 1:n relationship was
        synchronized with a live database, the relationship then failed
        to render in the EER Diagram.
       (Bug #53252)</p></li><li><p>
        Loading a large script was loaded into the SQL Editor resulted
        in an out of memory exception. Memory exhaustion was caused by
        inefficient end of line conversion. The SQL Editor now supports
        custom end of line formats and preserves the original line
        endings used in the file. End of line conversion is no longer
        used and large files load faster and more efficiently.
       (Bug #53190)</p></li><li><p>
        In the <span class="guilabel">Manage DB Connections</span> dialog,
        selecting <span class="guilabel">Use ANSI quote to quote
        identifiers</span> had no effect with respect to subsequent
        queries using that connection.
       (Bug #53160)</p></li><li><p>
        Delimiters were erroneously added to trigger code if the
        currently selected schema was changed.
       (Bug #53151)</p></li><li><p>
        In the <span class="guilabel">Triggers</span> tab of the <span class="guilabel">Table
        Editor</span>, if a trigger was written that contained a
        <code class="literal">DROP TRIGGER</code> statement, the statement was
        automatically removed.
       (Bug #53023)</p></li><li><p>
        MySQL Workbench generated an exception when an attempt was made to
        change the configuration file in the <span class="guilabel">System
        Profile</span> tab of the <span class="guilabel">Manage Server
        Instances</span> dialog.
       (Bug #52947)</p></li><li><p>
        In the <span class="guilabel">Alter Table</span> dialog of the SQL
        Editor, entering a column comment in the
        <span class="guilabel">Comments</span> tab and applying the changes did
        not save the comment.
       (Bug #52893)</p></li><li><p>
        Setting <code class="literal">WB_NO_GNOME_KEYRING=1</code> on Kubuntu did
        not appear to disable the Gnome keyring. It was therefore
        impossible to connect without an active keyring daemon.
       (Bug #52866)</p></li><li><p>
        When scrolling in an EER Diagram, MySQL Workbench repeatedly
        displayed an error dialog containing the message “<span class="quote">OpenGL
        error: invalid value</span>”.
       (Bug #52840)</p></li><li><p>
        In the <span class="guilabel">Data Dump</span> section of the
        Administrator, when a schema was dumped to multiple files, the
        stored routines were not exported.
       (Bug #52798)</p></li><li><p>
        It was not possible to set <code class="literal">ON UPDATE
        CURRENT_TIMESTAMP</code> as the default value for a column.
       (Bug #52350)</p></li><li><p>
        If a table was dragged from the catalog tree on to the EER
        Diagram, the catalog tree collapsed.
       (Bug #51862)</p></li><li><p>
        In the <span class="guilabel">Connections</span> tab of the
        Administrator, queries containing a comment did not always
        display correctly in the <span class="guilabel">Info</span> column.
       (Bug #51848)</p></li><li><p>
        Output did not scale correctly for print sizes other than A4.
       (Bug #51515)</p></li><li><p>
        When synchronizing to a live database, triggers showed as
        requiring updating, even when the model and live database were
        identical.
       (Bug #51409)</p></li><li><p>
        If an SQL file saved in Windows file format was loaded into the
        SQL Editor, it was displayed with additional line breaks, and
        the SQL code was not interpreted correctly. Further, if code
        written in the SQL editor was saved to a file and then opened in
        an editor on Windows, it contained additional line breaks.
       (Bug #51308)</p></li><li><p>
        In the <span class="guilabel">Connections</span> tab of the Administrator
        facility, host names that contained a <code class="literal">'-'</code>
        character were sometimes not displayed correctly.
       (Bug #51119)</p></li><li><p>
        In the SQL Editor, if the <span class="guilabel">Add Table</span>
        facility was used to create a new table with the same name as an
        existing table, then after changes were applied, the content of
        both tables was the same as the existing table, and changes
        unique to the second table were lost.
       (Bug #51107)</p></li><li><p>
        Attempts to forward engineer a project that contained a view
        failed with this error:
      </p><pre class="programlisting">ERROR: Error 1046: No database selected</pre><p>(Bug #51091)</p></li><li><p>
        Inserts added to a model and saved on Windows were not visible
        when that model was loaded on Mac OS X.
       (Bug #51029)</p></li><li><p>
        In the SQL Editor, carrying out a <code class="literal">SELECT</code> on a
        table containing more than 1000 columns resulted in the error
        <span class="errortext">Too many SQL variables</span>.
       (Bug #50952)</p></li><li><p>
        In the Model Overview page, when small icons view was selected,
        if table names were truncated, there were no tooltips to enable
        visibility of the full names. The tooltips, however, were
        present for the large icons view, and the details view.
       (Bug #50739)</p></li><li><p>
        MySQL Workbench reported a server as not running, even if it was.
        The MySQL Server concerned was running on 64-bit Windows 7.
       (Bug #50585)</p></li><li><p>
        In the EER Diagram view, it was not possible to paste a copied
        layer. The paste menu item was disabled in the context-sensitive
        menu and main menu, and pressing <span><strong class="keycap">Control+V</strong></span> had
        no effect.
       (Bug #50253)</p></li><li><p>
        In the EER Diagram view, when the diagram was displayed over
        multiple pages, the gray line dividing pages in the Navigator
        was not visible in the diagram itself.
       (Bug #50243)</p></li><li><p>
        In the EER Diagram view, when zoomed out, a layer could be
        placed beyond the diagram's perimeter at the bottom right.
        Further, if a layer was placed beyond the perimeter at the top
        left, it snapped back within confines of the diagram correctly,
        but the navigator view was not updated accordingly.
       (Bug #50242)</p></li><li><p>
        Zooming out from a diagram in EER Diagram view resulted in
        severe flicker.
       (Bug #50240)</p></li><li><p>
        If a Workbench model file was double-clicked, MySQL Workbench
        crashed on launch. However, if MySQL Workbench was started using its
        application icon, and then the same model file was loaded from
        within MySQL Workbench, no problems were encountered.
       (Bug #49941)</p></li><li><p>
        When using <span class="guilabel">Create EER Model from SQL Script</span>
        from the Home screen, the specified engine type was not present
        in the resulting EER model.
       (Bug #49568)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-scripting-menu.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.5.1.8. The Scripting Menu</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-data-modeling-menus.html" title="7.5.1. Modeling Menus"><link rel="prev" href="wb-plugins-menu.html" title="7.5.1.7. The Plugins Menu"><link rel="next" href="wb-community-menu.html" title="7.5.1.9. The Community Menu"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-scripting-menu"></a>7.5.1.8. The Scripting Menu</h4></div></div></div><p>
      The <span class="guimenu">Scripting</span> menu has these items:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          <span class="guimenuitem">Scripting Shell</span>: Launches the
          MySQL Workbench Scripting Shell
        </p></li><li><p>
          <span class="guimenuitem">Run Workbench Script</span>: Executes the
          specified script
        </p></li><li><p>
          <span class="guimenuitem">Install Plugin/Module File</span>: Loads
          and installs a plugin or module file
        </p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-note-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.6.2. The Note 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-notes.html" title="7.7.6. Creating Notes"><link rel="prev" href="wb-notes-physical-schemata.html" title="7.7.6.1. Adding Notes"><link rel="next" href="wb-text-objects.html" title="7.7.7. Creating Text Objects"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="wb-note-editor"></a>7.7.6.2. The Note Editor</h4></div></div></div><p>
      To invoke the note editor, double-click a note object in the
      <code class="literal">Model Note</code> section on the <code class="literal">MySQL
      Model</code> page. This opens the note editor docked at the
      bottom of the application. Double-clicking the note tab undocks
      the editor. Double-click the title bar to redock it. Any number of
      notes may be open at the same time. Each additional note appears
      as a tab at the top of the note editor.
    </p><p>
      Use the editor to change the name of a note or its contents.
    </p></div></body></html>


path: /wb-html-guitools/wb-getting-started-tutorial-creating-a-model.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>4.2. Creating a Model</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-getting-started-tutorial.html" title="Chapter 4. Getting Started Tutorial"><link rel="prev" href="wb-getting-started-tutorial-admin.html" title="4.1. Administering a MySQL Server"><link rel="next" href="wb-getting-started-tutorial-adding-data.html" title="4.3. Adding Data to Your Database"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="wb-getting-started-tutorial-creating-a-model"></a>4.2. Creating a Model</h2></div></div></div><p>
      In this section, you will learn how to create a new database
      model, create a table, create an EER Diagram of your model, and
      then forward engineer your model to the live database server.
    </p><div class="orderedlist"><ol type="1"><li><p>
          Start MySQL Workbench. On the Home window, select <span class="guilabel">Create
          new EER Model</span>. A model can contain multiple
          schemata. Note that when you create a new model, it contains
          the <code class="literal">mydb</code> schema by default. You can change
          the name of this schema to serve your own purposes, or delete
          it.
        </p><div class="figure"><a name="wb-getting-started-tutorial-home-screen"></a><p class="title"><b>Figure 4.13. Getting Started Tutorial - Home Window</b></p><div class="mediaobject"><img src="images/wb-getting-started-tutorial-home-screen.png" width="1024" height="719" alt="Getting Started Tutorial - Home
              Window"></div></div></li><li><p>
          On the Physical Schemata toolbar, click the button
          <span class="guibutton">+</span> to add a new schema. This will create
          a new schema and display a tabsheet for the schema. In the
          tabsheet, change the name of the schema to
          “<span class="quote">dvd_collection</span>”, by typing into the field called
          <span class="guilabel">Name</span>. Ensure that this change is
          reflected on the Physical Schemata tab. Now you are ready to
          add a table to your schema. If at this stage you receive a
          message dialog asking to rename all schema occurrences, you
          can click <span class="guibutton">Yes</span> to apply your name
          change.
        </p><div class="figure"><a name="wb-getting-started-tutorial-new-schema"></a><p class="title"><b>Figure 4.14. Getting Started Tutorial - New Schema</b></p><div class="mediaobject"><img src="images/wb-getting-started-tutorial-new-schema.png" width="1024" height="719" alt="Getting Started Tutorial - New
              Schema"></div></div></li><li><p>
          In the Physical Schemata section, double-click <span class="guilabel">Add
          Table</span>.
        </p></li><li><p>
          Double-click <span class="guilabel">table1</span> to launch the table
          editor (you may not have to do this as the table editor will
          automatically load at this point if you are using later
          versions of MySQL Workbench). In the table editor, change the name
          of the table to “<span class="quote">movies</span>” and press
          <span><strong class="keycap">Enter</strong></span>.The table editor will then switch from
          the <span class="guilabel">Table</span> tab to the
          <span class="guilabel">Columns</span> tab, to permit you to enter
          details of your table columns.
        </p></li><li><p>
          Change the name of the first column to
          “<span class="quote">movie_id</span>”. Select a data type of
          <code class="literal">INT</code>. You will then make this column have
          the following properties: primary key, not null,
          autoincrement. Click the <span class="guilabel">PK</span>,
          <span class="guilabel">NN</span>, and <span class="guilabel">AI</span> check
          boxes.
        </p></li><li><p>
          Add two further columns:
        </p><div class="informaltable"><table border="1"><colgroup><col><col><col></colgroup><thead><tr><th>Column Name</th><th>Data Type</th><th>Column Properties</th></tr></thead><tbody><tr><td>movie_title</td><td>VARCHAR(45)</td><td>NN</td></tr><tr><td>release_date</td><td>DATE (YYYY-MM-DD)</td><td>None</td></tr></tbody></table></div><div class="figure"><a name="wb-getting-started-tutorial-columns"></a><p class="title"><b>Figure 4.15. Getting Started Tutorial - Columns</b></p><div class="mediaobject"><img src="images/wb-getting-started-tutorial-columns.png" width="1024" height="719" alt="Getting Started Tutorial -
              Columns"></div></div></li><li><p>
          Now you can obtain a visual representation of this schema so
          far. From the main menu, select <span class="guimenu">Model</span>,
          <span class="guimenuitem">Create Diagram from Catalog
          Objects</span>. The EER Diagram will be created and
          displayed.
        </p><div class="figure"><a name="wb-getting-started-tutorial-eer-diagram"></a><p class="title"><b>Figure 4.16. Getting Started Tutorial - EER Diagram</b></p><div class="mediaobject"><img src="images/wb-getting-started-tutorial-eer-diagram.png" width="1024" height="719" alt="Getting Started Tutorial - EER
              Diagram"></div></div></li><li><p>
          In the table editor, change the name of the column
          “<span class="quote">movie_title</span>” to “<span class="quote">title</span>”. Note that
          the EER Diagram is automatically updated to reflect this
          change.
        </p></li><li><p>
          At this point, you can save your model. Click the main toolbar
          button <span class="guibutton">Save Model to Current File</span>. You
          have not yet saved this file so you will be prompted to enter
          a model file name. For this tutorial, enter
          “<span class="quote">Home_Media</span>”. The Home_Media model may contain
          further schemata in addition to
          <code class="literal">dvd_collection</code>, such as
          <code class="literal">cd_collection</code>. Click
          <span class="guibutton">Save</span> to save the model.
        </p></li><li><p>
          You can synchronize your model with the live database server.
          First, you must tell MySQL Workbench how to connect to the live
          server. From the main menu, select
          <span class="guimenu">Database</span>, <span class="guimenuitem">Manage
          Connections...</span>.
        </p></li><li><p>
          In the <span class="guilabel">Manage DB Connections</span> dialog,
          click <span class="guibutton">New</span>.
        </p></li><li><p>
          Enter “<span class="quote">Big Iron Server</span>” for the connection name.
          This enables you to identify the server to which this
          connection corresponds, although it is possible to create
          multiple connections to the same server.
        </p></li><li><p>
          Enter the user name for the account you will use to connect to
          the server.
        </p></li><li><p>
          Click on the <span class="guibutton">Store in Vault...</span> button
          and enter the password for the user name you entered in the
          previous step. You can optionally ignore this step, and you
          will be prompted for this password whenever MySQL Workbench
          connects to the server.
        </p></li><li><p>
          Click <span class="guibutton">Test Connection</span> to test your
          connection parameters. If everything is okay at this point,
          you can click <span class="guibutton">Close</span>.
        </p><div class="figure"><a name="wb-getting-started-tutorial-manage-connections"></a><p class="title"><b>Figure 4.17. Getting Started Tutorial - Manage Connections</b></p><div class="mediaobject"><img src="images/wb-getting-started-tutorial-manage-connections.png" width="898" height="498" alt="Getting Started Tutorial - Manage
              Connections"></div></div></li><li><p>
          You are now ready to forward engineer your model to the live
          server. From the main menu, select
          <span class="guimenu">Database</span>, <span class="guimenuitem">Forward
          Engineer...</span>. The <span class="guilabel">Forward Engineer to
          Database</span> wizard will be displayed.
        </p></li><li><p>
          The first page of the wizard is the Catalog Validation page.
          Click the <span class="guibutton">Run Validations</span> button to
          validate the Catalog. If everything is in order, the wizard
          will report that validaton finished successfully. Click
          <span class="guilabel">Next</span> to continue.
        </p></li><li><p>
          The Options page of the wizard shows various advanced options.
          For this tutorial, you can ignore these and simply click
          <span class="guilabel">Next</span>.
        </p></li><li><p>
          On the next page, you can select the object you want to export
          to the live server. In this case, you only have a table, so no
          other objects need be selected. Click
          <span class="guibutton">Next</span>.
        </p></li><li><p>
          The next page, Review SQL Script, displays the script that
          will be run on the live server to create your schema. Review
          the script to make sure that you understand the operations
          that will be carried out. Click <span class="guibutton">Next</span>.
        </p><div class="figure"><a name="wb-getting-started-tutorial-review-script"></a><p class="title"><b>Figure 4.18. Getting Started Tutorial - Review Script</b></p><div class="mediaobject"><img src="images/wb-getting-started-tutorial-review-script.png" width="798" height="598" alt="Getting Started Tutorial - Review
              Script"></div></div></li><li><p>
          Select the connection you created earlier, “<span class="quote">Big Iron
          Server</span>”. Click <span class="guibutton">Execute</span>. Check
          the messages for any errors, then click
          <span class="guibutton">Close</span> to exit the wizard.
        </p></li><li><p>
          Ensure that the script ran without error on the server, then
          click <span class="guibutton">Close</span>. As a simple test that the
          script worked launch the MySQL Command Line Client
          (<span><strong class="command">mysql</strong></span>). Enter <code class="literal">SHOW
          DATABASES;</code> and identify your schema. Enter
          <code class="literal">USE dvd_collection;</code> to select your schema.
          Now enter <code class="literal">SHOW TABLES;</code>. Enter
          <code class="literal">SELECT * FROM movies;</code>, this will return the
          empty set as you have not yet entered any data into your
          database. Note that it is possible to use MySQL Workbench to carry
          out such checks, and you will see how to do this later, but
          the MySQL Command Line Client has been used here as you have
          probably used it previously.
        </p></li><li><p>
          Ensure that your model is saved. Click <span class="guilabel">Save Model to
          Current File</span> on the main toolbar.
        </p></li></ol></div></div></body></html>


path: /wb-html-guitools/wb-news-5-2-29.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.11. Changes in MySQL Workbench 5.2.29 (12 October 2010)</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="changes-5.2.x.html" title="A.1. Changes in Release 5.2"><link rel="prev" href="wb-news-5-2-30.html" title="A.1.10. Changes in MySQL Workbench 5.2.30 (20 November 2010)"><link rel="next" href="wb-news-5-2-28.html" title="A.1.12. Changes in MySQL Workbench 5.2.28 (19 September 2010)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-news-5-2-29"></a>A.1.11. Changes in MySQL Workbench 5.2.29 (12 October 2010)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.2.28.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        An open model that has not been saved is now automatically saved
        after a user-settable 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. Note
        that for automatic recovery to be available for a new file, it
        will have to have been saved by the user at least once.
       (Bug #56718)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p><span class="bold"><strong>Security Fix</strong></span>: Bug #57080 was fixed.</p></li><li><p>
        Clicking the <span class="guilabel">Inserts</span> tab of the Table
        Editor resulted in the <span class="guilabel">MySQL Workbench Unexpected
        Error</span> dialog being displayed.
       (Bug #57346)</p></li><li><p>
        If an EER diagram was created and then closed, attempting to
        reopen it caused MySQL Workbench to display an unexpected error
        dialog.
       (Bug #57259)</p></li><li><p>
        In the Model View, MySQL Workbench crashed when the
        <span class="guilabel">Output</span> tab was reopened after previously
        being closed.
       (Bug #57150)</p></li><li><p>
        Attempting to open the Table Editor in the SQL Editor multiple
        times for a table that contained no primary key caused
        MySQL Workbench to crash.
       (Bug #57139)</p></li><li><p>
        Changes made to a server instance were not saved. In particular,
        changing installation type to “<span class="quote">Custom</span>” was not
        saved, and changes to the <span><strong class="command">sudo</strong></span> command were
        also not saved.
       (Bug #57026)</p></li><li><p>
        When attempting to open an EER Diagram by double-clicking it in
        the Model Overview, MySQL Workbench generated this unexpected error:
      </p><pre class="programlisting">Cannot access a disposed object.
Object Name: ModelDiagramForm.</pre><p>(Bug #56963)</p></li><li><p>
        When synchronizing a model to a live database, if a database was
        deselected in the wizard, a <code class="literal">DROP</code> statement
        for that database was generated in the SQL code to prevent it
        from being part of the synchronization process. This caused that
        database to be dropped from the live database, with
        corresponding loss of all data.
       (Bug #56938)</p></li><li><p>
        In the <span class="guilabel">Alter Table</span> dialog of the SQL
        Editor, attempting to create a new index in the
        <span class="guilabel">Index</span> tab was not actioned when the
        <span class="guibutton">Apply</span> button was clicked. The dialog
        reported that “<span class="quote">no changes to object were detected</span>”.
       (Bug #56906)</p></li><li><p>
        It was only possible to connect to a MySQL server for
        administration using an SSH connection.
       (Bug #56874)</p></li><li><p>
        Scripts could successfully be executed on the MySQL Server
        failed to execute in the MySQL Workbench SQL Editor.
       (Bug #56833)</p></li><li><p>
        If a table containing a User Defined Type based on
        <code class="literal">VARCHAR</code> was forward engineered, the resulting
        SQL did not correctly quote the <code class="literal">VARCHAR</code>
        value, resulting in a server error. For example, this code was
        generated:
      </p><pre class="programlisting">CREATE  TABLE IF NOT EXISTS `x`.`tabley` (`customstring` VARCHAR(10));
INSERT INTO `x`.`tabley` (`id_customstring`) VALUES (example);</pre><p>
        The correct <code class="literal">INSERT</code> statement should be:
      </p><pre class="programlisting">INSERT INTO `x`.`tabley` (`id_customstring`) VALUES ('example');</pre><p>(Bug #56710)</p></li><li><p>
        In the Administrator, clicking the <span class="guilabel">Data
        Dump</span> tab generated the error <code class="literal">Error updating
        DB: float division</code> and schemata were not displayed.
       (Bug #56658)</p></li><li><p>
        In the SQL Editor, if some table data was edited, and then the
        connection to the server was lost, clicking the <span class="guibutton">Apply
        changes to data</span> toolbar button caused MySQL Workbench to
        crash.
      </p><p>
        Now MySQL Workbench shows an error message in the
        <span class="guilabel">Output</span> tab when a connection is lost. Once
        the connection is back up, clicking <span class="guibutton">Apply changes to
        data</span> re-establishes the connection and sends the
        changes to the server.
       (Bug #56170)</p></li><li><p>
        Screen areas in the Administrator did not redraw correctly. It
        was necessary to move the main window to force a redraw.
       (Bug #55490)</p></li><li><p>
        Folding of iteration statement blocks, such as
        <code class="literal">WHILE</code>, <code class="literal">REPEAT</code>, and
        <code class="literal">LOOP</code>, did not work correctly in the SQL
        Editor. The loop end constructs such as <code class="literal">END
        WHILE</code>, <code class="literal">END REPEAT</code>, and <code class="literal">END
        LOOP</code> were not recognized as expected.
       (Bug #55358)</p></li><li><p>
        If a foreign key was set to <code class="literal">RESTRICT</code> for On
        Delete and On Update on the <span class="guilabel">Foreign Keys</span>
        tab of the Table Editor, MySQL Workbench generated SQL code to drop
        and add this key on every subsequent synchronization attempt.
       (Bug #55155)</p></li></ul></div></div></body></html>


path: /wb-html-guitools/wb-preferences-diagram.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>5.4.6. The Diagram 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-mysql.html" title="5.4.5. The MySQL Tab"><link rel="next" href="wb-preferences-appearance.html" title="5.4.7. The Appearance 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-diagram"></a>5.4.6. The Diagram Tab</h3></div></div></div><p>
      Use this tab to determine display settings for an EER diagram.
    </p><p>
      Select whether to expand new objects by checking the
      <span class="guilabel">Expand New Objects</span> check box and select
      whether to draw line crossings by checking the <span class="guilabel">Draw Line
      Crossings</span> check box.
    </p><p>
      This tab also enables you to set the maximum number of characters
      for the following items:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          Column Names
        </p></li><li><p>
          Column Types
        </p></li><li><p>
          Routine Names
        </p></li></ul></div><p>
      Changes to these values change the display properties only, not
      the objects themselves.
    </p></div></body></html>


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

VSQLite++ - virtuosic bytes SQLite3 C++ wrapper

Copyright (c) 2006 Vinzenz Feenstra vinzenz.feenstra@virtuosic-bytes.com
All rights reserved.

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

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

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

 * Neither the name of virtuosic bytes 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-text-objects.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. Creating Text Objects</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-working-with-models.html" title="7.7. Working with Models"><link rel="prev" href="wb-note-editor.html" title="7.7.6.2. The Note Editor"><link rel="next" href="wb-using-text-object-tool.html" title="7.7.7.1. Adding Text Objects 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-text-objects"></a>7.7.7. Creating Text Objects</h3></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-using-text-object-tool.html">7.7.7.1. Adding Text Objects to an EER Diagram</a></span></dt><dt><span class="section"><a href="wb-text-object-editor.html">7.7.7.2. The Text Object Editor</a></span></dt></dl></div><p>
    Text objects are applicable only to an EER diagram. They can be used
    for documentation purposes; for example, to explain a grouping of
    schema objects. They are also useful for creating titles for an EER
    diagram should you decide to export a diagram as a PDF or PNG file.
  </p></div></body></html>


path: /wb-html-guitools/wb-model-overview-privileges.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>7.5.5. The Schema Privileges Panel</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="wb-model-editor.html" title="7.5. Model Editor"><link rel="prev" href="wb-overview-schema-objects.html" title="7.5.4.1. The Schema Objects Panel"><link rel="next" href="wb-adding-roles.html" title="7.5.5.1. Adding Roles"></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-model-overview-privileges"></a>7.5.5. The Schema Privileges Panel</h3></div></div></div><div class="toc"><dl><dt><span class="section"><a href="wb-adding-roles.html">7.5.5.1. Adding Roles</a></span></dt><dt><span class="section"><a href="wb-adding-users.html">7.5.5.2. Adding Users</a></span></dt></dl></div><p>
      The <code class="literal">Schema Privileges</code> panel has the following
      sections, used to create users for your schemata and to define
      roles —:
    </p><div class="itemizedlist"><ul type="disc"><li><p>
          Users
        </p></li><li><p>
          Roles
        </p></li></ul></div><p>
      The following image displays the <code class="literal">Schema
      Privileges</code> section of the <code class="literal">MySQL Model</code>
      tab.
    </p><div class="figure"><a name="wb-schema-privileges-image"></a><p class="title"><b>Figure 7.3. Roles and Privileges</b></p><div class="mediaobject"><img src="images/wb-schema-privileges.png" width="306" height="151" alt="Roles and
          privileges"></div></div></div></body></html>


path: /wb-html-guitools/wb-news-5-2-28.html
content_type: text/html
content:
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>A.1.12. Changes in MySQL Workbench 5.2.28 (19 September 2010)</title><link rel="stylesheet" type="text/css" href="/webui/stylesheets/docs.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1"><link rel="start" href="index.html" title="MySQL Workbench"><link rel="up" href="changes-5.2.x.html" title="A.1. Changes in Release 5.2"><link rel="prev" href="wb-news-5-2-29.html" title="A.1.11. Changes in MySQL Workbench 5.2.29 (12 October 2010)"><link rel="next" href="wb-news-5-2-27.html" title="A.1.13. Changes in MySQL Workbench 5.2.27 (01 September 2010)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="wb-news-5-2-28"></a>A.1.12. Changes in MySQL Workbench 5.2.28 (19 September 2010)</h3></div></div></div><p>
        This section documents all changes and bug fixes applied since
        the release of 5.2.27.
      </p><p><span class="bold"><strong>Functionality Added or Changed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        Added the ability to copy column names from result sets to the
        clipboard.
       (Bug #53000, Bug #11760578)</p></li><li><p>
        The SQL Editor now displays the number of rows matched after a
        query.
       (Bug #48772)</p></li><li><p>
        The following command line options have been added to
        MySQL Workbench:
      </p><div class="itemizedlist"><ul type="circle"><li><p>
            <code class="option">--admin
            <em class="replaceable"><code>instance</code></em></code>: Launch
            MySQL Workbench and load the specified server instance
          </p></li><li><p>
            <code class="option">--query
            <em class="replaceable"><code>connection</code></em></code>: Launch
            MySQL Workbench and load the specified connection
          </p></li><li><p>
            <code class="option">--model
            <em class="replaceable"><code>modelfile</code></em></code>: Launch
            MySQL Workbench and load the specified model
          </p></li><li><p>
            <code class="option">--script <em class="replaceable"><code>script</code></em></code>:
            Launch MySQL Workbench and run the specified script
          </p></li><li><p>
            <code class="option">--run <em class="replaceable"><code>code</code></em></code>:
            Launch MySQL Workbench and run the specified code snippet
          </p></li><li><p>
            <code class="option">--quit-when-done</code>: Quit MySQL Workbench after
            <code class="option">--script</code> or <code class="option">--run</code> finishes
          </p></li></ul></div><p>(Bug #46340)</p></li></ul></div><p><span class="bold"><strong>Bugs Fixed</strong></span></p><div class="itemizedlist"><ul type="disc"><li><p>
        Importing an exported file from a network share resulted in this
        error due to incorrect escaping of the path:
      </p><pre class="programlisting">
08:44:00 Restoring \\server\d$\file.sql

Running: mysql.exe --defaults-extra-file="c:\...\tmp3oc8ig"   --host=localhost
--user=root --port=3306 --default-character-set=utf8 --comments &lt;
"\\\\server\\d\$\\file.sql"

The specified path is invalid.
</pre><p>(Bug #56735)</p></li><li><p>
        In the SQL Editor, a crash occurred if <span class="guimenu">User
        Snippets</span> was selected after another snippet collection
        had been selected, and then the <span class="guibutton">Replace active SQL
        Editor contents with selected snippet</span> button was
        clicked.
       (Bug #56626)</p></li><li><p>
        Running a <code class="literal">TRUNCATE</code> statement in the SQL
        editor with safe updates enabled resulted in this error:
      </p><pre class="programlisting">Error Code: 1175
You are using safe update mode and you tried to update a table without a WHERE that uses
a KEY column</pre><p>(Bug #56597)</p></li><li><p>
        In the <span class="guilabel">Accounts</span> tab of the Administrator,
        an <span class="guilabel">Unexpected Error</span> occurred if a foreign
        character was used in the <span class="guilabel">Login Name</span> field
        of the <span class="guilabel">Server Access Management</span> tab. The
        same bug also affected the <span class="guilabel">Schema
        Privileges</span> tab.
       (Bug #56534)</p></li><li><p>
        The <span class="guilabel">Table</span> tab of the Table Editor contained
        a typo in the description for the <span class="guilabel">Name</span>
        field. Replaced was spelled as “<span class="quote">raplaced</span>”.
       (Bug #56518)</p></li><li><p>
        Attempts to define a foreign key for a table with a composite
        primary key caused MySQL Workbench to crash. This happened while
        trying to select the fields of the composite primary key to be
        associated with the referenced columns.
       (Bug #56496)</p></li><li><p>
        If a foreign key was about to be renamed, and the corresponding
        text field had focus, MySQL Workbench crashed if the model was then
        closed.
       (Bug #56315)</p></li><li><p>
        In the SQL Editor, a statement containing <code class="literal">CREATE
        DATABASE</code> resulted in an unexpected error.
       (Bug #56295)</p></li><li><p>
        The <code class="literal">mydb</code> database was created by default when
        reverse engineering from an existing database or script.
       (Bug #56183)</p></li><li><p>
        If an SQL script containing international characters was saved
        in the SQL Editor and then restored, the last character in the
        restored file was missing.
       (Bug #56083)</p></li><li><p>
        In MySQL Workbench list controls, when an item was selected and
        another item right-clicked, the context-sensitive menu displayed
        options related to the first list item selected, rather than the
        current list item being right-clicked, and any action selected
        was carried out on the first item.
       (Bug #56077)</p></li><li><p>
        The Workbench Scripting Shell dialog could be increased in size, but not
        subsequently reduced in size.
       (Bug #56049)</p></li><li><p>
        There were two problems in the <span class="guilabel">new_table</span>
        dialog of the SQL Editor:
      </p><div class="itemizedlist"><ul type="circle"><li><p>
            When <span class="guibutton">Apply</span> was clicked, in the
            <span class="guilabel">Apply SQL Script to Database</span> dialog, if
            <span class="guibutton">Apply SQL</span> was clicked, the SQL would
            be applied without error. However, if the
            <span class="guibutton">Back</span> button was clicked and the
            <span class="guibutton">Apply SQL</span> button clicked again, an
            error would be generated. If this process was repeated, each
            time a slightly different error would be added to the list
            of errors displayed.
          </p></li><li><p>
            The <span class="guibutton">Cancel</span> and
            <span class="guibutton">Finish</span> buttons appeared to have the
            same functionality, and simply returned the user to the
            <span class="guilabel">new_table</span> dialog.
          </p></li></ul></div><p>(Bug #56000)</p></li><li><p>
        If a model contained two schemata, and an attempt was made to
        forward engineer only one of the schemata by use of the object
        filters, data loss could result. This happened because a
        <code class="literal">DROP</code> statement was generated for both
        schemata in the model, rather than just the one being forward
        engineered.
       (Bug #55918)</p></li><li><p>
        When OpenGL rendering was selected, the EER Diagram area was not
        redrawn due to faulty OpenGL drivers. The workaround was to
        launch MySQL Workbench using the <code class="option">-swrendering</code>
        command line option. Now MySQL Workbench includes an option to
        select software rendering in the <span class="guilabel">Workbench
        Preferences</span> dialog.
       (Bug #55863)</p></li><li><p>
        In the View Editor, if the name of a view was changed in the
        code editor to the name of a pre-existing view of that name, the
        contents of the pre-existing view were replaced by the contents
        of the new view, even though the new view was created with a
        different name.
       (Bug #55661)</p></li><li><p>
        MySQL Workbench application failed to start on Mac OS X.
       (Bug #55412)</p></li><li><p>
        MySQL Workbench exhibited a variety of crashes if, in the Model
        View, EER diagrams were repeatedly created and deleted.
        MySQL Workbench also crashed if all objects in the diagram were
        copied and pasted to the same diagram several times, and then
        the diagram was deleted. Unexpected errors generated included:
      </p><div class="itemizedlist"><ul type="circle"><li><p>
            Object is currently in use elsewhere
          </p></li><li><p>
            Index is outside the bounds of the array
          </p></li><li><p>
            Index must be within the bounds of the List
          </p></li></ul></div><p>(Bug #55304)</p></li><li><p>
        A plugin that used Mforms generated this error at MySQL Workbench
        startup:
      </p><pre class="programlisting">..... line 16, in &lt;module&gt;
import mforms
ImportError: No module named mforms</pre><p>(Bug #55243)</p></li><li><p>
        If the MySQL server configuration file was modified using the
        Administrator to deactivate <code class="literal">InnoDB</code>, the MySQL
        server failed to restart, and generated this error in the log:
      </p><pre class="programlisting">[ERROR] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: Error while
setting value 'FALSE' to 'innodb'</pre><p>(Bug #55029)</p></li><li><p>
        It was no longer possible to rename a schema by double-clicking
        the schema tab in the Physical Schemata section of the Model
        View.
       (Bug #55010)</p></li><li><p>
        If a view was created with correct syntax for an existing
        schema, and then <span class="guimenu">Model</span> menu,
        <span class="guilabel">Validate (SQL)</span> was selected, and either
        <span class="guilabel">Validate All</span> or <span class="guilabel">Check
        Syntax</span> was selected, this error message was generated
        in the <span class="guilabel">Output</span> window:
      </p><pre class="programlisting">Syntax error in view '<em class="replaceable"><code>view_name</code></em>'. View code is 'CREATE VIEW ...'
</pre><p>(Bug #54969)</p></li><li><p>
        On Microsoft Windows, MySQL Workbench crashed if the Trebuchet MS
        font was missing or corrupted. Now MySQL Workbench falls back to a
        secondary font if the Trebuchet MS font is missing or corrupted.
       (Bug #54953)</p></li><li><p>
        If all objects were selected in the model view, and then the
        <span class="guilabel">Edit Selected</span> menu item was selected,
        MySQL Workbench generated an unexpected error.
       (Bug #54695)</p></li><li><p>
        Added MySQL Server 5.5 support.
       (Bug #51365, Bug #11759082)</p></li><li><p>
        On Microsoft Windows, when saving a MySQL configuration file
        from within the Administrator, Windows displayed the UAC dialog
        twice. MySQL Workbench has been changed so that Windows now only
        displays the UAC dialog once.
       (Bug #49674)</p></li></ul></div></div></body></html>


