# page_content_content

c1title: Creating Other Schema Objects
c2content:
 7.8.2.2. Creating Other Schema Objects 7.8.2.2. Creating Other Schema Objects Additional objects such as views or routines can be added in the same way as tables. Any objects you have created can be found in the Catalog palette on the right. To view these schema objects, select the Catalog tab in the middle palette on the right. View all the objects by clicking the + button to the left of the schema name. Save your changes to a MySQL Workbench Models file ( mwb extension) by choosing Save from the File menu or by using the keyboard command Control+S . 


c1title: The Model Navigator Panel
c2content:
 7.5.9. The Model Navigator Panel 7.5.9. The Model Navigator Panel Docked at the top left of the application is the Model Navigator , or Bird's Eye panel. This panel provides an overview of the objects placed on an EER diagram canvas and for this reason it is most useful when an EER diagram is active. Any objects that you have placed on the canvas should be visible in the navigator. The Model Navigator shows the total area of an EER diagram. A black rectangular outline indicates the view port onto the visible area of the canvas. To change the view port of an EER diagram, left-click this black outline and drag it to the desired location. You can zoom in on selected areas of an EER diagram by using the slider tool at the bottom of this window. The dimensions of the view port change as you zoom in and out. If the slider tool has the focus, you can also zoom using the arrow keys. The default size of the Model Navigator is two pages. To change this, use the Model menu, Diagram Size menu item. Figure 7.5. The Model Navigator Palette 


c1title: GRT and Workbench Data Organization
c2content:
 9.1. GRT and Workbench Data Organization 9.1. GRT and Workbench Data Organization The GRT, or Generic RunTime, is the internal system used by Workbench to hold model document data. It is also the mechanism by which Workbench can interact with Modules and Plugins. Workbench model data, such as diagrams, schemata, and tables, is stored in a hierarchy of objects that can be accessed by any plugin. The information is represented using standard data types: integers, doubles, strings, dicts, lists, and objects. The GRT can be accessed using external scripting languages such as Lua and Python. Awareness is required of how the GRT data types map into the scripting language. In Python, for example, the GRT integer, double, and string data types are seen as corresponding Python data types. Lists and dicts are kept in their internal representation, but can generally be treated as Python lists and dicts, and accessed in the usual way. Objects contain data fields and methods, but the GRT recognizes only objects from a pre-registered class hierarchy. It is possible to fully examine the classes contained within the GRT using the Workbench Scripting Shell. Dots in class names are changed to underscores in their Python counterparts. For example, db.mysql.Table becomes db_mysql_Table in Python. The Application Objects Tree (GRT Tree) As mentioned previously, Workbench document data is stored in an object hierarchy. This hierarchy is known as the GRT Tree. The GRT Tree can be accessed and modified from supported external scripting languages such as Python. Care should be taken when modifiying the GRT Tree, to prevent a mistake from leading to corruption of the document. Backups should be made before manipulating the tree. Read-only access to the tree is the safest approach, and is sufficient in most cases. The main nodes in the Application Object Tree Node Description wb.registry Application data such as plugin registry, list of editors, and options. wb.customData A generic dictionary for data you can use to store your own data. This dictionary is saved and reloaded with Workbench and is global (not document specific). wb.options Contains some default options that are used by Workbench. wb.rdbmsMgmt Internal registry of supported RDBMS modules, known data types. wb.doc The currently loaded model document. wb.doc.physicalModels[0] The currently loaded model object, containing the database catalog and diagrams. wb.doc.physicalModels[0].catalog The database catalog for the model. Contains the list of schemata. wb.doc.physicalModels[0]catalog.schemata List of schemata in the model. Individual schema can be accessed as a list: schemata[0], schemata[1] ... wb.doc.physicalModels[0].catalog.schemata[0].tables (.views, .routines, ...) Lists of tables, views, routines in the schema. wb.doc.physicalModels[0].diagrams List of EER diagrams in the model. wb.doc.physicalModels[0].diagrams[0].figures (.layers, .connections, ...) List of figures, layers, connections (relationships) in the diagram. 


c1title: Chapter 5. The Home Window
c2content:
 Chapter 5. The Home Window Chapter 5. The Home Window Table of Contents 5.1. Workbench Central 5.2. Workspace 5.3. Workbench Application Minimum Window Size 5.4. Workbench Preferences 5.4.1. The General Tab 5.4.2. The Administrator Tab 5.4.3. The SQL Editor Tab 5.4.4. The Model Tab 5.4.5. The MySQL Tab 5.4.6. The Diagram Tab 5.4.7. The Appearance Tab When MySQL Workbench first starts, it presents the Home window, which has two main sections: Workbench Central Workspace Note MySQL Workbench 5.2 introduced the Home window. MySQL Workbench 5.1 displays the MySQL Model workspace rather than the Home window. Note that 5.1 does not support the SQL Editor and Server Administration functionality of 5.2. The two sections can be seen in the following screenshot. For more information, see the following sections. Figure 5.1. The Home Window 


c1title: Adding Layers to an EER Diagram
c2content:
 7.7.5.1. Adding Layers to an EER Diagram 7.7.5.1. Adding Layers to an EER Diagram 7.7.5.1.1. Adding Objects to a Layer To add layers to an EER Diagram, use the Layer tool on the vertical toolbar. Select an EER Diagram tab and right-click the layer icon on the vertical toolbar. The layer icon is the rectangle with an ‘L’ in the lower left corner and it is found below the eraser icon. Clicking the mouse on this icon changes the mouse pointer to a layer pointer. You can also change the mouse pointer to a layer pointer by pressing the L key. Choosing the Layer tool changes the contents of the toolbar that appears immediately below the menu bar. When the Layers pointer is active, this toolbar contains a color chart list. Use this list to select the color accent for the new layer. The color of your layer can be changed later using the Properties palette. Create a layer by clicking anywhere on the EER Diagram canvas and, while holding the left mouse button down, draw a rectangle of a suitable size. This creates a new layer with the default name layer1 . To revert to the default mouse pointer, click the arrow icon at the top of the vertical toolbar. The following image shows a layer containing a number of views. Figure 7.13. The Layer Object To change the name of a layer, use the name property of the Properties palette. Right-clicking a layer opens a pop-up menu with the following items: Cut ' layer_name ' Copy ' layer_name ' Delete ' layer_name ' The cut and copy items are useful for copying layers between different schemata. Since layers are not schema objects, no confirmation dialog box opens when you delete a layer regardless of how you have configured MySQL Workbench. Deleting a layer does not delete schema objects from the catalog. 7.7.5.1.1. Adding Objects to a Layer To add an object to a layer, drag and drop it directly from the Catalog palette onto a layer. If you pick up an object from an EER diagram, you must press Control as you drag it onto the layer, otherwise it will not be “ locked ” inside the layer. Locking objects to a layer prevents their accidental removal. You cannot remove them by clicking and dragging; to remove an object, you also must press the Control key while dragging it. As a visual cue that the object is being “ locked ”, the outline of the layer is highlighted as the object is dragged over it. If you drag a layer over a table object, the table object will automatically be added to the layer. This also works for multiple table objects. Layers cannot be nested. That is, a layer cannot contain another layer object. 


c1title: Dojo Toolkit v1.7.0b1 License
c2content:
 B.8. Dojo Toolkit v1.7.0b1 License B.8. Dojo Toolkit v1.7.0b1 License The following software may be included in this product: Dojo Toolkit v1.7.0b1 Copyright (c) 2005-2006, The Dojo Foundation All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of the Dojo Foundation nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 


c1title: Changes in MySQL Workbench 5.0.29 (12 December 2008)
c2content:
 A.3.2. Changes in MySQL Workbench 5.0.29 (12 December 2008) A.3.2. Changes in MySQL Workbench 5.0.29 (12 December 2008) This section documents all changes and bug fixes applied since the release of 5.0.28. Bugs Fixed Workbench crashed when objects other than tables were moved out of a layer. (Bug #41358) In the EER Diagram view an icon was not displayed for Not-NULL items. (Bug #41326) When a diagram was renamed, the label of the corresponding tab was not automatically updated. However, when the focus was changed, the text was correctly updated. (Bug #38867) The table figures in the Diagram view had insufficient information. They did not display information such as constraints or default values. (Bug #38553) When the grid was activated, dragged objects on layers were incorrectly placed with an offset of -1,-1. (Bug #35989) The last column in a table disappeared in the table editor, and it was not possible to add further columns. (Bug #35905) 


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


c1title: Creating Notes
c2content:
 7.7.6. Creating Notes 7.7.6. Creating Notes 7.7.6.1. Adding Notes 7.7.6.2. The Note Editor You can add notes to a database only from the Model Notes section of the MySQL Model page. Notes are typically used to help document the design process. 


c1title: Creating a Custom Template
c2content:
 7.12.2. Creating a Custom Template 7.12.2. Creating a Custom Template In the simplest case, a template consists of two files: a template file, which has a .tpl extension, and a special file info.xml . The info.xml file has important metadata about the template. A third file is optional, which is the preview image file. This preview file provides a thumbnail image illustrating the appearance of the generated report. One of the easiest ways to create a custom template is to make a copy of any existing template. For example, the following procedure describes how to make a custom template based on the Text Basic template. Navigate to the folder where the templates are stored. Assuming that MySQL Workbench has been installed into the default location on Windows, this would be C:\Program Files\MySQL\MySQL Workbench 5.0 SE\modules\data\wb_model_reporting . Copy the Text_Basic.tpl folder. The copy can be given any suitable name; for example, Custom_Basic.tpl . Edit the info.xml file to reflect your custom template. The unedited file in this case is shown here: &lt;?xml version="1.0"?&gt; &lt;data&gt; &lt;value type="object" struct-name="workbench.model.reporting.TemplateInfo" id="{BD6879ED-814C-4CA3-A869-9864F83B88DF}" struct-checksum="0xb46b524d"&gt; &lt;value type="string" key="description"&gt;A basic TEXT report listing schemata and objects.&lt;/value&gt; &lt;value type="string" key="name"&gt;HTML Basic Frame Report&lt;/value&gt; &lt;value type="list" content-type="object" content-struct-name="workbench.model.reporting.TemplateStyleInfo" key="styles"&gt; &lt;value type="object" struct-name="workbench.model.reporting.TemplateStyleInfo" id="{7550655C-CD4B-4EB1-8FAB-AAEE49B2261E}" struct-checksum="0xab08451b"&gt; &lt;value type="string" key="description"&gt;Designed to be viewed with a fixed sized font.&lt;/value&gt; &lt;value type="string" key="name"&gt;Fixed Size Font&lt;/value&gt; &lt;value type="string" key="previewImageFileName"&gt;preview_basic.png&lt;/value&gt; &lt;value type="string" key="styleTagValue"&gt;fixed&lt;/value&gt; &lt;/value&gt; &lt;/value&gt; &lt;value type="string" key="mainFileName"&gt;report.txt&lt;/value&gt; &lt;/value&gt; &lt;/data&gt; The file defines wwo objects: the TemplateInfo object and the TemplateStyleInfo object. These objects contain information about the template that will be displayed in the DBDoc Model Reporting wizard main page. Change the object GUIDs that are used in the file. In this example, there are two that need replacing: id="{BD6879ED-814C-4CA3-A869-9864F83B88DF}" ... id="{7550655C-CD4B-4EB1-8FAB-AAEE49B2261E}" Generate two new GUIDS. This can be done using any suitable command-line tool. There are also free online tools that can be used to generate GUIDs. Another way to generate GUIDs is by using the MySQL UUID() function: mysql&gt; SELECT UUID(); +--------------------------------------+ | UUID() | +--------------------------------------+ | 648f4240-7d7a-11e0-870b-89c43de3bd0a | +--------------------------------------+ Once you have the new GUID values, edit the info.xml file accordingly. Edit the textual information for the TemplateInfo and TemplateStyleInfo objects to reflect the purpose of the custom template. The modified file will now look something like the following: &lt;?xml version="1.0"?&gt; &lt;data&gt; &lt;value type="object" struct-name="workbench.model.reporting.TemplateInfo" id="{cac9ba3f-ee2a-49f0-b5f6-32580fab1640}" struct-checksum="0xb46b524d"&gt; &lt;value type="string" key="description"&gt;Custom basic TEXT report listing schemata and objects.&lt;/value&gt; &lt;value type="string" key="name"&gt;Custom Basic text report&lt;/value&gt; &lt;value type="list" content-type="object" content-struct-name="workbench.model.reporting.TemplateStyleInfo" key="styles"&gt; &lt;value type="object" struct-name="workbench.model.reporting.TemplateStyleInfo" id="{39e3b767-a832-4016-8753-b4cb93aa2dd6}" struct-checksum="0xab08451b"&gt; &lt;value type="string" key="description"&gt;Designed to be viewed with a fixed sized font.&lt;/value&gt; &lt;value type="string" key="name"&gt;Fixed Size Font&lt;/value&gt; &lt;value type="string" key="previewImageFileName"&gt;preview_basic.png&lt;/value&gt; &lt;value type="string" key="styleTagValue"&gt;fixed&lt;/value&gt; &lt;/value&gt; &lt;/value&gt; &lt;value type="string" key="mainFileName"&gt;custom_report.txt&lt;/value&gt; &lt;/value&gt; &lt;/data&gt; Create the new template file. This too may best be achieved, depending on your requirements, by editing an existing template. In this example the template file report.txt.tpl is shown here: +--------------------------------------------+ | MySQL Workbench Report | +--------------------------------------------+ Total number of Schemata: {{SCHEMA_COUNT}} ============================================= {{#SCHEMATA}} {{SCHEMA_NR}}. Schema: {{SCHEMA_NAME}} ---------------------------------------------- ## Tables ({{TABLE_COUNT}}) ## {{#TABLES}}{{TABLE_NR_FMT}}. Table: {{TABLE_NAME}} {{#COLUMNS_LISTING}}## Columns ## Key Column Name Datatype Not Null Default Comment {{#COLUMNS}}{{COLUMN_KEY}}{{COLUMN_NAME}}{{COLUMN_DATATYPE}} » {{COLUMN_NOTNULL}}{{COLUMN_DEFAULTVALUE}}{{COLUMN_COMMENT}} {{/COLUMNS}}{{/COLUMNS_LISTING}} {{#INDICES_LISTING}}## Indices ## Index Name Columns Primary Unique Type Kind Comment {{#INDICES}}{{INDEX_NAME}}{{#INDICES_COLUMNS}}{{INDEX_COLUMN_NAME}} » {{INDEX_COLUMN_ORDER}}{{INDEX_COLUMN_COMMENT}}{{/INDICES_COLUMNS}} » {{INDEX_PRIMARY}}{{INDEX_UNIQUE}}{{INDEX_TYPE}}{{INDEX_KIND}}{{INDEX_COMMENT}} {{/INDICES}}{{/INDICES_LISTING}} {{#REL_LISTING}}## Relationships ## Relationship Name Relationship Type Parent Table Child Table Cardinality {{#REL}}{{REL_NAME}}{{REL_TYPE}}{{REL_PARENTTABLE}}{{REL_CHILDTABLE}}{{REL_CARD}} {{/REL}}{{/REL_LISTING}} --------------------------------------------- {{/TABLES}} {{/SCHEMATA}} ============================================= End of MySQL Workbench Report This template shows details for all schemata in the model. The preceding template file can be edited in any way you like, with new markers being added, and existing markers being removed as required. For the custom template example, you might want to create a much simpler template, such as the one following: +--------------------------------------------+ | MySQL Workbench Custom Report | +--------------------------------------------+ Total number of Schemata: {{SCHEMA_COUNT}} ============================================= {{#SCHEMATA}} Schema Name: {{SCHEMA_NAME}} ---------------------------------------------- ## Tables ({{TABLE_COUNT}}) ## {{#TABLES}} Table Name: {{TABLE_NAME}} {{/TABLES}} {{/SCHEMATA}} Report Generated On: {{GENERATED}} ============================================= End of MySQL Workbench Custom Report This simplified report just lists the schemata and the tables in a model. The date and time the report was generated is also displayed as a result of the use of the {{GENERATED}} variable. The custom template can then be tested. Start MySQL Workbench, load the model to generate the report for, select the Model , DBDOC - Model Reporting menu item. Then select the new custom template from the list of available templates, select an output directory, and click Finish to generate the report. Finally, navigate to the output directory to view the finished report. 


c1title: Changes in MySQL Workbench 5.2.31a (13 December 2010)
c2content:
 A.1.8. Changes in MySQL Workbench 5.2.31a (13 December 2010) A.1.8. Changes in MySQL Workbench 5.2.31a (13 December 2010) This section documents all changes and bug fixes applied since the release of 5.2.31. Functionality Added or Changed It was not possible to launch the MySQL Command Line Client from the SQL Editor. MySQL Workbench has been changed so that it is now possible to launch a MySQL Command Line Client from the Home screen. This can be done through the context-sensitive menu available for items listed in the connections list on the Home screen. (Bug #56631) Bugs Fixed An unexpected error was generated when attempting to modify the script created in the Forward Engineer to Database wizard. (Bug #58893) SQL Editor did not load certain text files correctly, and inserted erroneous empty lines between text. (Bug #58850) MySQL Workbench closed silently when the User Defined Types Editor dialog was closed using the close button on the window frame, or by pressing Alt+F4 . (Bug #58846) Opening the Snippets tab in the SQL Editor caused MySQL Workbench to crash with the error: ** Message: query.explain built-in command is being overwritten mysql-workbench-bin: /usr/include/boost/smart_ptr/shared_ptr.hpp:418: T* boost::shared_ptr&lt; &lt;template-parameter-1-1&gt; &gt;::operator-&gt;() const [with T = Sql_editor]: Assertion `px != 0' failed. Aborted (Bug #58833) 


c1title: MySQL-Specific Validation
c2content:
 7.10.2. MySQL-Specific Validation 7.10.2. MySQL-Specific Validation The following list names the MySQL-specific validation types and gives examples of specific violations: Integrity Violation An object name longer than the maximum permitted A foreign key defined for an engine type that does not support foreign keys (not yet implemented) A view or routine that references a nonexistent table (not yet implemented) A default value that does not match a column's data type An invalid partitioning scheme Syntax Violation A routine, trigger, or view with incorrect SQL syntax A reserved keyword used as an identifier Use of an invalid character 


c1title: Main Tabsheets
c2content:
 6.7.4. Main Tabsheets 6.7.4. Main Tabsheets 6.7.4.1. Overview Tabsheet 6.7.4.2. Output Tabsheet 6.7.4.3. History Tabsheet 6.7.4.4. Snippets Tabsheet 6.7.4.5. Results Tabsheets 6.7.4.6. Live Editing Tabsheets The main tabsheets area contains several tabs: Overview Tabsheet Output Tabsheet History Tabsheet Results Tabsheets Live Editing Tabsheet Figure 6.8. SQL Editor - Main Tabsheets The following sections describe each of these in more detail. 


c1title: PCRE License
c2content:
 B.16. PCRE License B.16. PCRE License The following software may be included in this product: PCRE (Perl Compatible Regular Expressions) Library PCRE LICENCE PCRE is a library of functions to support regular expressions whose syntax and semantics are as close as possible to those of the Perl 5 language. Release 7 of PCRE is distributed under the terms of the "BSD" licence, as specified below. The documentation for PCRE, supplied in the "doc" directory, is distributed under the same terms as the software itself. The basic library functions are written in C and are freestanding. Also included in the distribution is a set of C++ wrapper functions. THE BASIC LIBRARY FUNCTIONS --------------------------- Written by: Philip Hazel Email local part: ph10 Email domain: cam.ac.uk University of Cambridge Computing Service, Cambridge, England. Phone: +44 1223 334714. Copyright (c) 1997-2006 University of Cambridge All rights reserved. THE C++ WRAPPER FUNCTIONS ------------------------- Contributed by: Google Inc. Copyright (c) 2006, Google Inc. All rights reserved. THE "BSD" LICENCE ----------------- Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of the University of Cambridge nor the name of Google Inc. nor the names of their contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. End 


c1title: The File Menu
c2content:
 7.5.1.1. The File Menu 7.5.1.1. The File Menu Use the File menu to open a project, begin a new project, or save a project. Choosing New Model opens the default schema, mydb . Choosing Open Model opens a file dialog box with the default file type set to MySQL Workbench Models ( mwb extension). To display a list of recently opened MWB files, choose the Open Recent menu item. The keyboard shortcut to create a new project is Control+N and the command to open an existing project is Control+O . To close the currently active MySQL Model or EER Diagram tab, use the Close Tab menu item. You can also do this from the keyboard by pressing Control+W . To reopen the MySQL Model tab, see Section 7.5.1.3, “The View Menu” . To reopen an EER Diagram tab, double-click the EER Diagram icon in the EER Diagrams section of the MySQL Model page. Use the Save Model or Save Model As menu items to save a model. When you save a model, its name appears in the title bar of the application. If you have made changes to a project and have not saved those changes, an asterisk appears in the title bar following the model name. When you save a model, it is saved as a MySQL Workbench file with the extension mwb . Use the Import menu item to import a MySQL data definition (DDL) script file. For example, this might be a file created by issuing the command mysqldump --no-data . MySQL Workbench handles the script as follows: If the script does not contain a CREATE DATABASE db_name ; statement, the schema objects are copied to the default schema, mydb . If the script creates a database, a new tab bearing the database name is added to the Physical Schemata section of the MySQL Model page. If the script contains data, the data is ignored. For details about importing a DDL script, see Section 7.7.9.1, “Reverse Engineering Using a Create Script” . Under the Import submenu, you can also import DBDesigner4 files. There are variety of items under the Export submenu. You may generate the SQL statements necessary to create a new database or alter an existing one. For more information about these menu items, see Section 7.7.10.1, “Forward Engineering Using an SQL Script” . Using the Export submenu, you can also export an EER diagram as a PNG, SVG, PDF, or Postscript file. For an example of a PNG file, see Figure 7.45, “The sakila Database EER Diagram” . The Page Setup menu item enables you to set the paper size, orientation, and margins for printing purposes. The printing options are enabled only if the EER Diagrams tab is selected. You have the choice of printing your model directly to your printer, printing it as a PDF file, or creating a PostScript file. For more information, see Section 7.9, “Printing” . Note The printing options are available only in commercial versions of MySQL Workbench. Use the Document Properties menu item to set the following properties of your project: Name : The model name (default is MySQL Model ) Version : The project version number Author : The project author Project : The project name Created : Not editable; determined by the MWB file attributes Last Changed : Not editable; determined by the MWB file attributes Description : A description of your project 


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


c1title: Changes in MySQL Workbench 5.2.14 (21 January 2010)
c2content:
 A.1.26. Changes in MySQL Workbench 5.2.14 (21 January 2010) A.1.26. Changes in MySQL Workbench 5.2.14 (21 January 2010) This section documents all changes and bug fixes applied since the release of 5.2.13. Bugs Fixed If a multiline configuration option in the MySQL server configuration file was removed using the configuration editor of the Administrator tab, MySQL Workbench generated an error. (Bug #50470) In the SQL Editor, the Alter Table dialog created incorrect DDL for changes to the partitioning. (Bug #49055) In the Physical Schemata section of the MySQL Model tab, the tables were not displayed in alphabetic order. (Bug #47143) 


c1title: Chapter 1. MySQL Workbench Introduction
c2content:
 Chapter 1. MySQL Workbench Introduction Chapter 1. MySQL Workbench Introduction MySQL Workbench provides a graphical tool for working with MySQL Servers and databases. MySQL Workbench fully supports MySQL Server versions 5.1 and above. It is also compatible with MySQL Server 5.0, but not every feature of 5.0 may be supported. It does not support MySQL Server versions 4.x. MySQL Workbench provides three main areas of functionality: SQL Development : Enables you to create and manage connections to database servers. As well as enabling you to configure connection parameters, MySQL Workbench provides the capability to execute SQL queries on the database connections using the built-in SQL Editor. This functionality replaces that previously provided by the Query Browser standalone application. Data Modeling : Enables you to create models of your database schema graphically, reverse and forward engineer between a schema and a live database, and edit all aspects of your database using the comprehensive Table Editor. The Table Editor provides easy-to-use facilities for editing Tables, Columns, Indexes, Triggers, Partitioning, Options, Inserts and Privileges, Routines and Views. Server Administration : Enables you to create and administer server instances. MySQL Workbench is available in two editions, the Community Edition and the Standard Edition. The Community Edition is available free of charge. The Standard Edition provides additional Enterprise features, such as database documentation generation, at low cost. 


c1title: Changes in MySQL Workbench 5.0.22 (27 May 2008)
c2content:
 A.3.9. Changes in MySQL Workbench 5.0.22 (27 May 2008) A.3.9. Changes in MySQL Workbench 5.0.22 (27 May 2008) This section documents all changes and bug fixes applied since the release of 5.0.21. Bugs Fixed Can not add values for TIMESTAMP columns in the Inserts editor. (Bug #37009) When columns are added to, or removed from a table, Workbench deletes all Inserts data. (Bug #37008) Trigger definition auto-formatting resulted in malformed code. (Bug #36815, Bug #37685) The script generated by the File , Export , Forward Engineer SQL CREATE Script menu item contains a spurious quotation mark. (Bug #36753) For CREATE TABLE statements, TIME column default values were not quoted properly. (Bug #36669) Print preview in landscape orientation did not work correctly. (Bug #36647) When opening a model created with an earlier version of Workbench, the Indexes tab displayed indexes of type FOREIGN as type INDEX , and it was not possible to change them back to FOREIGN . (Bug #36453) If a table column definition permits NULL and has been set with a default of NULL , integrity validation operations complained that the default value for the column is invalid. (Bug #36397) After use of Control+X to cut text from a text-edit box and Control+Z to undo the operation, the canvas was updated correctly but not the text box. (Bug #36358) Shifted content could not be scrolled or navigated. (Bug #36328) The mousewheel scrolled the overview pane when it was open behind the insert-editor. (Bug #36253) View renaming in overview did not work properly and has been disabled. (Bug #36202) The Copy to SQL operation caused a crash. (Bug #36184) Dragging objects out of a layer did not work properly. (Bug #36053) The enabled/disabled status of items in the Edit menu was not updated properly. (Bug #35962) Relationships were drawn over tables. (Bug #35867) The script generated by database synchronize contained errors. (Bug #35644) Setting up foreign key relationships across multiple schemas did not work. (Bug #34546) Scrollbars now appear correctly when editor windows are reduced in height. (Bug #32454) Table partitioning information was not exported properly. (Bug #32226) 


c1title: The Vertical Toolbar
c2content:
 7.6.1. The Vertical Toolbar 7.6.1. The Vertical Toolbar 7.6.1.1. The Standard Mouse Pointer 7.6.1.2. The Hand Tool 7.6.1.3. The Eraser Tool 7.6.1.4. The Layer Tool 7.6.1.5. The Text Tool 7.6.1.6. The Image Tool 7.6.1.7. The Table Tool 7.6.1.8. The View Tool 7.6.1.9. The Routine Group Tool 7.6.1.10. The Relationship Tools The vertical toolbar shows on the left sidebar when an EER diagram tab is selected. The tools on this toolbar assist in creating EER diagrams. Figure 7.6. The Vertical Toolbar Clicking a tool changes the mouse pointer to a pointer that resembles the tool icon, indicating which tool is active. These tools can also be activated from the keyboard by pressing the key associated with the tool. Hover the mouse pointer over a toolbar icon to display a description of the tool and its shortcut key. A more detailed description of each of these tools follows. 


c1title: Uninstalling MySQL Workbench on Mac OS X
c2content:
 3.3.9. Uninstalling MySQL Workbench on Mac OS X 3.3.9. Uninstalling MySQL Workbench on Mac OS X To uninstall MySQL Workbench for Mac OS X, locate MySQL Workbench in the Applications folder, right-click, and select Move to Trash . 


c1title: Workspace
c2content:
 5.2. Workspace 5.2. Workspace The Workspace is designed to enable you to quickly get to the task you would like to carry out. In alignment with MySQL Workbench functionality, it is divided into three main areas: SQL Development . For further information, see Chapter 6, SQL Development . Data Modeling . For further information, see Chapter 7, Data Modeling . Server Administration . For further information, see Chapter 8, Server Administration . 


c1title: Appendix B. Third Party Licenses
c2content:
 Appendix B. Third Party Licenses Appendix B. Third Party Licenses Table of Contents B.1. .NET Flat TabControl License B.2. Bitstream Vera License B.3. Boost Library License B.4. Cairo License B.5. CTemplate (Google Template System) License B.6. cURL ( libcurl ) License B.7. DockPanel Suite License B.8. Dojo Toolkit v1.7.0b1 License B.9. GLib License (for MySQL Workbench) B.10. Glitz License B.11. GNU Lesser General Public License Version 2.1, February 1999 B.12. HtmlRenderer (System.Drawing.Html) B.13. Libxml2 License B.14. Libzip License B.15. Lua (liblua) License B.16. PCRE License B.17. Pixman License B.18. PyCrypto License B.19. Python License B.20. Scintilla License B.21. ScintillaNET License B.22. TinyXML License B.23. TreeViewAdv for .NET License B.24. VSQLite++ License Use of any of this software is governed by the terms of the licenses that follow. MySQL Workbench Section B.1, “.NET Flat TabControl License” Section B.2, “Bitstream Vera License” Section B.3, “Boost Library License” Section B.4, “Cairo License” Section B.5, “CTemplate (Google Template System) License” Section B.6, “cURL ( libcurl ) License” Section B.7, “DockPanel Suite License” Section B.8, “Dojo Toolkit v1.7.0b1 License” Section B.9, “GLib License (for MySQL Workbench)” Section B.10, “Glitz License” Section B.11, “GNU Lesser General Public License Version 2.1, February 1999” Section B.12, “HtmlRenderer (System.Drawing.Html)” Section B.13, “Libxml2 License” Section B.14, “Libzip License” Section B.15, “Lua (liblua) License” Section B.16, “PCRE License” Section B.17, “Pixman License” Section B.18, “PyCrypto License” Section B.19, “Python License” Section B.20, “Scintilla License” Section B.21, “ScintillaNET License” Section B.22, “TinyXML License” Section B.23, “TreeViewAdv for .NET License” Section B.24, “VSQLite++ License” 


c1title: Changes in MySQL Workbench 5.1.4 (Not yet released)
c2content:
 A.2.15. Changes in MySQL Workbench 5.1.4 (Not yet released) A.2.15. Changes in MySQL Workbench 5.1.4 (Not yet released) This section documents all changes and bug fixes applied since the release of 5.1.3. Functionality Added or Changed 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 visible property can be set to True in the Properties window, thus making the relationship visible again. (Bug #40167) Bugs Fixed Loading a model using the Linux version of Workbench resulted in a crash. However, the model loaded correctly with the Windows versions of Workbench. (Bug #39992) A model created using the Windows version of Workbench caused the Linux version of Workbench to crash on loading the model. (Bug #39983) 


c1title: Live Editing Tabsheets
c2content:
 6.7.4.6. Live Editing Tabsheets 6.7.4.6. Live Editing Tabsheets It is possible to edit data in real time using the Live Editing tabsheets. In the Overview tab, if a table is double-clicked, a live editing tab is launched, enabling you to edit the data maintained in that table. Field data can be edited by clicking a field and entering the required data, or editing existing data. In addition to the controls offered by the Results tabsheet, the Live Editor tab features some additional controls. These controls are highlighted in the following screenshot. Figure 6.12. SQL Editor - Live Editing Tabsheet Navigation Controls These additional controls enable you to make changes to the data shown in the table and to apply or discard those changes. Applying the changes synchronizes the data with the live server. Discarding them leaves the live server unaffected. From left to right, the additional controls are: Edit current row : Enters edit mode for the currently selected row. Note It is possible to enter a function, or other expression, into a field. Use the prefix \func to prevent MySQL Workbench from escaping quotation marks. For example, for the expression md5('fred') , MySQL Workbench normally would generate the code md5(\'fred\') . To prevent this, enter the expression as \func md5('fred') to ensure that the quoting is not escaped. Insert new row : Inserts a new row and enables you to enter data. Your changes will not be reflected on the live server until you click Apply changes to data . Delete selected rows : Removes the selected rows. Your changes will not be reflected on the live server until you click Apply changes to data . Apply changes to data : Applies to the live server any changes that have been made in the data fields. Discard changes to data : Discards any changes that have been made in the data fields without applying them to the live server. See also Section 7.7.1.3.9, “The Inserts Tab” . 


c1title: Chapter 4. Getting Started Tutorial
c2content:
 Chapter 4. Getting Started Tutorial Chapter 4. Getting Started Tutorial Table of Contents 4.1. Administering a MySQL Server 4.2. Creating a Model 4.3. Adding Data to Your Database This tutorial provides a quick hands-on introduction to using MySQL Workbench for beginners. If you have used MySQL Workbench before you can safely skip this tutorial. This tutorial uses a locally installed MySQL Server. If you only have access to a remote MySQL server, you must enter appropriate connection parameters as necessary. This tutorial requires MySQL Workbench 5.2.16 or above. It is assumed that you have a basic understanding of MySQL concepts. This tutorial demonstrates the procedures on Microsoft Windows, but they are the same for all supported platforms. 


c1title: The Administrator Tab
c2content:
 5.4.2. The Administrator Tab 5.4.2. The Administrator Tab This section provides configuration options that affect the Administrator functionality in MySQL Workbench. It enables you to set paths to the mysqldump and mysql tools. If these paths are left blank, the defaults are used. This panel also enables you to set the directory for export dump files. 


c1title: Changes in MySQL Workbench 5.0.28 (06 December 2008)
c2content:
 A.3.3. Changes in MySQL Workbench 5.0.28 (06 December 2008) A.3.3. Changes in MySQL Workbench 5.0.28 (06 December 2008) This section documents all changes and bug fixes applied since the release of 5.0.27. Bugs Fixed If you attempted to select several tables in the table list of the MySQL Model view, and you accidentally included the Add Table button in your selection, a message box appeared warning of an unknown exception: "Unknown Exception caught in: c:\documents and settings\mysqldev\my documents\visual studio 2005\projects\workbench\backend\windows\wb.wr\src\Wb.h at line 1010" The program did not crash. Only the messagebox appeared. (Bug #41201) If two foreign keys were created in a table that referenced a second table and then an attempt was made to delete the relations and the referenced table, MySQL Workbench crashed. (Bug #41025) When clicking the + and - buttons in the Physical Schemata pane of the MySQL Model tab, an Unhandled Exception was generated: System.Runtime.InteropServices.SEHException: External component has thrown an exception. (Bug #40971) The Referenced Column pane of the Foreign Key tab became cleared if the foreign key was renamed. Subsequently, attempting to choose a Referenced Column did not display a link in the EER Diagram view. To get foreign key relationships working again it was necessary to de-select the check boxes from the Columns pane, re-select them, and then select the Referenced Column pane. (Bug #40649) When a table was renamed the inserted data was lost. (Bug #40327) A complex EER diagram threw an exception whenever an action was peformed on it. However, other diagrams in the same MWB file functioned correctly. The exception generated was: System.Runtime.InteropServices.SEHException: Un composant externe a levé une exception. à wb.ModelViewForm.handle_mouse_button(ModelViewForm* , MouseButton , Boolean , Int32 , Int32 , EventState ) à MySQL.Workbench.ModelViewForm.OnMouseUp(MouseEventArgs e, Int32 X, Int32 Y, Keys keystate, MouseButtons buttons) à MySQL.GUI.Workbench.ModelViewForm.CanvasPanel_MouseUp(Object sender, MouseEventArgs e) à System.Windows.Forms.Control.OnMouseUp(MouseEventArgs e) à MySQL.Utilities.WindowsCanvasViewerPanel.OnMouseUp(MouseEventArgs e) à System.Windows.Forms.Control.WmMouseUp(Message&amp; m, MouseButtons button, Int32 clicks) à System.Windows.Forms.Control.WndProc(Message&amp; m) à System.Windows.Forms.ScrollableControl.WndProc(Message&amp; m) à System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message&amp; m) à System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message&amp; m) à System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) (Bug #39360) 


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


c1title: Changes in MySQL Workbench 5.2.8 (18 November 2009 Beta)
c2content:
 A.1.32. Changes in MySQL Workbench 5.2.8 (18 November 2009 Beta) A.1.32. Changes in MySQL Workbench 5.2.8 (18 November 2009 Beta) First Beta release of 5.2. This section documents all changes and bug fixes applied since the release of 5.2.7. Bugs Fixed When a table was edited in the EER Diagram view, and Control+S was pressed to save the model, the model file was not saved. (Bug #48682) If an model object, such as a schema or table, was deleted or its creation was undone using the undo feature, while the object editor was open, a crash occurred if the editor was then subsequently closed. (Bug #48664) When running MySQL Workbench, this error occurred when an attempt was made to change the Windows screen resolution: cairo error: out of memory (Bug #48520) MySQL Workbench did not start correctly. At startup it generated this error: Microsoft Visual C++ Runtime Library Runtime Error! Program C:\Pro... This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. (Bug #48389) Once a default value had been set for a column in the Table Editor, it was not possible to remove it. (Bug #47085) The View text editor was overly aggressive in trimming excess whitespace from View definitions. If there was some hesitation after the user entered one or more spaces, the editor would trim whitespace back to the last non-space character entered. (Bug #46894) In the EER Diagram view, the auto-resizing of tables did not work correctly, tables were too small to permit all columns to be visible. (Bug #46806) When using the Fedora 10 RPM installation packages on Fedora 11, opening a database connection produced this error: Cannot Connect to Database Server Connection 'antonia' could not be established: Database driver: Failed to open library '/usr/lib/mysql-workbench/mysqlcppconn.so'. Check settings. The MySQL Workbench libraries were installed in /usr/lib64/ , not /usr/lib/ . (Bug #46428) In the Manage DB Connections dialog, the text fields Username , Password , and Default Schema accepted text, but as the text was being entered only the top half of the characters entered displayed. However, once the text had been submitted, the characters were displayed correctly. (Bug #45106) Printing of an EER Diagram did not work correctly if a table vertically spanned multiple pages. In this case pages would be printed up to and including the page that contained the first part of the table that spanned multiple pages, but the pages containing the remaining parts of the table would not be printed. This problem typically occurred when a table had more fields than could comfortably fit on a single page. (Bug #33919) 


c1title: Using the Default Schema
c2content:
 7.8.2. Using the Default Schema 7.8.2. Using the Default Schema 7.8.2.1. Creating a New Table 7.8.2.2. Creating Other Schema Objects When you first open MySQL Workbench a default schema, mydb appears as the leftmost tab of the Physical Schemata section of MySQL Workbench. You can begin designing a database by using this default schema. Figure 7.43. The Default Schema To change the name of the default schema, double-click the schema tab. This opens a schema editor window docked at the bottom of the application. To undock or redock this window, double-click anywhere in the editor title bar. To rename the schema, use the field labeled Name . After you have renamed the schema, a lightning bolt icon appears right aligned in the Name field, indicating that other changes are pending. Click the Comments field and a dialog box opens asking if you wish to rename all schema occurrences. Clicking Yes ensures that your changes are propagated throughout the application. Add comments to the database and change the collation if you wish. Close the schema editor by clicking the x button. 


c1title: Boost Library License
c2content:
 B.3. Boost Library License B.3. Boost Library License The following software may be included in this product: Boost C++ Libraries Use of any of this software is governed by the terms of the license below: Boost Software License - Version 1.0 - August 17th, 2003 Permission is hereby granted, free of charge, to any person or organization obtaining a copy of the software and accompanying documentation covered by this license (the "Software") to use, reproduce, display, distribute, execute, and transmit the Software, and to prepare derivative works of the Software, and to permit third-parties to whom the Software is furnished to do so, all subject to the following: The copyright notices in the Software and this entire statement, including the above license grant, this restriction and the following disclaimer, must be included in all copies of the Software, in whole or in part, and all derivative works of the Software, unless such copies or derivative works are solely in the form of machine-executable object code generated by a source language processor. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. 


c1title: Open Connection to Start Querying
c2content:
 6.1. Open Connection to Start Querying 6.1. Open Connection to Start Querying Clicking this action item launches the Connect to Database Wizard. From this wizard, you can select a predefined connection. A new SQL Editor tab is launched. 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. To read more about the SQL Editor, see Section 6.7, “SQL Editor” . 


c1title: Changes in MySQL Workbench 5.2.23 (Internal release only)
c2content:
 A.1.17. Changes in MySQL Workbench 5.2.23 (Internal release only) A.1.17. Changes in MySQL Workbench 5.2.23 (Internal release only) This section documents all changes and bug fixes applied since the release of 5.2.22. Functionality Added or Changed In the SQL Editor, when more result tabs were generated than could fit into the current panel, it was not obvious how to navigate to those result sets that could not currently be displayed. This could be achieved using the left and right arrow keys, but MySQL Workbench now also includes a spin control to navigate the available tabs. (Bug #52998) The Overview tab in the SQL Editor now supports scrolling of content using the mouse wheel. (Bug #50782) Bugs Fixed In the SQL Editor, attempting to execute a selection in the SQL Query tab caused all text to be executed, not just the selected text. (Bug #54536) Clicking a table caused MySQL Workbench to produce this error message: MySQL Workbench has encountered a problem Cannot access a disposed object Object name: 'DockedWindowPlugin'. (Bug #54498) In the SQL Editor, exporting a record set failed if the target path contained an international character. (Bug #54479) In the Inserts tab of the Table Editor, adding a new row and applying changes had no effect. (Bug #54456) In the General tab of Configuration in the Administrator, when the Temp directory option was selected, and a directory was selected using the file browser, MySQL Workbench inserted backslashes rather than forward slashes. If backslashes were used in this location in the configuration file, the server crashed at startup. (Bug #54445) In the SQL Editor, if a table in the Overview tab was double-clicked, the query generated replaced code already entered into the SQL Query tab, resulting in the loss of that code. (Bug #54362) Synchronizing a model with a live database produced incorrect SQL code: ALTER TABLE `mydb`.`table1` AUTO_INCREMENT = ; (Bug #54319) In the SQL Editor, for result set exports to a tab-delimited file, MySQL Workbench added a .CSV file name extension. (Bug #54302) In the SQL Editor, selecting Alter Table from the context-sensitive menu had no effect. (Bug #54283) In the SQL Editor, editing a table with a row highlighted, right-clicking a BLOB column and loading a value from a file resulted in this error: An external component has triggered an exception (Bug #54266) Changing the name of a stored procedure in the modeler and saving changes caused an erroneous ';' character to be added to the SQL code sent to the database. That resulted in this error: ERROR 1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '; USE `911datashop`' at line 1 SQL Statement: ; USE `911datashop` (Bug #54258, Bug #11761738) Clicking the Edit Table Data action item from the Home screen caused MySQL Workbench to crash. (Bug #54230) The forward engineering Omit Schema Qualifier in Object Names option was not correctly applied to some statements in Trigger code. In these cases, the schema name remained in place. (Bug #54222) Clicking external links in the embedded browser launched Internet Explorer rather than the default browser. (Bug #54192) When entering binary data into the Inserts tab for a table, the data was truncated at the first null byte (\0). (Bug #54156) Select All ( Control+A ) did not work when editing comments for a table or column. (Bug #54154) After a foreign key was created, and the referenced table or column was changed, the change was not reflected in the foreign key, resulting in errors. (Bug #54134) MySQL Workbench crashed if a pinned result tab was refreshed in the SQL Editor. (Bug #54114) The integrated docs web server listened on a fixed port (8811), and was not able to handle the situation where this port may be used by another service, such as another MySQL Workbench instance. (Bug #54104) In the SQL Editor, attempting to create a new schema using Create Schema with a server collation of utf8 - default collation produced SQL that resulted in an error when applied. (Bug #54097) Performing an undo operation in SQL Editor actually resulted in an undo operation in the Modeler. (Bug #54091) MySQL Workbench suffered user interface issues when used on a KDE-based system using a dark theme. (Bug #54083) The HTTP server thread started by MySQL Workbench to provide documentation to the local web browser listened on all IP interfaces, even though it is intended only for local use. (Bug #54083) Database export failed due to a faulty path in the command line: 15:42:52 Dumping rma3 (etat_produit) Running: "mysqldump.exe" --defaults-extra-file=c:\docume~1\user\local settings\temp\tmp9ypdhd --no-create-info=FALSE --order-by-primary=FALSE --force=FALSE --no-data=FALSE --tz-utc=TRUE --flush-privileges=FALSE --compress=FALSE --replace=FALSE --host=127.0.0.1 --insert-ignore=FALSE --extended-insert=TRUE --user=root --quote-names=TRUE --hex-blob=FALSE --complete-insert=FALSE --add-locks=TRUE --port=3306 --disable-keys=TRUE --delayed-insert=FALSE --delete-master-logs=FALSE --comments=TRUE --default-character-set=utf8 --flush-logs=FALSE --dump-date=TRUE --allow-keywords=FALSE --create-options=TRUE --events=FALSE "rma3" "etat_produit" Could not open required defaults file: c:\docume~1\user\local Fatal error in defaults handling. Program aborted mysqldump: Got error: 1045: Access denied for user 'root'@'localhost' (using password: NO) when trying to connect Operation failed with exitcode 2 (Bug #54067) In the Alter Table dialog of the SQL Editor, if an attempt was made to set the NN flag for a column that did not have it set, an error was generated when the changes are applied. (Bug #53918) When carrying out an Alter Routine operation in the SQL Editor, if a routine was modified, and a statement used that, although syntactically correct, was not permitted in a routine, all modifications were lost when changes were applied. (Bug #53887) An EER Diagram appeared to contain hidden tables. Although the diagram contained 12 tables, when a 'select all' was performed the user was informed that 14 tables were selected. It seemed that certain tables had been resized to be so small as to no longer be visible in the diagram. (Bug #53885) In the Layer Tree panel, if a layer was given a blank name, MySQL Workbench subsequently crashed, rather than warning about the of a blank name. (Bug #53807) Keyboard shortcuts such as Command+C , Command+V , and Command+Z were not useable consistently in all parts of MySQL Workbench. (Bug #53790) Columns defined as BIT appeared as requiring synchronization, even if no changes had been made. (Bug #53747) In the Alter Routine dialog of the SQL Editor, if the Find and Replace dialog was invoked with Control+F , and Control+V was used to paste in some search text, the text was actually pasted into the routine code area. (Bug #53735) MySQL Workbench failed to build from source on Debian Linux. This error was generated: libtool: compile: g++ -DHAVE_CONFIG_H -I. -I./src -I./src -pthread -DNDEBUG -Wall -Wwrite-strings -Woverloaded-virtual -Wno-sign-compare -g -O2 -Wextra -Wall -Wno-unused -Wno-deprecated -c src/template.cc -fPIC -DPIC -o .libs/libctemplate_wb_la-template.o In file included from ./src/ctemplate/per_expand_data.h:48, from ./src/ctemplate/template_modifiers.h:69, from src/template_modifiers_internal.h:53, from src/template.cc:61: ./src/ctemplate/template_string.h:88: error: ISO C++ forbids declaration of 'TemplateId' with no type ./src/ctemplate/template_string.h: In member function 'size_t ctemplate::TemplateIdHasher::operator()(ctemplate::TemplateId) const': ./src/ctemplate/template_string.h:234: warning: right shift count &gt;= width of type ./src/ctemplate/template_string.h: At global scope: ./src/ctemplate/template_string.h:344: warning: overflow in implicit constant conversion src/template.cc: In static member function 'static void ctemplate::Template::AssureGlobalsInitialized()': src/template.cc:2365: warning: comparison between signed and unsigned integer expressions make[5]: *** [libctemplate_wb_la-template.lo] Error 1 (Bug #53668) In the EER Diagram view, it was not possible to delete a relationship by right-clicking the relationship, then selecting Delete from the context-sensitive menu. (Bug #53659) In the SQL Query tab of SQL Editor, tooltip error messages were still displayed, even after switching to another tab. (Bug #53634) In the Diagram Size dialog, displayed using Model , Diagram Properties and Size , it was possible to set the size to 100 pages by 100 pages, but then click outside this area. This caused a MySQL Workbench Unexpected Error. (Bug #53559) The Document Properties dialog was displayed across two screens in a multiple-screen setup. (Bug #53262) After a default primary key name was set in the Workbench Preferences dialog, the PK flag was not selected as expected in the Table Editor and the column flags could not be selected. (Bug #52578) When synchronizing with a live database, MySQL Workbench did not interpret whitespace in ENUM s correctly. For example, ENUM('image', 'video', 'swf') was seen as different from ENUM('image','video','swf') , causing the live server and model to appear unsynchronized. (Bug #49182) When editing a column in the table editor, pressing Control+Z to undo the edit resulted in a previous operation being undone instead. (Bug #46286) 


c1title: Manage Server Instances
c2content:
 8.5. Manage Server Instances 8.5. Manage Server Instances Clicking this action item launches the Manage Server Instances dialog. Within this dialog, you can change the configuration of existing server instances or create a new server instance. For further details, see Section 8.6, “Creating and Managing Server Instances” . 


c1title: Standard TCP/IP over SSH Connection
c2content:
 6.6.4. Standard TCP/IP over SSH Connection 6.6.4. Standard TCP/IP over SSH Connection This connection method enables MySQL Workbench to connect to MySQL Server using TCP/IP over an SSH connection. Parameters In addition to a number of parameters that are in common with Standard TCP/IP connections, this connection method features a number of specialized parameters. These are listed here: SSH Hostname : This is the name of the SSH server. An optional port number can also be provided. SSH Username : This is the name of the SSH user name to connect with. SSH Password : The SSH password. It is recommended that an SSH key file is also used. SSH Key File : A path to the SSH key file. Note: Only key files in OpenSSH format are currently supported. These options can be seen in the following screenshot. Figure 6.4. Manage DB Connections - SSH Parameters Advanced The options here are the same as for the Standard TCP/IP connection. See Section 6.6.2, “Standard TCP/IP Connection” . 


c1title: Adding Roles
c2content:
 7.5.5.1. Adding Roles 7.5.5.1. Adding Roles To add a role, double-click the Add Role icon. This creates a role with the default name role1 . Right-clicking a role opens a pop-up menu with the following items: Cut ' role_name ' : Cuts the role Copy ' role_name ' : Copies the role Edit Role... : Opens the role editor Edit in New Window... : Opens the role editor in a new editor window Delete ' role_name ' : Removes the role Copy SQL to Clipboard : Currently not implemented To rename a role, click the role name. Then you will be able to edit the text. All roles that have been defined are listed under Roles on the left side of the role editor. Double-clicking a role object opens the role editor docked at the bottom of the page. Figure 7.4. Role Editor Select the role to which you wish to add objects. You may drag and drop objects from the Physical Schemata to the Objects section of the role editor. To assign privileges to a role, select it from the Roles section, then select an object in the Objects section. In the Privileges section, check the rights you wish to assign to this role. For example, a web_user role might have only SELECT privileges and only for database objects exposed through a web interface. Creating roles can make the process of assigning rights to new users much easier. 


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


c1title: The Connections Tab
c2content:
 8.7.4. The Connections Tab 8.7.4. The Connections Tab The Connections tab lists all current connections to the monitored server. Figure 8.7. Administrator - Connections Tab 


c1title: Adding Tables to an EER Diagram
c2content:
 7.7.1.2. Adding Tables to an EER Diagram 7.7.1.2. Adding Tables to an EER Diagram Tables can also be added to an EER Diagram using the table tool on the vertical toolbar. Make sure that the EER Diagram tab is selected, then right-click the table icon on the vertical toolbar. The table icon is the rectangular tabular icon. Clicking the mouse on this icon changes the mouse pointer to a table pointer. You can also change the mouse pointer to a table pointer by pressing the T key. Choosing the table tool changes the contents of the toolbar that appears immediately below the menu bar. When the Tables pointer is active, this toolbar contains a schemata list, an engines list, a collations list, and a color chart list. Use these lists to select the appropriate schema, engine, collation, and color accent for the new table. Make sure that you associate the new table with a database. The engine and collation of a table can be changed using the table editor. The color of your table can be changed using the Properties palette. The Default Engine and Default Collation values refer to the database defaults. Create a table by clicking anywhere on the EER Diagram canvas. This creates a new table with the default name table1 . To revert to the default mouse pointer, click the arrow icon at the top of the vertical toolbar. Figure 7.7. A Table on an EER Diagram As shown in the preceding diagram, the primary key is indicated by a key icon and indexed fields are indicated by a different colored diamond icon. Click the arrow to the right of the table name to toggle the display of the fields. Toggle the display of indexes and triggers in the same way. Right-clicking a table opens a pop-up menu with the following items: Cut ' table_name ' Copy ' table_name ' Edit Table... Edit in New Window... Copy SQL to Clipboard Copy Insert to Clipboard Delete ' table_name ' With the exception of the deletion item, these menu items function as described in Section 7.7.1.1, “Adding Tables to the Physical Schemata” . The behavior of the delete option is determined by your MySQL Workbench options settings. For more information, see Section 5.4.4, “The Model Tab” . 


c1title: EER Diagrams
c2content:
 7.5.3. EER Diagrams 7.5.3. EER Diagrams Use the Add Diagram icon in the MySQL Model area to create EER diagrams. When you add an EER diagram, a new tab appears below the toolbar. Use this tab to navigate to the newly created EER diagram. For further discussion of EER Diagrams, see Section 7.6, “EER Diagram Editor” . 


c1title: Changes in MySQL Workbench 5.2.1 (22 May 2009)
c2content:
 A.1.39. Changes in MySQL Workbench 5.2.1 (22 May 2009) A.1.39. Changes in MySQL Workbench 5.2.1 (22 May 2009) This section documents all changes and bug fixes applied since the release of 5.2.0. This section has no changelog entries. 


c1title: Uninstalling MySQL Workbench on Windows
c2content:
 3.3.3. Uninstalling MySQL Workbench on Windows 3.3.3. Uninstalling MySQL Workbench on Windows The method for uninstalling MySQL Workbench depends on how you installed MySQL Workbench in the first place. Removing MySQL Workbench After Installation Using the Installer Package To uninstall MySQL Workbench, open the Control Panel and Choose Add or Remove Programs . Find the MySQL Workbench entry and choose the Remove button. This will remove MySQL Workbench. Any modules added to the C:\%PROGRAMFILES%\MySQL\MySQL Workbench version \modules directory will not be deleted. Note If you installed MySQL Workbench using the Installer package, it is not possible to remove MySQL Workbench from the command line. Although you can manually remove some of the components, there is no command-line option for removing MySQL Workbench. Removing the MySQL Workbench directory manually will not remove all the files belonging to MySQL Workbench. Removing MySQL Workbench After Installation from a Zip File To remove MySQL Workbench, just delete the MySQL Workbench directory. Note If you installed any additional modules within the modules directory and you want to keep them, make sure you copy those modules to a different directory before deleting the MySQL Workbench directory. 


c1title: Installing MySQL Workbench on Linux
c2content:
 3.3.4. Installing MySQL Workbench on Linux 3.3.4. Installing MySQL Workbench on Linux There are binary distributions of MySQL Workbench available for several variants of Linux, including Fedora, Oracle Linux, and Ubuntu. In addition to the binary distributions, it is also possible to download the MySQL Workbench source code as a tar.gz or RPM package. Check the MySQL Workbench download page for the latest packages. The procedure for installing on Linux depends on which Linux distribution you are using. Installing DEB packages On Ubuntu, and other systems that use the Debian package scheme, you can install MySQL Workbench using a command such as: shell&gt; sudo dpkg -i package .deb package .deb is the MySQL Workbench package name; for example, mysql-workbench-oss- version _i386.deb , where version is the MySQL Workbench version number. Note You may be warned that certain libraries are not available, depending on what you already have installed. Install the required libraries and then install the MySQL Workbench package again. Installing RPM packages On Red Hat-based systems, and other systems that use the RPM package format, MySQL Workbench can be installed by a command such as: shell&gt; sudo rpm -i package .rpm package .rpm is the MySQL Workbench package name; for example, mysql-workbench-oss- version -1fc10.x86_64.rpm , where version is the MySQL Workbench version number. 


c1title: EER Diagram Editor
c2content:
 7.6. EER Diagram Editor 7.6. EER Diagram Editor 7.6.1. The Vertical Toolbar EER diagrams are created by double-clicking the Add Diagram icon. You may create any number of EER diagrams just as you may create any number of physical schemata. Each EER diagram shows as a tab below the toolbar; a specific EER diagram is selected by clicking its tab. Clicking an EER diagram tab navigates to the canvas used for graphically manipulating database objects. The Vertical Toolbar is on the left side of this page. 


c1title: A PNG File of the sakila Database
c2content:
 7.8.4.1. A PNG File of the sakila Database 7.8.4.1. A PNG File of the sakila Database Find following an EER digram showing all the tables in the sakila database. This image was created using the File , Export , Export as PNG... menu item. Figure 7.45. The sakila Database EER Diagram The object notation style used in Figure 7.45, “The sakila Database EER Diagram” is Workbench (PKs only) . This notation shows only primary keys and no other columns, which is especially useful where space is at a premium. The relationship notation is the default, Crow's Foot. As the connection lines show, each table is related to at least one other table in the database (with the exception of the film_text table). Some tables have two foreign keys that relate to the same table. For example the film table has two foreign keys that relate to the language table, namely fk_film_language_original and fk_film_language . Where more than one relationship exists between two tables, the connection lines run concurrently. Identifying and nonidentifying relationships are indicated by solid and broken lines respectively. For example, the foreign key category_id is part of the primary key in the film_category table so its relationship to the category table is drawn with a solid line. On the other hand, in the city table, the foreign key, country_id , is not part of the primary key so the connection uses a broken line. 


c1title: Changes in MySQL Workbench 5.1.19 (06 September 2010)
c2content:
 A.2.1. Changes in MySQL Workbench 5.1.19 (06 September 2010) A.2.1. Changes in MySQL Workbench 5.1.19 (06 September 2010) This section documents all changes and bug fixes applied since the release of 5.1.18. Functionality Added or Changed In the Forward Engineer SQL Script wizard the check box Generate DROP SCHEMA now causes every CREATE SCHEMA statement to be prepended with DROP SCHEMA IF EXISTS `schemaname` . (Bug #46706) Bugs Fixed The Omit Schema Qualifier in Object Names option in the Forward Engineer SQL Script wizard appeared to have no effect. After selecting this option and proceeding through the wizard, the generated script still contained schema qualifiers. (Bug #46268) Synchronizing a model with a live database, without having made any changes to the model or the database, caused the model to appear as unsaved, indicating that unnecessary changes may have been made to the model. (Bug #40914) When synchronizing with a live database, if the direction of synchronization was changed to inbound, the script generated indicated that no inbound changes would be made. (Bug #40648) MySQL Workbench EER Diagram view did not permit the creation of a foreign key constraint on a primary key. (Bug #39546) 


c1title: The Model Notes Panel
c2content:
 7.5.7. The Model Notes Panel 7.5.7. The Model Notes Panel Use the Model Notes panel to write project notes. Any scripts or notes added will be saved with your project. 


c1title: Changes in MySQL Workbench 5.1.17 (14 August 2009)
c2content:
 A.2.3. Changes in MySQL Workbench 5.1.17 (14 August 2009) A.2.3. Changes in MySQL Workbench 5.1.17 (14 August 2009) This section documents all changes and bug fixes applied since the release of 5.1.16. Functionality Added or Changed Bug reported: If code with an error was entered into the Triggers tab of the Table Editor, the code disappeared when typing stopped. What actually happened was when a table name was given that was not that of the table currently being edited, the trigger code was moved to the table specified. MySQL Workbench has now been changed so that if a table name is specified other than other than that of the table being edited, then the table name is highlighted as a syntax error, rather than moving the trigger code to the table actually specified. (Bug #46349) When a model with multiple EER Diagrams was opened, all EER Diagrams would be displayed in tabs. This happened whether or not a EER Diagram had been displayed in a tab prior to saving the model. MySQL Workbench has been changed so that the EER Diagram tab state is saved, so that when a model is opened, only those EER Diagram tabs that were open on save are restored. This prevents unnecessary cluttering of the interface. (Bug #44454, Bug #50732) When a Text Object was placed on an EER Diagram it could not be resized and also did not appear to automatically resize correctly around any text entered. Text Objects on the EER Diagram canvas can now be resized by grabbing the sizing handles that appear when the object is selected. As with Table Objects, a manual modification of the object sets the manualSizing attribute of the Text Object to true . This property can also be set in the Properties pane. This means that these Text Objects automatically expand on entering more text, but the size isn't automatically reduced when text is removed or wrapped manually. By setting this property to false , the Text Object size is also automatically reduced to fit the containing text. (Bug #39887) In the Foreign Keys tab it was not possible to rename a foreign key by renaming the corresponding index entry. MySQL Workbench has been changed so that it is possible to rename a foreign key by renaming its corresponding index. The foreign key name is now automatically updated when the index is renamed. The index name is also updated when the foreign key name is changed. (Bug #39511) In MySQL Workbench it was not possible to generate an export script without schema information. MySQL Workbench has been changed to include the option Omit Schema Qualifier in Object Names . This can be found in the Forward Engineer SQL Script and Forward Engineer to Database wizards. Note that this does not change the script used in Procedures or Views. If you are using schema qualifiers in these locations you will have to remove them manually. (Bug #34827) The menu item Help , View Reported Bugs has been added to the main menu. This opens the bugs listing for MySQL Workbench in the default browser. (Bug #32813) Bugs Fixed When trying to connect to a server from MySQL Workbench, this error was generated: Connection 'Server' could not be established: No bool value passed for CLIENT_COMPRESS This occurred when using connections created in MySQL Workbench 5.2.1 with 5.2.2. (Bug #46635) On the EER Diagram, if an Undo operation was carried out after an Autosize operation, table objects were reduced to their minimum size. (Bug #46605) An Unknown Exception was caught after placing a relationship between two tables in the EER Diagram. The exception generated was: Unknown Exception caught in: c:\documents and settings\mysqldev\my documents\visual studio 2008\projects\workbench\backend\windows\wbprivate.wr\src\Wb.h at line 1026 (Bug #46562) In the Columns tab of the Table Editor, if a default value was added for a column, it could not then be removed. (Bug #46509) Calling the Plugins , Catalog , Dump All Table Columns item from the main menu generated this error: Error executing plugin wb.catalog.util.dumpColumns: error calling PyWbUtils.printAllColumns: 'str' object is not callable (Bug #46477) In the EER Diagram, if a layer was double-clicked a new tab was added to the Table Editor. However, if a relationship or table was double-clicked any existing tab would be reused, rather than a new tab being created. There appeared to be no consistent policy on how double-clicks should be handled. (Bug #46466) The INSERT statements generated for columns of type TEXT by the Insert Editor were not correct because the values were not quoted. Also, when the Insert Editor was closed and then reopened the last column entry was lost. (Bug #46390) When an attempt was made to synchronize Stored Procedures from the source database to MySQL Workbench, the Stored Procedures were deleted from the source database. (Bug #46346) If an attempt was made to load a new model file while a model file was already loaded, this error dialog was generated: OverviewBE::get_node: invalid node 1.1 (Bug #46292) When Plugins , Catalog , Give a Prefix to All Tables in Catalog , was selected from the main menu, MySQL Workbench crashed with this error: ** (mysql-workbench-bin:5898): WARNING **: /home/miguel/.mysql/workbench/wb_options.xml:325: link 'b7ee49b4-67f5-11de-9d1e-0800272fd858' &lt;object GrtObject&gt; key=owner could not be resolved ** Message: item_activated: 0xadbb608 -&gt; 'plugin:wb.file.newDocument' ** Message: unhandled message 4: wb.file.newDocument finished in 0.34s ** Message: item_activated: 0xaacbea8 -&gt; 'plugin:wb.util.prefixTables' glibmm-ERROR **: unhandled exception (type std::exception) in signal handler: what: request_input_becb not implemented aborting... Aborted This only happened when running on Linux. (Bug #46280) If the Table Editor had been invoked then the Text Boxes in the Tools , Preferences dialog became vertically misaligned. This only happened for MySQL Workbench running on Mac OS X. (Bug #46255) When an SQL Script was added and then its name changed, the name would erroneously revert back to “ Script ”. (Bug #46246) Reverse Engineering from a live database failed if the server had sql_mode set to ANSI_QUOTES . (Bug #46185) In the Columns tab of the Table Editor, selecting the AI check box before entering a name for the column caused MySQL Workbench to crash. (Bug #46150) The Microsoft Windows version of MySQL Workbench leaked GDI objects, resulting in a drop in performance. (Bug #46101) The text contained in a Text Object in an EER Diagram was syntax highlighted. This was not appropriate for a simple text note. (Bug #46092) When using the Reverse Engineer Database wizard a Segmentation Fault was generated by MySQL Workbench on Ubuntu Linux: (mysql-workbench-bin:22735): Gtk-CRITICAL **: gtk_tree_selection_get_selected: assertion `selection-&gt;type != GTK_SELECTION_MULTIPLE' failed ** Message: item_activated: 0x30d4920 -&gt; 'plugin:db.plugin.database.rev_eng' ** Message: unhandled message 4: db.plugin.database.rev_eng finished in 0,00s (Bug #46078) When writing code in the Routine Editor it appeared that the code was lost if the Routine Editor was closed. (Bug #46049) MySQL Workbench crashed if a table was selected, right-clicked, and then the menu item Copy SQL to Clipboard chosen. MySQL Workbench also crashed with the same model if an attempt was made to export the schema using the Forward Engineer SQL CREATE Script wizard. (Bug #46025) In the EER Diagram, when hovering the cursor over a column in a table, the hint box contained the text associated with the subsequent column, and the first column hint box contained the name of the table. (Bug #45997) The Synchronize Model with Database wizard contain a spelling mistake. The word “ synchronization ” was mispelled as “ synchronizatiob ”. (Bug #45939) If an attempt was made to copy and paste a trigger, the trigger code would revert to the source trigger, when the pasted trigger was edited. MySQL Workbench has been changed so that triggers are associated with the table in which they are edited. If a trigger has the wrong schema or table pointed to by its CREATE TRIGGER statement, it will be highlighted as a syntax error. (Bug #45931) MySQL Workbench 5.1.16 failed to create INSERTs in the exported DDL for some tables. (Bug #45920) MySQL Workbench crashed at startup on Mac OS X. (Bug #45869) When a model was synchronized with a live database, and only stored procedures needed to be synchronized, this error was generated: ERROR: Error 1046: No database selected (Bug #45867) In MySQL Workbench running on Mac OS X, if any changes were made in the Page Setup dialog, this error was generated: builtin:wb.page_setup Type mismatch: expected object of type app.PaperType, but got app.PaperType Note, the Page Setup dialog is accessed by selecting File , Page setup... from the main menu. (Bug #45861) The Forward Engineering SQL ALTER Script wizard generated DROP INDEX and ADD UNIQUE INDEX statements for any unique index, even for one that had not been modified. These unnecessary statements had to be manually deleted from the script. (Bug #45830) When compiling the MySQL Workbench source with GNU C Compiler (GCC) version 4.4.0, the compilation failed because the version of the Boost library used was not compatible with GCC 4.4.0. The version of the Boost library required for compatibility with GCC 4.4.0 is 1.37 or later. (Bug #45798) MySQL Workbench crashed and also lost procedure objects when attempting to synchronize with a live database. (Bug #45773) When building MySQL Workbench on PowerPC/PowerPC64 on Linux, the build failed because “ bswap32 ” was not defined. In file included from src/template_string.cc:47: src/base/arena.h: In member function 'void google::BaseArena::ReturnMemory(void*, size_t)': src/base/arena.h:211: warning: comparison between signed and unsigned integer expressions src/template_string.cc: In function 'uint32 UNALIGNED_LOAD32(const void*)': src/template_string.cc:120: error: 'bswap32' was not declared in this scope (Bug #45629) Relationship lines were not always drawn on the EER Diagram. (Bug #45583) During Forward Engineering, clicking the Copy to Clipboard button generated code that contained an extra newline per line. (Bug #45579) Attempts to rebuild the MySQL Workbench source RPM failed. The RPM appeared to contain an unmodified template mysql-workbench.spec.in instead of the correct spec file with variable placeholders replaced by actual values. When using the following command to rebuild the RPM: shell&gt; rpmbuild -ba --clean SPECS/mysql-workbench.spec.in This error was generated: error: File /usr/src/packages/SOURCES/mysql-workbench-oss-@VERSION@.tar.gz: No such file or directory Further, the spec file in the package had the incorrect suffix “ .spec.in ” instead of “ .spec ”. (Bug #45515) MySQL Workbench 5.1.13 running on Ubuntu Linux crashed when it attempted to load a model file created using MySQL Workbench 5.0 on Windows XP. The same model file did load correctly using MySQL Workbench 5.1.12. (Bug #45491) On Mac OS X, it was not possible to resize a Text Object on the EER Diagram canvas. (Bug #45472) See also Bug #39887. When synchronizing a model with a live database, clicking the Update Model actually caused the server to be updated as if Update Source had been clicked. (Bug #45456) The settings for ON UPDATE and ON DELETE in Foreign Key/Relationship Defaults set in the Model tab of Tools , Preferences , were not taken into account when new tables and relationships were created. (Bug #45393, Bug #45239) The Inserts Editor did not have functionality to remove a row once added. This problem only occurred with MySQL Workbench running on Linux. (Bug #44458) In the Columns tab of the Table Editor, if the column was of type ENUM and was given a default value, when an attempt was made to forward engineer the schema it would not validate. (Bug #44368) In the Forward Engineer SQL Script wizard, on the SQL Object Export Filter page, if Back was clicked to go to the SQL Export Options page, and then Next was clicked to return to the SQL Object Export Filter page, on that page all sections were duplicated. If this was repeated the objects were triplicated and so on. (Bug #44317) In the Columns tab of the Table Editor, when setting a column data type to ENUM it was not possible to choose Collation for the column details. Only the Table Default collation was available. (Bug #43352) In the Columns tab of the Table Editor, a column name could be entered with leading or trailing spaces. That led to this error when exporting the schema: ERROR 1166 (42000): Incorrect column name 'name ' (Bug #43345) The script created by Forward Engineer SQL CREATE Script failed with an error if the model contained a view that referenced a column defined in another view. (Bug #43061) In the Columns tab of the Table Editor, if a column is dragged and dropped to change its position, after the move the column highlighted is not the one moved. (Bug #42476) In the Columns tab of the Table Editor, if a column was deleted, and it had inserts in the Inserts tab, in the Inserts tab the last entry would be incorrectly deleted. (Bug #41931) In the Foreign Keys tab of the Table Editor, the values of the On Update and On Delete fields, in the Foreign Key Options pane, did not always refresh for each Foreign Key constraint selected in the table on the left side. For example, if the currently selected constraint was SET NULL for On Delete , and then a different selection was made for a constraint that has no action specified for On Delete , the field remained with the value from the previous selection, which gave a false indication that such action was specified in the definition of the newly selected constraint. Note that incorrect field values were only displayed when the last selected constraint did not have an action defined. (Bug #41887) When the flags of a User Defined Type were changed in the User Types panel, the change was not updated in the EER Diagram, the Table Editor, or the exported SQL. (Bug #41453) A model failed to synchronize with a live database because a column of type DOUBLE was exported as a type DOUBLE(256) . (Bug #41290) When a MySQL Workbench model was synchronized with a live database, a foreign key relationship, recently added to the database, was not reflected in the EER Diagram. Although the foreign key was created in the table object, the relationship connector widget was not drawn on the canvas. (Bug #41219) In the Columns tab of the Table Editor, when moving a column lower in the list of columns using drag and drop, the column was incorrectly placed one position below the point indicated by the position marker. (Bug #40641) When Connect to Columns was selected for the Relationship Notation option, the line connecting a foreign key to its referenced table was drawn to the incorrect column. (Bug #40627) When Help , About was selected from the main menu, it was not possible to copy MySQL Workbench version information to the clipboard. (Bug #39610) Foreign Key checks were not enabled before the standard inserts section of the script started. (Bug #35180) 


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


c1title: Changes in MySQL Workbench 5.1.18 (03 September 2009 General Availability)
c2content:
 A.2.2. Changes in MySQL Workbench 5.1.18 (03 September 2009 General Availability) A.2.2. Changes in MySQL Workbench 5.1.18 (03 September 2009 General Availability) This section documents all changes and bug fixes applied since the release of 5.1.17. Functionality Added or Changed The Column Editor has been updated to remove the feature whereby a column could be toggled to a primary key by double-clicking it. Primary key status can now only be set by selecting the appropriate check box in the adjacent Column Details frame. (Bug #46579) It was not possible to change column order by dragging and dropping columns in the Columns tab of the Table Editor. MySQL Workbench has been changed to enable you to drag and drop a column to change the column order as required. (Bug #40601) Bugs Fixed When editing a stored routine or trigger in the Table Editor, the cursor would relocate to the top of the editing window if a key was not pressed for a few seconds. Note On Windows this issue was fixed in 5.1.18. On Mac OS X this issue was fixed in 5.2.4. On Linux this issue was fixed in 5.2.7. (Bug #48156) MySQL Workbench generated an unhandled exception when using File , Export , Forward Engineer SQL CREATE Script . The exception was generated if an attempt was made to generate a script so that it wrote over a script already created. (Bug #47115) Clicking the Test Connection button in DB Connection Editor wizard did not appear to have any effect. (Bug #47083) MySQL Workbench crashed on launch on Mac OS X 10.6.0. (Bug #46953) When the data type of a table column was changed in the Table Editor, it was not reflected in the EER Diagram, although the tooltip was udpated correctly. This only happened in MySQL Workbench 5.1.17. (Bug #46940) In the Columns tab of the Table Editor, when the empty row at the end of the column list was right clicked, MySQL Workbench crashed with this error: ** (mysql-workbench-bin:15234): WARNING **: /tmp/sakila.mwbd1/document.mwb.xml:26: link '{591FC376-B82F-4F3D-B185-BA5C65B77080}' &lt;object workbench.Workbench&gt; key=owner could not be resolved ** Message: unhandled message 4: wb.file.openRecentModel finished in 0.58s glibmm-ERROR **: unhandled exception (type std::exception) in signal handler: what: Index out of range. aborting... Aborted (Bug #46937) The DDL was generated without foreign keys, regardless of whether the Skip generation of foreign keys option was turned on. (Bug #46875) In the Column tab of the Table Editor, if the NN check box was selected or deselected, the change was not immediately reflected in the EER Diagram, but was seen if some other operation caused the table object in the diagram to be refreshed. This also happened with the AI check box. (Bug #46869) The auto-completion of column names in the Table Editor completed names unnecessarily, requiring characters in the name to be manually deleted. This only happened on the Linux version of MySQL Workbench. (Bug #46847) The Esc key did not initiate the closing of an active dialog box. (Bug #46829) Editing of Text Objects did not work correctly. When Enter was hit, line feed did not move editing to the next line, and introduced a box character. (Bug #46789) The Forward Engineer SQL Script wizard generated invalid SQL code for a small model with foreign keys: SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0; SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0; SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='TRADITIONAL'; SET SQL_MODE=@OLD_SQL_MODE; SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS; SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS; (Bug #46787) MySQL Workbench did not export Foreign Keys when using the File , Export , Forward Engineer SQL CREATE Script wizard, even though the option Skip Creation of FOREIGN KEYS check box was cleared. Further, MySQL Workbench crashed when a column with a Foreign Key was added to a table. (Bug #46783) If the Default Storage Engine was selected as MyISAM in the Model Options dialog, when a new table was created in the EER Diagram it was found to have a storage engine type of InnoDB . (Bug #46752) When synchronizing with a live database, the script generated included drop statements that were placed in the wrong order, this led to the a schema being dropped after it was created. (Bug #46740) When a N:M identifying relationship was created on a single table, a foreign key name collision occurred - both keys were given the same name. MySQL Workbench has been changed so that key names have a trailing number added to avoid conflicts. (Bug #46363) MySQL Workbench generated an exception when the mouse wheel was used to move between tabs in the Table Editor: (mysql-workbench-bin:4864): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed glibmm-ERROR **: unhandled exception (type std::exception) in signal handler: what: invalid index aborting... Aborted (Bug #46304) When an EER Diagram contained tables or views with underscores in their names, the context menu associated with them displayed their names incorrectly in the menu. The underscores where displayed as accelerator keys in the context menu. (Bug #46302) The User Defined Types dialog, launched from Model , User Defined Types... on the main menu, did not permit user-defined types to be changed. Further, it appeared to be possible to edit the new user type in the User Types side panel, but no changes made there were retained. MySQL Workbench has been changed to permit User Types to be edited only from the User Defined Types dialog, and correct operation of this dialog has been restored. (Bug #45936) When editing a trigger, the trigger editor would automatically insert a delimiter during a pause in typing, and also relocate the cursor. (Bug #45929) In the Synchronize Model with Database dialog the text in the upper right area of the dialog did not wrap correctly, resulting in some text not being visible. (Bug #45455) The DBDoc documentation generation system did not support facilities for Stored Routines, Views and Triggers. (Bug #41589) After using the Help , Update... to upgrade MySQL Workbench, the application failed to start correctly. After the splash screen was displayed MySQL Workbench displayed an error dialog - “ MySQL Workbench has stopped working ”. (Bug #41460) In the Physical Schemata pane if more schema were added than could fit within the pane, these schema could not be viewed because there was no ability to scroll the pane. Further, double-clicking the schema in the Catalog pane did not locate the schema in the Physical Schemata pane. MySQL Workbench was changed so that a small down arrow button was added to the right side of the Physical Schemata tab bar. This provides a list to select a specific schema tab. (Bug #39735) When a diagram was exported as PNG it used the height and width of the model as displayed in the EER Diagram. This resulted in the exported picture being too small or too large, rather than being scaled to a consistent size. (Bug #36226) Printing of an EER Diagram did not work correctly if a table vertically spanned multiple pages. In this case pages would be printed up to and including the page that contained the first part of the table that spanned multiple pages, but the pages containing the remaining parts of the table would not be printed. This problem typically occurred when a table had more fields than could comfortably fit on a single page. (Bug #33919) 


c1title: Workbench Central
c2content:
 5.1. Workbench Central 5.1. Workbench Central Workbench Central enables you to keep up to date with MySQL Workbench news, events, and resources. You can read the developer blogs, find out what's new in the release, access the forums, check for updates, and file a bug report. Workbench Central includes the following facilities: What's new: A list of bug fixes and changes MySQL Doc Library: Built-in documentation MySQL Bug Reporter: Links to the MySQL bug system, where you can report bugs Workbench Team Blog: Links to the Workbench team blog Planet MySQL: Links to MySQL-related blogs and news Workbench forums: Links to the MySQL user and developer forums 


c1title: Create New EER Model
c2content:
 7.2. Create New EER Model 7.2. Create New EER Model Clicking this action item launches a new MySQL Model tab, with a blank model ready for you to work on. To read more about modeling, see Section 7.5, “Model Editor” . 


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


c1title: Chapter 10. Keyboard Shortcuts
c2content:
 Chapter 10. Keyboard Shortcuts Chapter 10. Keyboard Shortcuts The following tables list keyboard shortcuts for MySQL Workbench commands. Modifier in the tables stands for the platform-specific modifier key. This is Command on Mac OS X, Control on other platforms. On Mac OS X, the Alt key is Option . File Menu Function Context Keyboard Shortcut New Model All Modifier+N Open Model All Modifier+O Open SQL Script SQL Editor Modifier+Shift+O Close Tab All Modifier+W Save Model Model Modifier+S Save Script SQL Editor Modifier+S Save Model As Model Modifier+Shift+S Save Script As SQL Editor Modifier+Shift+S Forward Engineer SQL CREATE Script Model Modifier+Shift+G Forward Engineer SQL ALTER Script Model Modifier+Alt+Y Synchronize With SQL CREATE Script Model Modifier+Shift+Y Print EER Diagram mode only Modifier+P Exit All Modifer+Q Edit Menu Function Context Keyboard Shortcut Undo Model, EER Diagram Modifier+Z Redo Model, EER Diagram Modifier+Y, Modifier+Shift+Z (Mac OS X) Cut All Modifier+X Copy All Modifier+C Paste All Modifier+V Delete All Modifier+Delete, Command+BackSpace (Mac OS X) Edit Selected Model, EER Diagram Modifier+E Edit Selected in New Window Model, EER Diagram Modifier+Shift+E Select All EER Diagram Modifier+A Find All Modifier+F Find Advanced All Modifier+Alt+F Find Next All F3 Find Previous All Shift+F3 Search and Replace All Modifier+Shift+F View Menu Function Context Keyboard Shortcut Output Window All Modifier+F2, Modifier+Option+2 (Mac OS X) Set Marker n EER Diagram Modifier+Shift+n (n is integer 1..9) Go to Marker n EER Diagram Modifier+n (n is integer 1..9) Arrange Menu Function Context Keyboard Shortcut Bring to Front EER Diagram Modifier+Shift+F Send to Back EER Diagram Modifier+Shift+B Model Menu Function Context Keyboard Shortcut Add Diagram Model, EER Diagram Modifier+T Validate All Model, EER Diagram Modifier+Alt+V Validate All (MySQL) Model, EER Diagram Modifier+Alt+B Model Options Model, EER Diagram Command+Alt+, (Shorcut available only on Mac OS X) Query Menu Function Context Keyboard Shortcut Execute statement SQL Editor Modifier+Return Execute statements SQL Editor Modifier+Shift+Return New Tab SQL Editor Modifier+T Database Menu Function Context Keyboard Shortcut Query Database All Modifier+U Reverse Engineer Model, EER Diagram Modifier+R Forward Engineer Model, EER Diagram Modifier+G Synchronize Model Model, EER Diagram Modifier+Y Scripting menu Function Context Keyboard Shortcut Scripting Shell All Modifier+F3, Modifier+Option+3 (on Mac OS X) Run Workbench Script File All Modifier+Shift+R Help Menu Function Context Keyboard Shortcut Help Index All F1, Command+Option+question (on Mac OS X) EER Diagram Mode In the EER Diagram view, a number of other keyboard shortcuts are available. Function Keyboard Shortcut Selection tool Escape Hand tool H Delete tool D Layer tool L Note tool N Image tool I Table tool T View tool V Routine Group tool G Non-Identfying Relationship 1:1 1 Non-Identfying Relationship 1:n 2 Identifying Relationship 1:1 3 Identifying Relationship 1:n 4 Identifying Relationship n:m 5 Relationship Using Existing Columns 6 


c1title: Changes in MySQL Workbench 5.2.12 (Not released)
c2content:
 A.1.28. Changes in MySQL Workbench 5.2.12 (Not released) A.1.28. Changes in MySQL Workbench 5.2.12 (Not released) This section documents all changes and bug fixes applied since the release of 5.2.11. Functionality Added or Changed In the SQL Editor, if a table was edited with the Edit Data facility, and table values changed, no warning was given if an attempt was made to close the tab without having first applied changes using the apply button. MySQL Workbench has been changed so that if the user attempts to close a live editing tab, without having applied any changes made, a warning dialog is displayed. (Bug #49925) MySQL Workbench has been changed to permit a connection to be created where the password does not have to be stored. In this case, MySQL Workbench prompts the user to enter the correct password when the connection is established. (Bug #49409) Undo operations are no longer tracked in the editors that work with live databases, such as table editors within the SQL Editor. (Bug #49284) Bugs Fixed Security Fix : The password for the connected MySQL Server was exposed by the SQL Administrator in MySQL Workbench. The password was displayed in plain text form in the Startup Message Log on the Startup tab of the Admin page. (Bug #43287) In SQL Editor, SELECT statements that called functions, for example SELECT md5('abcd') , did not give the expected result. (Bug #50248) In the Table Editor, the list for selecting the table engine type contained a reference to calpont . This should now be infinidb . (Bug #50159) In Mac OS X, the context-sensitive menu was missing from the live editing tab of the SQL Editor. Right-clicking in the editing tab simply displayed a Mac OS X menu, rather than the context-sensitive menu to enable actions such as copying, deletion and setting selections to NULL . (Bug #50114) Custom Python modules failed to load and were not displayed in the MySQL Workbench Plugins menu. In MySQL Workbench 5.2 the syntax used has changed from @wbplugin to @ModuleInfo.Plugin . (Bug #50108) On the Model page, if some text was entered into a note in Model Notes, and then the model was saved and closed, on reloading the note would be empty. This also happened for a script added in SQL Scripts. After the model was saved and reloaded, the script would be empty. (Bug #50108) The script code generated from a model for routines did not quote schema names in USE statements. (Bug #50051) Lower panels such as the Table Editor remained open, even when the user returned to the Home screen. (Bug #49926) In the SQL Editor, when using the Query , Export Results... menu item, the file extension was omitted when selection of an existing output file was made. (Bug #49870) After selecting Edit Table Data from the Home screen, and launching the Edit Table Data wizard, MySQL Workbench crashed if a connection was selected and then the Next button clicked. (Bug #49864) In the Manage DB Connections dialog, when attempting to create a Standard TCP/IP over SSH connection, errors occurred when testing the connection in the case where a key file had been specified. If the path to the key file was quoted the error was: Cannot open SSH Tunnel: ERROR Invalid request If the same path was not quoted the error generated was: Could not connect SSH tunnel: ERROR [Errno 22] invalid mode ('r') or filename: 'D:\\Documents and Settings\\tf221715\\.ssh\\id_dsa' It should be noted that currently only key files using the OpenSSH format are supported. (Bug #49812) In the SQL Editor, if a Stored Procedure was executed and then immediately executed again, this error was generated: Error code 2014 Commands out of sync; you can't run this command now This problem only affected MySQL Workbench running on the Mac OS X platform. (Bug #49553) Right-clicking a Routine Group and then selecting Copy SQL to Clipboard did not work. No code was copied to the clipboard. (Bug #49440) Opening a model file, closing it and quickly reopening it caused MySQL Workbench to hang. (Bug #49428) Clicking the Test Connection button in the Manage DB Connections dialog caused MySQL Workbench to lock up. The error generated on the console was: 18743 INFO Connecting to SSH server at 127.0.0.1:22... Unhandled exception in thread started by &lt;bound method Tunnel._threadloop of &lt;__main__.Tunnel instance at 0x9acea8&gt;&gt; This happened for the connection method Standard TCP/IP over SSH. (Bug #49419) Two SSH tunnels were opened for a single connection to an SSH server. The user was also prompted for a password when a new connection was established, even when the existing tunnel was reused. (Bug #49412) SSH Tunnels opened by MySQL Workbench were never closed. SSH Tunnels created when clicking Test Connection in the Manage DB Connections dialog, were not closed. This was also the case when the SQL Editor and Server Administration tabs were closed. (Bug #49411) In the Partitioning tab of the alter table dialog it was possible to enter a number greater than 10 into the Partition Count textfield. However, when these changes were applied the DDL generated substituted any value entered that was greater than 10 with the value 2. (Bug #49380) MySQL Workbench generated an unhandled exception when trying to add a new column using the Alter Table facility in the SQL Editor. After the VARCHAR(45) column was added, without selecting any column check boxes, the exception occurred when the Apply button was clicked. (Bug #49364) If a database was reversed engineered from a source, and a table renamed, then although this change was detected by MySQL Workbench, no DDL code was generated if an attempt was then made to synchronize this change with the source. (Bug #49313) In the SQL Editor, when a schema was dropped, it was still displayed in the Overview tab and in the schemata explorer of the side panel. Further, MySQL Workbench did not provide any confirmation that the schema had been dropped successfully or otherwise. (Bug #49282) The Alter Schema dialog in the SQL Editor permitted the schema name to be changed using the Name textfield, even though doing this is not supported at the server level. (Bug #49281) In the SQL Editor, if an item in the History tab was right-clicked, and the menu option Append selected items to SQL script selected, MySQL Workbench generated an unhandled exception: glibmm-ERROR **: unhandled exception (type std::exception) in signal handler: what: vector::_M_range_check (Bug #49245) In the Create a new server instance wizard, if the check box Enable SSH login based administration was cleared, the wizard still prompted the user to enter an SSH password when the Next button was clicked. (Bug #49226) In the Server Status section of the Admin page, the SYSTEM graphic showed CPU usage at 50%, while the corresponding text label showed CPU usage at 0%. The graphic and label remained out of synchronization for around 15 seconds. (Bug #49212) In the SQL Editor if an EDIT table operation was being carried out, it appeared that data in the table was not updated, and also a row already inserted would be erroneously deleted when attempting to add a new row of data, when changes were applied. MySQL Workbench has been changed so that if an error occurs during changes being applied, an error dialog is displayed showing any errors that occurred. Also, the status text is now updated to say “ Apply Failed ”, rather than “ Changes Applied ”. (Bug #49179) The Manage DB Connections dialog did not prevent duplicate connection names or an empty string as a valid connection name. (Bug #49150) The toolbar buttons on the Home screen did not reflect the order of the action items in the Workspace. The Open Server Profile button and Open DB Connection Manager buttons needed to exchange positions. (Bug #49149) In the Logs tab of the Administrator, the Oldest and Newest buttons appeared to have reversed functionality. Oldest displayed the most recent timestamps and Newest displayed the oldest. (Bug #49065) In the Manage DB Connections dialog, many textfield labels appeared truncated. (Bug #49052, Bug #49378) The ID for a connection was displayed in the Connections tab of the Admin page, even after the corresponding administration session had been closed. (Bug #48989) The Connections list in the Manage Server Instances dialog did not display the user name for socket and pipe connections. For example it displayed Localhost - @:0 &lt;Local Socket/Pipe&gt; , rather than Localhost - root@:0 &lt;Local Socket/Pipe&gt; . (Bug #48969) Various errors occurred when attempting to modify the server configuration using the Configuration tab of the Administrator: Unhandled exception: global name 'tempfile' is not defined Unhandled exception: [Errno 22] Invalid argument: 'C:\\users\\tax\\appdata\\local\\temp\\tmpo47ttn' Also, if the Logs tab was selected to view the server log files, this error occurred: Unhandled exception: Error executing 'Select @ @ log_output': Unknown system variable 'log_output' (Bug #48906) In the Forward Engineer an ALTER Script wizard, the textfields and associated buttons for selecting input and output files were not positioned correctly within the window, when the selected file name was long. Although the files could be selected when the wizard was first launched, if the wizard was launched subsequently, the text fields would be filled with the previously selected file names, causing the textfields and Browse buttons to be located beyond the borders of the window. A similar problem also affected the Forward Engineer SQL Script wizard. (Bug #48222) In the Partitioning tab of the Alter Schema dialog, it was not possible to create a single partition. If a partition count of 1 was specified this was actually set to 2 in the generated DDL. (Bug #48114) When performing a Synchronize Model operation, all foreign key relationships in the EER diagram that had the setting draw split were redrawn as fully visible . (Bug #47767) When running MySQL Workbench from the command line, it could not open model files where the path contained a space. (Bug #46297) 


c1title: Documenting the sakila Database
c2content:
 7.8.4. Documenting the sakila Database 7.8.4. Documenting the sakila Database 7.8.4.1. A PNG File of the sakila Database This chapter highlights the capabilities of MySQL Workbench as a documentation tool using the sakila database as an example. This is a sample database provided by MySQL that you can find by visiting the http://dev.mysql.com/doc/ page, selecting the Other Docs tab, and looking in the Example Databases section An EER diagram is an invaluable aid to a quick understanding of any database. There is no need to read through table definition statements; glancing at an EER diagram can immediately indicate that various tables are related. You can also see how tables are related; what the foreign keys are and what the nature of the relationship is. 


c1title: Server Administration and Configuration
c2content:
 8.7. Server Administration and Configuration 8.7. Server Administration and Configuration 8.7.1. The Startup Tab 8.7.2. The Configuration Tab 8.7.3. The Accounts Tab 8.7.4. The Connections Tab 8.7.5. The Variables Tab 8.7.6. The Data Dump Tab 8.7.7. The Logs Tab The Administrator functionality in MySQL Workbench is grouped into several tabs: Startup : Enables you to start and stop the MySQL server, and view the startup message log Configuration : Enables you to view and edit the MySQL Configuration file ( my.ini or my.cnf ) using GUI controls Accounts : Enables you to create user accounts and assign roles and privileges Connections : Displays connections to MySQL Server Variables : Displays system and status variables Data Dump : Import and export of data Logs : Displays server log file entries The Administrator also displays system and server status. System status includes: CPU utilization Memory usage Connection Health For server health, the following are displayed: Connection Usage Traffic Query Cache Hit Rate Key Efficiency Figure 8.3. MySQL Workbench - Admin Page 


c1title: Creating a Catalog Diff Report
c2content:
 7.7.10.4. Creating a Catalog Diff Report 7.7.10.4. Creating a Catalog Diff Report This facility enables you to create a report detailing the differences between your MySQL Workbench model, and a live database or script. Choose Database , Generate Catalog Diff Report from the main menu to run the Compare and Report Differences in Catalogs wizard. The first step in the wizard is to specify which catalogs to compare. For example, you may wish to compare your live database against your current MySQL Workbench model. Figure 7.40. Catalog Sources You then proceed through the wizard, providing connection information if accessing a live database. The wizard then produces a catalog diff report showing the differences between the compared catalogs. Figure 7.41. Catalog Diff Report 


c1title: The Database Menu
c2content:
 7.5.1.6. The Database Menu 7.5.1.6. The Database Menu The Database menu has these items: Query Database : Launches the SQL Editor, which enables you to create SQL code and execute it on a live server. For more information, see Section 6.7, “SQL Editor” . Manage Connections : Launches the Manage DB Connections dialog, which enables you to create and manage multiple connections. For more information, see Section 6.6, “Manage DB Connections Dialog” Reverse Engineer : Creates a model from an existing database. For more information, see Section 7.7.9.2, “Reverse Engineering a Live Database” . Forward Engineer : Creates a database from a model. For more information, see Section 7.7.10.2, “Forward Engineering to a Live Server” . Synchronize Model : Synchronizes your database model with an existing database. For more information, see Section 7.7.10.3, “Database Synchronization” . Generate Catalog Diff Report : Compares your schema model with a live database or a script file. Section 7.7.10.4, “Creating a Catalog Diff Report” . 


c1title: Changes in MySQL Workbench 5.1.6 (Not yet released)
c2content:
 A.2.14. Changes in MySQL Workbench 5.1.6 (Not yet released) A.2.14. Changes in MySQL Workbench 5.1.6 (Not yet released) This section documents all changes and bug fixes applied since the release of 5.1.5. Functionality Added or Changed MySQL Workbench has been changed so that layers and tables listed in the Layers palette are sorted in alphabetic order, making it easier to find the required object. (Bug #39781) Bugs Fixed A dialog displayed a message with a missing file name. The message displayed was: Import of SQL script file '' has finished successfully. Note the file name is missing from the message. This dialog is located in the File , Import , Reverse Engineer SQL CREATE Script wizard. It is displayed on the page after importing the file, clicking Next and then Execute . (Bug #39922) The Advanced button displayed the text label &amp;Advanced . This button is located in the File , Import , Reverse Engineer SQL CREATE Script wizard. It is displayed on the page after importing the file. (Bug #39921) 


c1title: Chapter 2. MySQL Workbench Editions
c2content:
 Chapter 2. MySQL Workbench Editions Chapter 2. MySQL Workbench Editions The Community Edition (OSS) The Community Edition is the foundation of all MySQL Workbench editions—versions that are currently available or those that will become available in the future. All editions of MySQL Workbench are based on the Community Edition and all future improvements to the base framework and feature set will be included in this version. The Community Edition is a full feature product that puts a powerful database management tool into the hands of the MySQL community. The Standard Edition The Standard Edition is a commercial extension that builds on top of the OSS Edition and adds modules and plugins, enabling an optimized work flow. The highlights of this edition are: MySQL Specific Schema Validation Model Validation General Schema Validation DBDoc DBDoc provides the following features: Document complex database schemata Document all SQL object types Document output available in different file formats A comparison of edition features can be found at MySQL Workbench Developer Central . 


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


c1title: Adding Views to an EER Diagram
c2content:
 7.7.3.2. Adding Views to an EER Diagram 7.7.3.2. Adding Views to an EER Diagram Views can also be added to an EER Diagram using the View tool on the vertical toolbar. Make sure that the EER Diagram tab is selected, then left-click the view icon on the vertical toolbar. The view icon is the two overlapping rectangles found below the table icon. Clicking this icon changes the mouse pointer to a view pointer. To change the mouse pointer to a view pointer from the keyboard, use the V key. Choosing the View tool changes the contents of the toolbar that appears immediately below the main menu bar. When the Views pointer is active, this toolbar contains a schemata list and a color chart list. Use these lists to select the appropriate schema and color accent for the new view. Make sure that you associate the new view with a database. The color of your view can be changed using the Properties palette. Create a view by clicking anywhere on the EER Diagram canvas. This creates a new view with the default name view1 . To revert to the default mouse pointer, click the arrow icon at the top of the vertical toolbar. Right-clicking a view opens a pop-up menu. With the exception of the delete item, these menu items function as described in Section 7.7.3.1, “Adding Views to the Physical Schemata” . The behavior of the delete option is determined by your MySQL Workbench options settings. For more information, see Section 5.4.4, “The Model Tab” . 


c1title: Manage Security
c2content:
 8.4. Manage Security 8.4. Manage Security This action item takes you quickly to the page that enables you to manage user accounts. It launches an Admin page and locates you on the Accounts tab. For further details, see Section 8.7.3, “The Accounts Tab” . 


c1title: Python License
c2content:
 B.19. Python License B.19. Python License The following software may be included in this product: Python Programming Language This is the official license for the Python 2.7 release: A. HISTORY OF THE SOFTWARE Python was created in the early 1990s by Guido van Rossum at Stichting Mathematisch Centrum (CWI, see http://www.cwi.nl) in the Netherlands as a successor of a language called ABC. Guido remains Python's principal author, although it includes many contributions from others. In 1995, Guido continued his work on Python at the Corporation for National Research Initiatives (CNRI, see http://www.cnri.reston.va.us) in Reston, Virginia where he released several versions of the software. In May 2000, Guido and the Python core development team moved to BeOpen.com to form the BeOpen PythonLabs team. In October of the same year, the PythonLabs team moved to Digital Creations (now Zope Corporation, see http://www.zope.com). In 2001, the Python Software Foundation (PSF, see http://www.python.org/psf/) was formed, a non-profit organization created specifically to own Python-related Intellectual Property. Zope Corporation is a sponsoring member of the PSF. All Python releases are Open Source (see http://www.opensource.org for the Open Source Definition). Historically, most, but not all, Python releases have also been GPL-compatible; the table below summarizes the various releases. Release Derived Year Owner GPL- from compatible? (1) 0.9.0 thru 1.2 1991-1995 CWI yes 1.3 thru 1.5.2 1.2 1995-1999 CNRI yes 1.6 1.5.2 2000 CNRI no 2.0 1.6 2000 BeOpen.com no 1.6.1 1.6 2001 CNRI yes (2) 2.1 2.0+1.6.1 2001 PSF no 2.0.1 2.0+1.6.1 2001 PSF yes 2.1.1 2.1+2.0.1 2001 PSF yes 2.2 2.1.1 2001 PSF yes 2.1.2 2.1.1 2002 PSF yes 2.1.3 2.1.2 2002 PSF yes 2.2.1 2.2 2002 PSF yes 2.2.2 2.2.1 2002 PSF yes 2.2.3 2.2.2 2003 PSF yes 2.3 2.2.2 2002-2003 PSF yes 2.3.1 2.3 2002-2003 PSF yes 2.3.2 2.3.1 2002-2003 PSF yes 2.3.3 2.3.2 2002-2003 PSF yes 2.3.4 2.3.3 2004 PSF yes 2.3.5 2.3.4 2005 PSF yes 2.4 2.3 2004 PSF yes 2.4.1 2.4 2005 PSF yes 2.4.2 2.4.1 2005 PSF yes 2.4.3 2.4.2 2006 PSF yes 2.5 2.4 2006 PSF yes 2.5.1 2.5 2007 PSF yes 2.5.2 2.5.1 2008 PSF yes 2.5.3 2.5.2 2008 PSF yes 2.6 2.5 2008 PSF yes 2.6.1 2.6 2008 PSF yes 2.6.2 2.6.1 2009 PSF yes 2.6.3 2.6.2 2009 PSF yes 2.6.4 2.6.3 2010 PSF yes 2.7 2.6 2010 PSF yes Footnotes: (1) GPL-compatible doesn't mean that we're distributing Python under the GPL. All Python licenses, unlike the GPL, let you distribute a modified version without making your changes open source. The GPL-compatible licenses make it possible to combine Python with other software that is released under the GPL; the others don't. (2) According to Richard Stallman, 1.6.1 is not GPL-compatible, because its license has a choice of law clause. According to CNRI, however, Stallman's lawyer has told CNRI's lawyer that 1.6.1 is "not incompatible" with the GPL. Thanks to the many outside volunteers who have worked under Guido's direction to make these releases possible. B. TERMS AND CONDITIONS FOR ACCESSING OR OTHERWISE USING PYTHON PYTHON SOFTWARE FOUNDATION LICENSE VERSION 2 -------------------------------------------- 1. This LICENSE AGREEMENT is between the Python Software Foundation ("PSF"), and the Individual or Organization ("Licensee") accessing and otherwise using this software ("Python") in source or binary form and its associated documentation. 2. Subject to the terms and conditions of this License Agreement, PSF hereby grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use Python alone or in any derivative version, provided, however, that PSF's License Agreement and PSF's notice of copyright, i.e., "Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006 Python Software Foundation; All Rights Reserved" are retained in Python alone or in any derivative version prepared by Licensee. 3. In the event Licensee prepares a derivative work that is based on or incorporates Python or any part thereof, and wants to make the derivative work available to others as provided herein, then Licensee hereby agrees to include in any such work a brief summary of the changes made to Python. 4. PSF is making Python available to Licensee on an "AS IS" basis. PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON WILL NOT INFRINGE ANY THIRD PARTY RIGHTS. 5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. 6. This License Agreement will automatically terminate upon a material breach of its terms and conditions. 7. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between PSF and Licensee. This License Agreement does not grant permission to use PSF trademarks or trade name in a trademark sense to endorse or promote products or services of Licensee, or any third party. 8. By copying, installing or otherwise using Python, Licensee agrees to be bound by the terms and conditions of this License Agreement. BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0 ------------------------------------------- BEOPEN PYTHON OPEN SOURCE LICENSE AGREEMENT VERSION 1 1. This LICENSE AGREEMENT is between BeOpen.com ("BeOpen"), having an office at 160 Saratoga Avenue, Santa Clara, CA 95051, and the Individual or Organization ("Licensee") accessing and otherwise using this software in source or binary form and its associated documentation ("the Software"). 2. Subject to the terms and conditions of this BeOpen Python License Agreement, BeOpen hereby grants Licensee a non-exclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use the Software alone or in any derivative version, provided, however, that the BeOpen Python License is retained in the Software, alone or in any derivative version prepared by Licensee. 3. BeOpen is making the Software available to Licensee on an "AS IS" basis. BEOPEN MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, BEOPEN MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT INFRINGE ANY THIRD PARTY RIGHTS. 4. BEOPEN SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THE SOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. 5. This License Agreement will automatically terminate upon a material breach of its terms and conditions. 6. This License Agreement shall be governed by and interpreted in all respects by the law of the State of California, excluding conflict of law provisions. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between BeOpen and Licensee. This License Agreement does not grant permission to use BeOpen trademarks or trade names in a trademark sense to endorse or promote products or services of Licensee, or any third party. As an exception, the "BeOpen Python" logos available at http://www.pythonlabs.com/logos.html may be used according to the permissions granted on that web page. 7. By copying, installing or otherwise using the software, Licensee agrees to be bound by the terms and conditions of this License Agreement. CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1 --------------------------------------- 1. This LICENSE AGREEMENT is between the Corporation for National Research Initiatives, having an office at 1895 Preston White Drive, Reston, VA 20191 ("CNRI"), and the Individual or Organization ("Licensee") accessing and otherwise using Python 1.6.1 software in source or binary form and its associated documentation. 2. Subject to the terms and conditions of this License Agreement, CNRI hereby grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use Python 1.6.1 alone or in any derivative version, provided, however, that CNRI's License Agreement and CNRI's notice of copyright, i.e., "Copyright (c) 1995-2001 Corporation for National Research Initiatives; All Rights Reserved" are retained in Python 1.6.1 alone or in any derivative version prepared by Licensee. Alternately, in lieu of CNRI's License Agreement, Licensee may substitute the following text (omitting the quotes): "Python 1.6.1 is made available subject to the terms and conditions in CNRI's License Agreement. This Agreement together with Python 1.6.1 may be located on the Internet using the following unique, persistent identifier (known as a handle): 1895.22/1013. This Agreement may also be obtained from a proxy server on the Internet using the following URL: http://hdl.handle.net/1895.22/1013". 3. In the event Licensee prepares a derivative work that is based on or incorporates Python 1.6.1 or any part thereof, and wants to make the derivative work available to others as provided herein, then Licensee hereby agrees to include in any such work a brief summary of the changes made to Python 1.6.1. 4. CNRI is making Python 1.6.1 available to Licensee on an "AS IS" basis. CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 1.6.1 WILL NOT INFRINGE ANY THIRD PARTY RIGHTS. 5. CNRI SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON 1.6.1 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 1.6.1, OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. 6. This License Agreement will automatically terminate upon a material breach of its terms and conditions. 7. This License Agreement shall be governed by the federal intellectual property law of the United States, including without limitation the federal copyright law, and, to the extent such U.S. federal law does not apply, by the law of the Commonwealth of Virginia, excluding Virginia's conflict of law provisions. Notwithstanding the foregoing, with regard to derivative works based on Python 1.6.1 that incorporate non-separable material that was previously distributed under the GNU General Public License (GPL), the law of the Commonwealth of Virginia shall govern this License Agreement only as to issues arising under or with respect to Paragraphs 4, 5, and 7 of this License Agreement. Nothing in this License Agreement shall be deemed to create any relationship of agency, partnership, or joint venture between CNRI and Licensee. This License Agreement does not grant permission to use CNRI trademarks or trade name in a trademark sense to endorse or promote products or services of Licensee, or any third party. 8. By clicking on the "ACCEPT" button where indicated, or by copying, installing or otherwise using Python 1.6.1, Licensee agrees to be bound by the terms and conditions of this License Agreement. ACCEPT CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2 -------------------------------------------------- Copyright (c) 1991 - 1995, Stichting Mathematisch Centrum Amsterdam, The Netherlands. All rights reserved. Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Stichting Mathematisch Centrum or CWI not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Licenses and Acknowledgements for Incorporated Software ======================================================== This section is an incomplete, but growing list of licenses and acknowledgements for third-party software incorporated in the Python distribution. Mersenne Twister ================ The _random module includes code based on a download from http://www.math.keio.ac.jp/ matumoto/MT2002/emt19937ar.html. The following are the verbatim comments from the original code: A C-program for MT19937, with initialization improved 2002/1/26. Coded by Takuji Nishimura and Makoto Matsumoto. Before using, initialize the state by using init_genrand(seed) or init_by_array(init_key, key_length). Copyright (C) 1997 - 2002, Makoto Matsumoto and Takuji Nishimura, All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The names of its contributors may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Any feedback is very welcome. http://www.math.keio.ac.jp/matumoto/emt.html email: matumoto@math.keio.ac.jp Sockets ======= The socket module uses the functions, getaddrinfo(), and getnameinfo(), which are coded in separate source files from the WIDE Project, http://www.wide.ad.jp/. Copyright (C) 1995, 1996, 1997, and 1998 WIDE Project. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. Neither the name of the project nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS "AS IS" AND GAI_ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE FOR GAI_ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON GAI_ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN GAI_ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Floating point exception control ================================ The source for the fpectl module includes the following notice: --------------------------------------------------------------------- / Copyright (c) 1996. \ | The Regents of the University of California. | | All rights reserved. | | | | Permission to use, copy, modify, and distribute this software for | | any purpose without fee is hereby granted, provided that this en- | | tire notice is included in all copies of any software which is or | | includes a copy or modification of this software and in all | | copies of the supporting documentation for such software. | | | | This work was produced at the University of California, Lawrence | | Livermore National Laboratory under contract no. W-7405-ENG-48 | | between the U.S. Department of Energy and The Regents of the | | University of California for the operation of UC LLNL. | | | | DISCLAIMER | | | | This software was prepared as an account of work sponsored by an | | agency of the United States Government. Neither the United States | | Government nor the University of California nor any of their em- | | ployees, makes any warranty, express or implied, or assumes any | | liability or responsibility for the accuracy, completeness, or | | usefulness of any information, apparatus, product, or process | | disclosed, or represents that its use would not infringe | | privately-owned rights. Reference herein to any specific commer- | | cial products, process, or service by trade name, trademark, | | manufacturer, or otherwise, does not necessarily constitute or | | imply its endorsement, recommendation, or favoring by the United | | States Government or the University of California. The views and | | opinions of authors expressed herein do not necessarily state or | | reflect those of the United States Government or the University | | of California, and shall not be used for advertising or product | \ endorsement purposes. / --------------------------------------------------------------------- MD5 message digest algorithm ============================ The source code for the md5 module contains the following notice: Copyright (C) 1999, 2002 Aladdin Enterprises. All rights reserved. This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software. Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions: 1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required. 2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software. 3. This notice may not be removed or altered from any source distribution. L. Peter Deutsch ghost@aladdin.com Independent implementation of MD5 (RFC 1321). This code implements the MD5 Algorithm defined in RFC 1321, whose text is available at http://www.ietf.org/rfc/rfc1321.txt The code is derived from the text of the RFC, including the test suite (section A.5) but excluding the rest of Appendix A. It does not include any code or documentation that is identified in the RFC as being copyrighted. The original and principal author of md5.h is L. Peter Deutsch &lt;ghost@aladdin.com&gt;. Other authors are noted in the change history that follows (in reverse chronological order): 2002-04-13 lpd Removed support for non-ANSI compilers; removed references to Ghostscript; clarified derivation from RFC 1321; now handles byte order either statically or dynamically. 1999-11-04 lpd Edited comments slightly for automatic TOC extraction. 1999-10-18 lpd Fixed typo in header comment (ansi2knr rather than md5); added conditionalization for C++ compilation from Martin Purschke &lt;purschke@bnl.gov&gt;. 1999-05-03 lpd Original version. Asynchronous socket services ============================ The asynchat and asyncore modules contain the following notice: Copyright 1996 by Sam Rushing All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Sam Rushing not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. SAM RUSHING DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL SAM RUSHING BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Cookie management ================= The Cookie module contains the following notice: Copyright 2000 by Timothy O'Malley &lt;timo@alum.mit.edu&gt; All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Timothy O'Malley not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. Timothy O'Malley DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL Timothy O'Malley BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Profiling ========= The profile and pstats modules contain the following notice: Copyright 1994, by InfoSeek Corporation, all rights reserved. Written by James Roskind Permission to use, copy, modify, and distribute this Python software and its associated documentation for any purpose (subject to the restriction in the following sentence) without fee is hereby granted, provided that the above copyright notice appears in all copies, and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of InfoSeek not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. This permission is explicitly restricted to the copying and modification of the software to remain in Python, compiled Python, or other languages (such as C) wherein the modified or derived code is exclusively imported into a Python module. INFOSEEK CORPORATION DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL INFOSEEK CORPORATION BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Execution tracing ================= The trace module contains the following notice: portions copyright 2001, Autonomous Zones Industries, Inc., all rights... err... reserved and offered to the public under the terms of the Python 2.2 license. Author: Zooko O'Whielacronx http://zooko.com/ mailto:zooko@zooko.com Copyright 2000, Mojam Media, Inc., all rights reserved. Author: Skip Montanaro Copyright 1999, Bioreason, Inc., all rights reserved. Author: Andrew Dalke Copyright 1995-1997, Automatrix, Inc., all rights reserved. Author: Skip Montanaro Copyright 1991-1995, Stichting Mathematisch Centrum, all rights reserved. Permission to use, copy, modify, and distribute this Python software and its associated documentation for any purpose without fee is hereby granted, provided that the above copyright notice appears in all copies, and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of neither Automatrix, Bioreason or Mojam Media be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. UUencode and UUdecode functions =============================== The uu module contains the following notice: Copyright 1994 by Lance Ellinghouse Cathedral City, California Republic, United States of America. All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Lance Ellinghouse not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. LANCE ELLINGHOUSE DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL LANCE ELLINGHOUSE CENTRUM BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Modified by Jack Jansen, CWI, July 1995: - Use binascii module to do the actual line-by-line conversion between ascii and binary. This results in a 1000-fold speedup. The C version is still 5 times faster, though. - Arguments more compliant with Python standard XML Remote Procedure Calls¶ The xmlrpclib module contains the following notice: The XML-RPC client interface is Copyright (c) 1999-2002 by Secret Labs AB Copyright (c) 1999-2002 by Fredrik Lundh By obtaining, using, and/or copying this software and/or its associated documentation, you agree that you have read, understood, and will comply with the following terms and conditions: Permission to use, copy, modify, and distribute this software and its associated documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies, and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Secret Labs AB or the author not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. SECRET LABS AB AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANT- ABILITY AND FITNESS. IN NO EVENT SHALL SECRET LABS AB OR THE AUTHOR BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. test_epoll ========== The test_epoll contains the following notice: Copyright (c) 2001-2006 Twisted Matrix Laboratories. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Select kqueue ============= The select and contains the following notice for the kqueue interface: Copyright (c) 2000 Doug White, 2006 James Knight, 2007 Christian Heimes All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. strtod and dtoa =============== The file Python/dtoa.c, which supplies C functions dtoa and strtod for conversion of C doubles to and from strings, is derived from the file of the same name by David M. Gay, currently available from http://www.netlib.org/fp/. The original file, as retrieved on March 16, 2009, contains the following copyright and licensing notice: /**************************************************************** * * The author of this software is David M. Gay. * * Copyright (c) 1991, 2000, 2001 by Lucent Technologies. * * Permission to use, copy, modify, and distribute this software for * any purpose without fee is hereby granted, provided that this entire * notice is included in all copies of any software which is or * includes a copy or modification of this software and in all copies * of the supporting documentation for such software. * * THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR * IMPLIED WARRANTY. IN PARTICULAR, NEITHER THE AUTHOR NOR LUCENT * MAKES ANY REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE * MERCHANTABILITY OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR * PURPOSE. * ***************************************************************/ 


c1title: Changes in MySQL Workbench 5.0.25 (12 September 2008)
c2content:
 A.3.6. Changes in MySQL Workbench 5.0.25 (12 September 2008) A.3.6. Changes in MySQL Workbench 5.0.25 (12 September 2008) This section documents all changes and bug fixes applied since the release of 5.0.24. Bugs Fixed If the user closed all tabs and then quit, Workbench crashed. (Bug #39346) Foreign keys referencing a deleted table were not removed. (Bug #39150) Forward Engineer SQL CREATE Script and Forward Engineer SQL ALTER Script generated scripts that did not put index names in quotation marks. (Bug #39140) When Workbench was started with the GRT Shell tab opened, the object tree in the GRT Tree pane was not displayed. (Bug #39122) When triggers were exported with the Generate DROP TABLES statements option checked, DROP TRIGGER IF EXISTS did not appear in the exported SQL. (Bug #39119) The Triggers tab would always enable Insert mode when opened. (Bug #39118) In the Foreign Key tab of the Table Editor , the menu that is displayed on clicking in the Referenced Table column, listed table names by creation date, rather than by sorted name. (Bug #38944) If any DEFAULT properties were defined for a model, they appeared to be lost after saving the model and restarting Workbench. (Bug #38825) When you loaded a UTF-8 encoded script file into Workbench, the embedded SQL editor replaced international characters with the ? symbol. (Bug #38783) When creating Views and Routines, the entry in the Undo History window showed “ Parse MySQL View ” instead of “ View Created ”, and “ Parse MySQL Routine ” instead of “ Routine Created ”. When subsequently undoing this operation the correct text was displayed. Performing a redo then resulted in the incorrect text being displayed again. Additionally, when undoing a Routine Group, the previous undo action in the history was incorrectly renamed and the last entry in the history was deleted. (Bug #36047) In the Table Editor tab, wherever data could be entered, such as in the Foreign Key Name entry field, the default wrap protocol was to go to a new line. This resulted in text that was only partially visible. (Bug #34510) The synchronization wizard could show a diff tree for schemata different from those that had been selected. (Bug #32365) 


c1title: TreeViewAdv for .NET License
c2content:
 B.23. TreeViewAdv for .NET License B.23. TreeViewAdv for .NET License The following software may be included in this product: TreeViewAdv for .NET The BSD License Copyright (c) 2009, Andrey Gliznetsov (a.gliznetsov@gmail.com) All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met - Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. - Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation andor other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 


c1title: Changes in MySQL Workbench 5.0.14abeta (28 February 2008)
c2content:
 A.3.17. Changes in MySQL Workbench 5.0.14abeta (28 February 2008) A.3.17. Changes in MySQL Workbench 5.0.14abeta (28 February 2008) This unscheduled beta release fixes bug#34847. Other bug fixes applied since the release of 5.0.14beta are also documented. Bugs Fixed MWB files were not saved properly if Workbench crashed. Reopening such files caused Workbench to crash. (Bug #34848) See also Bug #34847. Workbench models created in version 5.0.13 crashed when used with version 5.0.14. The unscheduled Beta release, 5.0.14a fixes this bug. (Bug #34847) When clicking the Browse button in the image editor, the default file name was openFileDialog1 . This now defaults to an empty string. (Bug #34622) Repeatedly changing the object notation crashed Workbench. This is no longer repeatable. (Bug #34499) Importing a DBDesigner file immediately threw an exception. This happened even when software rendering was used. DBDesigner files can now be imported without incident. (Bug #33588) 


c1title: Printing Options
c2content:
 7.9.1. Printing Options 7.9.1. Printing Options The printing menu items not enabled unless an EER Diagram is active. These items are available: Page Setup... Enables you to choose the paper size, orientation, and margins. Print Sends your EER Diagram directly to the printer. This option generates a preview before printing. From the preview you can adjust the scale of the view and also choose a multi-page view. Clicking the printer icon at the top left of this window, prints the currently selected EER Diagram. Close the print preview window if you need to adjust the placement of objects on the EER Diagram canvas. Print to PDF... Creates a PDF file of your EER Diagram. Print to PS... Creates a PostScript file of your EER Diagram. 


c1title: Changes in MySQL Workbench 5.0.20 (26 April 2008)
c2content:
 A.3.11. Changes in MySQL Workbench 5.0.20 (26 April 2008) A.3.11. Changes in MySQL Workbench 5.0.20 (26 April 2008) This section documents all changes and bug fixes applied since the release of 5.0.19. Bugs Fixed Re-creating a deleted relationship caused a crash. (Bug #36385) The message log on the Forward Engineer Progess/Results Advanced dialog had no scroll bar. (Bug #36192) 


c1title: Adding a Table
c2content:
 7.8.3.1. Adding a Table 7.8.3.1. Adding a Table The tools in the vertical toolbar on the left of the EER Diagram tab are used for designing an EER diagram. Start by creating a table using the table tool. The table tool is the rectangular grid in the middle of the vertical toolbar. Mousing over it shows the message, Place a New Table (T) . Clicking this tool changes the mouse pointer to a hand with a rectangular grid. Create a table on the canvas by clicking anywhere on the EER Diagram grid. Right-click the table and choose Edit in New Window from the pop-up menu. This opens the table editor, docked at the bottom of the application. The table name defaults to table1 . Change the name by entering invoice into the Name: field. Changes here affect the name of the tab in the table editor and the name of the table on the canvas. Pressing Tab or Enter while the cursor is in the table name field selects the Columns tab of the table editor and creates a default column named idinvoice . Pressing Tab or Enter again sets the focus on the Datatype list with INT selected. Notice that a field has been added to the table on the EER canvas. Pressing Tab yet again and the focus shifts to adding a second column. Add a Description and a Customer_id column. When you are finished, close the table editor, by clicking the x button on the top left of the table editor. 


c1title: Changes in MySQL Workbench 5.1.9 (Not yet released Beta)
c2content:
 A.2.11. Changes in MySQL Workbench 5.1.9 (Not yet released Beta) A.2.11. Changes in MySQL Workbench 5.1.9 (Not yet released Beta) This section documents all changes and bug fixes applied since the release of 5.1.8. Bugs Fixed In Model View after performing Edit , Select , Select All , it was not then possible to undo the operation. (Bug #43225) When a script was processed by File , Import , Reverse Engineer MySQL CREATE Script , columns with a boolean data type had their data type ignored. As a result, the type of the column in the Table Editor was empty. (Bug #43094) 


c1title: The Help Menu
c2content:
 7.5.1.10. The Help Menu 7.5.1.10. The Help Menu 7.5.1.10.1. System Info The Help menu has the following items. Use them to go online and learn more about MySQL Workbench. Help Index : Opens a window showing the MySQL Workbench documentation. Read, search, or print the documentation from this window. Check For Updates : Opens your default browser on the MySQL Workbench Web site and checks for a newer version. Update : Updates to the latest version. MySQL.com Website : Opens your default browser on the MySQL Web site home page. Workbench Product Page : Opens your default browser on the MySQL Workbench product page. System Info : Displays information about your system, which is useful when reporting a bug. For more information, see Section 7.5.1.10.1, “System Info” . Report a Bug : Opens your default browser on the MySQL bug report page. View Reported Bugs : Opens your default browser to see a list of current bugs. About Workbench : Displays the MySQL Workbench About window. 7.5.1.10.1. System Info Use the System Info menu item to display information about your system. This item is especially useful for determining your rendering mode. Sample output follows. read_mysql_cfg_file C:\Program Files\MySQL\MySQL Server 5.1\my.ini [('tmp_table_size', '9M'), ('myisam_sort_buffer_size', '18M'), ('table_cache', '256'), ('read_rnd_buffer_size', '256K'), ('port', '3306'), ('max_connections', '100'), ('innodb_buffer_pool_size', '18M'), ('myisam_max_sort_file_size', '100G'), ('sql-mode', '"STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"'), ('basedir', '"C:/Program Files/MySQL/MySQL Server 5.1/"'), ('default-character-set', 'latin1'), ('datadir', '"C:/ProgramData/MySQL/MySQL Server 5.1/Data/"'), ('innodb_log_buffer_size', '1M'), ('innodb_log_file_size', '10M'), ('innodb_thread_concurrency', '8'), ('read_buffer_size', '64K'), ('innodb_additional_mem_pool_size', '2M'), ('thread_cache_size', '8'), ('innodb_flush_log_at_trx_commit', '1'), ('query_cache_size', '0'), ('sort_buffer_size', '256K'), ('default-storage-engine', 'INNODB'), ('key_buffer_size', '11M')] MySQL Workbench OSS for Windows version 5.2.8 Cairo Version: 1.8.6 Rendering Mode: GDI requested (create a diagram to confirm) OpenGL Driver Version: Not Detected OS: unknown CPU: Intel(R) Core(TM)2 Duo CPU T9300 @ 2.50GHz, 1.0 GB RAM Video adapter info: Adapter type: VirtualBox Graphics Adapter Chip Type: VBOX BIOS String: Version 0xB0C2 or later Video Memory: 12288 KB 


c1title: Changes in MySQL Workbench 5.2.10 (01 December 2009)
c2content:
 A.1.30. Changes in MySQL Workbench 5.2.10 (01 December 2009) A.1.30. Changes in MySQL Workbench 5.2.10 (01 December 2009) This section documents all changes and bug fixes applied since the release of 5.2.9. Functionality Added or Changed MySQL Workbench now has the command line option --version , which is used to display the version of the application, when launching the application from the command line. (Bug #49136) The Help , Workbench Product Page menu item launched the default web browser, but displayed an outdated product page. This was due to a web server configuration issue. MySQL Workbench now displays the correct, up-to-date product page. (Bug #49066) Bugs Fixed When using Alter Table in the SQL Editor, if a column name was changed, and the Apply button clicked, the Apply Object Changes wizard was launched. The Review changes page indicated that the script that would be applied would drop the altered column then add a new column with the new name. This led to column data being lost because the script should instead have used CHANGE COLUMN , to change the name of the column. (Bug #49286) When using Alter Table in the SQL Editor, if a table name was changed, and the Apply button clicked, the Apply Object Changes wizard was launched. The Review changes page indicated that the script that would be applied would incorrectly create a new table as a duplicate of the table being renamed, rather than use ALTER to rename the table. (Bug #49275) In the configuration editor, in the Admin tab, the Discard button simply unchecked all options, rather than just those that had been checked during the current editing session. This made the button appear to have a “ clear all ” function, rather than the expected “ revert changes ” function. (Bug #49234) When using the Forward Engineer SQL CREATE Script wizard, if the check box Omit Schema Qualifier in Object Names was selected, the script code for views was omitted. (Bug #49153) In the Administrative Roles tab of Server Access Management , selection of Roles did not work correctly. For example, selecting the DBA check box, and then deselecting it, caused all roles to be deselected. Further, using the Revert button resulted in the selected user disappearing from the User Accounts panel. (Bug #49071) MySQL Workbench did not handle signed and unsigned integers correctly. For example, if performing a synchronization between a model and a live database where the only difference was a column was declared to be of type INTEGER in one case and UNSIGNED INTEGER in the other, the difference would not be detected and the ALTER script would imply the databases were the same. (Bug #49063) A MySQL configuration file caused MySQL Workbench to crash, when an attempt was made to view it in the configuration editor of the Admin tab. The error generated was: Unhandled exception: 'bool' object has no attribute 'strip' (Bug #49060, Bug #49602) In the SQL Editor, two buttons on the toolbar had no tooltips. These were the green check or tick mark, and the red back arrow buttons. Further, they did not seem to become enabled or disabled according to the context, making it difficult to determine their intended function. (Bug #49059) On the MySQL Config File page of the New Server Profile wizard, clicking Check section generated an exception if there were options in the MySQL configuration file that did not have values assigned: Check if mysqld section exists in /tmp/my.cnf ** Message: function call error Traceback (most recent call last): File "/usr/lib/mysql-workbench/modules/wb_admin_grt.py", line 292, in testInstanceSettingByName parser.read([config_file]) File "/usr/lib/python2.5/ConfigParser.py", line 267, in read self._read(fp, filename) File "/usr/lib/python2.5/ConfigParser.py", line 490, in _read raise e ConfigParser.ParsingError: File contains parsing errors: /tmp/my.cnf [line 2]: 'log-bin\n' glibmm-ERROR **: unhandled exception (type std::exception) in signal handler: what: error calling WbAdmin.testInstanceSettingByName: see output for details (Bug #49057, Bug #47954) On the Admin screen, the server configuration option Key buffer , was located under the General tab, rather than the MyISAM Parameters tab, even though it was a MyISAM -only option. (Bug #49017) In the configuration editor in the Admin tab, the lists for displaying units, such as for the Sort buffer size option, did not show 'G', which represents Gigabytes. This bug was fixed in 5.2.10. It was subsequently decided to standardize all units around uppercase characters. In particular the 'k' was changed to 'K'. This change was made in version 5.2.13. (Bug #49013) In the SQL Editor, the database explorer of the Schemata palette in the side panel did not work correctly. Incorrect behavior included random collapsing of expanded databases and occasional crashing. (Bug #48981) When using the data modeler, MySQL Workbench extended vertically to the maximum size of the screen, overlapping the dock, and thereby making it impossible to use. (Bug #48976) In the Manage Server Instances dialog, if the Server Instances list pane was empty, then on creating a new Server Instance, it was not possible to change the instance's name. The instance had to be created, the dialog closed. On reopening the dialog, the instance could be renamed. (Bug #48967) The Generate Catalog Diff Report feature did not permit the comparison of imported scripts because selecting the radio button for this option had no effect. (Bug #47230) If a collation was changed for a table in the Table Editor, there was no facility to then set this back to the schema default. A new entry has been now been added to the collation selection list: Schema Default . (Bug #46513) When a model containing stored routines was forward engineered to a script, the script contained an erroneous additional delimiter after each stored routine. This resulted in a “ No query specified ” error when an attempt was made to run the script on a server. (Bug #39929) 


c1title: Forward Engineering to a Live Server
c2content:
 7.7.10.2. Forward Engineering to a Live Server 7.7.10.2. Forward Engineering to a Live Server Use forward engineering to export your schema design to a MySQL server. Select the schema that you wish to forward engineer and then choose the Database , Forward Engineer... menu item from the main menu. The first page to be displayed is Catalog Validation (validation is available only in the Standard Edition). Figure 7.28. Catalog Validation Click Run Validations to validate the catalog. Click Next to continue. The next page enables you to set options for the database to be created. These options are as described in Section 7.7.10.1.1, “Creating a Schema” . Figure 7.29. Options Select the required options and then click Next . The next page enables you to select the objects to forward engineer. Figure 7.30. Select Objects to Forward Engineer To select a subset of objects to forward engineer, use the Show Filter / Hide Filter button, then select specific objects. After you have selected your objects, click Next to continue On the Review Script page you may review and edit the SQL script that will be executed. Figure 7.31. Review Script Click Next to continue if you are satisfied with the generated script. The next step of the process is to connect to a MySQL server in order to create the new database schema. This page enables you to use a previously stored connection, or enter the connection parameters. Figure 7.32. Set Parameters for Connecting to a DBMS After the connection parameters have been set, click Execute . The next page of the wizard displays the results of the forward engineering process. Figure 7.33. Forward Engineering Progress You can confirm that the script created the schema by connecting to the target MySQL server and issuing a SHOW DATABASES statement. 


c1title: Results Tabsheets
c2content:
 6.7.4.5. Results Tabsheets 6.7.4.5. Results Tabsheets The results area of the screen shows the results from any queries that have been executed. If the script contains multiple queries, a result tab will be generated for each query that returns results. Figure 6.10. SQL Editor - Results Tabsheets Controls are provided to enable you to easily move over the results. These are shown in the following screenshot. Figure 6.11. SQL Editor - Results Tabsheets Navigation Controls From left to right, the controls are: Move to first row : Highlights the first row in the current result set. Move to previous row : Highlights the previous row. Move to next row : Highlights the next row. Move to last row : Highlights the last row in the current result set. Toggle wrapping of cell contents : Toggles between truncating or wrapping the data in a cell. Sort Ascending : Sorts the selected column in ascending order. Sort Descending : Sorts the selected column in descending order. Export record set to an external file : Writes a result set to a CSV, HTML, or XML file as required. Refresh Data from Data Source : Refreshes the current result set from the data source. Search for substring within data : Searches the data for the string entered in the search box. 


c1title: The Physical Schemata Panel
c2content:
 7.5.4. The Physical Schemata Panel 7.5.4. The Physical Schemata Panel 7.5.4.1. The Schema Objects Panel The Physical Schemata panel of the MySQL Model page shows the active schemata and the objects that they contain. Expand and contract the Physical Schemata section by double-clicking the arrow on the left of the Physical Schemata title bar. When the Physical Schemata section is expanded, it displays all currently loaded schemata. Each schema shows as a tab. To select a specific schema, click its tab. When MySQL Workbench is first opened, a default schema, mydb , is selected. You can start working with this schema or you can load a new MySQL Workbench Models file ( mwb extensiona.) There are a variety of ways to add schema to the Physical Schemata panel. You can open an MWB file, reverse engineer a MySQL create script, or, if you are using a commercial version of MySQL Workbench, you can reverse engineer a database by connecting to a MySQL server. You can also add a new schema by clicking the + button on the top right of the Physical Schemata panel. To remove a schema, click its tab and use the - button found to the immediate left of the + button. To the left of these buttons are three buttons that control how database object icons are displayed: The left button displays database objects as large icons. The middle button displays small icons in multiple rows. The right button displays small icons in a single list. 


c1title: Changes in MySQL Workbench 5.2.4 (07 October 2009)
c2content:
 A.1.36. Changes in MySQL Workbench 5.2.4 (07 October 2009) A.1.36. Changes in MySQL Workbench 5.2.4 (07 October 2009) This section documents all changes and bug fixes applied since the release of 5.2.3. Functionality Added or Changed Some keyboard shortcuts have been changed. On Microsoft Windows and Linux Control+Y is now used for Redo. Mac OS X continues to use Command+Shift+Z as its default for Redo. For Synchronize Model, Control+Alt+Y is used on Windows and Linux, and Command+Control+Y is used on Mac OS X. (Bug #46285) Bugs Fixed When editing a stored routine or trigger in the Table Editor, the cursor would relocate to the top of the editing window if a key was not pressed for a few seconds. Note On Windows this issue was fixed in 5.1.18. On Mac OS X this issue was fixed in 5.2.4. On Linux this issue was fixed in 5.2.7. (Bug #48156) If a new empty EER diagram was created, then Model , Relationship Notation , Connect to Columns was selected, MySQL Workbench generated these messages: ** Message: item_activated: 0x28d5cf0 -&gt; 'plugin:wb.view.setRelationshipNotation:fromcolumn' ** Message: unhandled message 4: wb.view.setRelationshipNotation finished in 0.00s These messages were not generated if the EER diagram contained at least one table. (Bug #47565) When a model was synchronized, this incorrect SQL was generated: CREATE TABLE IF NOT EXISTS `synthescom`.`adx_clienti` ( `id` INT(11) UNSIGNED NOT NULL AUTO_INCREMENT , `citta` VARCHAR(100) NULL DEFAULT NULL , `provincia` VARCHAR(100) NULL DEFAULT NULL , PRIMARY KEY (`id`) ENGINE = MyISAM DEFAULT CHARACTER SET = utf8 COLLATE = utf8_general_ci; Note that the closing parenthesis, which should have been located after the PRIMARY KEY statement, is missing. Thats resulted in this error being generated: ERROR: Error 1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'ENGINE = MyISAM DEFAULT CHARACTER SET = utf8 COLLATE = utf8_general_ci' at line 13 (Bug #47407) When a table was opened for editing in the Query Editor, the DECIMAL column values appeared in the result set as integer values, disregarding precision and scale settings. The fractional part of the number was discarded. It was also not possible to add the fractional part of the number during editing. (Bug #47405) In the EER Diagram, Layer names were not rendered. This only happened with OpenGL rendering (only on Microsoft Windows). (Bug #47385) When the Query Database menu option was selected, the explorer on the right-hand side displayed Tables, Views and Routines, but when the Routines folder was expanded the routines contained in the model were missing. (Bug #47088) Clicking the Test Connection button in DB Connection Editor wizard did not appear to have any effect. (Bug #47083) In the Query Editor, when an attempt was made to expand a schema and select a table, this exception was generated: ************** Exception Text ************** System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. at MySQL.Grt.TreeModel.expand_node(NodeId node) at MySQL.Grt.GrtTreeModel.TreeViewExpanding(Object sender, TreeViewAdvEventArgs e) at System.EventHandler`1.Invoke(Object sender, TEventArgs e) at Aga.Controls.Tree.TreeViewAdv.OnExpanding(TreeNodeAdv node) at Aga.Controls.Tree.TreeViewAdv.SetIsExpanded(TreeNodeAdv node, Boolean value) at Aga.Controls.Tree.TreeViewAdv.SetIsExpanded(ExpandArgs eargs) at Aga.Controls.Tree.TreeViewAdv.SetIsExpanded(TreeNodeAdv node, Boolean value, Boolean ignoreChildren) ... (Bug #47044) On Mac OS X using cmd + backspace to delete a column in the table editor did not work. (Bug #46613) In the Synchronize Model with Database dialog the text in the upper right area of the dialog did not wrap correctly, resulting in some text not being visible. (Bug #45455) MySQL Workbench EER Diagram view did not permit the creation of a foreign key constraint on a primary key. (Bug #39546) 


c1title: Administering a MySQL Server
c2content:
 4.1. Administering a MySQL Server 4.1. Administering a MySQL Server In this section, you will use MySQL Workbench to carry out administrative functions, such as starting and stopping the server. Launch MySQL Workbench. You will be presented with the Home window. Figure 4.1. Getting Started Tutorial - Home Window To administer your MySQL Server, you must first create a Server Instance. The instance contains information about the target server, including how to connect to it. From the MySQL Workbench Home window, click New Server Instance . The Create New Server Instance Profile wizard will be displayed. In this tutorial, you will connect to a locally installed server, so click Next . Figure 4.2. Getting Started Tutorial - Specify Host Machine Next you will set up a connection, or select an existing connection to use to connect to the server. Assuming that you have not already created a connection, you can use the default values here, although if your MySQL Server has a password set for the root account, you can enter it here by clicking Store in Vault. This enables you to connect to the server without needing to enter a password each time. It is also possible to use a different account to connect to the server by setting the user name and password here, if required. Figure 4.3. Getting Started Tutorial - Database Connection You can now click Next . The connection will now be tested. You should see that the connection was successful. If not click Back and check that you have entered the information required. Figure 4.4. Getting Started Tutorial - Connection Test If the connection test was successful, click Next . Optionally, you may configure a method for remote management if a Remote Host was specified. Setting these options enables MySQL Workbench to determine the location of configuration files, and the correct start and stop commands to use for the server. SSH login based management and Native Windows remote management types are available. The Operating System and MySQL Installation Type are configured for the SSH login variant. Figure 4.5. Getting Started Tutorial - Management and OS Set the configuration method, then click Next . If the SSH login based management was chosen, then you will configure its parameters which includes the User Name, Host Name, and optionally the SSH key for authentication. Figure 4.6. Getting Started Tutorial - SSH Configuration Check that everything is in order, then click Next . If a Windows server is used, then the Windows configuration parameters must be set. Figure 4.7. Getting Started Tutorial - Windows Management Check that everything is in order, then click Next . The wizard will now check that it is able to access the MySQL Server configuration file, and access the start and stop commands. Figure 4.8. Getting Started Tutorial - Test Host Settings Check that everything is in order, then click Next . You now have a chance to review the configuration settings so far. The information displayed varies slightly depending on platform, connection method and installation type. Figure 4.9. Getting Started Tutorial - Review Settings Review the information, then click Next . Finally you can give the server instance a suitable name. This will be used to select this particular instance from a list of available instances. Figure 4.10. Getting Started Tutorial - Instance Name Set the desired name, then click Finish to complete the server instance creation process. You will now be returned to the Home window. You will see the new server instance you created, along with the new connection you created as part of the preceding procedure. Figure 4.11. Getting Started Tutorial - Home Window Instance You are now ready to test your new server instance. From the Home window, double-click the Server Instance you created. The Administrator will open on the Startup configuration page. Figure 4.12. Getting Started Tutorial - Admin Startup Click the Stop Server button. The message window will show that the server has stopped. Click the Start Server button to resume the server. The message window will confirm that the server is running. You have now seen how to create a server instance to enable you to manage a MySQL server. For further information, see Chapter 8, Server Administration . 


c1title: History Tabsheet
c2content:
 6.7.4.3. History Tabsheet 6.7.4.3. History Tabsheet The History tabsheet provides a history of SQL operations carried out. The time and SQL code for each operation is recorded. To view the SQL executed, click the time, and the SQL code executed will be displayed in the SQL column. 


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


c1title: The Image Tool
c2content:
 7.6.1.6. The Image Tool 7.6.1.6. The Image Tool Use the image tool to place an image on the canvas. When this tool is selected and you click the canvas, a dialog box opens enabling you to select the desired graphic file. To activate the image tool from the keyboard, use the I key. For more information about images, see Section 7.7.8, “Creating Images” . 


c1title: Modifying a Layer Using the Properties Palette
c2content:
 7.7.5.2. Modifying a Layer Using the Properties Palette 7.7.5.2. Modifying a Layer Using the Properties Palette When you select a layer on the EER Diagram canvas, its properties are displayed in the Properties palette. The properties accessible from the Properties palette apply to the appearance of a layer on the EER Diagram canvas. In some circumstances, you may want to make a layer invisible. Select the layer and, in the Properties palette, set the visible property to False . To locate an invisible object, open the Layers palette and select the object by double-clicking it. After an object is selected, you can reset the visible property from the Properties palette. For a list of properties accessible through the Properties palette, see Section 7.5.12, “The Properties Palette” . In addition to the properties listed there, a layer also has a description property. Use this property to document the purpose of the layer. 


c1title: Create EER Model from SQL Script
c2content:
 7.4. Create EER Model from SQL Script 7.4. Create EER Model from SQL Script This action item enables you to create a model from an SQL Create script. Such a script may have been created by hand or as a result of reverse engineering an existing database. The script may then be modified according to requirements. Clicking this action item launches the Reverse Engineer SQL Script wizard. This is a multi-stage wizard that enables you to select the script you want to create your model from. For further information, see Section 7.7.9.1, “Reverse Engineering Using a Create Script” . 


c1title: The Logs Tab
c2content:
 8.7.7. The Logs Tab 8.7.7. The Logs Tab The Logs tab features two subtabs: General Slow Query Log The General tab shows entries from the server's general log file. The Slow Query Log tab displays entries from the server's slow query log file. Figure 8.12. Administrator - Logs Tab 


c1title: Sidebar
c2content:
 6.7.5. Sidebar 6.7.5. Sidebar 6.7.5.1. Connection Information Panel 6.7.5.2. Object Browser The Sidebar contains these panels: Connection Information Panel Object Browser The following sections describe each panel in more detail. 


c1title: Adding a GUI to a Plugin Using MForms
c2content:
 9.4. Adding a GUI to a Plugin Using MForms 9.4. Adding a GUI to a Plugin Using MForms MySQL Workbench is implemented with a C++ core back-end, and a native front-end for each supported platform. Currently the front-end is implemented with Windows Forms on Microsoft Windows, GTK+ on Linux, and Cocoa on Mac OS X. This approach permits the application to have a native look and feel, while reducing the amount of work required to maintain the project. However, the GUI functionality required by MySQL Workbench can be met by a subset of graphical operations. These are implemented in a cross-platform GUI library, MForms. This further reduces the development effort because plugin developers can use MForms rather than writing front-end specific code for each supported platform. This also helps consistency of operation across all platforms. MForms is coded in C++, but provides a Python interface. To use it, the Python code must import the mforms module. MForms Containers Given the problems of using an absolute coordinate system across different platforms, MForms employs containers that perform automatic layout. The basic containers that MForms provides include: Form : A top-level window which can contain a single control, usually another container. The window will be sized automatically to fit its contents, but can also be sized statically. Box : This is a container that can be filled with one or more controls in a vertical or horizontal layout. Each child control can be set to use either the minimum of required space, or fill the box in the direction of the layout. In the direction perpendicular to the layout, for example vertical in a horizontal layout, the smallest possible size that can accommodate all child controls will be employed. So, in this example, the smallest height possible to accommodate the controls would be used. Table : This is a container that can organize one or more controls in a grid. The number of rows and columns in the table, and the location of controls within the grid, can be set by the developer. ScrollView : This is a container that can contain a single child control, and will add scrollbars if the contents do not fit the available space. 


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


c1title: Creating a New Table
c2content:
 7.8.2.1. Creating a New Table 7.8.2.1. Creating a New Table Create a new table by double-clicking the Add Table icon in the Physical Schemata panel. This opens the table editor docked at the bottom of the application. If you wish, you can undock or dock this editor in exactly the same way as the schema editor window. Use the first tab of the table editor to change the name, collation, and engine. You may also add a comment. Add columns to the new table by selecting the Columns tab. Use the default column name or enter a new name of your choosing. Use the Tab key to move to the next column and set the column's data type. Altering the table by adding indexes or other features is also easily done using the table editor. 


c1title: The Layers Palette
c2content:
 7.5.11. The Layers Palette 7.5.11. The Layers Palette 7.5.11.1. Finding Invisible Objects Using the Layers Palette This palette shows all the layers and figures that have been placed on an EER diagram. If a layer or figure is currently selected, an X appears beside the name of the object and its properties are displayed in the Properties palette. This can be especially useful in determining which objects are selected when you have selected multiple objects using the various options under the Select menu item. For more information on this topic, see Section 7.5.1.2, “The Edit Menu” . Selecting an object in the Layers palette also adjusts the view port to the area of the canvas where the object is located. 


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


c1title: The Text Tool
c2content:
 7.6.1.5. The Text Tool 7.6.1.5. The Text Tool The text tool is the square icon with a capital N in the top left corner. Use this tool to place text objects on the EER diagram canvas. Click the tool, then click the desired location on the canvas. After a text object has been dropped on the canvas, the mouse pointer reverts to its default. To add text to a text object, right-click the text object and choose Edit Note... or Edit in New Window... from the pop-up menu. You can manipulate the properties of a text object by selecting it and then changing its properties in the Properties panel. To activate the text tool from the keyboard, use the N key. For more information about text objects, see Section 7.7.7, “Creating Text Objects” . 


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


c1title: Advanced Export Options
c2content:
 8.7.6.3. Advanced Export Options 8.7.6.3. Advanced Export Options The Advanced Export Options tab contains a number of options to enable you to control the export operation. These options control the SQL generated during the operation. Figure 8.11. Administrator - Advanced Options 


c1title: Object Browser
c2content:
 6.7.5.2. Object Browser 6.7.5.2. Object Browser The Object Browser contains an Actions list and a Schemata list, as seen in the following screenshot. Figure 6.14. SQL Editor - Object Browser Object Browser Actions List The Object Browser contains an Actions list. The actions are: Execute SQL File : Opens a file chooser dialog that enables you to select an SQL script to execute. Add Schema : Enables you to add a new schema to your server. Add Table : Enables you to create a new table via the new_table dialog. Add View : Enables you to create a new view via the new_view dialog. Add Routine : Enables you to create a new routine via the new_routine dialog. Schemata List The Schemata list shows available schemata on the currently connected server. These can be explored to show tables, views, and routines within the schema. Figure 6.15. SQL Editor - Schemata Explorer It is possible to set a schema as the default schema by right-clicking the schema and selecting the Set As Default Schema menu item. This executes a USE schema_name statement so that subsequent statements without schema qualifiers are executed against this schema. This setting applies only to the query session. To set a default schema for multiple MySQL Workbench sessions, you must set the default schema for the stored connection. From the Home screen, click Manage Connections , then in the Manage DB Connection dialog, set the desired default schema on the Parameters tab. A useful feature that was introduced in MySQL Workbench 5.2.9 is the ability to rapidly enter table, view, or column names into the SQL Statement area. Double-clicking a table, view, or column name in the schemata explorer inserts the name into the SQL Query area. This reduces typing significantly when entering SQL statements containing references to several tables, views, or columns. The Object Browser also features a context menu which can be displayed by right-clicking an object. For example, right-clicking a table displays the following menu items: Select Rows - Limit 1000 : Pulls up to 1000 rows of table data from the live server into a Results tabsheet. Edit Table Data : Pulls table data from the live server into a named tabsheet, and enables editing. Data can be saved directly to the live server. Copy to Clipboard : There are various submenus, each of which copies information to the clipboard: Name (short): Copies the table name. Name (long): Copies the qualified table name in the form `schema`.`table` . Column Names: Copies qualified column names the form `table`.`column1`, `table`.`column2`,... . Select All Statement: Copies a statement to select all columns in this form: SELECT `table`.`column1`, `table`.`column2`, ... FROM `schema`.`table`; Insert Statement: Copies an INSERT statement to insert all columns. Update Statement: Copies an UPDATE statement to update all columns. Delete Statement: Copies a DELETE statement in the form DELETE FROM `world`.`country` WHERE &lt;where_condition&gt;; . Send to SQL Editor : Provides functionality similar to Copy to Clipboard. However, this item inserts the SQL code directly into the SQL Query panel, where it can be edited further as required. Alter Table : Displays the table editor loaded with the details of the table. Create Table : Launches a dialog to enable you to create a new table. Drop Table : Drops the table. All data in the table will be lost if this operation is carried out. Refresh All : Refreshes all schemata in the explorer by resynchronizing with the server. Right-clicking an empty area inside the object browser displays the following menu items: Create Schema : Enables you to create a new schema on the connected server. You can apply your changes to synchronize with the live server by clicking the Apply button. Refresh All : Synchronizes with the live server to update the information displayed by the schemata explorer. 


c1title: Chapter 7. Data Modeling
c2content:
 Chapter 7. Data Modeling Chapter 7. Data Modeling Table of Contents 7.1. Open an Existing EER Model 7.2. Create New EER Model 7.3. Create EER Model from Existing Database 7.4. Create EER Model from SQL Script 7.5. Model Editor 7.5.1. Modeling Menus 7.5.2. The Toolbar 7.5.3. EER Diagrams 7.5.4. The Physical Schemata Panel 7.5.5. The Schema Privileges Panel 7.5.6. The SQL Scripts Panel 7.5.7. The Model Notes Panel 7.5.8. The History Palette 7.5.9. The Model Navigator Panel 7.5.10. The Catalog Tree Palette 7.5.11. The Layers Palette 7.5.12. The Properties Palette 7.6. EER Diagram Editor 7.6.1. The Vertical Toolbar 7.7. Working with Models 7.7.1. Creating Tables 7.7.2. Creating Foreign Key Relationships 7.7.3. Creating Views 7.7.4. Creating Routines and Routine Groups 7.7.5. Creating Layers 7.7.6. Creating Notes 7.7.7. Creating Text Objects 7.7.8. Creating Images 7.7.9. Reverse Engineering 7.7.10. Forward Engineering 7.8. Modeling Tutorials 7.8.1. Importing a Data Definition SQL Script 7.8.2. Using the Default Schema 7.8.3. Basic Modeling 7.8.4. Documenting the sakila Database 7.9. Printing 7.9.1. Printing Options 7.10. MySQL Workbench Schema Validation Plugins (Commercial Version) 7.10.1. General Validation 7.10.2. MySQL-Specific Validation 7.11. The DBDoc Model Reporting Dialog Window (Commercial Version) 7.12. Customizing DBDoc Model Reporting Templates 7.12.1. Supported Template Markers 7.12.2. Creating a Custom Template MySQL Workbench provides extensive capabilities for creating and manipulating database models, including these: Create and manipulate a model graphically Reverse engineer a live database to a model Forward engineer a model to a script or live database Create and edit tables and insert data This is not an exhaustive list. The following sections discuss these and additional data-modeling capablities. The Home window is the typical starting point for work with data modeling. In the Data Modeling section of the Workspace, you can use the action items there to create and manage models, forward and reverse engineer, and compare and synchronize schemata: Open an Existing EER Model Create new EER Model Create EER Model from Existing Database Create EER Model from SQL Script The following sections describe these action items. 


c1title: The Plugins Menu
c2content:
 7.5.1.7. The Plugins Menu 7.5.1.7. The Plugins Menu The Plugins menu lists any plugins that you may have installed. For more information about this menu, see Section 9.3, “Plugins” . 


c1title: The Hand Tool
c2content:
 7.6.1.2. The Hand Tool 7.6.1.2. The Hand Tool The hand tool is used to move the entire EER diagram. Left-click on this tool and then left-click anywhere on the EER diagram canvas. Moving the mouse while holding down the mouse button changes the view port of the canvas. To determine your position on the canvas, look at the Model Navigator panel on the upper right. If the Model Navigator panel is not open, use View , Windows , Model Navigator to open it. To activate the hand tool from the keyboard, use the H key. You can also change the view port of an EER diagram using the Model Navigator panel. See Section 7.5.9, “The Model Navigator Panel” . 


c1title: MySQL Workbench Schema Validation Plugins (Commercial Version)
c2content:
 7.10. MySQL Workbench Schema Validation Plugins (Commercial Version) 7.10. MySQL Workbench Schema Validation Plugins (Commercial Version) 7.10.1. General Validation 7.10.2. MySQL-Specific Validation MySQL Workbench provides validation modules so that you can test your models before implementing them. The validation plugins are accessed from the Model menu. One plugin performs general validation for any Relational Database Management System (RDMS) and the other is MySQL specific. Beneath these menu items are a number of specific validation tests. Running any one of these tests opens an output window docked at the bottom of the application. Warning messages are displayed on the left side of this window and the tests performed are displayed on the right. The following sections outline the tasks performed by the validation modules. 


c1title: The Model Menu
c2content:
 7.5.1.5. The Model Menu 7.5.1.5. The Model Menu 7.5.1.5.1. The DBDoc Model Reporting Dialog Window (Commercial Version) 7.5.1.5.2. The Validation Submenus (Commercial Version) 7.5.1.5.3. The Object Notation Submenu 7.5.1.5.4. The Relationship Notation Submenu The Model menu has these items: Add Diagram : Creates a new EER Diagram. The keyboard shortcut is Control+T . Create Diagram From Catalog Objects : Creates an EER diagram from all the objects in the catalog. DBDoc – Model Reporting... : For information about this menu item, see Section 7.5.1.5.1, “The DBDoc Model Reporting Dialog Window (Commercial Version)” . Commercial version only. User Defined Types : Presents a dialog box that enables you to add and delete user defined data types. Object Notation : For information about this menu item, see Section 7.5.1.5.3, “The Object Notation Submenu” . Relationship Notation : For information about this menu item, see Section 7.5.1.5.4, “The Relationship Notation Submenu” . Diagram Properties and Size : Opens a diagram size dialog box that enables you to adjust the width or height of the canvas. The unit of measure is pages; the default value is two. When you have tables with numerous columns, use this menu item to increase the size of the EER. Validation : For information about this menu item, see Section 7.5.1.5.2, “The Validation Submenus (Commercial Version)” . Commercial version only. Model Options : Sets options at the model level. These options should not be confused with the options that are set globally for the Workbench application, and which are referred to as Workbench Preferences. The available model options are a subset of the Workbench Preferences options. For more information about Workbench Preferences, see Section 5.4.4, “The Model Tab” . 7.5.1.5.1. The DBDoc Model Reporting Dialog Window (Commercial Version) This dialog window is found by navigating to the Model menu and choosing the DBDoc - Model Reporting... item. Note The DBDoc - Model Reporting... item is not available in the MySQL Workbench OSS version. Use this dialog window to set the options for creating documentation of your database models. For more information, see Section 7.11, “The DBDoc Model Reporting Dialog Window (Commercial Version)” . 7.5.1.5.2. The Validation Submenus (Commercial Version) The Model menu has two validation submenus, Validation and Validation (MySQL) . Use these submenus for general validation and MySQL-specific validation of the objects and relationships defined in your model. Note These items are not available in the MySQL Workbench OSS version. The Validation submenu has these items: Validate All : Performs all available validation checks Empty Content Validation : Checks for objects with no content, such as a table with no columns Table Efficiency Validation : Checks the efficiency of tables, such as a table with no primary key defined Duplicate Identifiers Validation : Checks for duplicate identifiers, such as two tables with the same name Consistency Validation : Checks for consistent naming conventions Logic Validation : Checks, for example, that a foreign key does not reference a nonprimary key column in the source table The Validation (MySQL) submenu has these items: Validate All : Performs all available validation checks Integrity Validation : Checks for invalid references, such as a table name longer than the maximum permitted Syntax validation : Checks for correct SQL syntax Duplicate Identifiers Validation (Additions) : Checks for objects with the same name For detailed information about validation, see Section 7.10, “MySQL Workbench Schema Validation Plugins (Commercial Version)” . 7.5.1.5.3. The Object Notation Submenu The items under the Object Notation submenu apply exclusively to an EER diagram. They are not enabled unless an EER diagram tab is selected. The Object Notation submenu has these items: Workbench (Default) : Displays table columns, indexes, and triggers Workbench (Simplified) : Shows only a table's columns Workbench (PKs and FKs only) : Shows only columns that are primary and foreign keys Classic : Similar to the Workbench (Simplified) style showing only the table's columns IDEF1X : The ICAM DEFinition language information modeling style The object notation style that you choose persists for the duration of your MySQL Workbench session and is saved along with your model. When MySQL Workbench is restarted, the object notation reverts to the default. Note If you plan to export or print an EER diagram be sure to decide on a notation style first. Changing notation styles after objects have been placed on a diagram can significantly change the appearance of the diagram. 7.5.1.5.4. The Relationship Notation Submenu The items under the Relationship Notation submenu apply exclusively to an EER diagram. They are not enabled unless an EER diagram tab is selected. The Relationship Notation submenu has these items: Crow's Foot (IE) : The default modeling style. For an example, see Figure 7.42, “Adding Tables to the Canvas” . Classic : Uses a diamond shape to indicate cardinality. Connect to Columns UML : Universal Modeling Language style. IDEF1X : The ICAM DEFinition language information modeling method To view the different styles, set up a relationship between two or more tables and choose the different menu items. The relationship notation style that you choose persists for the duration of your MySQL Workbench session and is saved along with your model. When MySQL Workbench is restarted, the relationship notation reverts to the default, the Crow's Foot style. Note If you plan to export or print an EER diagram, be sure to decide on a notation style first. Changing notation styles after objects have been placed on a diagram can significantly change the appearance of the diagram. 


c1title: Routine Groups
c2content:
 7.7.4.2. Routine Groups 7.7.4.2. Routine Groups 7.7.4.2.1. Adding Routine Groups to the Physical Schemata 7.7.4.2.2. Adding Routine Groups to an EER Diagram 7.7.4.2.3. The Routine Group Editor 7.7.4.2.1. Adding Routine Groups to the Physical Schemata Double-clicking the Add Routine Group icon in the Physical Schemata section of the MySQL Model page adds a routine group with the default name of routines1 . If a routine group with this name already exists, the new routine group is named routines2 . Adding a new routine group automatically opens the routine groups editor docked at the bottom of the application. For information about using the routine groups editor, see Section 7.7.4.2.3, “The Routine Group Editor” . Right-clicking a routine group opens a pop-up menu with the following items: Rename Cut ' routine_group_name ' Copy ' routine_group_name ' Edit Routine... Edit in New Window... Copy SQL to Clipboard Delete ' routine_group_name ' The Edit Routine Group... item opens the routine group editor, which is described in Section 7.7.4.2.3, “The Routine Group Editor” . The cut and paste items are useful for copying routine groups between different schemata. Deleting a routine group from the MySQL Model page removes the group but does not remove any routines contained in that group. Any routine groups added to the Physical Schemata also show up in the Catalog palette on the right side of the application. They may be added to an EER Digram by dragging and dropping them from this palette. 7.7.4.2.2. Adding Routine Groups to an EER Diagram To add routine groups to an EER Diagram, use the Routine Groups tool on the vertical toolbar. Make sure that the EER Diagram tab is selected, then right-click the routine groups icon on the vertical toolbar. The routine groups icon is immediately above the lowest toolbar separator. Clicking the mouse on this icon changes the mouse pointer to a routine group pointer. You can also change the mouse pointer to a routine pointer by pressing the G key. Choosing the Routine Group tool changes the contents of the toolbar that appears immediately below the menu bar. When the Routine Groups pointer is active, this toolbar contains a schemata list and a color chart list. Use these lists to select the appropriate schema and color accent for the new routine group. Make sure that you associate the new routine group with a database. The color of your routine group can be changed later using the Properties palette. Create a routine group by clicking anywhere on the EER Diagram canvas. This creates a new routine group with the default name routines1 . To revert to the default mouse pointer, click the arrow icon at the top of the vertical toolbar. Right-clicking a routine group opens a pop-up menu. With the exception of the delete option and rename options, these menu options function as described in Section 7.7.4.2.1, “Adding Routine Groups to the Physical Schemata” . There is no rename option, and the behavior of the delete option is determined by your MySQL Workbench options settings. For more information, see Section 5.4.4, “The Model Tab” . 7.7.4.2.3. The Routine Group Editor 7.7.4.2.3.1. The Routine Groups Tab 7.7.4.2.3.2. The Privileges Tab 7.7.4.2.3.3. Modifying a Routine Group Using the Properties Palette To invoke the routine group editor, double-click a routine group object on the EER Diagram canvas or double-click a routine group in the Physical Schemata section on the MySQL Model page. This opens the routine group editor docked at the bottom of the application. Double-clicking the title bar undocks the editor. Do the same to redock it. Any number of routine groups may be open at the same time. Each additional routine group appears as a tab at the top of the routine editor, Routine group and Privileges tabs appear at the bottom of the routine editor. Navigate between different tabs using the mouse or from the keyboard by pressing Control+Alt+Tab . 7.7.4.2.3.1. The Routine Groups Tab Use the Routine Groups tab of the routine groups editor to perform the following tasks: Rename the routine group using the Name field. Add routines to the group by dragging and dropping them. Add comments to the routine group. 7.7.4.2.3.2. The Privileges Tab The Privileges tab of the routine group editor functions in exactly the same way as the Privileges tab of the table editor. For more information, see Section 7.7.1.3.10, “The Privileges Tab” . Note Privileges are available only in the Standard Edition of MySQL Workbench. 7.7.4.2.3.3. Modifying a Routine Group Using the Properties Palette When you select a routine group on the EER Diagram canvas, its properties are displayed in the Properties palette. All of the properties accessible from the Properties palette apply to the appearance of a routine group on the EER Diagram canvas. For a list of properties accessible through the Properties palette, see Section 7.5.12, “The Properties Palette” . 


c1title: Changes in Release 5.2
c2content:
 A.1. Changes in Release 5.2 A.1. Changes in Release 5.2 A.1.1. Changes in MySQL Workbench 5.2.37 (Not yet released) A.1.2. Changes in MySQL Workbench 5.2.36 (Not yet released) A.1.3. Changes in MySQL Workbench 5.2.35 (23 September 2011) A.1.4. Changes in MySQL Workbench 5.2.34 (26 May 2011) A.1.5. Changes in MySQL Workbench 5.2.33b (21 March 2011) A.1.6. Changes in MySQL Workbench 5.2.33 (11 March 2011) A.1.7. Changes in MySQL Workbench 5.2.32 (05 March 2011) A.1.8. Changes in MySQL Workbench 5.2.31a (13 December 2010) A.1.9. Changes in MySQL Workbench 5.2.31 (08 December 2010) A.1.10. Changes in MySQL Workbench 5.2.30 (20 November 2010) A.1.11. Changes in MySQL Workbench 5.2.29 (12 October 2010) A.1.12. Changes in MySQL Workbench 5.2.28 (19 September 2010) A.1.13. Changes in MySQL Workbench 5.2.27 (01 September 2010) A.1.14. Changes in MySQL Workbench 5.2.26 (06 August 2010) A.1.15. Changes in MySQL Workbench 5.2.25 (30 June 2010 General Availability) A.1.16. Changes in MySQL Workbench 5.2.24 (21 June 2010) A.1.17. Changes in MySQL Workbench 5.2.23 (Internal release only) A.1.18. Changes in MySQL Workbench 5.2.22 (02 June 2010) A.1.19. Changes in MySQL Workbench 5.2.21 (12 May 2010 Release Candidate) A.1.20. Changes in MySQL Workbench 5.2.20 (27 April 2010) A.1.21. Changes in MySQL Workbench 5.2.19 (16 April 2010) A.1.22. Changes in MySQL Workbench 5.2.18 (13 April 2010) A.1.23. Changes in MySQL Workbench 5.2.17 (02 April 2010) A.1.24. Changes in MySQL Workbench 5.2.16 (17 February 2010) A.1.25. Changes in MySQL Workbench 5.2.15 (28 January 2010) A.1.26. Changes in MySQL Workbench 5.2.14 (21 January 2010) A.1.27. Changes in MySQL Workbench 5.2.13 (Not released) A.1.28. Changes in MySQL Workbench 5.2.12 (Not released) A.1.29. Changes in MySQL Workbench 5.2.11 (18 December 2009) A.1.30. Changes in MySQL Workbench 5.2.10 (01 December 2009) A.1.31. Changes in MySQL Workbench 5.2.9 (Internal release only) A.1.32. Changes in MySQL Workbench 5.2.8 (18 November 2009 Beta) A.1.33. Changes in MySQL Workbench 5.2.7 (Internal release only) A.1.34. Changes in MySQL Workbench 5.2.6 (21 October 2009) A.1.35. Changes in MySQL Workbench 5.2.5 (Internal Release Only) A.1.36. Changes in MySQL Workbench 5.2.4 (07 October 2009) A.1.37. Changes in MySQL Workbench 5.2.3 (15 September 2009) A.1.38. Changes in MySQL Workbench 5.2.2 (27 July 2009) A.1.39. Changes in MySQL Workbench 5.2.1 (22 May 2009) A.1.40. Changes in MySQL Workbench 5.2.0 (30 April 2009 Alpha) 


c1title: Bitstream Vera License
c2content:
 B.2. Bitstream Vera License B.2. Bitstream Vera License The following software may be included in this product: Bitstream Vera Copyright (c) 2003 by Bitstream, Inc. All Rights Reserved. Bitstream Vera is a trademark of Bitstream, Inc. Permission is hereby granted, free of charge, to any person obtaining a copy of the fonts accompanying this license ("Fonts") and associated documentation files (the "Font Software"), to reproduce and distribute the Font Software, including without limitation the rights to use, copy, merge, publish, distribute, and/or sell copies of the Font Software, and to permit persons to whom the Font Software is furnished to do so, subject to the following conditions: The above copyright and trademark notices and this permission notice shall be included in all copies of one or more of the Font Software typefaces. The Font Software may be modified, altered, or added to, and in particular the designs of glyphs or characters in the Fonts may be modified and additional glyphs or characters may be added to the Fonts, only if the fonts are renamed to names not containing either the words "Bitstream" or the word "Vera". This License becomes null and void to the extent applicable to Fonts or Font Software that has been modified and is distributed under the "Bitstream Vera" names. The Font Software may be sold as part of a larger software package but no copy of one or more of the Font Software typefaces may be sold by itself. THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL BITSTREAM OR THE GNOME FOUNDATION BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM OTHER DEALINGS IN THE FONT SOFTWARE. Except as contained in this notice, the names of Gnome, the Gnome Foundation, and Bitstream Inc., shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Font Software without prior written authorization from the Gnome Foundation or Bitstream Inc., respectively. For further information, contact: fonts at gnome dot org. 


c1title: ScintillaNET License
c2content:
 B.21. ScintillaNET License B.21. ScintillaNET License The following software may be included in this product: ScintillaNET ScintillaNET is based on the Scintilla component by Neil Hodgson. ScintillaNET is released on this same license. The ScintillaNET bindings are Copyright 2002-2006 by Garrett Serack All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. GARRETT SERACK AND ALL EMPLOYERS PAST AND PRESENT DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL GARRETT SERACK AND ALL EMPLOYERS PAST AND PRESENT BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. The license for Scintilla is as follows: ----------------------------------------------------------- Copyright 1998-2006 by Neil Hodgson All Rights Reserved Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. NEIL HODGSON DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL NEIL HODGSON BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. 


c1title: Adding Foreign Key Relationships Using an EER Diagram
c2content:
 7.7.2.1. Adding Foreign Key Relationships Using an EER Diagram 7.7.2.1. Adding Foreign Key Relationships Using an EER Diagram The vertical toolbar on the left side of an EER Diagram has six foreign key tools: one-to-one non-identifying relationship one-to-many non-identifying relationship one-to-one identifying relationship one-to-many identifying relationship many-to-many identifying relationship Place a Relationship Using Existing Columns An identifying relationship is one where the child table cannot be uniquely identified without its parent. Typically this occurs where an intermediary table is created to resolve a many-to-many relationship. In such cases, the primary key is usually a composite key made up of the primary keys from the two original tables. An identifying relationship is indicated by a solid line between the tables and a nonidentifying relationship is indicated by a broken line. Create or drag and drop the tables that you wish to connect. Ensure that there is a primary key in the table that will be on the “ one ” side of the relationship. Click on the appropriate tool for the type of relationship you wish to create. If you are creating a one-to-many relationship, first click the table that is on the “ many ” side of the relationship, then on the table containing the referenced key. This creates a column in the table on the many side of the relationship. The default name of this column is table_name_key_name where the table name and the key name both refer to the table containing the referenced key. When the many-to-many tool is active, double-clicking a table creates an associative table with a many-to-many relationship. For this tool to function there must be a primary key defined in the initial table. Use the Model menu, Menu Options menu item to set a project-specific default name for the foreign key column (see Section 7.5.1.5.4, “The Relationship Notation Submenu” ). To change the global default, see Section 5.4.4, “The Model Tab” . To edit the properties of a foreign key, double-click anywhere on the connection line that joins the two tables. This opens the relationship editor. Mousing over a relationship connector highlights the connector and the related keys as shown in the following figure. The film and the film_actor tables are related on the film_id field and these fields are highlighted in both tables. Since the film_id field is part of the primary key in the film_actor table, a solid line is used for the connector between the two tables. Figure 7.11. The Relationship Connector If the placement of a connection's caption is not suitable, you can change its position by dragging it to a different location. If you have set a secondary caption, its position can also be changed. For more information about secondary captions, see Section 7.7.2.3, “Connection Properties” . Where the notation style permits, Classic for example, the cardinality indicators can also be repositioned. The relationship notation style in Figure 7.11, “The Relationship Connector” is the default, crow's foot. You can change this if you are using a commercial version of MySQL Workbench. For more information, see Section 7.5.1.5.4, “The Relationship Notation Submenu” . You can select multiple connections by holding down the Control key as you click a connection. This can be useful for highlighting specific relationships on an EER diagram. 


c1title: The Relationship Tools
c2content:
 7.6.1.10. The Relationship Tools 7.6.1.10. The Relationship Tools The five relationship tools are used to represent the following relationships: One-to-many nonidentifying relationships One-to-one nonidentifying relationships One-to-many identifying relationships One-to-one identifying relationships Many-to-many identifying relationships These tools appear at the bottom of the vertical tool bar. Hover the mouse pointer over each tool to see a text hint that describes its function. For more information about relationships, see Section 7.7.2, “Creating Foreign Key Relationships” . 


c1title: Changes in MySQL Workbench 5.2.5 (Internal Release Only)
c2content:
 A.1.35. Changes in MySQL Workbench 5.2.5 (Internal Release Only) A.1.35. Changes in MySQL Workbench 5.2.5 (Internal Release Only) This section documents all changes and bug fixes applied since the release of 5.2.4. Bugs Fixed The following exception was generated when closing the Relationship tab for an EER Diagram: System.NullReferenceException: Referência de objeto não definida para uma instância de um objeto. em MySQL.GUI.Workbench.MainForm.mainDockPanel_ActiveDocumentClosing(Object sender, ActiveDocumentClosingEventArgs e) em WeifenLuo.WinFormsUI.Docking.DockPanel.OnActiveDocumentClosing(ActiveDocumentClosingEventA rgs e) em WeifenLuo.WinFormsUI.Docking.DockPane.CloseContent(IDockContent content) em WeifenLuo.WinFormsUI.Docking.DockPane.CloseActiveContent() em WeifenLuo.WinFormsUI.Docking.VS2005DockPaneStrip.Close_Click(Object sender, EventArgs e) em System.Windows.Forms.Control.OnClick(EventArgs e) em System.Windows.Forms.Control.WmMouseUp(Message&amp; m, MouseButtons button, Int32 clicks) em System.Windows.Forms.Control.WndProc(Message&amp; m) em System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message&amp; m) em System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message&amp; m) em System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) (Bug #47958) When attempting to run MySQL Workbench, the splash screen appeared and then the application immediately crashed, generating the “ Send error report to Microsoft ” dialog. On debugging it was found that MySQL Workbench was throwing a TypeLoadException : Could not load type 'WeifenLuo.WinFormsUI.Docking.ActiveDocumentClosingEventArgs' from assembly 'WeifenLuo.WinFormsUI.Docking, Version=2.2.3428.40956, Culture=neutral, PublicKeyToken=null'. On inspection of the referenced assembly it was confirmed that there was no type ActiveDocumentClosingEventArgs defined. (Bug #47534, Bug #47480) 


c1title: The DBDoc Model Reporting Dialog Window (Commercial Version)
c2content:
 7.11. The DBDoc Model Reporting Dialog Window (Commercial Version) 7.11. The DBDoc Model Reporting Dialog Window (Commercial Version) This dialog window is found by navigating to the Model menu and choosing the DBDoc - Model Reporting... item. Note The DBDoc - Model Reporting... item is not available in the MySQL Workbench OSS version. Use this dialog window to set the options for creating documentation of your database models. Figure 7.46. The DBDoc Model Reporting Main Wizard You can choose from four available templates: HTML Basic Frames : Model documentation in HTML format that makes use of frames HTML Basic Single Page : Single Page HTML documentation, not using frames HTML Detailed Frames : Detailed HTML documentation, using frames Text Basic : Text file documentation When you click a template, a preview image displays on the right side of the page. For the HTML Basic Frames template, you can select either the Colorful or the Restrained Colors option from the Style list. The HTML Basic Single Page template offers only the Colorful style. The HTML Detailed Frames template offers the Vibrant style, and also the more subdued Coated style. The Text Basic template offers only the Fixed Size Font style. From the Base Options frame choose the report title and the output directory for the report files. As of MySQL Workbench 5.1.17, it is possible to specify variables in the output path: ~ : The user's home directory. Available on Linux and Mac OS X versions only. %desktopfolder% : The user's desktop. %documentsfolder% : The user's Documents folders. The following table shows typical values for various platforms. Platform Typical Default Documents Folder Windows C:\Documents and Settings\ user_name \My Documents Linux ~/Documents Mac OS X Users/ user_name /Documents %date% : The date in the format YYYY-MM-DD. %time% : The time in the format HHMM. %year% : The year in the format YYYY. %month% : The month in the format MM. January is 01 and December is 12. %monthname% : The name of the month, rather than the number. %day% : The day number in the format DD. For example, the 12th would be 12. Content options can also be set: Render Table Columns : Display all the columns. Render Table Indices : Display all the indexes. Render Foreign Keys : Display all the foreign keys. List Foreign Keys that refer to that table : Display the tables that foreign keys reference. Clicking the Finish button creates the directory defined in the Output directory text box. If you chose to create HTML Basic Frames , you will find the following files in this directory: basic.css : The style sheet for the overview.html page. index.html : The main page. overview.html : The model overview, the navigation links shown in the sidebar. restrained.css : The CSS file used if the Restrained Colors style option was chosen. table_details.html : The main frame of the model report. Choosing the HTML Basic Single Page option creates a style sheet and an index.html file. Choosing the HTML Detailed Frames option creates the following files: basic.css : The style sheet for the overview.html page. This is used if the vibrant style is chosen. coated.css : The CSS file used if the Coated style option was chosen. details_list.html : A Schema overview along with details of columns, indexes and foreign keys for each schema. full_list.html : List of all columns and indexes for the schema. index.html : The main page. overview.html : Overview information for the report such as report title, project name and author. overview_list.html : A summary of schema in the model along with a list of tables contained in each schema. table_details.html : The main report details. top.html : The top frame of the report. Choosing the Text Basic option creates a directory containing one text file. You can click index.html to view a report. The following screenshot shows the HTML Detailed Frames report being displayed: Figure 7.47. The DBDoc Model Report If you wish to create custom templates please refer to Section 7.12, “Customizing DBDoc Model Reporting Templates” . 


c1title: Exploring the Workbench Scripting Shell
c2content:
 9.5.1. Exploring the Workbench Scripting Shell 9.5.1. Exploring the Workbench Scripting Shell To open the Workbench Scripting Shell, select Scripting , Scripting Shell from the main menu. You can also open the Workbench Scripting Shell using the Control+F3 key combination on Windows and Linux, Command+F3 on Mac OS X, or by clicking the shell button above the EER diagram navigator. The Workbench Scripting Shell will then open in a new dialog. The following screenshot shows the Workbench Scripting Shell dialog. Figure 9.1. The Workbench Scripting Shell 


c1title: Changes in MySQL Workbench 5.2.0 (30 April 2009 Alpha)
c2content:
 A.1.40. Changes in MySQL Workbench 5.2.0 (30 April 2009 Alpha) A.1.40. Changes in MySQL Workbench 5.2.0 (30 April 2009 Alpha) This is the first alpha release of 5.2.0. This section has no changelog entries. 


c1title: The Variables Tab
c2content:
 8.7.5. The Variables Tab 8.7.5. The Variables Tab The Variables tab displays a list of all server and status variables. Figure 8.8. Administrator - Variables Tab 


c1title: Appendix A. MySQL Workbench Change History
c2content:
 Appendix A. MySQL Workbench Change History Appendix A. MySQL Workbench Change History Table of Contents A.1. Changes in Release 5.2 A.1.1. Changes in MySQL Workbench 5.2.37 (Not yet released) A.1.2. Changes in MySQL Workbench 5.2.36 (Not yet released) A.1.3. Changes in MySQL Workbench 5.2.35 (23 September 2011) A.1.4. Changes in MySQL Workbench 5.2.34 (26 May 2011) A.1.5. Changes in MySQL Workbench 5.2.33b (21 March 2011) A.1.6. Changes in MySQL Workbench 5.2.33 (11 March 2011) A.1.7. Changes in MySQL Workbench 5.2.32 (05 March 2011) A.1.8. Changes in MySQL Workbench 5.2.31a (13 December 2010) A.1.9. Changes in MySQL Workbench 5.2.31 (08 December 2010) A.1.10. Changes in MySQL Workbench 5.2.30 (20 November 2010) A.1.11. Changes in MySQL Workbench 5.2.29 (12 October 2010) A.1.12. Changes in MySQL Workbench 5.2.28 (19 September 2010) A.1.13. Changes in MySQL Workbench 5.2.27 (01 September 2010) A.1.14. Changes in MySQL Workbench 5.2.26 (06 August 2010) A.1.15. Changes in MySQL Workbench 5.2.25 (30 June 2010 General Availability) A.1.16. Changes in MySQL Workbench 5.2.24 (21 June 2010) A.1.17. Changes in MySQL Workbench 5.2.23 (Internal release only) A.1.18. Changes in MySQL Workbench 5.2.22 (02 June 2010) A.1.19. Changes in MySQL Workbench 5.2.21 (12 May 2010 Release Candidate) A.1.20. Changes in MySQL Workbench 5.2.20 (27 April 2010) A.1.21. Changes in MySQL Workbench 5.2.19 (16 April 2010) A.1.22. Changes in MySQL Workbench 5.2.18 (13 April 2010) A.1.23. Changes in MySQL Workbench 5.2.17 (02 April 2010) A.1.24. Changes in MySQL Workbench 5.2.16 (17 February 2010) A.1.25. Changes in MySQL Workbench 5.2.15 (28 January 2010) A.1.26. Changes in MySQL Workbench 5.2.14 (21 January 2010) A.1.27. Changes in MySQL Workbench 5.2.13 (Not released) A.1.28. Changes in MySQL Workbench 5.2.12 (Not released) A.1.29. Changes in MySQL Workbench 5.2.11 (18 December 2009) A.1.30. Changes in MySQL Workbench 5.2.10 (01 December 2009) A.1.31. Changes in MySQL Workbench 5.2.9 (Internal release only) A.1.32. Changes in MySQL Workbench 5.2.8 (18 November 2009 Beta) A.1.33. Changes in MySQL Workbench 5.2.7 (Internal release only) A.1.34. Changes in MySQL Workbench 5.2.6 (21 October 2009) A.1.35. Changes in MySQL Workbench 5.2.5 (Internal Release Only) A.1.36. Changes in MySQL Workbench 5.2.4 (07 October 2009) A.1.37. Changes in MySQL Workbench 5.2.3 (15 September 2009) A.1.38. Changes in MySQL Workbench 5.2.2 (27 July 2009) A.1.39. Changes in MySQL Workbench 5.2.1 (22 May 2009) A.1.40. Changes in MySQL Workbench 5.2.0 (30 April 2009 Alpha) A.2. Changes in Release 5.1 A.2.1. Changes in MySQL Workbench 5.1.19 (06 September 2010) A.2.2. Changes in MySQL Workbench 5.1.18 (03 September 2009 General Availability) A.2.3. Changes in MySQL Workbench 5.1.17 (14 August 2009) A.2.4. Changes in MySQL Workbench 5.1.16 (30 June 2009 General Availability) A.2.5. Changes in MySQL Workbench 5.1.15 (26 June 2009) A.2.6. Changes in MySQL Workbench 5.1.14 (19 June 2009) A.2.7. Changes in MySQL Workbench 5.1.13 (12 June 2009) A.2.8. Changes in MySQL Workbench 5.1.12 (27 April 2009) A.2.9. Changes in MySQL Workbench 5.1.11 (Not yet released) A.2.10. Changes in MySQL Workbench 5.1.10 (10 April 2009) A.2.11. Changes in MySQL Workbench 5.1.9 (Not yet released Beta) A.2.12. Changes in MySQL Workbench 5.1.8 (Not yet released) A.2.13. Changes in MySQL Workbench 5.1.7 (Not yet released) A.2.14. Changes in MySQL Workbench 5.1.6 (Not yet released) A.2.15. Changes in MySQL Workbench 5.1.4 (Not yet released) A.3. Changes in Release 5.0 A.3.1. Changes in MySQL Workbench 5.0.30 (18 February 2009) A.3.2. Changes in MySQL Workbench 5.0.29 (12 December 2008) A.3.3. Changes in MySQL Workbench 5.0.28 (06 December 2008) A.3.4. Changes in MySQL Workbench 5.0.27 (07 November 2008) A.3.5. Changes in MySQL Workbench 5.0.26 (16 October 2008) A.3.6. Changes in MySQL Workbench 5.0.25 (12 September 2008) A.3.7. Changes in MySQL Workbench 5.0.24 (12 August 2008) A.3.8. Changes in MySQL Workbench 5.0.23 (25 June 2008) A.3.9. Changes in MySQL Workbench 5.0.22 (27 May 2008) A.3.10. Changes in MySQL Workbench 5.0.21 (27 April 2008) A.3.11. Changes in MySQL Workbench 5.0.20 (26 April 2008) A.3.12. Changes in MySQL Workbench 5.0.19 (15 April 2008) A.3.13. Changes in MySQL Workbench 5.0.18rc (not released) A.3.14. Changes in MySQL Workbench 5.0.17rc (07 April 2008) A.3.15. Changes in MySQL Workbench 5.0.16rc (26 March 2008) A.3.16. Changes in MySQL Workbench 5.0.15rc (17 March 2008) A.3.17. Changes in MySQL Workbench 5.0.14abeta (28 February 2008) A.3.18. Changes in MySQL Workbench 5.0.14beta (25 February 2008) The following sections outline the changes between versions for MySQL Workbench. 


c1title: GNU Lesser General Public License Version 2.1, February 1999
c2content:
 B.11. GNU Lesser General Public License Version 2.1, February 1999 B.11. GNU Lesser General Public License Version 2.1, February 1999 The following applies to all products licensed under the GNU Lesser General Public License, Version 2.1: You may not use the identified files except in compliance with the GNU Lesser General Public License, Version 2.1 (the "License"). You may obtain a copy of the License at http://www.gnu.org/licenses/lgpl-2.1.html. A copy of the license is also reproduced below. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. GNU LESSER GENERAL PUBLIC LICENSE Version 2.1, February 1999 Copyright (C) 1991, 1999 Free Software Foundation, Inc. 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. [This is the first released version of the Lesser GPL. It also counts as the successor of the GNU Library Public License, version 2, hence the version number 2.1.] Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public Licenses are intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This license, the Lesser General Public License, applies to some specially designated software packages--typically libraries--of the Free Software Foundation and other authors who decide to use it. You can use it too, but we suggest you first think carefully about whether this license or the ordinary General Public License is the better strategy to use in any particular case, based on the explanations below. When we speak of free software, we are referring to freedom of use, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish); that you receive source code or can get it if you want it; that you can change the software and use pieces of it in new free programs; and that you are informed that you can do these things. To protect your rights, we need to make restrictions that forbid distributors to deny you these rights or to ask you to surrender these rights. These restrictions translate to certain responsibilities for you if you distribute copies of the library or if you modify it. For example, if you distribute copies of the library, whether gratis or for a fee, you must give the recipients all the rights that we gave you. You must make sure that they, too, receive or can get the source code. If you link other code with the library, you must provide complete object files to the recipients, so that they can relink them with the library after making changes to the library and recompiling it. And you must show them these terms so they know their rights. We protect your rights with a two-step method: (1) we copyright the library, and (2) we offer you this license, which gives you legal permission to copy, distribute and/or modify the library. To protect each distributor, we want to make it very clear that there is no warranty for the free library. Also, if the library is modified by someone else and passed on, the recipients should know that what they have is not the original version, so that the original author's reputation will not be affected by problems that might be introduced by others. Finally, software patents pose a constant threat to the existence of any free program. We wish to make sure that a company cannot effectively restrict the users of a free program by obtaining a restrictive license from a patent holder. Therefore, we insist that any patent license obtained for a version of the library must be consistent with the full freedom of use specified in this license. Most GNU software, including some libraries, is covered by the ordinary GNU General Public License. This license, the GNU Lesser General Public License, applies to certain designated libraries, and is quite different from the ordinary General Public License. We use this license for certain libraries in order to permit linking those libraries into non-free programs. When a program is linked with a library, whether statically or using a shared library, the combination of the two is legally speaking a combined work, a derivative of the original library. The ordinary General Public License therefore permits such linking only if the entire combination fits its criteria of freedom. The Lesser General Public License permits more lax criteria for linking other code with the library. We call this license the "Lesser" General Public License because it does Less to protect the user's freedom than the ordinary General Public License. It also provides other free software developers Less of an advantage over competing non-free programs. These disadvantages are the reason we use the ordinary General Public License for many libraries. However, the Lesser license provides advantages in certain special circumstances. For example, on rare occasions, there may be a special need to encourage the widest possible use of a certain library, so that it becomes a de-facto standard. To achieve this, non-free programs must be allowed to use the library. A more frequent case is that a free library does the same job as widely used non-free libraries. In this case, there is little to gain by limiting the free library to free software only, so we use the Lesser General Public License. In other cases, permission to use a particular library in non-free programs enables a greater number of people to use a large body of free software. For example, permission to use the GNU C Library in non-free programs enables many more people to use the whole GNU operating system, as well as its variant, the GNU/Linux operating system. Although the Lesser General Public License is Less protective of the users' freedom, it does ensure that the user of a program that is linked with the Library has the freedom and the wherewithal to run that program using a modified version of the Library. The precise terms and conditions for copying, distribution and modification follow. Pay close attention to the difference between a "work based on the library" and a "work that uses the library". The former contains code derived from the library, whereas the latter must be combined with the library in order to run. GNU LESSER GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License Agreement applies to any software library or other program which contains a notice placed by the copyright holder or other authorized party saying it may be distributed under the terms of this Lesser General Public License (also called "this License"). Each licensee is addressed as "you". A "library" means a collection of software functions and/or data prepared so as to be conveniently linked with application programs (which use some of those functions and data) to form executables. The "Library", below, refers to any such software library or work which has been distributed under these terms. A "work based on the Library" means either the Library or any derivative work under copyright law: that is to say, a work containing the Library or a portion of it, either verbatim or with modifications and/or translated straightforwardly into another language. (Hereinafter, translation is included without limitation in the term "modification".) "Source code" for a work means the preferred form of the work for making modifications to it. For a library, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the library. Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running a program using the Library is not restricted, and output from such a program is covered only if its contents constitute a work based on the Library (independent of the use of the Library in a tool for writing it). Whether that is true depends on what the Library does and what the program that uses the Library does. 1. You may copy and distribute verbatim copies of the Library's complete source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and distribute a copy of this License along with the Library. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee. 2. You may modify your copy or copies of the Library or any portion of it, thus forming a work based on the Library, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a) The modified work must itself be a software library. b) You must cause the files modified to carry prominent notices stating that you changed the files and the date of any change. c) You must cause the whole of the work to be licensed at no charge to all third parties under the terms of this License. d) If a facility in the modified Library refers to a function or a table of data to be supplied by an application program that uses the facility, other than as an argument passed when the facility is invoked, then you must make a good faith effort to ensure that, in the event an application does not supply such function or table, the facility still operates, and performs whatever part of its purpose remains meaningful. (For example, a function in a library to compute square roots has a purpose that is entirely well-defined independent of the application. Therefore, Subsection 2d requires that any application-supplied function or table used by this function must be optional: if the application does not supply it, the square root function must still compute square roots.) These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Library, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Library, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Library. In addition, mere aggregation of another work not based on the Library with the Library (or with a work based on the Library) on a volume of a storage or distribution medium does not bring the other work under the scope of this License. 3. You may opt to apply the terms of the ordinary GNU General Public License instead of this License to a given copy of the Library. To do this, you must alter all the notices that refer to this License, so that they refer to the ordinary GNU General Public License, version 2, instead of to this License. (If a newer version than version 2 of the ordinary GNU General Public License has appeared, then you can specify that version instead if you wish.) Do not make any other change in these notices. Once this change is made in a given copy, it is irreversible for that copy, so the ordinary GNU General Public License applies to all subsequent copies and derivative works made from that copy. This option is useful when you wish to copy part of the code of the Library into a program that is not a library. 4. You may copy and distribute the Library (or a portion or derivative of it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange. If distribution of object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place satisfies the requirement to distribute the source code, even though third parties are not compelled to copy the source along with the object code. 5. A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, is called a "work that uses the Library". Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License. However, linking a "work that uses the Library" with the Library creates an executable that is a derivative of the Library (because it contains portions of the Library), rather than a "work that uses the library". The executable is therefore covered by this License. Section 6 states terms for distribution of such executables. When a "work that uses the Library" uses material from a header file that is part of the Library, the object code for the work may be a derivative work of the Library even though the source code is not. Whether this is true is especially significant if the work can be linked without the Library, or if the work is itself a library. The threshold for this to be true is not precisely defined by law. If such an object file uses only numerical parameters, data structure layouts and accessors, and small macros and small inline functions (ten lines or less in length), then the use of the object file is unrestricted, regardless of whether it is legally a derivative work. (Executables containing this object code plus portions of the Library will still fall under Section 6.) Otherwise, if the work is a derivative of the Library, you may distribute the object code for the work under the terms of Section 6. Any executables containing that work also fall under Section 6, whether or not they are linked directly with the Library itself. 6. As an exception to the Sections above, you may also combine or link a "work that uses the Library" with the Library to produce a work containing portions of the Library, and distribute that work under terms of your choice, provided that the terms permit modification of the work for the customer's own use and reverse engineering for debugging such modifications. You must give prominent notice with each copy of the work that the Library is used in it and that the Library and its use are covered by this License. You must supply a copy of this License. If the work during execution displays copyright notices, you must include the copyright notice for the Library among them, as well as a reference directing the user to the copy of this License. Also, you must do one of these things: a) Accompany the work with the complete corresponding machine-readable source code for the Library including whatever changes were used in the work (which must be distributed under Sections 1 and 2 above); and, if the work is an executable linked with the Library, with the complete machine-readable "work that uses the Library", as object code and/or source code, so that the user can modify the Library and then relink to produce a modified executable containing the modified Library. (It is understood that the user who changes the contents of definitions files in the Library will not necessarily be able to recompile the application to use the modified definitions.) b) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (1) uses at run time a copy of the library already present on the user's computer system, rather than copying library functions into the executable, and (2) will operate properly with a modified version of the library, if the user installs one, as long as the modified version is interface-compatible with the version that the work was made with. c) Accompany the work with a written offer, valid for at least three years, to give the same user the materials specified in Subsection 6a, above, for a charge no more than the cost of performing this distribution. d) If distribution of the work is made by offering access to copy from a designated place, offer equivalent access to copy the above specified materials from the same place. e) Verify that the user has already received a copy of these materials or that you have already sent this user a copy. For an executable, the required form of the "work that uses the Library" must include any data and utility programs needed for reproducing the executable from it. However, as a special exception, the materials to be distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. It may happen that this requirement contradicts the license restrictions of other proprietary libraries that do not normally accompany the operating system. Such a contradiction means you cannot use both them and the Library together in an executable that you distribute. 7. You may place library facilities that are a work based on the Library side-by-side in a single library together with other library facilities not covered by this License, and distribute such a combined library, provided that the separate distribution of the work based on the Library and of the other library facilities is otherwise permitted, and provided that you do these two things: a) Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities. This must be distributed under the terms of the Sections above. b) Give prominent notice with the combined library of the fact that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work. 8. You may not copy, modify, sublicense, link with, or distribute the Library except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense, link with, or distribute the Library is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. 9. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Library or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Library (or any work based on the Library), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Library or works based on it. 10. Each time you redistribute the Library (or any work based on the Library), the recipient automatically receives a license from the original licensor to copy, distribute, link with or modify the Library subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties with this License. 11. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Library at all. For example, if a patent license would not permit royalty-free redistribution of the Library by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Library. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply, and the section as a whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. 12. If the distribution and/or use of the Library is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Library under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License. 13. The Free Software Foundation may publish revised and/or new versions of the Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Library specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Library does not specify a license version number, you may choose any version ever published by the Free Software Foundation. 14. If you wish to incorporate parts of the Library into other free programs whose distribution conditions are incompatible with these, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. NO WARRANTY 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Libraries If you develop a new library, and you want it to be of the greatest possible use to the public, we recommend making it free software that everyone can redistribute and change. You can do so by permitting redistribution under these terms (or, alternatively, under the terms of the ordinary General Public License). To apply these terms, attach the following notices to the library. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. &lt;one line to give the library's name and a brief idea of what it does.&gt; Copyright (C) &lt;year&gt; &lt;name of author&gt; This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version. This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details. You should have received a copy of the GNU Lesser General Public License along with this library; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Also add information on how to contact you by electronic and paper mail. You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the library, if necessary. Here is a sample; alter the names: Yoyodyne, Inc., hereby disclaims all copyright interest in the library `Frob' (a library for tweaking knobs) written by James Random Hacker. &lt;signature of Ty Coon&gt;, 1 April 1990 Ty Coon, President of Vice That's all there is to it! 


c1title: Changes in MySQL Workbench 5.1.15 (26 June 2009)
c2content:
 A.2.5. Changes in MySQL Workbench 5.1.15 (26 June 2009) A.2.5. Changes in MySQL Workbench 5.1.15 (26 June 2009) This section documents all changes and bug fixes applied since the release of 5.1.14. Functionality Added or Changed A routine object was deleted if its code was removed from the routine group. This behavior has now been noted in the main documentation. (Bug #45738) Bugs Fixed Selecting Database , Generate Catalog Diff Report from the main menu caused MySQL Workbench to crash. (Bug #45652) Generated INSERT statements did not have a database name. The generated INSERT statements were at the end of the SQL output. However, there was no USE database statement before the group of inserts. The comment before the group of INSERTS did refer to the database table. If you had multiple databases, this generated errors on import. (Bug #45642) In the Forward Engineer SQL Script wizard, when the Show Filter button was clicked, the left hand panel containing database and table names was too narrow, especially if a long database name or table name was used. This made it hard to determine which tables to select. (Bug #45623) The File , Export , Forward Engineer SQL CREATE Script wizard contained malfunctioning buttons. When prompted with the message “ Do you want to overwrite an existing .sql file? ”, the Replace and Cancel buttons had the reverse effect. Clicking Replace cancelled the action, whereas clicking Cancel proceeded to the next step. (Bug #45619) In Ubuntu Linux, right-clicking any item in the Catalog , Layers , User Types , or History tabs, or other tabs typically docked in the right hand side of MySQL Workbench, did not display a context-sensitive menu. (Bug #44298) MySQL Workbench Syncronize Model feature had unexpected behavior. For example, synchronizing the model with the live database would cause changes to the database, even if this was not desired. Also, if tables were dropped in the live database, and the model synchronized, the changes to the live database were not reflected in the model. Further, if a model was created and synchronized to an empty schema in the live database, when synchronization took place again, MySQL Workbench would indicate many changes were required, even if no changes had been made to the model or database. (Bug #42149) Double-clicking a layer in the Layers tab did not select it in the EER Diagram canvas. However, other objects in the Layers tab could be selected on the EER Diagram canvas in this manner. (Bug #34938) Right-clicking a relationship in the EER Diagram canvas, and selecting Edit in New Window... from the context-sensitive menu, had no effect. (Bug #34069) 


c1title: The Text Object Editor
c2content:
 7.7.7.2. The Text Object Editor 7.7.7.2. The Text Object Editor 7.7.7.2.1. Modifying a Text Object Using the Properties Palette To invoke the text object editor, double-click a text object on the EER Diagram canvas. This opens the editor docked at the bottom of the application. Double-clicking the text object table undocks the editor. Double-click the title bar to redock it. Any number of text objects may be open at the same time. Each additional text objects appears as a tab at the top of the text editor. Use the editor to change the name of a text object or its contents. 7.7.7.2.1. Modifying a Text Object Using the Properties Palette When you select a text object on the EER Diagram canvas, its properties are displayed in the Properties palette. Most of the properties accessible from the Properties palette apply to the appearance of a view on the EER Diagram canvas. For a list of properties accessible through the Properties palette, see Section 7.5.12, “The Properties Palette” . There is no property in the Properties palette for changing the font used by a text object. To do so, choose the Appearance tab of the Workbench Preferences dialog. For more information, see Section 5.4.7, “The Appearance Tab” . 


c1title: Connection Information Panel
c2content:
 6.7.5.1. Connection Information Panel 6.7.5.1. Connection Information Panel This panel summarizes the current connection to the server. Figure 6.13. SQL Editor - Connection Information Palette 


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


c1title: The Catalog Tree Palette
c2content:
 7.5.10. The Catalog Tree Palette 7.5.10. The Catalog Tree Palette The Catalog Tree palette shows all the schemata that are present in the Physical Schemata section of the MySQL Model page. Expand the view of the objects contained in a specific schema by clicking the + button to the left of the schema name. This displays the following folder icons: Tables Views Routine Groups Expand each of these in turn by clicking the + button to the left of the folder icon. Selecting an object in this palette displays its properties in the Properties palette, which can be found in the lower left corner of the page. The Catalog Tree palette is primarily used to drag and drop objects onto an EER diagram canvas. Note On Linux, there is a quirk in the GTK tree control, where a simple click always generates a new selection. To drag multiple objects from the Catalog Tree to the EER diagram canvas, you must perform the operation as follows: Click the first item in the tree. Hold the Shift key, click the last item, and do not release the Shift key . Keep the Shift key depressed and commence the dragging operation. Release the Shift key before you release the mouse button to drop selected objects onto the canvas. This procedure also applies to use of the Control key when selecting multiple nonadjacent elements in the Catalog Tree. You can toggle the sidebar on and off using the Toggle Sidebar button, which is located in the top right of the application. 


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


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


c1title: .NET Flat TabControl License
c2content:
 B.1. .NET Flat TabControl License B.1. .NET Flat TabControl License The following software may be included in this product: .NET Flat TabControl Use of any of this software is governed by the terms of the license below: It is free. Public domain! Oscar Londono 


c1title: The Routine Group Tool
c2content:
 7.6.1.9. The Routine Group Tool 7.6.1.9. The Routine Group Tool Use this tool to create a routine group on the EER Diagram canvas. When this tool is activated, a schema list appears on the toolbar below the main menu, enabling you to associate the routine group with a specific schema. You can also select a color for the routine group by choosing from the color list to the right of the schema list. After selecting this tool, clicking the canvas creates a new group. To edit this view, right-click it and choose Edit Routine Group... or Edit in New Window... from the pop-up menu. To activate the routine group tool from the keyboard, use the G key. For more information about creating and editing routine groups, see Section 7.7.4.2, “Routine Groups” . 


c1title: Tutorial: Writing Plugins
c2content:
 9.6. Tutorial: Writing Plugins 9.6. Tutorial: Writing Plugins This tutorial shows you how to extend MySQL Workbench by creating a plugin. The Sample Plugin EER Diagrams are useful for visualizing complex database schemata. They are often created for existing databases, to clarify their purpose or document them. MySQL Workbench provides facilities for reverse engineering existing databases, and then creating an EER Diagram automatically. In this case, relationship lines between foreign keys in the table will automatically be drawn. This graphical representation makes the relationships between the tables much easier to understand. However, one of the most popular storage engines for MySQL, MyISAM, does not include support for foreign keys. This means that MyISAM tables that are reverse engineered will not automatically have the relationship lines drawn between tables, making the database harder to understand. The plugin that will be created in this tutorial gets around this problem by using the fact that a naming convention is very often used for foreign keys: tablename_primarykeyname . Using this convention, foreign keys can automatically be created after a database is reverse engineered, which will result in relationship lines being drawn in the EER diagram. Algorithm The basic algorithm for this task would be as follows: for each table in the schema for each column in the table look for another table whose name and primary key name match the current column name if such a table is found, add a foreign key referencing it As iterating the complete table list to find a match can be slow for models with a large number of tables, it is necessary to optimize by pre-computing all possible foreign key names in a given schema. import grt def auto_create_fks(schema): fk_name_format = "%(table)s_%(pk)s" possible_fks = {} # create the list of possible foreign keys from the list of tables for table in schema.tables: if table.primaryKey: format_args = {'table':table.name, 'pk':table.primaryKey.name} fkname = fk_name_format % format_args possible_fks[fkname] = table # go through all tables in schema, this time to find columns that may be a fk for table in schema.tables: for column in table.columns: if possible_fks.has_key(column.name): ref_table = possible_fks[column.name] if ref_table.primaryKey.formattedType != column.type: continue fk = table.createForeignKey(column.name+"_fk") fk.referencedTable = ref_table fk.columns.append(column) fk.referencedColumn.append(ref_table.primaryKey) print "Created foreign key %s from %s.%s to %s.%s" % (fk.name, table.name, column.name, ref_table.name, ref_table.primaryKey.name) auto_create_fks(grt.root.wb.doc.physicalModels[0].catalog.schemata[0]) Creating a Plugin from a Script To create a plugin from an arbitrary script, it is first necessary to make the file a module, and export the required function from it. It is then necessary to declare the module as a plugin, and specify the return type and input arguments. from wb import * import grt ModuleInfo = DefineModule(name="AutoFK", author="John Doe", version="1.0") @ModuleInfo.plugin("sample.createGuessedForeignKeys", caption="Create Foreign Keys from ColumnNames", input=[wbinputs.objectOfClass("db.mysql.schema")], groups=["Overview/Utility"]) @ModuleInfo.export(grt.INT, grt.classes.db_mysql_Schema) def auto_create_fks(schema): ... With the addition of the preceding code, the auto_create_fks() function is exported and will be added to the schema context menu in the model overview. When invoked, it receives the currently selected schema as its input. 


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


c1title: Adding Views to the Physical Schemata
c2content:
 7.7.3.1. Adding Views to the Physical Schemata 7.7.3.1. Adding Views to the Physical Schemata To add a view, double-clicking the Add View icon in the Physical Schemata section of the MySQL Model page. The default name of the view is view1 . If a view with this name already exists, the new view is named view2 . Adding a new view automatically opens the view editor docked at the bottom of the application. For information about using the view editor, see Section 7.7.3.3, “The View Editor” . Right-clicking a view opens a pop-up menu with the following items: Cut ' view_name ' Copy ' view_name ' Paste Edit View... Edit in New Window... Copy SQL to Clipboard Delete ' view_name ' If the table editor is not open, the Edit View... item opens it. If it is already open, the selected table replaces the previous one. Edit in New Window... opens a new view editor tab. The cut and copy items are useful for copying views between different schemata. Copy SQL to Clipboard copies the CREATE VIEW statement to the clipboard. Warning Use the Delete ' view_name ' item to remove a view from the database. There will be no confirmation dialog box. Any views added to the Physical Schemata section also show up in the Catalog palette on the left side of the application. They may be added to an EER Diagram, when in the EER Diagram tab, by dragging and dropping them from this palette. 


c1title: Chapter 11. MySQL Workbench FAQ
c2content:
 Chapter 11. MySQL Workbench FAQ Chapter 11. MySQL Workbench FAQ Frequently Asked Questions with answers. Questions 11.1: How does MySQL Workbench increase import performance? 11.2: MySQL Workbench 5.0 appears to run slowly. How can I increase performance? 11.3: I get errors when creating or placing objects on an EER Diagram. I am using OpenGL rendering, AMD processor, and ATI graphics hardware. Questions and Answers 11.1: How does MySQL Workbench increase import performance? When a model is exported using the main menu item File , Export , Forward Engineer SQL CREATE Script , some server variables are temporarily set to enable faster SQL import by the server. The statements added at the start of the code are: SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0; SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0; SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='TRADITIONAL'; These statements function as follows: SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0; : Determines whether InnoDB performs duplicate key checks. Import is much faster for large data sets if this check is not performed. SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0; : Determines whether the server should check that a referenced table exists when defining a foreign key. Due to potential circular references, this check must be turned off for the duration of the import, to permit defining foreign keys. SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='TRADITIONAL'; : Sets SQL_MODE to TRADITIONAL , causing the server to operate in a more restrictive mode. These server variables are then reset at the end of the script using the following statements: SET SQL_MODE=@OLD_SQL_MODE; SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS; SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS; 11.2: MySQL Workbench 5.0 appears to run slowly. How can I increase performance? Although graphics rendering may appear slow, there are several other reasons why performance may be less than expected. The following tips may offer improved performance: Upgrade to the latest version. MySQL Workbench 5.0 is still being continually maintained and some performance-related issues may have been resolved. Limit the number of steps to save in the Undo History facility. Depending on the operations performed, having an infinite undo history can use a lot of memory after a few hours of work. In Tools , Options , General , enter a number in the range 10 to 20 into the Undo History Size spinbox. Disable relationship line crossing rendering. In large diagrams, there may be a significant overhead when drawing these line crossings. In Tools , Options , Diagram , uncheck the option named Draw Line Crossings . Check your graphics card driver. The GDI rendering used in MySQL Workbench 5.0 is not inherently slow, as most video drivers support hardware acceleration for GDI functions. It can help if you have the latest native video drivers for your graphics card. Upgrade to MySQL Workbench 5.1. MySQL Workbench 5.1 has had many operations optimized. For example, opening an object editor, such as the table editor, is much faster, even with a large model loaded. However, these core optimizations will not be back-ported to 5.0. 11.3: I get errors when creating or placing objects on an EER Diagram. I am using OpenGL rendering, AMD processor, and ATI graphics hardware. To solve this problem renew the ATI drivers pack, which can be downloaded from the AMD Web site . 


c1title: Modules
c2content:
 9.2. Modules 9.2. Modules In the GRT Modules are libraries containing a list of functions that are exported for use by code in other modules, scripts, or Workbench itself. Modules can currently be written in C++, Lua, or Python, but the data types used for arguments and the return value must be GRT types. GRT modules are similar to Python modules, but are imported from the built-in grt module, instead of directly from an external file. The list of modules loaded into the grt module is obtained from grt.modules . Modules can be imported in Python using statements such as from grt.modules import WbModel . To export functions as a module from Python code, you must carry out the following steps: The source file must be located in the user modules folder. This path is displayed in the Workbench Scripting Shell with the label Looking for user plugins in... . It is also possible to install the file using the main menu item Scripting , Install Plugin/Module File . The source file name must have the extension _grt.py ; for example, my_module_grt.py . Some module metadata must be defined. This can be done using the DefineModule function from the wb module: from wb import * ModuleInfo = DefineModule(name='MyModule', author='Your Name', version='1.0') Functions to be exported require their signature to be declared. This is achieved using the export decorator in the previously created ModuleInfo object: @ModuleInfo.export(grt.INT, grt.STRING) def checkString(s): ... For the export statement, the return type is listed first, followed by the input parameter types, specified as GRT typenames. The following typenames can be used: grt.INT : An integer value. Also used for boolean values. grt.DOUBLE : A floating-point numeric value. grt.STRING : UTF-8 or ASCII string data. grt.DICT : A key/value dictionary item. Keys must be strings. grt.LIST : A list of other values. It is possible to specify the type of the contents as a tuple in the form (grt.LIST, &lt;type-or-class&gt;) . For example, (grt.LIST, grt.STRING) for a list of strings. For a list of table objects, the following would be specified: (grt.LIST, grt.classes.db_table) . grt.OBJECT : An instance of a GRT object or a GRT class object, from grt.classes . Note that these types are defined in the grt module, which must be imported before they can be used. The following code snippet illustrates declaring a module that exports a single function: from wb import * import grt ModuleInfo = DefineModule(name='MyModule', author="your name", version='1.0') @ModuleInfo.export(grt.DOUBLE, grt.STRING, (grt.LIST, grt.DOUBLE)) def printListSum(message, doubleList): sum = 0 for d in doubleList: sum = sum + d print message, sum return sum 


c1title: The View Tool
c2content:
 7.6.1.8. The View Tool 7.6.1.8. The View Tool Use this tool to create a view on an EER Diagram canvas. When the table tool is activated, a schema list appears on the toolbar below the main menu, enabling you to associate the new view with a specific schema. You can also select a color for the object by choosing from the color list to the right of the schema list. After selecting this tool, clicking the canvas creates a new view. To edit this view, right-click it and choose Edit View... or Edit in New Window... from the pop-up menu. To activate the view tool from the keyboard, use the V key. For more information about creating and editing views, see Section 7.7.3, “Creating Views” . 


c1title: Changes in MySQL Workbench 5.2.32 (05 March 2011)
c2content:
 A.1.7. Changes in MySQL Workbench 5.2.32 (05 March 2011) A.1.7. Changes in MySQL Workbench 5.2.32 (05 March 2011) This section documents all changes and bug fixes applied since the release of 5.2.31a. Functionality Added or Changed Changing the default schema now modifies the selected schema name to be bold. (Bug #57710, Bug #11764836) In the SQL Editor, in the event of a crash, the content and state of script tabs was lost if not previously saved. MySQL Workbench now autosaves the content and state of the SQL Editor. (Bug #57667, Bug #11764794) MySQL Workbench has been improved so that an errors are more clearly identified if they occur when synchronizing with a live server, or forward engineering to a live server. (Bug #55158, Bug #11762551) Bugs Fixed These query beautifier problems were corrected: Aggregate function text was deleted. In the SQL Editor, the beautifier did not process functions such as COUNT() or NOW() or correctly. It rendered the function with additional spaces, causing a syntax error. (Bug #60070, Bug #11766850, Bug #59450, Bug #11766354, Bug #58714, Bug #11765722) On Microsoft Windows 7, if a user profile launched MySQL Workbench, it crashed if additional user profiles attempted to launch it. The first instance needed to be closed before another user profile was able to run MySQL Workbench. (Bug #59913, Bug #11766733) MySQL Workbench crashed when closing the query results tab in the SQL Editor. (Bug #59774, Bug #11766626) When deleting a recursive foreign key constraint, the primary key was also mistakenly deleted. (Bug #59668, Bug #11766538) On the Home screen, right-clicking a connection and selecting Start Command Line Client produced this error: Error calling PyWbUtils.startCommandLineClientForConnection: see output for details output: Message: Error executing plugin wb.tools.comdlineClient: error calling wb.tools.cmdlineClient Traceback: File "C:\Program Files\MySQL\MySQL Workbench 5.2 CE\modules \wb_utils_grt.py", line 96, in startCommandLineClientForConnection schema = conn.parameterValues["schema"].replace("\\", "\\\\").replace('"', '\\"') AttributeError: 'NoneType' object has no attribute 'replace' (Bug #59638, Bug #11766510) Attempting to create a new server instance resulted in this error message: We are sorry for the inconvenience but an unexpected exception has been raised by one of the MySQL Workbench modules. In order to fix this issue we would kindly ask you to file a bug report. You can do that by pressing the [Report Bug] button below. (Bug #59578, Bug #11766465) In the EER Diagram view, clicking a table to edit its details sometimes resulted in this error: Cannot access a disposed object. Object name: 'DockedWindowPlugin' (Bug #59559, Bug #11766448) In the EER Diagram view, MySQL Workbench crashed on selecting a new table. This happened if the Privileges tab was open for the currently selected table. (Bug #59535, Bug #11766431) In the SQL Editor, if a '`' (grave accent) character was entered, any subsequently entered control keys such as the arrow keys or the backspace key failed to function correctly. (Bug #59528, Bug #11766425) Running the version of mysqldump supplied with the MySQL Server package resulted in this error: Operation failed with exitcode -1073741819 (Bug #59411) The collapsed state of Workbench Central, on the Home screen, was not saved between MySQL Workbench sessions. If after collapsing Workbench Central to save vertical space, the application was exited and restarted, Workbench Central was drawn in the expanded state. (Bug #59399) Attempting to create a new user with MySQL Workbench failed with this error: Unhandled exception: Error adding account accountName@%: (Bug #59000) Generated scripts did not manage connection variables cleanly. For example, the autocommit state was not preserved by the script produced by forward engineering an SQL CREATE script. The script switched off autocommit , but did not then restore it correctly to its previous state. (Bug #58998, Bug #11765974) On Windows, the Python debugger stopped the script being executed in MySQL Workbench after about one second. It then displayed the message "abort" in the output pane. (Bug #58960, Bug #11765943) When a model was forward engineered, the primary keys were not created in the generated script. (Bug #58926, Bug #11765913) SQL Editor did not load certain text files correctly, and inserted erroneous empty lines between text. (Bug #58850) In the Administrator, when making a backup with the --single-transaction option enabled, the --lock-tables option was erroneously still enabled. (Bug #58562, Bug #11765579) Trying to create a relationship between two tables, created in a plugin, produced this error: MySQL Workbench has encountered a problem Es wurde versucht, im geschützten Speicher zu lesen oder zu schreiben. Dies ist häufig ein Hinweis darauf, dass anderer Speicher beschädigt ist. (Bug #58554, Bug #11765571) When synchronizing a model with a server, indexes were unnecessarily dropped and recreated. (Bug #58238, Bug #11765284) Forward engineering a model containing two schema resulted in a generated script that contained incorrect SQL: DELIMITER ;USE `Schema2` ; The DELIMITER and USE statements should not have appeared on the same line. (Bug #58117, Bug #11765180) When running MySQL Workbench with the arguments “ -script [FILE.lua] -quit-when-done ”, it crashed with this message: [MySQL Workbench Unexpected Error] MySQL Workbench has encountered a problem Cannot access released / disposed object. Object name: "MainForm". (Bug #57570, Bug #11764708) In the SQL Editor, switching between query tabs did not switch the associated results panel. (Bug #57486, Bug #11764628) In the SQL Editor, when editing table data, this error dialog was displayed: Either schema or table is not selected. Each time the dialog was acknowledged, it was subsequently redisplayed, preventing further progress. (Bug #57127, Bug #11764305) In the Columns tab of the table editor, copying and pasting the Datatype field using Control+C and Control+V resulted in the text “ table_copy1 ” being pasted, rather than the copied datatype. (Bug #56501, Bug #11763749) When exporting a model, if the Skip Creation of FOREIGN KEYS option was selected, indexes were not created. (Bug #56389, Bug #11763649) At startup, MySQL Workbench displayed a blank screen if it had previously been closed after using the menu item Help , System Info , and then clicking the main application window close button. (Bug #55764, Bug #11763097) When forward engineering a model, the generated script resulted in SQL errors when executed on the server. This happened when the following options were selected: DROP Objects Before Each CREATE Object Omit Schema Qualifier in Object Names Generate Separate CREATE INDEX Statements Generate INSERT Statements for Tables (Bug #54836, Bug #11762262) The generated alter script contained erroneous statements adding and deleting indexes and foreign keys. (Bug #54180, Bug #11761666) The text in the SQL Editor was not anti-aliased, which hindered readability by causing the text to visually conflict with anti-aliased text elsewhere in MySQL Workbench. (Bug #54059, Bug #11761553) On Microsoft Windows, if the Windows Firewall application was not running, installation of MySQL Workbench would halt with an error dialog indicating that it was unable to connect to the firewall. (Bug #53603, Bug #11761143) Primary and foreign keys are now displayed with different icons. (Bug #53503, Bug #11761049) Dropping a table from the Object Browser did not remove the table's icon. (Bug #52878, Bug #11760462) There were numerous locations within MySQL Workbench where the availability of context-sensitive menus (right-clicking) was expected and useful, but not available. (Bug #49622, Bug #11757556) Forward engineering a table containing a multiple-line comment resulted in this error: ERROR 1105 (HY000) at line 97: Too long comment for table 'motd' (Bug #38597) 


c1title: The Configuration Tab
c2content:
 8.7.2. The Configuration Tab 8.7.2. The Configuration Tab The Configuration tab enables you to edit the my.ini or my.cnf configuration file by selecting check boxes and other GUI controls. This tab also features a number of subtabs, which provide access to various sub-sections within the configuration file. The subtabs are: General MyISAM InnoDB Performance Log Files Replication Networking Security Advanced Figure 8.5. Administrator - Configuration Tab 


c1title: Routines
c2content:
 7.7.4.1. Routines 7.7.4.1. Routines 7.7.4.1.1. Adding Routines to the Physical Schemata 7.7.4.1.2. The Routine Editor 7.7.4.1.1. Adding Routines to the Physical Schemata To add a routine, double-click the Add Routine icon in the Physical Schemata section of the MySQL Model page. The default name of the routine is routine1 . If a routine with this name already exists, the new routine is named routine2 . Adding a new routine automatically opens the routine editor docked at the bottom of the application. For information about using the routine editor, see Section 7.7.4.1.2, “The Routine Editor” . Right-clicking a routine opens a pop-up menu with the following items: Rename Cut ' routine_name ' Copy ' routine_name ' Paste Edit Routine... Edit in New Window... Copy SQL to Clipboard Delete ' routine_name ' The Edit Routine... item opens the routine editor. The cut and paste items are useful for copying routines between different schemata. Note Deleting the code for a routine from the Routines tab of the Routine Group Editor results in removal of the routine object from the model. Note To remove a routine from a routine group, use the controls on the Routine Group tab of the Routine Group Editor. The action of the delete option varies depending upon how you have configured MySQL Workbench. For more information, see Section 5.4.4, “The Model Tab” . 7.7.4.1.2. The Routine Editor 7.7.4.1.2.1. The Routine Tab 7.7.4.1.2.2. The Privileges Tab To invoke the routine editor, double-click a routine in the Physical Schemata section on the MySQL Model page. This opens the routine editor docked at the bottom of the application. Any number of routines may be open at the same time. Each additional routine appears as a tab at the top of the routine editor. Routine and Privileges tabs appear at the bottom of the routine editor. Navigate between different tabs using the mouse or from the keyboard by pressing Control+Alt+Tab . 7.7.4.1.2.1. The Routine Tab Use the Routine tab of the routine editor to perform the following tasks: Rename the routine using the Name field. Enter the SQL to create a routine using the SQL field. 7.7.4.1.2.2. The Privileges Tab The Privileges tab of the routine editor functions in exactly the same way as the Privileges tab of the table editor. For more information, see Section 7.7.1.3.10, “The Privileges Tab” . Note Privileges are available only in the Standard Edition of MySQL Workbench. 


c1title: The View Editor
c2content:
 7.7.3.3. The View Editor 7.7.3.3. The View Editor To invoke the view editor, double-click a view object on the EER Diagram canvas or double-click a view in the Physical Schemata section on the MySQL Model page. This opens the view editor docked at the bottom of the application. Double-clicking the title bar undocks the editor. Do the same to redock it. Any number of views may be open at the same time. Each additional view appears as a tab at the top of the view editor. There are three tabs at the bottom of the view editor: View , Comments , and Privileges . Navigate between different tabs using the mouse or from the keyboard by pressing Control+Alt+Tab . The View Tab Use the View tab to perform the following tasks: Rename the view using the Name text box. Enter the SQL to create a view using the SQL field. Comment a view using the Comments text area. The Comments Tab This tab enables you to enter comments for a particular view. The Privileges Tab The Privileges tab of the view editor functions in exactly the same way as the Privileges tab of the table editor. For more information, see Section 7.7.1.3.10, “The Privileges Tab” . 


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


c1title: Chapter 3. Installing and Launching MySQL Workbench
c2content:
 Chapter 3. Installing and Launching MySQL Workbench Chapter 3. Installing and Launching MySQL Workbench Table of Contents 3.1. Hardware Requirements 3.2. Software Requirements 3.3. Starting MySQL Workbench 3.3.1. Installing MySQL Workbench on Windows 3.3.2. Launching MySQL Workbench on Windows 3.3.3. Uninstalling MySQL Workbench on Windows 3.3.4. Installing MySQL Workbench on Linux 3.3.5. Launching MySQL Workbench on Linux 3.3.6. Uninstalling MySQL Workbench on Linux 3.3.7. Installing MySQL Workbench on Mac OS X 3.3.8. Launching MySQL Workbench on Mac OS X 3.3.9. Uninstalling MySQL Workbench on Mac OS X 3.4. Activation Procedure (Commercial Version) MySQL Workbench is available for the following platforms: Windows Linux Mac OS X Binary distributions of MySQL Workbench are available for the preceding platforms. Source code distributions are also available as a tar.gz package or an RPM package. The following sections explain the installation process for each of these platforms. 


c1title: General Validation
c2content:
 7.10.1. General Validation 7.10.1. General Validation The following list names the general validation types and gives examples of specific violations: Empty Content Validation A table with no columns A routine or view with no SQL code defined A routine group containing no routines A table, view, or routine not referenced by at least one role A user with no privileges Objects such as tables that do not appear on at least one EER Diagram Table Efficiency Validation A table with no primary key A primary key that does not use an integer-based data type A foreign key that refers to a column with a different data type Duplicated Identifiers Validation Duplicate object names Duplicate role or user names Duplicate index or routine names Consistency Validation Use of the same column with columns of differing data types Logic Validation A foreign key that refers to a column other than the primary key in the source table Any object that is object is either read only or write only by role definition Placeholder objects left over from reverse engineering 


c1title: Changes in MySQL Workbench 5.2.24 (21 June 2010)
c2content:
 A.1.16. Changes in MySQL Workbench 5.2.24 (21 June 2010) A.1.16. Changes in MySQL Workbench 5.2.24 (21 June 2010) This section documents all changes and bug fixes applied since the release of 5.2.23. Functionality Added or Changed A Kill Query button has been added to the Connections tab of the Administrator. (Bug #54409) Bugs Fixed In the Configuration tab of the Administrator, this error resulted when changes were applied: Could not Save Configuration File There was an error saving the configurationfile: exec_cmd() takes at least 3 arguments (2 given) This happened while connecting to a FreeBSD 7.1 server over an SSH connection. (Bug #54647) In the SQL Editor, entering a space into the SQL Query tab, selecting an external tab (such as the Overview tab or Output tab), and then selecting File , Close Tab caused MySQL Workbench to crash. Further, the Add Table dialog had numerous issues, including inability to select PK and other check boxes, failure to validate input, inability to apply changes, and deletion of user data in certain cases. (Bug #54124) The Connections tab in the Administrator did not feature automatic refresh. This had to be manually triggered using the Refresh button. Further, the Kill Connection button was sometimes incorrectly disabled. (Bug #53703) If a foreign key relationship was created, and its modelOnly property set, the relationship was correctly excluded when the model was synchronized with a live database. However, the DDL code for the foreign key indexes was still generated in the synchronization script. (Bug #53420) Synchronizing a model with a live database generated ALTER statements, even when there appeared to be no difference between the database and the model. (Bug #50938) In the SQL Editor, there was a space between the Execute and Stop toolbar buttons. Hovering the mouse cursor over this space resulted in the tooltip “ Explain selected SQL ” being displayed, which appeared to indicate a missing icon. (Bug #49316) 


c1title: Installing MySQL Workbench on Mac OS X
c2content:
 3.3.7. Installing MySQL Workbench on Mac OS X 3.3.7. Installing MySQL Workbench on Mac OS X MySQL Workbench for Mac OS X is distributed as a DMG file. The file is named mysql-workbench-oss- version -osx10.5-i686.dmg , where version is the MySQL Workbench version. To install MySQL Workbench on Mac OS X, download the file. Double-click the downloaded file. You will be presented with the installation window. Figure 3.1. MySQL Workbench Mac OS X Installation Window Drag the MySQL Workbench icon onto the Applications icon as instructed. MySQL Workbench is now installed. You can now launch MySQL Workbench from the Applications folder. 


c1title: Adding an EER Diagram
c2content:
 7.8.1.1. Adding an EER Diagram 7.8.1.1. Adding an EER Diagram To create an EER diagram for the sakila database, first add an EER diagram by double-clicking the Add Diagram icon in the EER Diagrams panel to create and open a new EER Diagram editor. The EER Diagram canvas is where object modeling takes place. To add a table to the canvas, select the Catalog tab in the middle panel on the right side of the application to display any schemata that appear in the MySQL Model tab. Find the sakila schema and expand the view of its objects by clicking the + button to the left of the schema name. Expand the tables list in the same way. You can add tables to the EER canvas by dragging them from the Catalog panel dropping them onto the canvas. Drop the address table and the city table onto the canvas. Figure 7.42. Adding Tables to the Canvas MySQL Workbench automatically discovers that address.city_id has been defined as a foreign key referencing the city.city_id field. Drop the country table onto the canvas and immediately you should see the relationship between the country table and the city table. (To view all the relationships in the sakila database, see Figure 7.45, “The sakila Database EER Diagram” .) Click the Properties tab of the panel on the lower right, then click one of the tables on the canvas. This displays the properties of the table in the Properties window. While a table is selected, you can use the Properties window to change a table's properties. For example, entering #FF0000 for the color value will change the color accent to red. Changing the color of a table is a good way to identify a table quickly—something that becomes more important as the number of tables increases. Changing the color of a table is also an easy way to identify a table in the Model Navigator panel. This panel, the uppermost panel on the left side of the page, gives a bird's eye view of the entire EER canvas. Save your changes to a MySQL Workbench Models file ( mwb extension) by choosing Save from the File menu or by using the keyboard command Control+S . 


c1title: Basic Modeling
c2content:
 7.8.3. Basic Modeling 7.8.3. Basic Modeling 7.8.3.1. Adding a Table 7.8.3.2. Creating a Foreign Key On the MySQL Model page, double-click the Add Diagram icon. This creates and opens a new EER Diagram canvas. Figure 7.44. Adding an EER Diagram From an EER diagram page you can graphically design a database. 


c1title: Pixman License
c2content:
 B.17. Pixman License B.17. Pixman License The following software may be included in this product: Pixman Pixman v0.21.2 The following is the MIT license, agreed upon by most contributors. Copyright holders of new code should use this license statement where possible. They may also add themselves to the list below. Copyright 1987, 1988, 1989, 1998 The Open Group Copyright 1987, 1988, 1989 Digital Equipment Corporation Copyright 1999, 2004, 2008 Keith Packard Copyright 2000 SuSE, Inc. Copyright 2000 Keith Packard, member of The XFree86 Project, Inc. Copyright 2004, 2005, 2007, 2008, 2009, 2010 Red Hat, Inc. Copyright 2004 Nicholas Miell Copyright 2005 Lars Knoll &amp; Zack Rusin, Trolltech Copyright 2005 Trolltech AS Copyright 2007 Luca Barbato Copyright 2008 Aaron Plattner, NVIDIA Corporation Copyright 2008 Rodrigo Kumpera Copyright 2008 André Tupinambá Copyright 2008 Mozilla Corporation Copyright 2008 Frederic Plourde Copyright 2009, Oracle and/or its affiliates. All rights reserved. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice (including the next paragraph) shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Pixman v0.17.4 and lower: The following is the 'standard copyright' agreed upon by most contributors, and is currently the canonical icense, though a modification is currently under discussion. Copyright holders of new code should use this license statement where possible, and append their name to this list. Copyright 1987, 1988, 1989, 1998 The Open Group Copyright 1987, 1988, 1989 Digital Equipment Corporation Copyright 1999, 2004, 2008 Keith Packard Copyright 2000 SuSE, Inc. Copyright 2000 Keith Packard, member of The XFree86 Project, Inc. Copyright 2004, 2005, 2007, 2008 Red Hat, Inc. Copyright 2004 Nicholas Miell Copyright 2005 Lars Knoll &amp; Zack Rusin, Trolltech Copyright 2005 Trolltech AS Copyright 2007 Luca Barbato Copyright 2008 Aaron Plattner, NVIDIA Corporation Copyright 2008 Rodrigo Kumpera Copyright 2008 AndrÃ© TupinambÃ¡ Copyright 2008 Mozilla Corporation Copyright 2008 Frederic Plourde Copyright 2009 Sun Microsystems, Inc. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice (including the next paragraph) shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. 


