Workbench en

MySQL Workbench
MySQL Workbench
Abstract This manual documents the MySQL Workbench SE version 5.2 and the MySQL Workbench OSS version 5.2. If you have not yet installed MySQL Workbench OSS please download your free copy from the download site. MySQL Workbench OSS is available for Windows, Mac OS X, and Linux. For legal information, see the Legal Notices. Document generated on: 2012-12-13 (revision: 33533)
Table of Contents
Preface and Legal Notices ................................................................................................................. ix 1. MySQL Workbench Introduction ...................................................................................................... 1 2. MySQL Workbench Editions ........................................................................................................... 3 3. Installing and Launching MySQL Workbench ................................................................................... 5 3.1. Hardware Requirements ....................................................................................................... 5 3.2. Software Requirements ........................................................................................................ 5 3.3. Starting MySQL Workbench ................................................................................................. 6 3.3.1. Installing MySQL Workbench on Windows ................................................................. 7 3.3.2. Launching MySQL Workbench on Windows ............................................................... 7 3.3.3. Uninstalling MySQL Workbench on Windows ............................................................. 8 3.3.4. Installing MySQL Workbench on Linux ....................................................................... 9 3.3.5. Launching MySQL Workbench on Linux ..................................................................... 9 3.3.6. Uninstalling MySQL Workbench on Linux ................................................................... 9 3.3.7. Installing MySQL Workbench on Mac OS X ............................................................. 10 3.3.8. Launching MySQL Workbench on Mac OS X ........................................................... 10 3.3.9. Uninstalling MySQL Workbench on Mac OS X .......................................................... 11 4. Getting Started Tutorial ................................................................................................................. 13 4.1. Administering a MySQL Server ........................................................................................... 13 4.2. Creating a Model ............................................................................................................... 25 4.3. Adding Data to Your Database ........................................................................................... 31 5. The Home Window ....................................................................................................................... 35 5.1. Workbench Central ............................................................................................................ 36 5.2. Workspace ........................................................................................................................ 37 5.3. Workbench Application Minimum Window Size .................................................................... 37 5.4. Workbench Preferences ..................................................................................................... 37 5.4.1. The General Tab .................................................................................................... 39 5.4.2. The Administrator Tab ............................................................................................. 39 5.4.3. The SQL Editor Tab ................................................................................................ 39 5.4.4. The Model Tab ....................................................................................................... 41 5.4.5. The MySQL Tab ..................................................................................................... 42 5.4.6. The Diagram Tab .................................................................................................... 42 5.4.7. The Appearance Tab .............................................................................................. 43 6. SQL Development ........................................................................................................................ 45 6.1. Open Connection to Start Querying .................................................................................... 45 6.2. New Connection ................................................................................................................ 46 6.3. Edit Table Data ................................................................................................................. 46 6.4. Edit SQL Script .................................................................................................................. 46 6.5. Manage Connections ......................................................................................................... 46 6.6. Manage DB Connections Dialog ......................................................................................... 46 6.6.1. The Password Storage Vault ................................................................................... 47 6.6.2. Standard TCP/IP Connection ................................................................................... 48 6.6.3. Local Socket/Pipe Connection ................................................................................. 49 6.6.4. Standard TCP/IP over SSH Connection ................................................................... 50 6.7. SQL Editor ........................................................................................................................ 50 6.7.1. Main Menu ............................................................................................................. 51 6.7.2. Toolbar ................................................................................................................... 53 6.7.3. SQL Query Panel .................................................................................................... 53 6.7.4. Main Tabsheets ...................................................................................................... 54 6.7.5. Sidebar ................................................................................................................... 57 7. Data Modeling .............................................................................................................................. 63 7.1. Open an Existing EER Model ............................................................................................. 64
iii
MySQL Workbench
Create New EER Model ..................................................................................................... 64 Create EER Model from Existing Database ......................................................................... 64 Create EER Model from SQL Script ................................................................................... 64 Model Editor ...................................................................................................................... 65 7.5.1. Modeling Menus ...................................................................................................... 66 7.5.2. The Toolbar ............................................................................................................ 76 7.5.3. EER Diagrams ........................................................................................................ 77 7.5.4. The Physical Schemata Panel ................................................................................. 77 7.5.5. The Schema Privileges Panel .................................................................................. 78 7.5.6. The SQL Scripts Panel ............................................................................................ 79 7.5.7. The Model Notes Panel ........................................................................................... 79 7.5.8. The History Palette ................................................................................................. 79 7.5.9. The Model Navigator Panel ..................................................................................... 80 7.5.10. The Catalog Tree Palette ...................................................................................... 80 7.5.11. The Layers Palette ................................................................................................ 81 7.5.12. The Properties Palette ........................................................................................... 81 7.6. EER Diagram Editor .......................................................................................................... 82 7.6.1. The Vertical Toolbar ................................................................................................ 82 7.7. Working with Models .......................................................................................................... 86 7.7.1. Creating Tables ...................................................................................................... 86 7.7.2. Creating Foreign Key Relationships ......................................................................... 98 7.7.3. Creating Views ...................................................................................................... 101 7.7.4. Creating Routines and Routine Groups .................................................................. 103 7.7.5. Creating Layers ..................................................................................................... 107 7.7.6. Creating Notes ...................................................................................................... 108 7.7.7. Creating Text Objects ............................................................................................ 109 7.7.8. Creating Images .................................................................................................... 110 7.7.9. Reverse Engineering ............................................................................................. 111 7.7.10. Forward Engineering ........................................................................................... 120 7.8. Modeling Tutorials ............................................................................................................ 140 7.8.1. Importing a Data Definition SQL Script ................................................................... 141 7.8.2. Using the Default Schema ..................................................................................... 142 7.8.3. Basic Modeling ...................................................................................................... 143 7.8.4. Documenting the sakila Database ....................................................................... 144 7.9. Printing ............................................................................................................................ 146 7.9.1. Printing Options .................................................................................................... 146 7.10. MySQL Workbench Schema Validation Plugins (Commercial Version) .............................. 146 7.10.1. General Validation ............................................................................................... 146 7.10.2. MySQL-Specific Validation ................................................................................... 147 7.11. The DBDoc Model Reporting Dialog Window (Commercial Version) .................................. 148 7.12. Customizing DBDoc Model Reporting Templates ............................................................. 151 7.12.1. Supported Template Markers ............................................................................... 155 7.12.2. Creating a Custom Template ............................................................................... 158 8. Generating code overview ........................................................................................................... 163 8.1. Generating SQL queries ................................................................................................... 163 8.2. Generating PHP code ...................................................................................................... 163 9. Server Administration .................................................................................................................. 165 9.1. Server Administration ....................................................................................................... 165 9.2. New Server Instance ........................................................................................................ 166 9.3. Manage Data Import/Export .............................................................................................. 166 9.4. Manage Security .............................................................................................................. 166 9.5. Manage Server Instances ................................................................................................. 166 9.6. Creating and Managing Server Instances .......................................................................... 166 9.6.1. New Server Instance Wizard ................................................................................. 166
7.2. 7.3. 7.4. 7.5.
iv
MySQL Workbench
9.6.2. Manage Server Instances Dialog ........................................................................... 9.7. Server Administration and Configuration ............................................................................ 9.7.1. The Startup Tab .................................................................................................... 9.7.2. The Configuration Tab ........................................................................................... 9.7.3. The Accounts Tab ................................................................................................. 9.7.4. The Connections Tab ............................................................................................ 9.7.5. The Variables Tab ................................................................................................. 9.7.6. The Data Dump Tab ............................................................................................. 9.7.7. The Logs Tab ....................................................................................................... 10. Database Migration Wizard ....................................................................................................... 10.1. General installation requirements .................................................................................... 10.1.1. ODBC Libraries ................................................................................................... 10.1.2. ODBC Drivers ..................................................................................................... 10.2. Migration Overview ......................................................................................................... 10.2.1. A visual guide to performing a database migration ................................................ 10.2.2. Migrating from supported databases ..................................................................... 10.2.3. Migrating from unsupported (generic) databases ................................................... 10.3. Conceptual DBMS equivalents ........................................................................................ 10.4. Microsoft SQL Server migration ...................................................................................... 10.4.1. Preparations ........................................................................................................ 10.4.2. Drivers ................................................................................................................ 10.4.3. Connection Setup ................................................................................................ 10.4.4. Microsoft SQL Server Type Mapping .................................................................... 10.5. PostgreSQL migration .................................................................................................... 10.5.1. Preparations ........................................................................................................ 10.5.2. Drivers ................................................................................................................ 10.5.3. Connection Setup ................................................................................................ 10.5.4. PostgreSQL Type Mapping .................................................................................. 10.6. MySQL migration ........................................................................................................... 10.7. Using the MySQL Workbench Migration Wizard ............................................................... 10.7.1. Connecting to the databases ............................................................................... 10.7.2. Schemata Retrieval and Selection ........................................................................ 10.7.3. Reverse Engineering ........................................................................................... 10.7.4. Object Selection .................................................................................................. 10.7.5. Migration ............................................................................................................. 10.7.6. Manual Editing .................................................................................................... 10.7.7. Target Creation Options ....................................................................................... 10.7.8. Schema Creation ................................................................................................. 10.7.9. Create Target Results ......................................................................................... 10.7.10. Data Migration Setup ......................................................................................... 10.7.11. Bulk Data Transfer ............................................................................................ 10.7.12. Migration Report ................................................................................................ 10.8. MySQL Workbench Migration Wizard FAQ ...................................................................... 11. Extending Workbench ............................................................................................................... 11.1. GRT and Workbench Data Organization ......................................................................... 11.2. Modules ......................................................................................................................... 11.3. Plugins .......................................................................................................................... 11.4. Adding a GUI to a Plugin Using MForms ......................................................................... 11.5. The Workbench Scripting Shell ....................................................................................... 11.5.1. Exploring the Workbench Scripting Shell .............................................................. 11.5.2. The Shell Window ............................................................................................... 11.5.3. The Files, Globals, Classes, and Modules Tabs .................................................... 11.6. Tutorial: Writing Plugins .................................................................................................. 12. Keyboard Shortcuts ...................................................................................................................
169 171 173 174 176 178 179 180 183 185 186 186 187 187 188 202 203 203 205 205 205 207 207 208 208 208 209 209 210 210 210 211 211 211 211 211 211 212 212 212 212 212 212 213 213 214 215 216 217 217 218 219 220 223
MySQL Workbench
13. MySQL Utilities ......................................................................................................................... 227 13.1. Introduction .................................................................................................................... 227 13.1.1. Introduction to MySQL Utilities ............................................................................. 227 13.1.2. Connection Parameters ....................................................................................... 228 13.1.3. Introduction to extending the MySQL Utilities ........................................................ 229 13.2. Commands .................................................................................................................... 235 13.2.1. mysql.utilities.command.grep Search Databases for Objects ................. 235 13.2.2. mysql.utilities.command.proc Search Processes on Servers ................. 236 13.3. Manual Pages ................................................................................................................ 238 13.3.1. MySQL Utilities Overview Brief overview of command-line utilities ...................... 238 13.3.2. mut MySQL Utilities Testing ............................................................................ 240 13.3.3. mysqldbcompare Compare Two Databases and Identify Differences ................ 243 13.3.4. mysqldbcopy Copy Database Objects Between Servers .................................. 249 13.3.5. mysqldbexport Export Object Definitions or Data from a Database ................. 253 13.3.6. mysqldbimport Import Object Definitions or Data into a Database ................... 260 13.3.7. mysqldiff Identify Differences Among Database Objects ................................ 263 13.3.8. mysqldiskusage Show Database Disk Usage ............................................... 267 13.3.9. mysqlfailover Automatic replication health monitoring and failover ................ 271 13.3.10. mysqlindexcheck Identify Potentially Redundant Table Indexes ................... 277 13.3.11. mysqlmetagrep Search Database Object Definitions .................................... 280 13.3.12. mysqlprocgrep Search Server Process Lists ............................................... 283 13.3.13. mysqlreplicate Set Up and Start Replication Between Two Servers ............ 286 13.3.14. mysqlrpladmin Administration utility for MySQL replication ........................... 290 13.3.15. mysqlrplcheck Check Replication Prerequisites .......................................... 297 13.3.16. mysqlrplshow Show Slaves for Master Server ............................................. 300 13.3.17. mysqlserverclone Clone Existing Server to Create New Server .................. 303 13.3.18. mysqlserverinfo Display Common Diagnostic Information from a Server ..... 305 13.3.19. mysqluserclone Clone Existing User to Create New User ............................ 307 13.3.20. mysqluc Command line client for running MySQL Utilities .............................. 309 13.4. Parsers .......................................................................................................................... 312 13.4.1. mysql.utilities.parser Parse MySQL Log Files ................................................... 312 13.5. Appendix ....................................................................................................................... 314 13.5.1. MySQL Utilities FAQ ........................................................................................... 314 A. Third Party Licenses ................................................................................................................... 317 A.1. .NET Flat TabControl License .......................................................................................... 318 A.2. ANTLR 3.4 License ......................................................................................................... 319 A.3. Bitstream Vera License .................................................................................................... 319 A.4. Boost Library License ...................................................................................................... 320 A.5. Cairo License .................................................................................................................. 321 A.6. CTemplate (Google Template System) License ................................................................. 321 A.7. cURL (libcurl) License ................................................................................................ 322 A.8. DockPanel Suite License ................................................................................................. 322 A.9. Dojo Toolkit v1.7.0b1 License .......................................................................................... 323 A.10. GLib License (for MySQL Workbench) ............................................................................ 323 A.11. Glitz License .................................................................................................................. 323 A.12. GNU Lesser General Public License Version 2.1, February 1999 ..................................... 324 A.13. HtmlRenderer (System.Drawing.Html) ............................................................................. 332 A.14. iODBC License .............................................................................................................. 332 A.15. Libiconv License ............................................................................................................ 333 A.16. Libintl License ................................................................................................................ 334 A.17. Libxml2 License ............................................................................................................. 334 A.18. Libzip License ................................................................................................................ 335 A.19. Lua (liblua) License ....................................................................................................... 335 A.20. Paramiko License .......................................................................................................... 336
vi
MySQL Workbench
A.21. PCRE License ............................................................................................................... A.22. Pixman License ............................................................................................................. A.23. PyCrypto License ........................................................................................................... A.24. PyODBC License ........................................................................................................... A.25. Python License .............................................................................................................. A.26. Scintilla License ............................................................................................................. A.27. ScintillaNET License ...................................................................................................... A.28. TinyXML License ........................................................................................................... A.29. TreeViewAdv for .NET License ....................................................................................... A.30. VSQLite++ License ........................................................................................................ A.31. zlib License ................................................................................................................ B. MySQL Workbench FAQ ............................................................................................................ C. MySQL Workbench and Utilities Change History .......................................................................... C.1. MySQL Workbench Change History ................................................................................. C.1.1. Changes in MySQL Workbench 5.2 ....................................................................... C.1.2. Changes in MySQL Workbench 5.1 ....................................................................... C.1.3. Changes in MySQL Workbench 5.0 ....................................................................... C.2. MySQL Utilities Change History ....................................................................................... C.2.1. Changes in Release 1.1 ....................................................................................... C.2.2. Changes in Release 1.0 .......................................................................................
336 337 339 339 340 350 352 352 353 353 354 355 357 357 357 455 473 489 489 489
vii
viii
Preface and Legal Notices

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

The Community Edition (OSS) The Community Edition is the foundation of all MySQL Workbench editionsversions 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.
Chapter 3. Installing and Launching MySQL Workbench

Table of Contents
3.1. Hardware Requirements ............................................................................................................... 5 3.2. Software Requirements ................................................................................................................ 5 3.3. Starting MySQL Workbench ......................................................................................................... 6 3.3.1. Installing MySQL Workbench on Windows ......................................................................... 7 3.3.2. Launching MySQL Workbench on Windows ....................................................................... 7 3.3.3. Uninstalling MySQL Workbench on Windows ..................................................................... 8 3.3.4. Installing MySQL Workbench on Linux ............................................................................... 9 3.3.5. Launching MySQL Workbench on Linux ............................................................................. 9 3.3.6. Uninstalling MySQL Workbench on Linux ........................................................................... 9 3.3.7. Installing MySQL Workbench on Mac OS X ..................................................................... 10 3.3.8. Launching MySQL Workbench on Mac OS X ................................................................... 10 3.3.9. Uninstalling MySQL Workbench on Mac OS X ................................................................. 11 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.
3.1. Hardware Requirements

MySQL Workbench requires a system that runs smoothly. The minimum hardware requirements are: CPU: 32-bit or 64-bit Cores: Single (Single Core 3GHz or higher, Dual Core 2GHz or higher recommended) RAM: 4 GB (6 GB or higher recommended) Graphic Accelerators: nVidia or ATI with support of OpenGL 2 or higher Display Resolution: 12801024 minimum (19201200 or higher recommended)
3.2. Software Requirements

The following operating systems are officially supported: Apple Mac OS X v10.6.1+ (32-bit/64-bit) Fedora 15 (32-bit/64-bit) Microsoft Windows 7 (32-bit/64-bit) Oracle Linux 6 (32-bit/64-bit)
Starting MySQL Workbench
Ubuntu 10.04 LTS (32-bit/64-bit) Ubuntu 11.04 (32-bit/64-bit) MySQL Workbench also has the following general requirements: Note On startup, the application checks the OpenGL version and chooses between software and hardware rendering. To determine which rendering method is being used, open the Help menu and choose the System Info item. Requirements for Linux: The requirements for Linux are embedded within their respective packages. Use the platform specific tool (for example, yum or apt) to install the package and their dependencies. Requirements for Microsoft Windows: Microsoft .NET 4.0 Framework Microsoft Visual C++ 2010 Redistributable Package (x86) Note For convenience, the Windows libraries are available as the download Dependencies for Compiling in Windows.
3.3. Starting MySQL Workbench

The procedure for launching MySQL Workbench depends on the platform. Generally, there are two ways to launch MySQL Workbench: either from the command line or from the graphical user interface of the host operating system. Using the command-line launching facility is useful when you want to customize some aspects of the way MySQL Workbench operates. The following sections describe how to launch MySQL Workbench for each of the supported platforms. In addition to platform-specific command-line options, MySQL Workbench has the following command-line options: --log-level level: Controls the verbosity level for logging output from Workbench. With increasingly levels of verbosity, the valid values for level are: error, warning, info, debug1, debug2, and debug3. The location of the generated log files are as follows: Linux: ~/.mysql/workbench/log/wb.log, Mac: ~/Library/Application Support/Workbench/log/wb.log, and on Windows: C:\Users \[your user id]\AppData\Roaming\MySQL\Workbench\wb.log --admin instance: Load the server instance specified. --query connection: Load the connection specified. --model modelfile: Load the model specified. --script script: Run the script specified. --run code: Run the code snippet specified.
Installing MySQL Workbench on Windows
--quit-when-done: Quits MySQL Workbench after --script or --run finishes.
3.3.1. Installing MySQL Workbench on Windows

MySQL Workbench for Windows can be installed using the Windows Installer package or installed manually from a Zip file. Important Installing MySQL Workbench using the Installer package requires either Administrator or Power User privileges. If you are using the Zip file without an installer, you do not need Administrator or Power User privileges. Installing MySQL Workbench Using the Installer Package MySQL Workbench can be installed using the Windows Installer (.msi) installation package. The MSI package bears the name mysql-workbench-version-win32.msi, where version indicates the MySQL Workbench version number. Improving the MySQL Installation Wizard depends on the support and feedback of users. If you find that the MySQL Installation Wizard lacks some feature important to you, or if you discover a bug, please report it in our bugs database. Select the Report a Bug item from the Help menu. 1. To install MySQL Workbench, right-click the MSI file and select the Install item from the pop-up menu, or double-click the file. 2. In the Setup Type window you may choose a Complete or Custom installation. To use all features of MySQL Workbench choose the Complete option. 3. Unless you choose otherwise, MySQL Workbench is installed in C:\%PROGRAMFILES%\MySQL \MySQL Workbench 5.1 edition_type\, where %PROGRAMFILES% is the default directory for programs for your locale. The %PROGRAMFILES% directory may be C:\Program Files or C: \programme. Installing from the Zip File If you have problems running the Installer package, an alternative is to install from a Zip file without an installer. That file is called mysql-workbench-version-win32.zip. To install using the Zip file, download the Zip file to a convenient location and decompress the file using a Zip utility. You can place the resulting directory anywhere on you system. You need not install or configure the application before using it. You may want to create a shortcut on your desktop or the quick launch bar.
3.3.2. Launching MySQL Workbench on Windows

To start MySQL Workbench on Windows, select Start, Programs, MySQL, then select MySQL Workbench. Alternatively, start MySQL Workbench from the command line. To view the available command-line options, issue the command MySQLWorkbench -help | more from the MySQL Workbench installation directory. You will see the following output:
MySQL Workbench 5.2.34 SE. (C) 2006-2011 by Oracle Corporation. All rights reserved. Usage: MySQLWorkbench [options] [model file] Options -admin instance .... Open an admin tab to the named server instance at startup -open filename ..... Open the given filename at startup
Uninstalling MySQL Workbench on Windows
-query server ...... -run script ........ -run-python script . -run-lua script .... -script scriptfile . -quit-when-done .... -swrendering ....... -nologo ............ -log ............... -verbose (-v) ...... -version ........... -grtversion ........ -help (-h) .........
Open a DB query tab to the named server connection at startup Executes the given Workbench script at startup Executes the given Workbench Python script at startup Executes the given Workbench Lua script at startup Executes the given Workbench script file at startup Quits Workbench once the given script finishes executing Force the canvas to use software rendering instead of OpenGL Do not display the splash screen Instruction to save messages (other debug info) to file Print verbose output in the GRT Shell Print the version information Print the GRT version information Print this output
The MySQL Workbench help output includes a version number, a usage message, and the option descriptions. Use the -swrendering option if your video card does not support OpenGL 1.5. The version option can be used to display the MySQL Workbench version number. The -grtversion can be used to display the GRT (Generic RunTime) shell version number. The other options are selfexplanatory. Note When using the -help and -version, command-line options that display output to a console window, be sure that you pipe the output through the more command. Otherwise, nothing will be displayed.
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 1. 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. 2. 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.
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> sudo dpkg -i package.deb
package.deb is the MySQL Workbench package name; for example, mysql-workbenchoss-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> sudo rpm -i package.rpm
package.rpm is the MySQL Workbench package name; for example, mysql-workbenchoss-version-1fc10.x86_64.rpm, where version is the MySQL Workbench version number.
3.3.5. Launching MySQL Workbench on Linux

After MySQL Workbench has been installed, it can be launched by selecting Applications, Programming, MySQL Workbench from the main menu. MySQL Workbench can also be launched from the command line on Linux. Type the command:
shell> /usr/bin/mysql-workbench --help
This will display the available command-line options:

mysql-workbench [<options>] [<model file>] Options: --force-sw-render Force Xlib rendering --force-opengl-render Force OpenGL rendering --help, -h Show command line options and exit
3.3.6. Uninstalling MySQL Workbench on Linux

The procedure for uninstalling MySQL Workbench on Linux depends on the package you are using. Uninstalling DEB packages
Installing MySQL Workbench on Mac OS X
To uninstall a Debian package, use this command:

shell> sudo dpkg -r mysql-workbench-oss
This command does not remove the configuration files. If you wish to also remove the configuration files, use this command:
shell> sudo dpkg --purge mysql-workbench-oss
Uninstalling RPM packages To uninstall an RPM package, use this command:

shell> sudo rpm -e mysql-workbench-oss
This command does not remove the configuration files.
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-workbenchoss-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.
3.3.8. Launching MySQL Workbench on Mac OS X

To launch MySQL Workbench on Mac OS X, open the Applications folder in the Finder, then double-click MySQL Workbench.
10
Uninstalling MySQL Workbench on Mac OS X
It is also possible to start MySQL Workbench from the command line:

shell> open MySQLWorkbench.app model_file
A model file must be specified.
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, rightclick, and select Move to Trash.
11
12
Chapter 4. Getting Started Tutorial

Table of Contents
4.1. Administering a MySQL Server .................................................................................................. 13 4.2. Creating a Model ....................................................................................................................... 25 4.3. Adding Data to Your Database ................................................................................................... 31 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.
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. 1. Launch MySQL Workbench. You will be presented with the Home window.
13
Administering a MySQL Server
Figure 4.1. Getting Started Tutorial - Home Window
2. 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. 3. In this tutorial, you will connect to a locally installed server, so click Next.
14
Figure 4.2. Getting Started Tutorial - Specify Host Machine
4. 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.
15
Figure 4.3. Getting Started Tutorial - Database Connection
You can now click Next. 5. 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.
16
Figure 4.4. Getting Started Tutorial - Connection Test
If the connection test was successful, click Next. 6. 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.
17
Figure 4.5. Getting Started Tutorial - Management and OS
Set the configuration method, then click Next. 7. 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.
18
Figure 4.6. Getting Started Tutorial - SSH Configuration
Check that everything is in order, then click Next. 8. If a Windows server is used, then the Windows configuration parameters must be set.
19
Figure 4.7. Getting Started Tutorial - Windows Management
Check that everything is in order, then click Next. 9. The wizard will now check that it is able to access the MySQL Server configuration file, and access the start and stop commands.
20
Figure 4.8. Getting Started Tutorial - Test Host Settings
Check that everything is in order, then click Next. 10. 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.
21
Figure 4.9. Getting Started Tutorial - Review Settings
Review the information, then click Next. 11. 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.
22
Figure 4.10. Getting Started Tutorial - Instance Name
Set the desired name, then click Finish to complete the server instance creation process. 12. 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.
23
Figure 4.11. Getting Started Tutorial - Home Window Instance
You are now ready to test your new server instance. 13. From the Home window, double-click the Server Instance you created. The Administrator will open on the Startup configuration page.
24
Creating a Model
Figure 4.12. Getting Started Tutorial - Admin Startup
14. Click the Stop Server button. The message window will show that the server has stopped. 15. 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 9, Server Administration.
4.2. Creating a Model

In this section, you will learn how to create a new database model, create a table, create an EER Diagram of your model, and then forward engineer your model to the live database server. 1. Start MySQL Workbench. On the Home window, select Create new EER Model. A model can contain multiple schemata. Note that when you create a new model, it contains the mydb schema by default. You can change the name of this schema to serve your own purposes, or delete it.
25
Creating a Model
Figure 4.13. Getting Started Tutorial - Home Window
2. On the Physical Schemata toolbar, click the button + to add a new schema. This will create a new schema and display a tabsheet for the schema. In the tabsheet, change the name of the schema to dvd_collection, by typing into the field called Name. Ensure that this change is reflected on the Physical Schemata tab. Now you are ready to add a table to your schema.
26
Creating a Model
Figure 4.14. Getting Started Tutorial - New Schema
3. In the Physical Schemata section, double-click Add Table. 4. This will automatically load the table editor, with the default table name being table1. In the table editor, change the name of the table from table1 to movies. 5. Next, add several columns. Double click a cell within the Column Name column, and the first field will default to moviesid because MySQL Workbench appends id to the table name as the default for the initial field. Change the name to movie_id and keep the Datatype as INT. Then, be sure PK (PRIMARY KEY), NN (NOT NULL), and AI (AUTO_INCREMENT) are all checked. 6. Add two additional columns using the same method as described above:
Column Name movie_title release_date
Data Type VARCHAR(45) DATE (YYYY-MM-DD)
Column Properties NN None
27
Creating a Model
Figure 4.15. Getting Started Tutorial - Columns
7. Now you can obtain a visual representation of this schema so far. From the main menu, select Model, Create Diagram from Catalog Objects. The EER Diagram will be created and displayed.
28
Creating a Model
Figure 4.16. Getting Started Tutorial - EER Diagram
8. In the table editor, change the name of the column movie_title to title. Note that the EER Diagram is automatically updated to reflect this change. 9. At this point, you can save your model. Click the main toolbar button Save Model to Current File. You have not yet saved this file so you will be prompted to enter a model file name. For this tutorial, enter Home_Media. The Home_Media model may contain further schemata in addition to dvd_collection, such as cd_collection. Click Save to save the model. 10. You can synchronize your model with the live database server. First, you must tell MySQL Workbench how to connect to the live server. From the main menu, select Database, Manage Connections.... 11. In the Manage DB Connections dialog, click New. 12. Enter Big Iron Server for the connection name. This enables you to identify the server to which this connection corresponds, although it is possible to create multiple connections to the same server. 13. Enter the user name for the account you will use to connect to the server. 14. Click on the Store in Vault... button and enter the password for the user name you entered in the previous step. You can optionally ignore this step, and you will be prompted for this password whenever MySQL Workbench connects to the server. 15. Click Test Connection to test your connection parameters. If everything is okay at this point, you can click Close.
29
Creating a Model
Figure 4.17. Getting Started Tutorial - Manage Connections
16. You are now ready to forward engineer your model to the live server. From the main menu, select Database, Forward Engineer.... The Forward Engineer to Database wizard will be displayed. 17. The Options page of the wizard shows various advanced options. For this tutorial, you can ignore these and simply click Next. 18. On the next page, you can select the object you want to export to the live server. In this case, you only have a table, so no other objects need be selected. Click Next. 19. The next page, Review SQL Script, displays the script that will be run on the live server to create your schema. Review the script to make sure that you understand the operations that will be carried out. Click Next.
30
Adding Data to Your Database
Figure 4.18. Getting Started Tutorial - Review Script
20. Select the connection you created earlier, Big Iron Server. Click Execute. Check the messages for any errors, then click Close to exit the wizard. 21. Ensure that the script ran without error on the server, then click Close. As a simple test that the script worked launch the MySQL Command Line Client (mysql). Enter SHOW DATABASES; and identify your schema. Enter USE dvd_collection; to select your schema. Now enter SHOW TABLES;. Enter SELECT * FROM movies;, this will return the empty set as you have not yet entered any data into your database. Note that it is possible to use MySQL Workbench to carry out such checks, and you will see how to do this later, but the MySQL Command Line Client has been used here as you have probably used it previously. 22. Ensure that your model is saved. Click Save Model to Current File on the main toolbar.
4.3. Adding Data to Your Database

In the previous section, you created a model, schema, and table. You also forward engineered your model to the live server. In this section, you will see how you can use MySQL Workbench to add data into your database on the live server. 1. On the Home window, click the link Edit Table Data in the SQL Development area of the Workspace. This launches Edit Table Data wizard.
31
Figure 4.19. Getting Started Tutorial - Edit Table Data
2. In the wizard, select the Big Iron Server connection from the stored connection list. Click Next. 3. Select the schema, dvd_collection. Select the table to edit, movies. Click Finish. 4. You will see a data grid. This is where you can enter the data for your database. Remember that the movie_id was set to be autoincrement, so you need not enter values directly for this column. In the data grid, enter the movie information shown in the following table.
title Gone with the Wind The Hound of the Baskervilles The Matrix Above the Law Note
release_date 1939-04-17 1939-03-31 1999-06-11 1988-04-08
Do not modify any values in the movie_id column. 5. Now click the Apply button in the toolbar located in the bottom right corner. A list of SQL statements will be displayed. Confirm that you understand the operations to be carried out. Click Apply to apply these changes to the live server. 6. Confirm that the script was executed correctly, then click Finish.
32
7. View the data grid again and observe that the autoincrement values have been generated. Figure 4.20. Getting Started Tutorial - Edit Data
8. Now you will check that the data really has been applied to the live server. Launch the MySQL Command Line Client. Enter SELECT * FROM movies; to see the data just entered. 9. You can also carry out a similar check from within MySQL Workbench. Click on the Home window tab. 10. Click the link Open Connection to start Querying in the SQL Development section of the Workspace. This will launch the Connect to Database dialog. Select Big Iron Server from the list. Click OK. 11. A new SQL Editor tab will be displayed. In the SQL Statements area, enter the following code:
USE dvd_collection; SELECT * FROM movies;
12. Now click the Execute toolbar button. This resembles a small lightning bolt. The SQL Editor will display a new Result tab contain the result of executing the SQL statements.
33
Figure 4.21. Getting Started Tutorial - Results
In this section of the tutorial, you have learned how to add data to your database, and also how to execute SQL statements using MySQL Workbench.
34
Chapter 5. The Home Window

Table of Contents
5.1. 5.2. 5.3. 5.4. Workbench Central .................................................................................................................... Workspace ................................................................................................................................ Workbench Application Minimum Window Size ............................................................................ 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 ...................................................................................................... 36 37 37 37 39 39 39 41 42 42 43
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.
35
Workbench Central
Figure 5.1. The Home Window
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
36
Workspace
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
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 9, Server Administration.
5.3. Workbench Application Minimum Window Size

As of version 5.2.10, the MySQL Workbench application features a fixed minimum window size of 1024x768. You cannot reduce the size of the application to less than this resolution.
5.4. Workbench Preferences

The Preferences menu sets MySQL Workbench defaults. Choosing this menu item opens the following dialog box.
37
Workbench Preferences
Figure 5.2. The Preferences Dialog Box
The preferences dialog box contains the following tabs: General: Configuration of general-purpose options Administrator: Configuration of tools used by the Administrator functionality SQL Editor: Configuration of the SQL Editor Model: Default object names MySQL: Configuration of the default storage engine Diagram: EER diagram settings Appearance: Change colors and fonts used by various Workbench components A more detailed discussion of these options follows.
38
The General Tab
5.4.1. The General Tab

The General tab enables you to set the following options: Automatically Reopen Previous Model When Started: Check this if you want the model on which you previously worked to be automatically reopened when you start MySQL Workbench. Place Sidebar on the Right Side: By default, the Sidebar is placed on the left-hand side of the MySQL Workbench application. Select this option to place it on the right-hand side. Force use of software rendering for EER diagrams: MySQL Workbench will use OpenGL for rendering when available. However, due to faulty drivers, problems do occasionally occur. These issues can be resolved by selecting the software rendering option here. Undo History Size: You can limit the size of the undo history here. Set this value to 0 to have an unlimited undo history. Auto-save model interval: An open model that has not been saved will automatically be saved after this period. On loading a model file, MySQL Workbench will notify the user if the file was not previously saved correctly, due to a crash or power failure. MySQL Workbench can then attempt to recover the last auto-saved version. For automatic recovery to be available for a new file, it will have to have been saved at least once by the user. Interactive GRT Shell Language: You can select the language to be used in the GRT (Generic RunTime) shell by choosing a language from the list Interactive GRT Shell Language. Currently, the choices are Lua and Python. Python is the recommended option. Create new tabs as Query tabs instead of File: By default, opening a new SQL Editor tab opens as an SQL File tab. Check this option if you prefer the simpler Query tabs that, for example, will not prompt to be saved when closed. Added as of MySQL Workbench 5.2.45.
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.
5.4.3. The SQL Editor Tab

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

This section provides configuration options that affect the Modeling functionality in MySQL Workbench. Use the When Deleting Physical Model Figures in Diagram section to determine the behavior when deleting objects from the EER diagram canvas. Choose Ask and whenever you delete an object, you will be asked whether you wish to remove the object from an EER diagram only or also from the catalog. The Keep Database Object in Catalog is the safest option. You also have the option of deleting the object from both the EER diagram and the catalog. Note If you choose the Ask option, a confirmation dialog box opens only when you are deleting an object from an EER Diagram. When deleting in the MySQL Model view, there is no confirmation dialog window and the delete action always removes the object from the catalog. There are a variety of ways to delete an object from an EER canvas: using the eraser tool; choosing a pop-up menu item; using the delete key; and by choosing the delete option from the Edit menu. In each case, the action performed by the delete key is determined by the option chosen from the When Deleting Physical Model Figures in Diagram section. Use the Model tab to set the default value for various object names and the primary key data type. The following table shows the object names and their default values. Object Name PK Column Name PK Column Type Default Value id%table% INT
41
The MySQL Tab
Object Name Column Name Column Type FK Name Foreign Key Column Name ON UPDATE ON DELETE Associative Table Name
Default Value %table%col VARCHAR(45) fk%stable_%dtable% %table%_%column% NO ACTION NO ACTION %stable%_has_%dtable%
The PK Column Name, PK Column Type, Column Name, and Column Type values are the defaults used by the table editor, and only function on Microsoft Windows and Mac OS X. The others are the default names used when using the relationship tools on an EER diagram. Within object values items enclosed by percentage signs are variables. Their meanings are as follows: %table%: The table associated with the object %stable%: The source table associated with the object %dtable%: The destination table associated with the object %column%: The column associated with the object Legitimate values for the foreign key update or delete rules are: RESTRICT CASCADE SET NULL NO ACTION (default) For more information about these actions, see Section 7.7.1.3.4, The Foreign Keys Tab.
5.4.5. The MySQL Tab

This enables you to set the default table storage engine.
5.4.6. The Diagram Tab

Use this tab to determine display settings for an EER diagram. Select whether to expand new objects by checking the Expand New Objects check box and select whether to draw line crossings by checking the Draw Line Crossings check box. This tab also enables you to set the maximum number of characters for the following items: Column Names Column Types Routine Names Changes to these values change the display properties only, not the objects themselves.
42
The Appearance Tab
5.4.7. The Appearance Tab

Use this tab to set the available colors for the objects that appear on an EER diagram canvas. You can also add colors if you wish. Changes made here affect the list of colors that appears on the toolbar when adding objects to an EER diagram canvas. For information about using this list, see Section 7.5.2.1, Tool-Specific Toolbar Items. You can also use this tab to set the font face, size, and style for the following items: Editor Layer Title Text Figure Text Text Figure Title Connection Caption Routine Group Figure Item Routine Group Figure Title Table Figure Items Table Figure Section Table Figure Title View Figure Title Note On Windows, the default font for the editor supports only latin-1 characters. If you need to use characters not supported by the latin-1 character set, you must change the font here.
43
44
Chapter 6. SQL Development

Table of Contents
6.1. 6.2. 6.3. 6.4. 6.5. 6.6. Open Connection to Start Querying ............................................................................................ New Connection ........................................................................................................................ Edit Table Data ......................................................................................................................... Edit SQL Script .......................................................................................................................... Manage Connections ................................................................................................................. Manage DB Connections Dialog ................................................................................................. 6.6.1. The Password Storage Vault ........................................................................................... 6.6.2. Standard TCP/IP Connection ........................................................................................... 6.6.3. Local Socket/Pipe Connection ......................................................................................... 6.6.4. Standard TCP/IP over SSH Connection ........................................................................... 6.7. SQL Editor ................................................................................................................................ 6.7.1. Main Menu ..................................................................................................................... 6.7.2. Toolbar ........................................................................................................................... 6.7.3. SQL Query Panel ............................................................................................................ 6.7.4. Main Tabsheets .............................................................................................................. 6.7.5. Sidebar ........................................................................................................................... 45 46 46 46 46 46 47 48 49 50 50 51 53 53 54 57
MySQL Workbench provides extensive facilities for working directly with SQL code. Before working directly with a live server, a connection must be created. After a connection is established, it is possible to execute SQL code directly on the server and manipulate the server using SQL code. The starting point for embarking on SQL Development work is the SQL Development area of the Home window, which has the following action items: Open Connection to start Querying New Connection Edit Table Data Edit SQL Script Manage Connections The following sections describe each of these action items. Note The SQL Development facility in MySQL Workbench provides the functionality that was formerly available in MySQL Query Browser.
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. Doubleclicking the icon directly launches an SQL Editor tab, and connects you to the database as defined by the connection.
45
New Connection
To read more about the SQL Editor, see Section 6.7, SQL Editor.
6.2. New Connection

Clicking the New Connection action item launches the Manage DB Connections wizard. This wizard enables you to create a new connection. Note that the wizard when launched from here does not display existing connections, it only enables you to create a new connection. To read more about creating and managing connections, see Section 6.6, Manage DB Connections Dialog.
6.3. Edit Table Data

Clicking this action item launches the Edit Table Data wizard, which enables you to edit table data. This is a two-stage wizard. The first stage enables you to select a Stored Connection. The second stage enables you to select the Schema and Table you want to edit. After the wizard is completed, an SQL Editor tab is launched, which displays a data grid that enables you to interactively edit table data as required. To read more about the SQL Editor, see Section 6.7, SQL Editor.
6.4. Edit SQL Script

Clicking this action item launches the Edit SQL Script wizard. This is a two-stage wizard. The first stage enables you to select a Stored Connection. The second stage enables you to select an SQL Script file, and optionally have the script executed after it is opened. After the wizard is completed, an SQL Editor tab will be launched, with the script displayed. If you selected to run the script, MySQL Workbench runs the script and displays the results. Working with large data sets The Edit SQL Script wizard is not well-suited for executing large dump files, and instead the Server Administration, Manage Import/Export feature should be used.
6.5. Manage Connections

Clicking this action item launches the Manage DB Connections wizard. This wizard also displays Stored Connections, which can be selected and changed as desired. This wizard can also be used to create new connections. To read more about managing connections, see Section 6.6, Manage DB Connections Dialog.
6.6. Manage DB Connections Dialog

MySQL Workbench provides a Manage DB Connections dialog for creating and managing connections to servers. The connections created can then be used from the wizards that must connect to a server, such as the wizard used to reverse engineer a live database. However, it is still possible to set connection parameters from these wizards if required, without invoking the Manage DB Connections dialog directly. The Manage DB Connections dialog is invoked by selecting Database, Manage Connections from the main menu. It can also be invoked from any of the wizards requiring access to a live database. This is achieved by using the Manage Stored Connections item, found in the wizard's Stored Connection list. After the Manage DB Connections dialog is launched, you are presented with the following dialog, which enables you to create or delete connections.
46
The Password Storage Vault
Figure 6.1. Manage DB Connections - Dialog
Click New to create a new connection. Once created, the connection can be selected from the Stored Connections list. You can then set various parameters for the connection, including the following: Connection Name: The name used to refer to this connection. This connection can then be selected from a list in other wizards requiring a connection. Connection Method: The methods available are Standard TCP/IP, Local Socket/Pipe, and Standard TCP/IP over SSH. After you select a connection method, the fields available in the Parameters tab and the Advanced tab of the dialog changes accordingly. More details about these options and parameters are available in the following sections. After all parameters have been set as required, you can click the Test Connection button to test the connection to the live server. After you are satisfied that the connection works as expected, you can close the wizard by clicking the Close button. The stored connection then is available for use from any of the wizards requiring a connection to a live server. You can duplicate an existing connection using the Duplicate button. This is an easy way to begin setting up a new connection that differs only slightly from an existing one.
6.6.1. The Password Storage Vault

The vault provides a convenient secure storage for passwords used to access MySQL servers. By using the vault, you need not enter credentials every time MySQL Workbench attempts to connect to a server. The vault is implemented differently on each platform: Windows: The vault is an encrypted file in the MySQL Workbench data directory. This is where connections.xml and related files are located. The file is encrypted using a Windows API which performs the encryption based on the current user, so only the current user can decrypt it. As a result it is not possible to decrypt the file on any other computer. It is possible to delete the file, in which case all
47
Standard TCP/IP Connection
stored passwords are lost, but MySQL Workbench will otherwise perform as expected. You then must re-enter passwords as required. Mac OS X: The vault is implemented using the Mac OS X Secure Keychain. The keychain contents can be viewed using the Keychain Access.app utility. Linux: The vault works by storing passwords using the gnome-keyring daemon, which must be running for password persistency to work. The daemon is automatically started in GNOME desktops, but normally is not in KDE and others. The gnome-keyring daemon can be used for password storage in MySQL Workbench on non-GNOME platforms, but must be started manually.
6.6.2. Standard TCP/IP Connection

This connection method enables MySQL Workbench to connect to MySQL Server using TCP/IP. Parameters tab Hostname: The host name or IP address of the MySQL server. Username: User name to use for the connection. Password: Optional password for the account used. If you enter no password here, you will be prompted to enter the password when MySQL Workbench attempts to establish the connection. MySQL Workbench can store the password in a vault (see Section 6.6.1, The Password Storage Vault). Port: The TCP/IP port on which the MySQL server is listening (the default is 3306). Default Schema: When the connection to the server is established, this is the schema that will be used by default. It becomes the default schema for use in other parts of MySQL Workbench. Advanced tab More parameters can be set for the connection by using the Advanced tab. Figure 6.2. Manage DB Connections - Advanced Tab
48
Local Socket/Pipe Connection
The Advanced tab includes these check boxes: Use compression protocol: If checked, the communication between the application and the MySQL server will be compressed, which may increase transfer rates. This corresponds to starting a MySQL command-line client with the --compress option. Use SSL if available: This option turns on SSL encryption. The client library must support this option. Note: This feature is currently not supported. Use ANSI quotes to quote identifiers: Treat " as an identifier quote character (like the ` quote character) and not as a string quote character. You can still use ` to quote identifiers with this mode enabled. With this option enabled, you cannot use double quotation marks to quote literal strings, because it is interpreted as an identifier. Note: If this option is selected, it overrides the server setting.
6.6.3. Local Socket/Pipe Connection

This connection method enables MySQL Workbench to connect to MySQL Server using a socket file (on Unix) or a named pipe (on Windows). Parameters The unique field here is Socket/Pipe Path. Enter the name of the socket or pipe here. If the field is left blank, the default socket or pipe name is used. On Unix, the default socket name is /tmp/mysql.sock. On Microsft Windows, the default pipe name is MySQL. This option can be seen in the following screenshot. Figure 6.3. Manage DB Connections - Socket/Pipe Parameters
Advanced The only option available in this tab is Use ANSI quotes to quote identifiers. This option was discussed in Section 6.6.2, Standard TCP/IP Connection.
49
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.
6.7. SQL Editor

MySQL Workbench 5.2 introduced the SQL Editor facility. The SQL Editor can be launched using various action items on the Home window. It can also be launched by selecting Database, Query Database from the main menu, or by using the keyboard shortcut Control+U on Windows, or Command+U on Mac
50
Main Menu
OS X. At this point, you will be asked to either select a stored connection or enter the details for a new connection. After a connection has been made to the server, a new tab called SQL Editor (schema) is displayed. Figure 6.5. SQL Editor
The SQL Editor user interface has these main elements: Main Menu Toolbar SQL Query Panel Main Tabsheets (Overview, Output, History, Snippets, Results) Sidebar Auto-completion (in the Main Menu) The following sections describe each of these elements.
6.7.1. Main Menu

When an SQL Editor tab is selected, the most important items on the main menu bar are the Query and Edit menus.
51
Main Menu
Query Menu The Query menu features the following items: Execute (All or Selection): Executes all statements in the SQL Query area, or only the selected statements. Execute Current Statement: Executes the current SQL statement. Explain (All or Selection): Describes all statements, or the selected statement. Explain Current Statement: Describes the current statement. Stop: Stops executing the currently running script. Reconnect to Server: Reconnects to the MySQL server. New Tab: Creates a duplicate of the current SQL Editor tab. Commit Transaction: Commits a database transaction. Rollback Transaction: Rolls back a database transaction. Refresh: Synchronizes with the live server and refreshes views such as the live Overview tabsheet. Commit Result Edits: Commits any changes you have made to the server. Discard Result Edits: Discards any changes you have made. Export Results: Exports result sets to a file. Selecting this option displays the Export Query Results to File dialog. The dialog enables you to select which result set you wish to export, the file format (CSV, HTML, XML), and the name and location of the output file. Then click Export to export the data. Edit Menu The Edit menu features the Format submenu. The Format submenu includes the following menu items that are of importance when in SQL Editor mode: Beautify Query: Reformats the query selected in the query tab and lays it out in nicely indented fashion. UPCASE Keywords: Converts keywords to uppercase in the currently selected query in the query tab. lowercase Keywords: Converts keywords to lowercase in the currently selected query in the query tab. Indent Lines: Indents the lines selected in the query tab. Unindent Lines: Unindents the lines selected in the query tab. Un/Comment Selection: Comments the lines currently selected in the query tab. If the lines are already commented, this operation removes the comments. Auto-complete: Triggers the auto-completion wizard. This is enabled (and triggered) by default, and can be disabled with Preferences, SQL Editor, Automatically Start Code Completion. Auto-completion will list functions, keywords, schema names, table names and column names. Note This feature was added in MySQL Workbench 5.2.41.
52
Toolbar
6.7.2. Toolbar
The toolbar features buttons in two locations, in the main toolbar and within the SQL Editor itself. The SQL Editor buttons are described below. Figure 6.6. SQL Editor - Toolbar
From left to right, these buttons are: Open a SQL Script File: Loads a saved SQL script to be ready for execution. The script is displayed in the SQL Query area. Save SQL Script to File: Saves the currently loaded SQL script to a file specified by the user. Execute SQL Script: Executes the selected portion of the query, or the entire query if nothing is selected. Execute Current SQL script: Execute the statement under the keyboard cursor. Explain (All or Selection): Execute the EXPLAIN command on the query under the keyboard cursor. Stop the query being executed: Halts execution of the currently executing SQL script. Note: the database connection will not be restarted, and open transactions will remain open. Toggle whether execution of SQL script should continue after failed statements: If the red breakpoint circle is displayed, the script terminates on a statement that fails. If the button is depressed so that the green arrow is displayed, execution continues past the failed code, possibly generating additional result sets. In either case, any error generated from attempting to execute the faulty statement is recorded in the Output tabsheet. Commit: Commits the current transaction. Note: All query tabs in the same connection share the same transactions. To have independent transactions, a new connection must be opened. Rollback: Rolls back the current transaction. Note: All query tabs in the same connection share the same transactions. To have independent transactions, a new connection must be opened. Toggle Auto-Commit Mode: If selected, each statement will be committed independently. Note: All query tabs in the same connection share the same transactions. To have independent transactions, a new connection must be opened. Beautify SQL: Beautify/reformat the SQL script. Find panel: Show the Find panel for the editor. Invisible characters: Toggle display of invisible characters, such as newlines, tabs, spaces.
6.7.3. SQL Query Panel

In this area, you can enter SQL statements directly. The statements entered can be saved to a file or snippet for later use. At any point, you can also execute the statements you have entered. To save a snippet of code entered into the SQL Query panel, click the Save SQL to Snippets List icon in the Snippets panel, enter a name (optional), and click OK. The snippet can be inserted into the SQL Query panel at any time by double-clicking the snippet in the SQL Snippets panel.
53
Main Tabsheets
Figure 6.7. SQL Editor - SQL Query Panel
Executing a SELECT query will display the associated result set in the SQL View panel, directly below the SQL Query panel. These cells are editable if MySQL Workbench is able to determine how, as for example they are editable if a Primary or Unique key exists within the result set. If not, MySQL Workbench will display a "read-only" icon at the bottom-right corner of the SQL View panel, and hovering the mouse cursor over this icon will provide a hint as to why it's not editable. Note To quickly enter the name of a table, view, or column, double-click the item in the Schemata Palette. The item name will be inserted into the SQL Query panel.
6.7.4. Main Tabsheets

The main tabsheets area contains several tabs: Output and History Tabsheet Results Tabsheets Live Editing Tabsheet Figure 6.8. SQL Editor - Main Tabsheets
54
Main Tabsheets
The following sections describe each of these in more detail.
6.7.4.1. Output and History Tabsheet

The Output and History tabsheet is located at the bottom of MySQL Workbench, and can be toggled on or off. It contains a select box that includes Action Output, Text Output, and History options. The Action Output tabsheet displays a summary of the communication between the script and the server. The messages displayed can be information or errors. Each message displays the time, the action that was carried out, and the response from the server. This output is useful for troubleshooting scripts. The Text Output tabsheet will display a textual representation of the query, as displayed using the MySQL Console. Use Query, Execute (All or Selection) to Text to send output to this 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.
6.7.4.2. 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.9. 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.10. SQL Editor - Results Tabsheets Navigation Controls
From left to right, the controls are:
55
Main Tabsheets
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.
6.7.4.3. Live Editing Tabsheets

It is possible to edit data in real time using the Live Editing tabsheets. The live editor is the default view type, so it will be displayed after running a SELECT query or by right-clicking a table in the Schema Viewer and choosing Edit Data Table. The top part of the result set may be resized to reveal the SELECT query that it originated from. This query can be altered to show only columns you want, which might mean adding a WHERE clause. 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.11. SQL Editor - Live Editing Tabsheet Navigation Controls
56
Sidebar
These additional controls enable you to make changes other than simple edits, like inserting/removing rows and exporting the data. From left to right, the additional controls are: Edit current row: Enters edit mode for the currently selected row. Double-clicking a cell has the same effect. 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. Export recordset to an external file: Exports the result set as a file to a defined location. The same as choosing Query, Export Results... from the main menu. Data may be exported as several formats, including CSV, CSV (; separated), HTML, JSON, SQL, and XML. Import records from an external file: Imports data from a CSV file. Data is separated by a comma, and not the alternative CSV (; separated) MySQL Workbench export option. This feature was added in MySQL Workbench 5.2.45. See also Section 7.7.1.3.8, The Inserts Tab.
6.7.5. Sidebar
The Sidebar contains these panels: Session (connection) Information Snippets Schemas The following sections describe each panel in more detail.
6.7.5.1. Snippets panel

The Snippets sidebar offers both built-in and custom snippets. The sidebar contains a select box, with My Snippets for custom snippets, and built-in options titled DB Mgmt (Database Management), SQL DDL (SQL Data Definition Language), and SQL DML (SQL Data Manipulation Language). Snippets may be given names, and these snippets can be viewed and edited from the Snippets sidebar. To load a snippet into the SQL Query area, either choose the Snippets Insert icon or right-click on the desired snippet and choose Insert. Double-click a snippet to open an edit context, to edit the snippet body or title. This example shows two snippets, with only the first having defined a name. 57
Sidebar
Figure 6.12. SQL Editor - Snippets Palette
6.7.5.2. Session and Object Information Panel

This panel summarizes the current connection to the server.
58
Sidebar
Figure 6.13. SQL Editor - Connection Information Palette
This panel also summarizes information about the object. Figure 6.14. SQL Editor - Object Info
6.7.5.3. Object Browser

The Object Browser contains an Actions list and a Schemata list, as seen in the following screenshot.
59
Sidebar
Figure 6.15. 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.
60
Sidebar
Figure 6.16. 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:
61
Sidebar
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 <where_condition>;. 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.
62
Chapter 7. Data Modeling

Table of Contents
7.1. 7.2. 7.3. 7.4. 7.5. Open an Existing EER Model ..................................................................................................... 64 Create New EER Model ............................................................................................................. 64 Create EER Model from Existing Database ................................................................................. 64 Create EER Model from SQL Script ........................................................................................... 64 Model Editor .............................................................................................................................. 65 7.5.1. Modeling Menus .............................................................................................................. 66 7.5.2. The Toolbar .................................................................................................................... 76 7.5.3. EER Diagrams ................................................................................................................ 77 7.5.4. The Physical Schemata Panel ......................................................................................... 77 7.5.5. The Schema Privileges Panel .......................................................................................... 78 7.5.6. The SQL Scripts Panel ................................................................................................... 79 7.5.7. The Model Notes Panel ................................................................................................... 79 7.5.8. The History Palette ......................................................................................................... 79 7.5.9. The Model Navigator Panel ............................................................................................. 80 7.5.10. The Catalog Tree Palette .............................................................................................. 80 7.5.11. The Layers Palette ........................................................................................................ 81 7.5.12. The Properties Palette ................................................................................................... 81 7.6. EER Diagram Editor .................................................................................................................. 82 7.6.1. The Vertical Toolbar ........................................................................................................ 82 7.7. Working with Models .................................................................................................................. 86 7.7.1. Creating Tables .............................................................................................................. 86 7.7.2. Creating Foreign Key Relationships ................................................................................. 98 7.7.3. Creating Views .............................................................................................................. 101 7.7.4. Creating Routines and Routine Groups .......................................................................... 103 7.7.5. Creating Layers ............................................................................................................. 107 7.7.6. Creating Notes .............................................................................................................. 108 7.7.7. Creating Text Objects .................................................................................................... 109 7.7.8. Creating Images ............................................................................................................ 110 7.7.9. Reverse Engineering ..................................................................................................... 111 7.7.10. Forward Engineering ................................................................................................... 120 7.8. Modeling Tutorials .................................................................................................................... 140 7.8.1. Importing a Data Definition SQL Script ........................................................................... 141 7.8.2. Using the Default Schema ............................................................................................. 142 7.8.3. Basic Modeling .............................................................................................................. 143 7.8.4. Documenting the sakila Database .............................................................................. 144 7.9. Printing .................................................................................................................................... 146 7.9.1. Printing Options ............................................................................................................ 146 7.10. MySQL Workbench Schema Validation Plugins (Commercial Version) ...................................... 146 7.10.1. General Validation ....................................................................................................... 146 7.10.2. MySQL-Specific Validation ........................................................................................... 147 7.11. The DBDoc Model Reporting Dialog Window (Commercial Version) .......................................... 148 7.12. Customizing DBDoc Model Reporting Templates ..................................................................... 151 7.12.1. Supported Template Markers ....................................................................................... 155 7.12.2. Creating a Custom Template ....................................................................................... 158 MySQL Workbench provides extensive capabilities for creating and manipulating database models, including these:
63
Open an Existing EER Model
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.
7.1. Open an Existing EER Model

Clicking this action item launches a file browser. You can then select the model file you wish to load. A new MySQL Model tab will then be created, and your model displayed. If you have already created one or more model files, each will appear in this panel as an icon. Doubleclicking the item of the model you wish to load creates a new MySQL Model tab and displays your model. If you already have created a connection to a database, it will appear in this panel as an icon. Doubleclicking the icon directly launches an SQL Editor tab, and connects you to the database as defined by the connection. To read more about modeling, see Section 7.5, Model Editor.
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.
7.3. Create EER Model from Existing Database

This action item enables you to create an EER Model from an existing live database. Clicking this action item launches the Reverse Engineer Database. This is a multi-stage wizard that enables you to select a connection to a live server, and select the schema and objects you wish to reverse engineer into your new model. This is a convenient way to see how an existing database is structured. For further information about reverse engineering, see Section 7.7.9.2, Reverse Engineering a Live Database.
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
64
Model Editor
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.
7.5. Model Editor

When the Model Editor is executed from the Home window, MySQL Workbench displays the MySQL Model page. The MySQL Model page has three main panels, as shown in the following screenshot: Description Editor, User Types List/History panel, and Model Overview. Figure 7.1. The MySQL Model Page
65
Modeling Menus
The Description Editor and User Types List/History panel are contained within the Sidebar. The Sidebar is located on the left by default, but can be relocated to the right using a setting in the Workbench Preferences dialog. The Model Overview panel has several sections: EER Diagrams Physical Schemata Schema Privileges SQL Scripts Model Notes For each of these sections, add objects to a project by clicking the appropriate add-object icon. You may also rename, edit, cut, copy, or delete objects on this page by right-clicking to open a pop-up menu. The following sections further discuss the MySQL Model page.
7.5.1. Modeling Menus

Some menu items are not available in the OSS version of this application, and are available only in the Standard Edition. This is indicated where applicable.
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.
66
Modeling Menus
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.50, 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
7.5.1.2. The Edit Menu

Use the Edit menu to make changes to objects. The text description for several of the menu items changes to reflect the name of the currently selected object. This menu has items for cutting, copying, and pasting. These actions can also be performed using the Control+X, Control+C, and Control+V key combinations. Undo a deletion using the Undo Delete 'object_name' item. The Control+Z key combination can also be used to undo an operation. It is also possible to carry out a Redo operation using either the menu item, or the key combination Control+Y. Also find a Delete 'object_name' menu item for removing the currently selected object. The keyboard command for this action is Control+Delete. You can also right-click an object and choose the delete option from the pop-up menu. The Delete 'object_name' menu item behaves differently depending upon circumstances. For example, if an EER Diagram is active and a table on the canvas is the currently selected object, a dialog box may open asking whether you want to remove the table from the canvas only or from the database as well. For
67
Modeling Menus
information about setting the default behavior when deleting from an EER Diagram, see Section 5.4.4, The Model Tab. Warning If the MySQL Model page is active, the selected object is deleted from the catalog and there will be no confirmation dialog box. Choose Edit Selected to edit the currently selected object. You can also perform edits in a new window by selecting Edit Selected in New Window. The keyboard shortcuts for Edit Selected and Edit Selected in New Window are Control+E and Control+Shift+E, respectively. The Select item has the following submenus: Select All (Keyboard shortcut, Control+A): Selects all the objects on the active EER diagram. Similar Figures (Objects of the same type): Finds objects similar to the currently selected object. Connected Figures: Finds all the objects connected to the currently selected object. These menu items are active only when an EER Diagram tab is selected. The Similar Figures and the Connected Figures menu items are disabled if no object is currently selected on an EER diagram. When multiple objects have been selected using one of these menu items, you can navigate between selected items by choosing the Go to Next Selected or Go to previous Selected menu item. Selecting objects changes some of the Edit menu items. If only one object is selected, that object's name appears after the Cut, Copy and Delete menu items. If more than one object is selected, these menu items show the number of objects selected.
7.5.1.2.1. Find Dialog Window

Each MySQL Workbench window includes search functionality. The Find panel with Find & Replace enabled is shown below:
68
Modeling Menus
Figure 7.2. The Find Panel with Find & Replace
Find options The Find dialogue options are described below: String Matching (default) or Regular Expression: Search by matching a string, or a PCRE regular expression. Ignore Case: A case-insensitive search. Works with both the String Matching and Regular Expression search methods. Enabled by default. Match Whole Words: If enabled, only whole strings are matched. For example, a search for "home" would not match "home_id". Disabled by default. Wrap Around: The search will wrap around to the beginning of the document, as otherwise it will only search from the cursor position to the end of the document. Enabled by default. And the arrows jump to the discovered search terms, and behave according to the Wrap Around option. The Standard Edition of MySQL Workbench includes a more advanced Find facility:
69
Modeling Menus
Figure 7.3. The Find Window
You can search the following locations: Entire Model: Searches the entire model. Current View: Searches the current view only. This may be the MySQL Model page. All Views: Searches the MySQL Model Page and all EER diagrams. Database Objects: Searches database objects only. Selected Figures: Searches the currently selected objects. This feature works only for EER diagrams. Enter the text you wish to search for in the Find Text list. You may also select any or all of the following check boxes: Match Case Whole Word Use Regular Expression Search in Comments Search in SQL for Views, SPs etc. Any text you enter into the Find Text list is retained for the duration of your session. Use the Next or Previous buttons to find occurrences of your search criterion. Clicking the Find All button opens a Find Results window anchored at the bottom of the application. If you wish, you may undock this window as you would any other. Use this window to navigate to objects. For example, double-clicking the Description of an object located on an EER diagram navigates to the specific diagram and selects the object. Notice that the properties of the object are displayed in the Properties palette. The Find dialog window can also be opened using the Control+F key combination. Use Control+G to find the next occurrence and Control+Shift+G to find a previous occurrence. Close the Find dialog window by clicking the x in the top right corner or by pressing the Esc key.
7.5.1.2.2. Workbench Preferences

This menu item enables you to set global preferences for the MySQL Workbench application.
70
Modeling Menus
For further information, see Section 5.4, Workbench Preferences.
7.5.1.3. The View Menu

The View menu has these items: Home: Selects the Home window Windows: A submenu with items that provide a means for opening the windows associated with them: Model Navigator: Opens the Model Navigator palette Catalog: Opens the Catalog palette Layers: Opens the Layers palette User Datatypes: Opens the User Datatypes palette Object Descriptions: Opens the Description palette Object Properties: Opens the Properties palette Undo History: Opens the History palette Output: Displays the console output. The keyboard shortcut for this menu item is Control+F2. Reset Window Layout: Resets all windows to their default layout Zoom 100%: The default level of detail of an EER diagram Zoom In: Zooms in on an EER diagram. Zoom Out: Zooms out from an EER diagram. The ability to zoom in on an EER diagram is also available using the slider tool in the Model Navigator palette. See Section 7.5.9, The Model Navigator Panel. Set Marker: Bookmarks an object. From the keyboard, select the object you wish to bookmark, then use the key combination Control+Shift and the number of the marker (1 through 9). You may create up to nine markers. Go To Marker: Returns to a marker. From the keyboard, use the Control key and the number of the marker. Toggle Grid: Displays grid lines on an EER diagram. Toggle Page Guides: Toggles Page Guides.
7.5.1.4. The Arrange Menu

The Arrange menu items apply only to objects on an EER diagram canvas and are enabled only if an EER diagram view is active. The Arrange menu has these items: Align to Grid: Aligns items on the canvas to the grid lines Bring to Front: Brings objects to the foreground Send to Back: Sends objects to the background
71
Modeling Menus
Center Diagram Contents: Centers objects on the canvas Autolayout: Automatically arranges objects on the canvas Reset Object Size: Expands an object on an EER diagram. For example, if a table has a long column name that is not fully displayed, this menu item expands the table to make the column visible. This menu item is not enabled unless an object is selected. Expand All: Use this item to expand all objects on an EER diagram. This item will display a table's columns if the object notation supports expansion. Some object notations, such as Classic, do not permit expansion or contraction. Indexes will not automatically be expanded unless they were previously expanded and have been collapsed using the Collapse All menu item. Collapse All: Undo the operation performed by Expand All.
7.5.1.5. The Model Menu

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.
72
Modeling Menus
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 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.
73
Modeling Menus
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.47, 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.
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 with Any Source: Allows you to compare a target database or script with the open model, external script, or a second database, and apply these changes back to the target. Synchronize Model: Synchronizes your database model with an existing database. For more information, see Section 7.7.10.3, Database Synchronization.
74
Modeling Menus
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.
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 11.3, Plugins.
7.5.1.8. The Scripting Menu

The Scripting menu has these items: Scripting Shell: Launches the MySQL Workbench Scripting Shell New Script: Opens a New Script File dialogue, with options to create a Python Script, Lua Script, Python Plugin, or Python Module. Open Script: Opens a Open GRT Script dialogue, which defaults to the Workbench scripts directory. Files are opened into the Workbench Scripting Shell window. Run Workbench Script File: Executes the specified script Install Plugin/Module File: Loads and installs a plugin or module file Plugin Manager: Displays information about the plugins that are are installed, and allows disabling and uninstalling the plugins.
7.5.1.9. The Community Menu

The Community menu has the following items. Use them to go online and learn more about MySQL Workbench. Workbench Blog FAQs About Workbench Learn How To Code For Workbench Discuss Workbench Topics Contribute To Workbench
7.5.1.10. The Help Menu

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. 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 a form to submit a bug to bugs.mysql.com, and optionally attaches the log file to the report. Additional information such as the MySQL Workbench version, configuration and data
75
The Toolbar
directory paths, operating system, and more, are appended to the report but is made private so only those with proper permissions (such as MySQL developers) can view this helpful debugging information. View Reported Bugs: Opens your default browser to see a list of current bugs. Locate log file: Opens up the directory that contains the MySQL Workbench log files. Check For Updates: Opens the MySQL Workbench website using your default browser, and checks for a newer version. 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
7.5.2. The Toolbar

The MySQL Workbench toolbar is located immediately below the menu bar. Click the tools in the toolbar to perform the following actions: The new document icon: Creates a new document The folder icon: Opens a MySQL Workbench file (mwb extension) The save icon: Saves the current MySQL Workbench project
76
EER Diagrams
The right and left arrows: The left arrow performs an Undo operation. The right arrow performs a Redo operation. Other tools appear on the toolbar depending upon the context.
7.5.2.1. Tool-Specific Toolbar Items

When an EER diagram canvas is selected, the following icons appear to the right of the arrow icons: The toggle grid icon: Turns the grid on and off The grid icon: Aligns objects on the canvas with the grid The new EER diagram icon: Creates a new EER diagram tab. The toolbar also changes depending upon which tool from the vertical toolbar is active. For discussion of these tools, see Section 7.6.1, The Vertical Toolbar. If the Table tool is active, schemata lists, engine types, and collations appear on the toolbar. The table properties can be modified using the Properties Editor. When an object is selected, the object's properties, such as color, can be changed in the Properties Editor.
7.5.3. EER Diagrams

Use the Add new 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.
7.5.4. The Physical Schemata 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.
77
The Schema Privileges Panel
7.5.4.1. The Schema Objects Panel

The Physical Schemata panel has the following sections: Tables Views Routines Routine Groups Each section contains the specified database objects and an icon used for creating additional objects. Any database objects added to an EER diagram canvas also show up in the Physical Schemata section. For information about adding objects to an EER diagram canvas, see Section 7.6, EER Diagram Editor.
7.5.5. The Schema Privileges Panel

The Schema Privileges panel has the following sections, used to create users for your schemata and to define roles : Users Roles The following image displays the Schema Privileges section of the MySQL Model tab. Figure 7.4. Roles and Privileges
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. Rightclicking 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
78
The SQL Scripts Panel
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.5. 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.
7.5.5.2. Adding Users

To add a user, double-click the Add User icon. This creates a user with the default name user1. Doubleclicking this user opens the user editor docked at the bottom of the application. In the User Editor, set the user's name and password using the Name and Password fields. Assign one role or a number of roles to the user by selecting the desired roles from the field on the right and then clicking the < button. Roles may be revoked by moving them in the opposite direction. Right-clicking a user opens a pop-up menu. The items in the menu function as described in Section 7.5.5.1, Adding Roles.
7.5.6. The SQL Scripts Panel

Use the SQL Scripts panel to load and modify SQL scripts. If you created your project from an SQL script and plan to create an ALTER script, you may want to add the original script here, since it will be needed to create an ALTER script. For more information, see Section 7.7.10.1.2, Altering a Schema.
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.
7.5.8. The History Palette

Use the History palette to review the actions that you have taken. Left-clicking an entry opens a popup menu with the item, Copy History Entries to Clipboard. Choose this item to select a single entry. You
79
The Model Navigator Panel
can select multiple contiguous entries by pressing the Shift key and clicking the entries you wish to copy. Select noncontiguous entries by using the Control key. Only actions that alter the MySQL model or change an EER diagram are captured by the History palette.
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.6. The Model Navigator 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:
80
The Layers Palette
1. Click the first item in the tree. 2. Hold the Shift key, click the last item, and do not release the Shift key. 3. Keep the Shift key depressed and commence the dragging operation. 4. 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.
7.5.11. 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.
7.5.11.1. Finding Invisible Objects Using the Layers Palette

In some circumstances, you may want to make an object on an EER diagram invisible. Select the object and, in the Properties palette, set the visible property to False. The Layer palette provides an easy way to locate an object, such as a relationship, that has been set to hidden. Open the Layers palette and select the object by double-clicking it. You can then edit the object and change its visibility setting to Fully Visible.
7.5.12. The Properties Palette

The Properties palette is used to display and edit the properties of objects on an EER diagram. It is especially useful for editing display objects such as layers and notes. All objects except connections have the following properties except as noted: color: The color accent of the object, displayed as a hexadecimal value. Change the color of the object by changing this value. Only characters that are legal for hexadecimal values may be entered. You can also change the color by clicking the ... button to open a color changer dialog box. description: Applicable to layers only. A means of documenting the purpose of a layer. expanded: This attribute applies to objects such as tables that can be expanded to show columns, indexes, and triggers. height: The height of the object. Depending upon the object, this property may be read only or read/ write. left: The number of pixels from the object to the left side of the canvas.
81
EER Diagram Editor
locked: Whether the object is locked. The value for this attribute is either true or false. manualSizing: Whether the object has been manually sized. The value for this attribute is either true or false. name: The name of the object. top: The number of pixels from the object to the top of the canvas. visible: Whether the object shows up on the canvas. Use 1 for true and 0 for false. It is currently used only for relationships. width: The width of the object. Depending upon the object, this property may be read only or read/write.
Tables have the following additional properties: indexesExpanded: Whether indexes are displayed when a table is placed on the canvas. Use 1 for true and 0 for false. triggersExpanded: Whether triggers are displayed when a table is placed on the canvas. Use 1 for true and 0 for false. For a discussion of connection properties, see Section 7.7.2.3, Connection Properties.
7.6. EER Diagram Editor

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.
7.6.1. The Vertical Toolbar

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.
82
The Vertical Toolbar
Figure 7.7. 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.
7.6.1.1. The Standard Mouse Pointer

The standard mouse pointer, located at the top of the vertical toolbar, is the default mouse pointer for your operating system. Use this tool to revert to the standard mouse pointer after using other tools. To revert to the default pointer from the keyboard, use the Esc key.
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.
83
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.
7.6.1.3. The Eraser Tool

Use the eraser tool to delete objects from the EER Diagram canvas. Change the mouse pointer to the eraser tool, then click the object you wish to delete. Depending upon your settings, the delete dialog box should open, asking you to confirm the type of deletion. Note The delete action of the eraser tool is controlled by the general option setting for deletion. Before using the eraser tool, be sure that you understand the available options described in Section 5.4.4, The Model Tab. To activate the eraser tool from the keyboard, use the D key. You can also delete an object by selecting it and pressing Control+Delete or by right-clicking it and choosing Delete from the pop up menu.
7.6.1.4. The Layer Tool

The layer tool is the rectangular icon with a capital L in the lower left corner. Use the layer tool to organize the objects on an EER Diagram canvas. It is useful for grouping similar objects. For example, you may use it to group all your views. Click the layer tool and use it to draw a rectangle on the canvas. Change to the standard mouse pointer tool and pick up any objects you would like to place on the newly created layer. To change the size of a layer, first select it by clicking it. When a layer is selected, small rectangles appear at each corner and in the middle of each side. Adjust the size by dragging any of these rectangles. You can also make changes to a layer by selecting the layer and changing properties in the Properties panel. Using the Properties panel is the only way to change the name of a layer. To activate the layer tool from the keyboard, use the L key. For more information about layers, see Section 7.7.5, Creating Layers.
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.
84
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.
7.6.1.7. The Table Tool

Use this tool to create a table on the EER Diagram canvas. Clicking the canvas creates a table. To edit the table with MySQL Table Editor, right-click it and choose Edit Table... or Edit in New Window... from the pop-up menu. You can also double-click the table to load it into the table editor. To activate the table tool from the keyboard, use the T key. For more information about creating and editing tables, see Section 7.7.1.3, The MySQL Table Editor.
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.
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.
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
85
Working with Models
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.
7.7. Working with Models

7.7.1. Creating Tables
7.7.1.1. Adding Tables to the Physical Schemata
Double-clicking the Add table icon in the Physical Schemata section of the MySQL Model page adds a table with the default name of table1. If a table with this name already exists, the new table is named table2. Adding a new table automatically opens the table editor docked at the bottom of the application. For information about using the table editor, see Section 7.7.1.3, The MySQL Table Editor. 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: Copies INSERT statements based on the model's inserts. Nothing is copied to the clipboard if the table has no inserts defined. Copy Insert Template to Clipboard: Copies a generic INSERT statement that is based on the model. Delete 'table_name' If the table editor is not open, the Edit Table... item opens it. If it is already open, the selected table replaces the previous one. Edit in New Window... opens a new table editor tab. The cut and copy items are useful for copying tables between different schemata. Warning Use the Delete 'table_name' item to remove a table from the database. There will be no confirmation dialog box. Any tables added to the Physical Schemata section also show up in the Catalog palette on the right side of the application. They may be added to an EER Diagram by dragging and dropping them from this palette.
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.
86
Creating Tables
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.8. 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.
7.7.1.3. The MySQL Table Editor

The MySQL Table Editor is a component that enables the creation and modification of tables. You can add or modify a table's columns or indexes, change the engine, add foreign keys, or alter the table's name. The MySQL Table Editor can be accessed in several ways, and most commonly by right-clicking on a table name within the Object Viewer and choosing ALTER TABLE. This will open a new tab within the
87
Creating Tables
main SQL Editor window. You can also access the MySQL Table Editor from an EER Diagram by doubleclicking a table object.
7.7.1.3.1. The Main Editor Window

Any number of tables may be edited in the MySQL Table Editor at any one time. Adding another table creates a new tab at the top of the editor. By default, the MySQL Table Editor appears docked at the top of the table editor tab, within the SQL editor.. The MySQL Table Editor is shown on top of the following figure. Figure 7.9. The Table Editor
The MySQL Table Editor provides a work space that has tabs used to perform these actions: Columns: Add or modify columns Indexes: Add or modify indexes Foreign Keys: Add or modify foreign keys Triggers: Add or modify triggers Partitioning: Manage partitioning Options: Add or modify various general, table, and row options
88
Creating Tables
The following sections discuss these tabs in further detail.
7.7.1.3.2. The Columns Tab

Use the Columns tab to display and edit all the column information for a table. With this tab, you can add, drop, and alter columns. You can also use the Columns tab to change column properties such as name, data type, and default value. Figure 7.10. The Columns Tab
Right-click a row under the Column Name column to open a pop-up menu with the following items: Move Up: Move the selected column up. Move Down: Move the selected column down. Copy: Copies the column for a model. Added in MySQL Workbench 5.2.45. Cut: Copies and then deletes the column for a model. Added in MySQL Workbench 5.2.45. Paste: Pastes the column. If a column with the same name already exists, then _copy1 is appended to the column name. Added in MySQL Workbench 5.2.45. Delete Selected Columns: Select multiple contiguous columns by right-clicking and pressing the Shift key. Use the Control key to select noncontiguous columns. Refresh: Update all information in the Columns tab. Clear Default: Clear the assigned default value. Default NULL: Set the column default value to NULL.
89
Creating Tables
Default 0: Set the column default value to 0. Default CURRENT_TIMESTAMP: Available for TIMESTAMP data types. Default CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP: Available for TIMESTAMP data types. To add a column, click the Column Name field in an empty row and enter an appropriate value. Select a data type from the Datatype list. Select the column property check boxes as required according to the list of column properties below, and also read the CREATE TABLE documentation for information about what these options mean. PK: PRIMARY KEY NN: NOT NULL UQ: UNIQUE INDEX BIN: BINARY UN: UNSIGNED ZF: ZEROFILL AI: AUTO_INCREMENT To change the name, data type, default value, or comment of a column, double-click the value you wish to change. The content then becomes editable. You can also add column comments to the Column Comment field. It is also possible to set the column collation, using the list in the Column Details panel. To the left of the column name is an icon that indicates whether the column is a member of the primary key. If the icon is a small key, that column belongs to the primary key, otherwise the icon is a blue diamond or a white diamond. A blue diamond indicates the column has NN set. To add or remove a column from the primary key, double-click the icon. You can also add a primary key by checking the PRIMARY KEY check box in the Column Details section of the table editor. If you wish to create a composite primary key you can select multiple columns and check the PK check box. However, there is an additional step that is required, you must click the Indexes tab, then in the Index Columns panel you must set the desired order of the primary keys. Note When entering default values, in the case of CHAR and VARCHAR data types MySQL Workbench will attempt to automatically add quotation marks, if the user does not start their entry with one. For other data types the user must manage quoting if required, as it will not be handled automatically by MySQL Workbench. Caution Care must be taken when entering a default value for ENUM columns because a nonnumeric default will not be automatically quoted. You must manually add single quote characters for the default value. Note that MySQL Workbench will not prevent you from entering the default value without the single quotation marks. If a nonnumeric default value is entered without quotation marks, this will lead to errors. For example, if the model is reverse engineered, the script will contain unquoted default values for ENUM columns and will fail if an attempt is made to run the script on MySQL Server.
90
Creating Tables
7.7.1.3.3. The Indexes Tab

The Indexes tab holds all index information for your table. Use this tab to add, drop, and modify indexes. Figure 7.11. The Indexes Tab
Select an index by right-clicking it. The Index Columns section displays information about the selected index. To add an index, click the last row in the index list. Enter a name for the index and select the index type from the list. Select the column or columns that you wish to index by checking the column name in the Index Columns list. You can remove a column from the index by removing the check mark from the appropriate column. You can also specify the order of an index by choosing ASC or DESC under the Order column. Create an index prefix by specifying a numeric value under the Length column. You cannot enter a prefix value for fields that have a data type that does not support prefixing. To drop an index, right-click the row of the index you wish to delete, then select the Delete Selected Indexes menu item.
91
Creating Tables
7.7.1.3.4. The Foreign Keys Tab

The Foreign Keys tab is organized in much the same fashion as the Indexes tab and adding or editing a foreign key is similar to adding or editing an index. Figure 7.12. The Foreign Keys Tab
To add a foreign key, click the last row in the Foreign Key Name list. Enter a name for the foreign key and select the column or columns that you wish to index by checking the column name in the Column list. You can remove a column from the index by removing the check mark from the appropriate column. Under Foreign Key Options, choose an action for the update and delete events. The options are: RESTRICT CASCADE SET NULL NO ACTION To drop a foreign key, right-click the row you wish to delete, then select the Delete Selected FKs menu item. To modify properties of a foreign key, select it and make the desired changes.
7.7.1.3.5. The Triggers Tab

The Triggers tab opens a field for editing an existing trigger or creating a new trigger. Create a trigger as you would from the command line.
92
Creating Tables
Figure 7.13. The Triggers Tab
7.7.1.3.6. The Partitioning Tab

To enable partitioning for your table, check the Enable Partitioning check box. This enables the partitioning options.
93
Creating Tables
Figure 7.14. The Partitioning Tab
The Partition By pop-up menu displays the types of partitions you can create: HASH LINEAR HASH KEY LINEAR KEY RANGE LIST Use the Parameters field to define any parameters to be supplied to the partitioning function, such as an integer column value. Choose the number of partitions from the Partition Count list. To manually configure your partitions, check the Manual check box. This enables entry of values into the partition configuration table. The entries in this table are: Partition Values Data Directory Index Directory Min Rows
94
Creating Tables
Max Rows Comment Subpartitioning is also available. For more information about partitioning, see Partitioning.
7.7.1.3.7. The Options Tab

The Options tab enables you to set several types of options. Figure 7.15. The Options Tab
which are grouped into the following sections: General Options Row Options Storage Options Merge Table options The following discussion describes these options in more detail. General Options Section
95
Creating Tables
In the General Options section, choose a pack keys option. The options are Default, Pack None, and Pack All. You may also encrypt the definition of a table. The AUTO_INCREMENT and delayed key update behaviors apply only to MyISAM tables. Row Options Section To set the row format, choose the desired row format from the list. For more information about the different row formats that are available, see MyISAM Table Storage Formats. These options are: Default Dynamic Fixed Compressed Redundant Compact When you expect a table to be particularly large, use the Avg. Row, Min. Rows, and Max. Rows options to enable the MySQL server to better accommodate your data. See CREATE TABLE Syntax for more information on how to use these options. Storage Options Section The Storage Options section is available only for MyISAM tables. Use it to configure a custom path to the table storage and data files. This can help improve server performance by locating different tables on different hard drives. Merge Table Options Section Use the Merge Table Options section to configure MERGE tables. To create a MERGE table, select MERGE as your storage engine and then specify the MyISAM tables you wish to merge in the Union Tables dialog. You may specify the action the server should take when users attempt to perform INSERT statements on the merge table. You may also select the Merge Method by selecting from the list. For more information about MERGE tables, see The MERGE Storage Engine.
7.7.1.3.8. The Inserts Tab

Use the Inserts tab to insert rows into the table. To edit a row, click the field you wish to change and enter the new data. Right-clicking a row displays a menu with the following items: Set Field(s) to NULL: Set the column value to NULL. Delete Row(s): Delete the selected row or rows. Copy Row Content: Copies the row to the clipboard. Strings are copied quoted, and NULL values are preserved. Copy Row Content (unquoted): Copies the row to the clipboard. Strings are not quoted and NULL are copied as a space.
96
Creating Tables
Copy Field Content: Copies the value of the selected field to the clipboard. Strings are quoted. Copy Field Content (unquoted): Copies the value of the selected field to the clipboard. Strings are not quoted. Note that the insert editor features a toolbar. This has the same functionality as explained in Section 6.7.4.2, Results Tabsheets and Section 6.7.4.3, Live Editing Tabsheets. You can also hover the cursor over the toolbar to display tooltips. Any rows you add will be inserted when you forward engineer the database (if you choose the Generate INSERT statements for tables option). Note When entering string values that there is slightly different behavior between the 5.0, 5.1, and 5.2 versions of MySQL Workbench. For 5.0 and 5.1, if a string is entered without leading and trailing quotation marks, the Inserts Editor adds quoting and escapes characters that require it. However, if quoted text is entered, the Inserts Editor performs no further checks and assumes that a correctly escaped and quoted sequence has been entered. 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. 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.
7.7.1.3.9. The Privileges Tab

Use the Privileges tab to assign specific roles and privileges to a table. You may also assign privileges to a role using the role editor. For a discussion of this topic, see Section 7.5.5.1, Adding Roles. When this tab is first opened, all roles that have been created are displayed in the list on the right. Move the roles you wish to associate with this table to the Roles list on the left. Do this by selecting a role and then clicking the < button. Use the Shift key to select multiple contiguous roles and the Control key to select noncontiguous roles. To assign privileges to a role, click the role in the Roles list. This displays all available privileges in the Assigned Privileges list. The privileges that display are: ALL CREATE DROP GRANT OPTION REFERENCES ALTER
97
Creating Foreign Key Relationships
DELETE INDEX INSERT SELECT UPDATE TRIGGER You can choose to assign all privileges to a specific user or any other privilege as listed previously. Privileges irrelevant to a specific table, such as the FILE privilege, are not shown. If a role has already been granted privileges on a specific table, those privileges show as already checked in the Assigned Privileges list.
7.7.2. Creating Foreign Key Relationships

Foreign key constraints are supported for the InnoDB storage engine only. For other storage engines, the foreign key syntax is correctly parsed but not implemented. For more information, see Foreign Key Differences. Using MySQL Workbench you may add a foreign key from within the table editor or by using the relationship tools on the vertical toolbar of an EER Diagram. This section deals with adding a foreign key using the foreign key tools. To add a foreign key using the table editor, see Section 7.7.1.3.4, The Foreign Keys Tab. The graphical tools for adding foreign keys are most effective when you are building tables from the ground up. If you have imported a database using an SQL script and need not add columns to your tables, you may find it more effective to define foreign keys using the table editor.
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
98
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-tomany 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.16. 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.16, 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.
7.7.2.2. The Relationship Editor

Double-clicking a relationship on the EER diagram canvas opens the relationship editor. This has two tabs: Relationship, and Foreign Key.
99
The Relationship Tab In the Relationship tab, you can set the caption of a relationship using the Caption field. This name displays on the canvas and is also the name used for the constraint itself. The default value for this name is fk_source_table_destination_table. Use the Model menu, Menu Options menu item to set a project-specific default name for foreign keys. To change the global default, see Section 5.4.4, The Model Tab. You can also add a secondary caption and a caption to a relationship. The Visibility Settings section is used to determine how the relationship is displayed on the EER Diagram canvas. Fully Visible is the default but you can also choose to hide relationship lines or to use split lines. The split line style is pictured in the following figure. Figure 7.17. The Split Connector
Note A broken line connector indicates a nonidentifying relationship. The split line style can be used with either an identifying relationship or a nonidentifying relationship. It is used for display purposes only and does not indicate anything about the nature of a relationship. To set the notation of a relationship use the Model menu, Relationship Notation menu item. For more information, see Section 7.5.1.5.4, The Relationship Notation Submenu. The Foreign Key Tab The Foreign Key tab contains several sections: Referencing Table, Cardinality and Referenced Table. The Mandatory check boxes are used to select whether the referencing table and the referenced table are mandatory. By default, both of these constraints are true (indicated by the check boxes being checked). The Cardinality section has a set of radio buttons that enable you to choose whether the relationship is one-to-one or one-to-many. There is also a check box that enables you to specify whether the relationship is an identifying relationship.
7.7.2.3. Connection Properties

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

You can add views to a database either from the Physical Schemata section of the MySQL Model page or from the EER Diagram.
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.
101
Creating Views
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' As of MySQL Workbench 5.2.45, the 'view_name' is only cut from the EER canvas. Before, it was also removed from the schema. Copy 'view_name' Paste Edit View... Edit in New Window... Copy SQL to Clipboard Delete 'view_name': deletes from both the EER canvas and schema. Remove 'view_name': deletes from the EER canvas, but not the schema. This option exists as of MySQL Workbench 5.2.45. 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.
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.
102
Creating Routines and Routine Groups
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.
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.9, The Privileges Tab.
7.7.3.4. Modifying a View Using the Properties Palette

When you select a view 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.
7.7.4. Creating Routines and Routine Groups

You can add Routine Groups to a database either from the Physical Schemata section of the MySQL Model page or from an EER Diagram. Routines may be added only from the Physical Schemata section of the MySQL Model page. To view an existing schema, along with its Routines and Routine Groups, choose Database, Reverse Engineer... from the main menu. After the schema has been added to the current model, you can see the schema objects on the Physical Schemata panel on the MySQL Model page. The Routines and Routine Groups are listed there. MySQL Workbench unifies both stored procedures and stored functions into one logical object called a Routine. Routine Groups are used to group routines that are related. You can decide how many Routine
103
Groups you want to create and you can use the Routine Group Editor to assign specific routines to a group, using a drag and drop interface. When designing an EER Diagram, you can place the Routine Groups on the canvas by dragging them from the Catalog Palette. Placing individual routines on the diagram is not permitted, as it would clutter the canvas.
7.7.4.1. Routines
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

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.
104
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.9, The Privileges Tab. Note Privileges are available only in the Standard Edition of MySQL Workbench.
7.7.4.2. Routine Groups

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

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.9, The Privileges Tab. Note Privileges are available only in the Standard Edition of MySQL Workbench.
106
Creating Layers
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.
7.7.5. Creating Layers

You can add layers to a database only from an EER Diagram. Layers are used to help organize objects on the canvas. Typically, related objects are added to the same layer; for example, you may choose to add all your views to one layer.
7.7.5.1. Adding Layers to an EER Diagram

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.18. 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.
107
Creating Notes
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.
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.
7.7.6. Creating Notes

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.
7.7.6.1. Adding Notes

Double-clicking the Add Note icon in the Model Notes section of the MySQL Model page adds a note with the default name of note1. If a note with this name already exists, the new note is named note2. Adding a new note automatically opens the note editor docked at the bottom of the application. For information about using the note editor, see Section 7.7.6.2, The Note Editor. Right-clicking a note opens a pop-up menu with the following items: Rename Cut 'note_name' Copy 'note_name'
108
Creating Text Objects
Delete 'note_name' The Edit Note... item opens the note editor. For information about using the note editor, see Section 7.7.6.2, The Note Editor. The cut and copy items are useful for copying notes between different schemata. Notes can be added only on the MySQL Model page.
7.7.6.2. The Note Editor

To invoke the note editor, double-click a note object in the Model Note section on the MySQL Model page. This opens the note editor docked at the bottom of the application. Double-clicking the note tab undocks the editor. Double-click the title bar to redock it. Any number of notes may be open at the same time. Each additional note appears as a tab at the top of the note editor. Use the editor to change the name of a note or its contents.
7.7.7. Creating Text Objects

Text objects are applicable only to an EER diagram. They can be used for documentation purposes; for example, to explain a grouping of schema objects. They are also useful for creating titles for an EER diagram should you decide to export a diagram as a PDF or PNG file.
7.7.7.1. Adding Text Objects to an EER Diagram

To add text objects to an EER Diagram, use the Text Object tool on the vertical toolbar. Make sure that the EER Diagram tab is selected, then right-click the text object icon on the vertical toolbar. The text object icon is the rectangular icon found below the label icon. Clicking the mouse on this icon changes the mouse pointer to a text object pointer. You can also change the mouse pointer to a text object pointer by pressing the N key. Choosing the Text Object tool changes the contents of the toolbar that appears immediately below the menu bar. When the Text Object pointer is active, this toolbar contains a color chart list. Use this list to select the color accent for the new text object. The color of your text object can be changed later using the Properties palette. Create a text object by clicking anywhere on the EER Diagram canvas. This creates a new text object with the default name text1. To revert to the default mouse pointer, click the arrow icon at the top of the vertical toolbar. Right-clicking a text object opens a pop-up menu. These menu options are identical to the options for other objects. However, since a text object is not a database object, there is no confirmation dialog box when you delete a text object.
7.7.7.2. The Text Object Editor

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.
109
Creating Images
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.
7.7.8. Creating Images

Images exist only on the EER Diagram canvas; you can add them only from the EER Diagram window.
7.7.8.1. Adding Images to an EER Diagram

To add images to an EER Diagram, use the Image tool on the vertical toolbar. Make sure that the EER Diagram tab is selected, then right-click the image icon on the vertical toolbar. The image icon is the icon just above the table icon. Clicking the mouse on this icon changes the mouse pointer to an image pointer. You can also change the mouse pointer to an image pointer by pressing the I key. Create an image by clicking anywhere on the EER Diagram canvas. This opens a file open dialog box. Select the desired image, then close the dialog box to create an image on the canvas. To revert to the default mouse pointer, click the arrow icon at the top of the vertical toolbar. Right-clicking this object opens a pop-up menu with the following items: Cut 'Image' Copy 'Image' Edit Image... Edit in New Window... Delete 'Image' These menu items function in exactly the same way as they do for other objects on an EER diagram. However, images are not database objects so there is no confirmation dialog box when they are deleted.
7.7.8.2. The Image Editor

To invoke the image editor, double-click an image object on an EER Diagram canvas. This opens the image editor docked at the bottom of the application. Double-clicking the image editor tab undocks the editor. Double-click the title bar to redock it. Any number of images may be open at the same time. Each additional image appears as a tab at the top of the image editor.
7.7.8.2.1. The Image Tab

Use the Image tab of the image editor to perform the following tasks:
110
Reverse Engineering
Rename the image using the Name text box. Browse for an image using the Browse button.
7.7.9. Reverse Engineering

With MySQL Workbench, you can reverse engineer a database using a MySQL create script or you can connect to a live MySQL server and import a single database or a number of databases. All versions of MySQL Workbench can reverse engineer using a MySQL DDL script. Only commercial versions of MySQL Workbench can reverse engineer a database directly from a MySQL server.
7.7.9.1. Reverse Engineering Using a Create Script

To reverse engineer using a create script, choose the File, Import, Reverse Engineer MySQL Create Script... menu items. This opens a file open dialog box with the default file type set to an SQL script file, a file with the extension sql. You can create a data definition (DDL) script by executing the mysqldump db_name --no-data > script_file.sql command. Using the --no-data option ensures that the script contains only DDL statements. However, if you are working with a script that also contains DML statements you need not remove them; they will be ignored. Note If you plan to redesign a database within MySQL Workbench and then export the changes, be sure to retain a copy of the original DDL script. You will need the original script to create an ALTER script. For more information, see Section 7.7.10.1.2, Altering a Schema. Use the --databases option with mysqldump if you wish to create the database as well as all its objects. If there is no CREATE DATABASE db_name statement in your script file, you must import the database objects into an existing schema or, if there is no schema, a new unnamed schema is created. If your script creates a database, MySQL Workbench creates a new physical schemata tab on the MySQL Model page. Any database objects may be imported from a script file in this fashion: tables, views, routines, and routine groups. Any indexes, keys, and constraints are also imported. Objects imported using an SQL script can be manipulated within MySQL Workbench the same as other objects. Before exiting, be sure to save the schema. Choose the File, Save menu item and the reverse-engineered database will be saved as a MySQL Workbench file with the extension mwb. See Section 7.8.1, Importing a Data Definition SQL Script, for a tutorial on reverse engineering the sakila database.
7.7.9.2. Reverse Engineering a Live Database

To reverse engineer a live database, choose the Database, Reverse Engineer... menu item from the main menu. This opens the Reverse Engineer Database wizard.
111
Reverse Engineering
Figure 7.19. Reverse Engineer Database Wizard
The first page of the wizard enables you to set up a connection to the live database you wish to reverse engineer. You can set up a new connection or select a previously created stored connection. Typical information required for the connection includes host name, user name and password. After this information has been entered, or you have selected a stored connection, click the Next button to proceed to the next page.
112
Reverse Engineering
Figure 7.20. Connect to DBMS
Review the displayed information to make sure that the connection did not generate errors, then click Next. The next page displays the schemata available on the server. Click the check box or check boxes for any schemata you wish to process.
113
Reverse Engineering
Figure 7.21. Select Schemata
After you have selected the desired schemata, click the Next button to continue. The wizard then displays the tasks it carried out and summarizes the results of the operation.
114
Reverse Engineering
Figure 7.22. Retrieve Object Information
Review the results before clicking Next to continue. The next page is the Select Objects page. It has a section for each object type present in the schema (tables, views, routines, and so forth). This page is of special interest if you do not wish to import all the objects from the existing database. It gives you the option of filtering which objects are imported. Each section has a Show Filter button. Click this button if you do not want to import all the objects of a specific type.
115
Reverse Engineering
Figure 7.23. Select Objects
For the Import MySQL Table Objects section, if you click the Show Filter button, the following page is displayed.
116
Reverse Engineering
Figure 7.24. Show Filter
This page enables you to select specific tables for import. Having selected the desired tables, you can optionally hide the filter by clicking the Hide Filter button. The other sections, such as MySQL Routine Objects, have similar filters available. Click Execute to continue to the next page. The wizard then imports objects, displaying the tasks that have been carried out and whether the operation was successful. If errors were generated, you can click the Show Logs button to see the nature of the errors.
117
Reverse Engineering
Figure 7.25. Progress
Click Next to continue to the next page. The final page of the wizard provides a summary of the reverse engineered objects.
118
Reverse Engineering
Figure 7.26. Results
Click Finish to exit the wizard. Before exiting MySQL Workbench be sure to save the schema. Choose the File, Save menu item to save the reverse-engineered database as a MySQL Workbench file with the extension mwb.
7.7.9.2.1. Errors During Reverse Engineering

During reverse engineering, the application checks for tables and views that duplicate existing names and disallows duplicate names if necessary. If you attempt to import an object that duplicates the name of an existing object you will be notified with an error message. To see any errors that have occurred during reverse engineering, you can click the button Show Logs. This will create a panel containing a list of messages, including any error messages than may have been generated. Click the Hide Logs button to close the panel.
119
Forward Engineering
Figure 7.27. Message Log
If you wish to import an object with the same name as an existing object, rename the existing object before reverse engineering. If you import objects from more than one schema, there will be a tab in the Physical Schemata section of the MySQL Model page for each schema imported. You cannot reverse engineer a live database that has the same name as an existing schema. If you wish to do this, first rename the existing schema.
7.7.10. Forward Engineering

It is possible to forward engineer a database using an SQL script or by connecting to a live database.
120
Forward Engineering
7.7.10.1. Forward Engineering Using an SQL Script

To create a script of your database model, choose the Export item from the File menu. You may export a script to alter an existing database or create a new database. The script to create a database is similar to the one created using the mysqldump db_name command. If you choose to create a database, there are several export options available.
7.7.10.1.1. Creating a Schema

Select the File, Export, Forward Engineer SQL CREATE Script menu item to start the Forward Engineer SQL Script wizard. The following figure shows the first page of the wizard. Figure 7.28. SQL Export Options
The SQL Export Options displays the following facilities: Output SQL Script File
121
Forward Engineering
To specify the output file name, enter it into the Output SQL Script File field, or use the Browse button to select a file. If this field is left blank, you will be able to view the generated script, but it will not be saved to a file. Generate DROP Statements Before Each CREATE Statement Select this option to generate a statement to drop each object before the statement that creates it. This ensures that any existing instance of each object is removed when the output is executed. Omit Schema Qualifier in Object Names Select this option to generate unqualified object names in SQL statements. Generate Separate CREATE INDEX Statements Select this option to create separate statements for index creation instead of including index definitions in CREATE TABLE statements. Add SHOW WARNINGS after every DDL statement Select this option to add SHOW WARNINGS statements to the output. This causes display of any warnings generated when the output is executed, which can be useful for debugging. Do Not Create Users. Only Export Privileges Select this option to update the privileges of existing users, as opposed to creating new users. Exporting privileges for nonexistent users will result in errors when you execute the CREATE script. Exporting users that already exist will also result in an error. Generate INSERT Statements for Tables Select this option if you have added any rows to a table. For more information about inserting rows, see Section 7.7.1.3.8, The Inserts Tab. Clicking Next takes you to the SQL Object Export Filter page where you select the objects you wish to export.
122
Forward Engineering
Figure 7.29. SQL Object Export Filter
Precise control over the objects to export can be fine tuned by clicking the Show Filter button. After the objects to export have been selected, it is possible to reduce the expanded panel by clicking the same button, now labeled Hide Filter. After selecting the objects to export, click the Next button to review the script that has been generated.
123
Forward Engineering
Figure 7.30. Review Generated Script
You may return to the previous page using the Back button. The Finish button saves the script file and exits. You can then use the saved script to create a database.
7.7.10.1.2. Altering a Schema

The menu item for altering a schema, Forward Engineer SQL ALTER Script..., is used for updating a database that has been redesigned within MySQL Workbench. Typically, this option is used when the SQL script of a database has been imported into MySQL Workbench and changed, and then you want to create a script that can be run against the database to alter it to reflect the adjusted model. For instructions on importing a DDL script, see Section 7.7.9.1, Reverse Engineering Using a Create Script. Select the File, Export, Forward Engineer SQL ALTER Script menu item to start the Forward Engineer an ALTER Script wizard. You will be presented with the first page showing the available options.
124
Forward Engineering
Figure 7.31. Options
This first page enables you to select an SQL script and compare it with the model currently in MySQL Workbench. The difference between the two models will be used to create an alter script that can be used to modify the target schema to match the model held in MySQL Workbench. To view the script generated, rather than saving it to a file, leave the Output File field empty. Note The script selected as the Input File must use full schema qualifiers, such as schema_name.table_name. Otherwise, MySQL Workbench cannot generate a useable alter script. Clicking Next brings you to the Review SQL Script page.
125
Forward Engineering
Figure 7.32. Script
Here you can review and change the alter script that will be generated. Make any changes you wish and, if you are happy with the changes, save the ALTER script to file using the Save to File... button. You can also click the Execute button to tell MySQL Workbench to write the script to the previously specified output file. The generated script can then be used to update the database.
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).
126
Forward Engineering
Figure 7.33. 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.
127
Forward Engineering
Figure 7.34. Options
Select the required options and then click Next. The next page enables you to select the objects to forward engineer.
128
Forward Engineering
Figure 7.35. 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.
129
Forward Engineering
Figure 7.36. 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.
130
Forward Engineering
Figure 7.37. 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.
131
Forward Engineering
Figure 7.38. 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.
7.7.10.3. Database Synchronization

It is possible to synchronize a model in MySQL Workbench with a live database. By default, the synchronization process will change the live database to be the same as the model, but this is configurable during the synchronization process. MySQL Workbench enables control over the direction of synchronization, and which objects to synchronize, in a completely flexible way. You can choose to synchronize only certain tables, enable synchronization to the live database only, enable synchronization from the live database to the model only, or a combination of directions. In effect you have complete control as to whether the synchronization is unidirectional or bidirectional, and which objects exactly are subject to synchronization. This is all controlled in the Select Changes to Apply page of the synchronization wizard.
132
Forward Engineering
Figure 7.39. Model and Database Differences
In the preceding example, the live database consists of table1, table2 and table3. In MySQL Workbench an additional table, table4, has been created, along with a relationship between it and table3. Further, table5 exists in the live database, but not in the model. The actions that are configured to occur would result in table3 being altered (to include the relationship with table4), table4 being created and table5 being dropped, in the live database. It is possible to reconfigure this, though. The next example shows how the direction of synchronization can be changed.
133
Forward Engineering
Figure 7.40. Controlling Synchronization Direction
In this case, the synchronization direction has been changed so that rather than the default action of table5 being dropped from the live database, it will be incorporated into the MySQL Workbench model. For convenience, the wizard provides three additional buttons to enable synchronization directions to be applied to a group of selected changes. The Update Model button causes the selected changes to be applied only to the model itself. In the following example, table7 would be added to the model.
134
Forward Engineering
Figure 7.41. Update Model Button
The Ignore button causes the selected changes to be ignored. No synchronization will take place for those changes. In the following example, no changes would take place.
135
Forward Engineering
Figure 7.42. Ignore Button
The Update Source button causes the selected changes to be applied only to the live database. In the following example, table6 would be added to the live database and table7 would be dropped from the live database.
136
Forward Engineering
Figure 7.43. Update Source Button
It is also possible to control individual changes by clicking the arrows. Clicking an arrow causes it to change between the three available synchronization directions: from model to source, from source to model, or bidirectionally. In the following example, table6 will be created in the live database, and table7 will be created in the model.
137
Forward Engineering
Figure 7.44. Click Arrows to Change Direction of Synchronization
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.
138
Forward Engineering
Figure 7.45. 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.
139
Modeling Tutorials
Figure 7.46. Catalog Diff Report
7.8. Modeling Tutorials

This chapter contains three short tutorials intended to familiarize you with the basics of MySQL Workbench. These tutorials show how MySQL Workbench can be used both to design and to document databases. Creating a database from scratch is the focus of Section 7.8.2, Using the Default Schema and exploring the graphic design capabilities of MySQL Workbench is touched upon in Section 7.8.3, Basic Modeling. Both these tutorials show the database design capabilities of MySQL Workbench. Importing an SQL data definition script is probably the quickest way to familiarize yourself with MySQL Workbenchthis tutorial makes use of the sakila database and emphasizes the use of MySQL Workbench as a documentation tool. Examples taken from the sakila database are used throughout the documentation, so doing this tutorial can be very helpful in understanding MySQL Workbench.
140
Importing a Data Definition SQL Script
7.8.1. Importing a Data Definition SQL Script

For this tutorial, use the sakila database script, which you can find by visiting the http://dev.mysql.com/ doc/ page, selecting the Other Docs tab, and looking in the Example Databases section After downloading the file, extract it to a convenient location. Open MySQL Workbench and find the Reverse Engineer MySQL Create Script menu item by first choosing File and then Import. Find and import the sakila-schema.sql file. This is the script that contains the data definition statements for the sakila database. The file filter for the file open dialog window defaults to *.sql so you should be able to view only files with the sql extension. If the file was successfully imported, the application's status bar reads, Import MySQL Create Script done. To view the newly imported script, expand the Physical Schemata section by double-clicking the arrow on the left of the Physical Schemata title bar. Select the tab labeled sakila. You may also wish to remove the default schema tab, mydb. Select this tab, then click the - button on the upper right in the Physical Schemata panel. To view all the objects in the sakila schema, you may need to expand the Physical Schemata window. Move the mouse pointer anywhere over the gray area that defines the lower edge of the Physical Schemata window. Hold down the right mouse button and move the mouse to adjust the size of the window. After you have expanded the window, all the objects in the sakila database should be visible. Tables appear at the top followed by views and then routines. There are no routine groups in this schema, but you should see the Routine Groups section and an Add Group icon. For a complete description of importing a MySQL create script, see Section 7.7.9.1, Reverse Engineering Using a Create Script.
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.47. Adding Tables to the Canvas
141
Using the Default Schema
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.50, 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 quicklysomething 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.
7.8.2. Using the Default Schema

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.48. 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.
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.
142
Basic Modeling
Altering the table by adding indexes or other features is also easily done using the table editor.
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.
7.8.3. Basic Modeling

On the MySQL Model page, double-click the Add Diagram icon. This creates and opens a new EER Diagram canvas. Figure 7.49. Adding an EER Diagram
From an EER diagram page you can graphically design a database.
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.
143
Documenting the sakila Database
7.8.3.2. Creating a Foreign Key

Select the table tool again and place another table on the canvas. Name this table invoice_item. Next click the 1:n Non-Identifying Relationship tool. First, click the invoice_item table; notice that a red border indicates that this table is selected. Next, click the invoice table. This creates a foreign key in the invoice_item table, the table on the many side of the relationship. This relationship between the two tables is shown graphically in crow's foot notation. Revert to the default mouse pointer by clicking the arrow at the top of the vertical toolbar. Click on the invoice_item table and select the Foreign keys tab. Click the Foreign key Name field. The referenced table should show in the Referenced Table column and the appropriate column in the Referenced Column column. To delete the relationship between two tables, click the line joining the tables and then press Control +Delete. Experiment with the other tools on the vertical toolbar. Delete a relationship by selecting the eraser tool and clicking the line joining two tables. Create a view, add a text object, or add a layer. 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.
7.8.4. Documenting 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.
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.
144
Documenting the sakila Database
Figure 7.50. The sakila Database EER Diagram
The object notation style used in Figure 7.50, 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.
145
Printing
7.9. Printing
The printing options used to create printouts of your EER Diagrams are found under the File menu. To create documentation of your models, see Section 7.5.1.5.1, The DBDoc Model Reporting Dialog Window (Commercial Version).
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.
7.10. MySQL Workbench Schema Validation Plugins (Commercial Version)

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.
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 146
MySQL-Specific Validation
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
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
147
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.51. The DBDoc Model Reporting Main Wizard
148
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 Windows Linux Mac OS X %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. Include DDL code for objects: Generates DDL code. 149 Typical Default Documents Folder C:\Documents and Settings \user_name\My Documents ~/Documents Users/user_name/Documents
Clicking the Generate 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. 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. routine_details.html: List of all routines for the schema. table_details.html: The main report details. table_details_list.html: A Schema overview along with details of columns, indexes and foreign keys for each schema. table_element_details.html: The details for every element of the table. top.html: The top frame of the report. view_details.html: List of all columns and indexes for the schema. 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:
150
Customizing DBDoc Model Reporting Templates
Figure 7.52. The DBDoc Model Report
If you wish to create custom templates please refer to Section 7.12, Customizing DBDoc Model Reporting Templates.
7.12. Customizing DBDoc Model Reporting Templates

This section provides an overview of creating and modifying DBDoc Model Reporting templates, as used by MySQL Workbench. The MySQL Workbench DBDoc Model Reporting system is based on the Google Template System. This discussion does not attempt to explain the Google Template System in detail. For a useful overview of how the Google Template System works, see the Google document, How To Use the Google Template System. The templates employed by the DBDoc Model Reporting system are text files that contain Markers. These text files are processed by the template system built into MySQL Workbench, and the markers replaced by actual data. The output files are then generated. It is these output files, typically HTML or text, that are then viewed by the user. Markers can be of six types: Template Include Comment
151
Set delimiter Pragma Variable Section start and Section end The last two are the most commonly used in MySQL Workbench templates and these important markers are briefly described in the following sections. Variables The use of variables in the templates is straightforward. Any variables denoted by markers in the template file are replaced by their corresponding data prior to the output file being generated. The mapping between variables and their corresponding data is stored by MySQL Workbench in what is known as a data dictionary. In the data dictionary, the variable name is the key and the variable's corresponding data is the value. The data dictionaries are built by MySQL Workbench and filled with the data contained in the model being processed. By way of example, the following code snippet shows part of a template file:
Total number of Schemata: {{SCHEMA_COUNT}}
In the generated output file, the variable {{SCHEMA_COUNT}} is replaced by the number of schemata in the model:
Total number of Schemata: 2
A variable can appear as many times as required in the template file. Sections Sections are used to perform iteration in the templates. When MySQL Workbench exchanges the variables in a section for data, it does so iteratively, using all data in the data dictionary in which the variable is defined. MySQL Workbench builds the data dictionaries according to the model currently being processed. Consider the following code snippet:
{{#SCHEMATA}} Schema: {{SCHEMA_NAME}} {{/SCHEMATA}}
In the preceding snippet, the section start and end are indicated by the {{#SCHEMATA}} and {{/ SCHEMATA}} markers. When MySQL Workbench processes the template, it notes the section and iterates it until the variable data for {{SCHEMA_NAME}} in the corresponding data dictionary is exhausted. For example, if the model being processed contains two schemata, the output for the section might resemble the following:
Schema: Airlines Schema: Airports
Data Dictionaries It is important to understand the relationship between sections and data dictionaries in more detail. In a data dictionary the key for a variable is the variable name, a marker. The variable value is the variable's data. The entry for a section in a data dictionary is different. For a section entry in a data dictionary, the key is the section name, the marker. However, the value associated with the key is a list of data dictionaries. In
152
MySQL Workbench each section is usually associated with a data dictionary. You can think of a section as activating its associated dictionary (or dictionaries). When a template is processed, data dictionaries are loaded in a hierarchical pattern, forming a tree of data dictionaries. This is illustrated by the following table. Table 7.1. Data Dictionaries Tree Data Dictionary MAIN SCHEMATA TABLES COLUMNS_LISTING REL_LISTING INDICES_LISTING Loads Data Dictionary SCHEMATA TABLES, COLUMNS (Detailed is true), FOREIGN_KEYS (Detailed is true), INDICES (Detailed is true) REL_LISTING, INDICES_LISTING, COLUMNS_LISTING, TABLE_COMMENT_LISTING, DDL_LISTING COLUMNS (Detailed is false) REL (Detailed is false) INDICES (Detailed is false)
The root of the tree is the main dictionary. Additional dictionaries are loaded from the root to form the dictionary tree. Note If a template has no sections, any variables used in the template are looked up in the main dictionary. If a variable is not found in the main dictionary (which can be thought of as associated with the default, or main, section), no data is generated in the output file for that marker. Evaluation of variables The tree structure of the data dictionaries is important with respect to variable evaluation. As variables are defined in data dictionaries, their associated values have meaning only when that particular data dictionary is active, and that means when the section associated with that data dictionary is active. When a variable lookup occurs, the system checks the data dictionary associated with the current section. If the variable value can be found there, the replacement is made. However, if the variable's value is not found in the current data dictionary, the parent data dictionary is checked for the variable's value, and so on up the tree until the main data dictionary, or root, is reached. Suppose that we want to display the names of all columns in a model. Consider the following template as an attempt to achieve this:
Report -----Column Name: {{COLUMN_NAME}}
This template produces no output, even for a model that contains many columns. In this example, the only data dictionary active is the main dictionary. However, COLUMN_NAME is stored in the COLUMNS data dictionary, which is associated with the COLUMNS section. With this knowledge, the template can be improved as follows:
Report -----{{#COLUMNS}} Column Name: {{COLUMN_NAME}}
153
{{/COLUMNS}}
This still does not produce output. To see why, see Table 7.1, Data Dictionaries Tree. The COLUMNS data dictionary has the parent dictionary COLUMNS_LISTING. COLUMNS_LISTING has the parent TABLES, which has the parent SCHEMATA, whose parent is the main dictionary. Remember that for a dictionary to be involved in variable lookup, its associated section must currently be active. To achieve the desired output, the template must be something like the following:
Report -----{{#SCHEMATA}} {{#TABLES}} {{#COLUMNS_LISTING}} {{#COLUMNS}} Column Name: {{COLUMN_NAME}} {{/COLUMNS}} {{/COLUMNS_LISTING}} {{/TABLES}} {{/SCHEMATA}}
The following template is the same, but with explanatory comments added:
Report -----{{! Main dictionary active}} {{#SCHEMATA}} {{! SCHEMATA dictionary active}} {{#TABLES}} {{! TABLES dictionary active}} {{#COLUMNS_LISTING}} {{! COLUMNS_LISTING dictionary active}} {{#COLUMNS}} {{! COLUMNS dictionary active}} Column Name: {{COLUMN_NAME}} {{! COLUMN_NAME variable is looked-up, and found, in COLUMNS data dictionary}} {{/COLUMNS}} {{/COLUMNS_LISTING}} {{/TABLES}} {{/SCHEMATA}}
Imagine now that for each column name displayed you also wanted to display its corresponding schema name, the template would look like this:
Report -----{{#SCHEMATA}} {{#TABLES}} {{#COLUMNS_LISTING}} {{#COLUMNS}} Schema Name: {{SCHEMA_NAME}} Column Name: {{COLUMN_NAME}} {{/COLUMNS}} {{/COLUMNS_LISTING}} {{/TABLES}} {{/SCHEMATA}}
When variable lookup is performed for SCHEMA_NAME, the COLUMNS dictionary is checked. As the variable is not found there the parent dictionary will be checked, COLUMNS_LISTING, and so on, until the variable is eventually found where it is held, in the SCHEMATA dictionary. If there are multiple schemata in the model, the outer section is iterated over a matching number of times, and SCHEMA_NAME accordingly has the correct value on each iteration. It's important to always consider which dictionary must be active (and which parents) for a variable to be evaluated correctly. The following section has a table that helps you identify section requirements.
154
Supported Template Markers
7.12.1. Supported Template Markers

The following table shows the supported markers. These markers can be used in any template, including custom templates. Using the table The table shows which variables are defined in which sections. The variable should be used in its correct section or its value will not be displayed. If a variable type is a variable, then the table describes its data dictionary, and a parent dictionary if type is a section. Also remember that the data dictionaries used to perform variable lookups form a hierarchical tree, so it is possible to use a variable in a child section that is defined in a parent section. Table 7.2. Supported Template Markers Marker text TITLE GENERATED STYLE_NAME Type Variable Variable Variable Data Dictionary or Parent Dictionary MAIN MAIN MAIN Corresponding data Title of the report Date and time when the report was generated The name of the style selected in MySQL Workbench, this is typically used to load the corresponding CSS file, depending on the name of the style selected in MySQL Workbench The number of schemata in the model Project title as set for the model in Document Properties Project name as set for the model in Document Properties Project author as set for the model in Document Properties Project version as set for the model in Document Properties Project description as set for the model in Document Properties Automatically set for the model project, but as displayed in Document Properties Automatically set for the model project, but as displayed in Document Properties The number of tables in all schemata in the model
SCHEMA_COUNT PROJECT_TITLE PROJECT_NAME PROJECT_AUTHOR PROJECT_VERSION PROJECT_DESCRIPTION
Variable Variable Variable Variable Variable Variable
MAIN MAIN MAIN MAIN MAIN MAIN
PROJECT_CREATED
Variable
MAIN
PROJECT_CHANGED
Variable
MAIN
TOTAL_TABLE_COUNT
Variable
MAIN
155
Marker text TOTAL_COLUMN_COUNT
Type Variable
Data Dictionary or Parent Dictionary MAIN
Corresponding data The number of columns in all tables in all schemata in the model The number of indexes in the model The number of foreign keys in the model Used to mark the start and end of a SCHEMATA section; the SCHEMATA data dictionary becomes active in this section The schema name The schema ID The number of tables in the current schema The number of columns in the current schema The number of indexes in the current schema The number of foreign keys in the current schema Marks the start and end of a TABLES section; the TABLES data dictionary becomes active in this section The table name The table ID Marks the start and end of a COLUMNS_LISTING section; the COLUMNS_LISTING data dictionary becomes active in this section Marks the start and end of a COLUMNS section; the COLUMNS data dictionary becomes active in this section Whether the column is a primary key The column name The column data type Whether the column permits NULL values The column default value
TOTAL_INDEX_COUNT TOTAL_FK_COUNT SCHEMATA
Variable Variable Section
MAIN MAIN MAIN
SCHEMA_NAME SCHEMA_ID TABLE_COUNT COLUMN_COUNT INDICES_COUNT FOREIGN_KEYS_COUNT TABLES
Variable Variable Variable Variable Variable Variable Section
SCHEMATA SCHEMATA SCHEMATA SCHEMATA SCHEMATA SCHEMATA SCHEMATA
TABLE_NAME TABLE_ID COLUMNS_LISTING
Variable Variable Section
TABLES TABLES TABLES
COLUMNS
Section
COLUMNS_LISTING
COLUMN_KEY COLUMN_NAME COLUMN_DATATYPE COLUMN_NOTNULL COLUMN_DEFAULTVALUE
Variable Variable Variable Variable Variable
COLUMNS COLUMNS COLUMNS COLUMNS COLUMNS
156
Marker text COLUMN_COMMENT COLUMN_ID COLUMN_KEY_PART COLUMN_NULLABLE COLUMN_AUTO_INC COLUMN_CHARSET COLUMN_COLLATION COLUMN_IS_USERTYPE INDICES_LISTING
Type Variable Variable Variable Variable Variable Variable Variable Variable Section
Data Dictionary or Parent Dictionary COLUMNS COLUMNS COLUMNS (if detailed) COLUMNS (if detailed) COLUMNS (if detailed) COLUMNS (if detailed) COLUMNS (if detailed) COLUMNS (if detailed) TABLES
Corresponding data The column comment The column ID The column key type Can the column contain NULL values Does the column autoincrement The column character set The column collation Whether the column is a user type Marks the start and end of an INDICES_LISTING section; the INDICES_LISTING data dictionary becomes active in this section Marks the start and end of an INDICES section; the INDICES data dictionary becomes active in this section The index name Whether this is a primary key Whether this is a unique index The index type; for example, PRIMARY The index kind The index comment The index ID Marks the start and end of an INDEX_COLUMNS section; the INDEX_COLUMNS data dictionary becomes active in this section The index column name The index column order; for example, ascending, descending The index comment The index key-block size Marks the start and end of a REL_LISTING section; the
INDICES
Section
INDICES_LISTING
INDEX_NAME INDEX_PRIMARY INDEX_UNIQUE INDEX_TYPE INDEX_KIND INDEX_COMMENT INDEX_ID INDEX_COLUMNS
Variable Variable Variable Variable Variable Variable Variable Section
INDICES INDICES INDICES INDICES INDICES INDICES INDICES INDICES
INDEX_COLUMN_NAME INDEX_COLUMN_ORDER
Variable Variable
INDEX_COLUMNS INDEX_COLUMNS
INDEX_COLUMN_COMMENT Variable INDEX_KEY_BLOCK_SIZE REL_LISTING Variable Section
INDEX_COLUMNS INDEX_COLUMNS (if detailed) TABLES
157
Creating a Custom Template
Marker text
Type
Data Dictionary or Parent Dictionary
Corresponding data REL_LISTING data dictionary becomes active in this section
REL
Section
REL_LISTING
Marks the start and end of a REL section; the REL data dictionary becomes active in this section The relationship name The relationship type The relationship parent table The relationship child table The relationship cardinality Foreign key ID Marks the start and end of a FOREIGN_KEYS section; the FOREIGN_KEYS data dictionary becomes active in this section The foreign key delete rule The foreign key update rule Whether the foreign key is mandatory Marks the start and end of a TABLE_COMMENT_LISTING section; the TABLE_COMMENT_LISTING data dictionary becomes active in this section Marks the start and end of a DDL_LISTING section; the DDL_LISTING data dictionary becomes active in this section Display the DDL script of the currently active entity; for example, SCHEMATA, TABLES
REL_NAME REL_TYPE REL_PARENTTABLE REL_CHILDTABLE REL_CARD FOREIGN_KEY_ID FOREIGN_KEYS
Variable Variable Variable Variable Variable Variable Section
REL, FOREIGN_KEYS REL, FOREIGN_KEYS REL, FOREIGN_KEYS REL, FOREIGN_KEYS REL, FOREIGN_KEYS REL SCHEMATA
FK_DELETE_RULE FK_UPDATE_RULE FK_MANDATORY
Variable Variable Variable
FOREIGN_KEYS FOREIGN_KEYS FOREIGN_KEYS TABLES
TABLE_COMMENT_LISTING Section
TABLE_COMMENT DDL_LISTING
Variable Section
TABLE_COMMENT_LISTING The table comment TABLES
DDL_SCRIPT
Variable
DDL_LISTING
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.
158
For example, the following procedure describes how to make a custom template based on the Text Basic template. 1. 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. 2. Copy the Text_Basic.tpl folder. The copy can be given any suitable name; for example, Custom_Basic.tpl. 3. Edit the info.xml file to reflect your custom template. The unedited file in this case is shown here:
<?xml version="1.0"?> <data> <value type="object" struct-name="workbench.model.reporting.TemplateInfo" id="{BD6879ED-814C-4CA3-A869-9864F83B88DF}" struct-checksum="0xb46b524d"> <value type="string" key="description"> A basic TEXT report listing schemata and objects. </value> <value type="string" key="name">HTML Basic Frame Report</value> <value type="list" content-type="object" content-struct-name="workbench.model.reporting.TemplateStyleInfo" key="styles"> <value type="object" struct-name="workbench.model.reporting.TemplateStyleInfo" id="{7550655C-CD4B-4EB1-8FAB-AAEE49B2261E}" struct-checksum="0xab08451b"> <value type="string" key="description"> Designed to be viewed with a fixed sized font. </value> <value type="string" key="name">Fixed Size Font</value> <value type="string" key="previewImageFileName"> preview_basic.png </value> <value type="string" key="styleTagValue">fixed</value> </value> </value> <value type="string" key="mainFileName">report.txt</value> </value> </data>
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. 4. 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> SELECT UUID(); +--------------------------------------+ | UUID() | +--------------------------------------+ | 648f4240-7d7a-11e0-870b-89c43de3bd0a | +--------------------------------------+
Once you have the new GUID values, edit the info.xml file accordingly.
159
5. Edit the textual information for the TemplateInfo and TemplateStyleInfo objects to reflect the purpose of the custom template. 6. The modified file will now look something like the following:
<?xml version="1.0"?> <data> <value type="object" struct-name="workbench.model.reporting.TemplateInfo" id="{cac9ba3f-ee2a-49f0-b5f6-32580fab1640}" struct-checksum="0xb46b524d"> <value type="string" key="description"> Custom basic TEXT report listing schemata and objects. </value> <value type="string" key="name">Custom Basic text report</value> <value type="list" content-type="object" content-struct-name="workbench.model.reporting.TemplateStyleInfo" key="styles"> <value type="object" struct-name="workbench.model.reporting.TemplateStyleInfo" id="{39e3b767-a832-4016-8753-b4cb93aa2dd6}" struct-checksum="0xab08451b"> <value type="string" key="description"> Designed to be viewed with a fixed sized font. </value> <value type="string" key="name">Fixed Size Font</value> <value type="string" key="previewImageFileName">preview_basic.png</value> <value type="string" key="styleTagValue">fixed</value> </value> </value> <value type="string" key="mainFileName">custom_report.txt</value> </value> </data>
7. 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
160
This template shows details for all schemata in the model. 8. 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. 9. 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.
161
162
Chapter 8. Generating code overview

Table of Contents
8.1. Generating SQL queries ........................................................................................................... 163 8.2. Generating PHP code .............................................................................................................. 163 This document provides a quick hands-on introduction to using MySQL Workbench to generate code for later use, for either in or outside of MySQL Workbench.
8.1. Generating SQL queries

MySQL Workbench can be used to generate SQL, most typically as either INSERT or SELECT queries. Below are the most common methods to generated SQL statements in MySQL Workbench. Right-clicking on a table or column name within the schema view will offer many different SQL generating options. For example, right-clicking on a table name will allow creating "SELECT All", "INSERT", "UPDATE", "DELETE", and "CREATE" queries. And with the option to either send these queries to the system's clipboard, or to the SQL Editor window. Right-clicking on a field within a cell in the SQL Editor offers the "Copy Row Content" and "Copy Field Content" options, and includes the option to leave the chosen values unquoted. All of the MySQL Workbench Export options include the option to export as SQL.
8.2. Generating PHP code

MySQL Workbench can be used to generate PHP code with the bundled PHP plugin, by using the Plugins, Utilities, Copy as PHP Code menu option. Below is an example scenario for how to create PHP code. It is a SELECT statement, and optionally uses SET to set variables. SQL @variables will generate PHP variables in the code, which will then be bounded to the statement before execution. 1. Generate or type in the desired SQL query into the SQL editor. This example will use the sakila database, with the query being:
SET @last_update = '2006-02-14'; SELECT actor_id, first_name, last_name, last_update FROM actor WHERE last_update > @last_update;
2. While in the SQL editor, choose Plugins, Utilities, Copy as PHP Code (Iterate SELECT Results) from the main menu. This will copy PHP code to the clipboard. 3. Paste the code to the desired location. Additionally, PHP code that connects to the MySQL database can also be generated by choosing Plugins, Utilities, Copy as PHP Code (Connect to Server).
163
Generating PHP code
The generated code will look like this:

<?php $host $port $socket $user $password $dbname = = = = = = "localhost"; 3306; ""; "nobody"; ""; "sakila";
$con = new mysqli($host, $user, $password, $dbname, $port, $socket) or die ('Could not connect to the database server' . mysqli_connect_error()); //$con->close(); $query = "SELECT actor_id, first_name, last_name, last_update FROM actor WHERE last_update > ?"; $last_update = ''; $stmt->bind_param('s', $last_update); if ($stmt = $con->prepare($query)) { $stmt->execute(); $stmt->bind_result($actor_id, $first_name, $last_name, $last_update); while ($stmt->fetch()) { // printf("%s, %s, %s, %s\n", // $actor_id, $first_name, $last_name, $last_update); } $stmt->close(); } ?>
Note that the PHP code uses the mysqli PHP extension. This extension must be enabled in your PHP distribution for this code to work. For additional details, see MySQL Improved Extension (Mysqli).
164
Chapter 9. Server Administration

Table of Contents
9.1. 9.2. 9.3. 9.4. 9.5. 9.6. Server Administration ............................................................................................................... New Server Instance ................................................................................................................ Manage Data Import/Export ...................................................................................................... Manage Security ...................................................................................................................... Manage Server Instances ......................................................................................................... Creating and Managing Server Instances .................................................................................. 9.6.1. New Server Instance Wizard ......................................................................................... 9.6.2. Manage Server Instances Dialog ................................................................................... 9.7. Server Administration and Configuration ................................................................................... 9.7.1. The Startup Tab ............................................................................................................ 9.7.2. The Configuration Tab ................................................................................................... 9.7.3. The Accounts Tab ......................................................................................................... 9.7.4. The Connections Tab .................................................................................................... 9.7.5. The Variables Tab ......................................................................................................... 9.7.6. The Data Dump Tab ..................................................................................................... 9.7.7. The Logs Tab ............................................................................................................... 165 166 166 166 166 166 166 169 171 173 174 176 178 179 180 183
Since version 5.2.6, MySQL Workbench has included functionality for managing server instances. A server instance is created to provide a way of connecting to a server to be managed. The first step is to create a server instance if none exists, or to work with an existing server instance. MySQL Workbench also provides functionality to administer and configure a server using these server instances. Thus, the Server Administrator functionality can be broadly grouped into two main areas: Creating and managing server instances Administration and configuration functions using a server instance The Workspace section of the Home window has an area for Server Administration tasks. This section of the Workspace has the following action items: Server Administration Server Administration (icon) New Server Instance Manage Data Import/Export Manage Security Manage Server Instances The following sections describe each of these action items.
9.1. Server Administration

This action item enables you to quickly connect to a predefined server instance and carry out administration functions on the associated server. Clicking this item launches the Server Administration dialog, from which you can select the server instance to which you wish to connect. A new Admin tab will be launched, which displays the Server Status and Configuration.
165
New Server Instance
Server Administration (icon) If you have already created server instances, you can most quickly launch these by clicking the icon for the Server Instance you wish to access. A new Admin tab will be launched, which displays Server Status and Configuration. For further details, see Section 9.7, Server Administration and Configuration.
9.2. New Server Instance

This action item enables you to create a new server instance. A server instance is primarily a combination of connection and configuration details for a specific server that you wish to manage. When you click this item, a wizard is launched that enables you to specify the connection and various other configuration parameters. After completion of the wizard, a new Admin tab is launched, which displays Server Status and Configuration. For further details, see Section 9.6.1, New Server Instance Wizard.
9.3. Manage Data Import/Export

This action item enables you to create a dump file from a database, or restore data from a file to a live database. Clicking this item launches the Import/Export MySQL Data wizard. This enables you to select a server instance to connect to. For further details, see Section 9.7.6, The Data Dump Tab.
9.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 9.7.3, The Accounts Tab.
9.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 9.6, Creating and Managing Server Instances.
9.6. Creating and Managing Server Instances

Server instances can be created and managed from the Home page. To create new server instances, use one of these methods: Click the New Server Instance action item from the Server Administration section of the Home window. This launches the Create a new server instance wizard. For further details, see Section 9.6.1, New Server Instance Wizard. Click the Manage Server Instances action item from the Server Administration section of the Home window. This launches the Manage Server Instances dialog, from within which a new server instance can be created. For further details, see Section 9.6.2, Manage Server Instances Dialog.
9.6.1. New Server Instance Wizard

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

The Manage Server Instances dialog enables you to create, delete, and manage server instances. The Connection tab of the wizard enables you to select a predefined connection to use for connecting to a server to be managed. It is also possible to connect to a remote server using an SSH connection. Figure 9.1. Manage Server Instances Dialog
169
Manage Server Instances Dialog
The System Profile tab of the wizard enables you to specify server-specific information. This is achieved primarily through selecting a Profile Template. A Profile Template contains standard information used in managing the server instance. The following Profile Templates are available: Fedora Linux (MySQL Package) Fedora Linux (Vendor Package) FreeBSD (MySQL Package) Generic Linux (MySQL tar package) Mac OS X (MySQL Package) OpenSolaris (MySQL Package) RHEL (MySQL Package) SLES (MySQL Package) Ubuntu Linux (MySQL Package) Ubuntu Linux (Vendor Package) Windows (MySQL 5.0 Installer Package) Windows (MySQL 5.1 Installer Package) Windows (MySQL zip package) Custom After you select a profile, a number of default parameters will be set, including commands used to start and stop MySQL, commands to check server status, and the location of the my.ini or my.cnf configuration file.
170
Server Administration and Configuration
Figure 9.2. Manage Server Instances Dialog
After an instance has been created, it can be launched by double-clicking its icon in the Server Administration panel of the Home page. This creates an Admin page, which has two main panels, Server Status and Configuration. The Configuration panel features multiple tabs: Startup, Configuration, Accounts, Connections, Variables, Data Dump, and Logs.
9.7. Server Administration and Configuration

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
171
Server Administration and Configuration
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
172
The Startup Tab
Figure 9.3. MySQL Workbench - Admin Page
9.7.1. The Startup Tab

The Startup tab has several purposes: To display database server status To start up and shut down the server To display the Startup Message log To select whether the server starts when the system starts
173
The Configuration Tab
Figure 9.4. Administrator - Startup Tab
9.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
174
The Configuration Tab
Log Files Replication Networking Security Advanced
General Tab
Figure 9.5. Administrator - Configuration - General Tab
175
The Accounts Tab
Security Tab
Figure 9.6. Administrator - Configuration - Security Tab
As of MySQL Workbench 5.2.45, the Password Validation Plugin (available as of MySQL Server 5.6.6) is supported in Workbench. For information about what these settings mean, see The Password Validation Plugin.
9.7.3. The Accounts Tab

The Accounts tab has two subtabs: Server Access Management Schema Privileges Server Access Management enables you to list existing user accounts. You can also add and delete accounts. You can allocate administrative roles and also set account limits. Schema Privileges enables you to set specific privileges on a user basis.
176
The Accounts Tab
Figure 9.7. Administrator - Accounts Tab
Note In the current version of MySQL Workbench, it is not possible to manage privileges below the schema level. For example, it is not possible to view or manage grants at the table, column, or procedure level.
9.7.3.1. Administrative Roles

To aid in assigning privileges to MySQL Server users, MySQL Workbench introduces the concept of Administrative Roles. Roles are a quick way of granting a set of privileges to a user, based on the work the user must carry out on the server. It is also possible to assign multiple roles to a user. To assign roles, click the User Account you wish to modify, then click the Administrative Roles tab. Then click the check boxes
177
The Connections Tab
according to the roles you wish to allocate to the user. After you select a role to a user, you will see the accumulated privileges in the Global Privileges Assigned to User panel. For example, if you select the role BackupAdmin, the privileges granted include EVENT, LOCK TABLES, SELECT, SHOW DATABASES. If you also select the role of ReplicationAdmin, the list of privileges expands to include REPLICATION CLIENT, REPLICATION SLAVE and SUPER. These roles are available: DBA: Grants all privileges MaintenanceAdmin: Grants privileges to maintain the server ProcessAdmin: Grants privileges to monitor and kill user processes UserAdmin: Grants privileges to create users and reset passwords SecurityAdmin: Grants privileges to manage logins and grant and revoke server privileges MonitorAdmin: Grants privileges to monitor the server DBManager: Grants privileges to manage databases DBDesigner: Grants privileges to create and reverse engineer any database schema ReplicationAdmin: Grants privileges to set up and manage replication BackupAdmin: Grants privileges required to back up databases
9.7.4. The Connections Tab

The Connections tab lists all current connections to the monitored server.
178
The Variables Tab
Figure 9.8. Administrator - Connections Tab
9.7.5. The Variables Tab

The Variables tab displays a list of all server and status variables.
179
The Data Dump Tab
Figure 9.9. Administrator - Variables Tab
9.7.6. The Data Dump Tab

The Import/Export Server Data tab enables you to create a dump file, or restore data from a dump file. Clicking the Import/Export Server Data action item launches a new Admin page, at the Data Dump tab. Within the Data Dump tab are three further tabbed windows: Export to Disk Import from Disk Advanced Options
180
The Data Dump Tab
9.7.6.1. Export to Disk

The Export to Disk tab enables you to select the schema and tables to export. You also have the option to export tables to their own files, or all tables to a single file. Exporting tables to individual files enables you to restore on a per-table basis. Figure 9.10. Administrator - Export to Disk
9.7.6.2. Import from Disk

The Import from Disk tab enables you to import a previously exported project. You can select to import a project where tables were stored in individual files. In this case, you will also be able to select which of these tables to import. You can also import a project saved to a single file.
181
The Data Dump Tab
Figure 9.11. Administrator - Import from Disk
9.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.
182
The Logs Tab
Figure 9.12. Administrator - Advanced Options
9.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.
183
The Logs Tab
Figure 9.13. Administrator - Logs Tab
184
Chapter 10. Database Migration Wizard

Table of Contents
10.1. General installation requirements ............................................................................................ 10.1.1. ODBC Libraries ........................................................................................................... 10.1.2. ODBC Drivers ............................................................................................................. 10.2. Migration Overview ................................................................................................................. 10.2.1. A visual guide to performing a database migration ........................................................ 10.2.2. Migrating from supported databases ............................................................................. 10.2.3. Migrating from unsupported (generic) databases ........................................................... 10.3. Conceptual DBMS equivalents ................................................................................................ 10.4. Microsoft SQL Server migration .............................................................................................. 10.4.1. Preparations ................................................................................................................ 10.4.2. Drivers ........................................................................................................................ 10.4.3. Connection Setup ........................................................................................................ 10.4.4. Microsoft SQL Server Type Mapping ............................................................................ 10.5. PostgreSQL migration ............................................................................................................ 10.5.1. Preparations ................................................................................................................ 10.5.2. Drivers ........................................................................................................................ 10.5.3. Connection Setup ........................................................................................................ 10.5.4. PostgreSQL Type Mapping .......................................................................................... 10.6. MySQL migration ................................................................................................................... 10.7. Using the MySQL Workbench Migration Wizard ....................................................................... 10.7.1. Connecting to the databases ....................................................................................... 10.7.2. Schemata Retrieval and Selection ................................................................................ 10.7.3. Reverse Engineering ................................................................................................... 10.7.4. Object Selection .......................................................................................................... 10.7.5. Migration ..................................................................................................................... 10.7.6. Manual Editing ............................................................................................................ 10.7.7. Target Creation Options .............................................................................................. 10.7.8. Schema Creation ......................................................................................................... 10.7.9. Create Target Results ................................................................................................. 10.7.10. Data Migration Setup ................................................................................................. 10.7.11. Bulk Data Transfer .................................................................................................... 10.7.12. Migration Report ........................................................................................................ 10.8. MySQL Workbench Migration Wizard FAQ .............................................................................. MySQL Workbench provides the ability to migrate ODBC compliant databases to MySQL. The MySQL Workbench Migration Wizard was added in MySQL Workbench 5.2.41. Convert (migrate) different database types, including MySQL, across servers Convert tables and copy data, but will not convert stored procedures, views, or triggers Allows customization and editing during the migration process Works on Linux, Mac OS X, and Microsoft Windows This is not an exhaustive list. The following sections discuss these and additional migration capabilities. Set up may be the most challenging aspect of using the MySQL Workbench Migration Wizard. There is the installation section, which describes setting up ODBC requirements for Linux, Mac OS X, and Microsoft 186 186 187 187 188 202 203 203 205 205 205 207 207 208 208 208 209 209 210 210 210 211 211 211 211 211 211 212 212 212 212 212 212
185
General installation requirements
Windows, and the Database Product Specific Notes section that references setup conditions for each RDBMS.
10.1. General installation requirements

The MySQL Workbench Migration Wizard uses ODBC to connect to a source database, except for MySQL. You will need the ODBC driver installed that corresponds to the database you want to migrate from. For example, PostgreSQL can be migrated with the psqlodbc ODBC driver; Microsoft SQL Server can be migrated using the native Microsoft SQL Server driver on Windows or with FreeTDS on Linux and Mac OS X. The following diagram shows the general components involved in an ODBC connection: Figure 10.1. MySQL Workbench migration installation diagram
When specifying the source RDBMS, you can either use a data source configured externally, or provide the individual connection parameters to MySQL Workbench. If you already have an ODBC Data Source configured in your system, then you can use that in MySQL Workbench.
10.1.1. ODBC Libraries

Note This section may be skipped when using a MySQL Workbench binary that is provided by Oracle. An ODBC Driver Manager library must be present. Both Windows and Mac OS X provides one.
Linux
iODBC: MySQL Workbench binaries provided by Oracle already include iODBC and no additional action is required. If you compile it yourself, you must install iODBC or unixODBC. iODBC is recommended. You can use the iODBC library provided by your distribution. pyodbc: is the Python module used by MySQL Workbench to interface with ODBC, and may be used to migrate ODBC compliant databases such as PostgreSQL and DB2. In Windows and Mac OS X, it is included with Workbench. In Linux, binaries provided by Oracle also include pyodbc.
186
ODBC Drivers
If you're using a self-compiled binary, make sure you have the latest version, and that it is compiled against the ODBC manager library that you chose, whether it is iODBC or unixODBC. As of version 3.0.6, pyodbc will compile against unixODBC by default. If you are compiling against iODBC then you must perform the following steps: 1. Install the development files for iODBC. Usually you just need to install the libiodbc-devel or libiodbc2-dev package provided by your distribution. 2. In the pyodbc source directory, edit the setup.py file and around line 157, replace the following line: settings['libraries'].append('odbc') with settings['libraries'].append('iodbc') 3. Execute the following command as the root user: CFLAGS=ìodbc-config --cflags` LDFLAGS=ìodbc-config --libs` python setup.py install
10.1.2. ODBC Drivers

For each RDBMS, you need its corresponding ODBC driver, which must also be installed on the same machine that MySQL Workbench is running on. This driver is usually provided by the RDBMS manufacturer, but in some cases they can also be provided by third party vendors or open source projects. Operating systems usually provide a graphical interface to help set up ODBC drivers and data sources. Use that to install the driver (i.e., make the ODBC Manager "see" a newly installed ODBC driver). You can also use it to create a data source for a specific database instance, to be connected using a previously configured driver. Typically you need to provide a name for the data source (the DSN), in addition to the database server IP, port, username, and sometimes the database the user has access to. If MySQL Workbench is able to locate an ODBC manager GUI for your system, a Plugins, Start ODBC Administrator menu item be present under the Plugins menu as a convenience shortcut to start it. Linux: There are a few GUI utilities, some of which are included with unixODBC. Refer to the documentation for your distribution. iODBC provides iodbcadm-gtk. Official binaries of MySQL Workbench include it and it can be accessed through the Plugins, Start ODBC Administrator menu item. Mac OS X: You can use the ODBC Administrator tool, which is provided as a separate download from Apple. If the tool is installed in the /Applications/Utilities folder, you can start it through the Plugins, Start ODBC Administrator menu item. Microsoft Windows: You can use the Data Sources (ODBC) tool under Administrative Tools. And it can be started through the Plugins, Start ODBC Administrator menu item. ODBC Driver architecture Since the ODBC driver needs to be installed in the client side, you will need an ODBC driver that supports your clients operating system and architecture. For example, if you are running MySQL Workbench from Linux x64, then you need a Linux x64 ODBC driver for your RDBMS. In Mac OS X, MySQL Workbench is built as a 32-bit application, so you need the 32-bit drivers.
10.2. Migration Overview

The Migration Wizard performs the following steps when migrating a database to MySQL: 1. Connects to the source RDBMS and retrieves a list of available databases/schemas. 2. Reverse engineers selected database/schemas into a internal representation specific to the source RDBMS. This step will also perform the renaming of objects/schemas depending on the type of object name mapping method that is chosen.
187
A visual guide to performing a database migration
3. Automatically migrates the source RDBMS objects into MySQL specific objects. a. Target schema objects are created. b. Target table objects are created. i. Columns for each table are copied. A. Datatypes are mapped to MySQL datatypes. B. Default values are mapped to a MySQL supported default value, if possible. ii. Indexes are converted. iii. Primary Keys are converted. iv. Triggers are copied, and commented out if the source is not MySQL. c. Foreign Keys for all tables (of all schemas) are converted. d. View objects are copied, and commented out if the source is not MySQL. e. Stored Procedure and Function objects are copied, and commented out if the source is not MySQL. 4. Provides an opportunity to review the changes, for editing and correcting errors in the migrated objects. 5. Creates the migrated objects in the target MySQL server. If there are errors, you can return to the previous step and correct them, and retry the target creation. 6. Copy data of the migrated tables from the source RDBMS to MySQL. MySQL Workbench provides support for migrating from some specific RDBMS products. The Migration Wizard will provide the best results when migrating from such products. However, in some cases, other unsupported database products can also be migrated by using its Generic database support, as long as you have an ODBC driver for it. In this case, the migration will be less automatic, but should still work nonetheless.
10.2.1. A visual guide to performing a database migration

This example will migrate a Microsoft SQL Server database to MySQL, and include a screenshot for each step. From MySQL Workbench, choose Database, Migrate to open the migration wizard. The opening screen will look like this:
188
Overview
Figure 10.2. MySQL Workbench migration: Overview
It describes the prerequisites and requirements that should be understood before proceeding further. The Open ODBC Administrator option will load odbcad32.exe, and is used to confirm that the ODBC Driver for SQL Server is installed, and to make configuration changes if needed. Click Start Migration to continue.
Source Selection
The source is the RDBMS that will be migrated to MySQL. Define the connection parameters and related information here by first choosing the Database System, as the other parameters will change accordingly to this choice.
189
Figure 10.3. MySQL Workbench migration: Source Selection (Parameters)
The optional Store connection option will save the connection details. It must be set before proceeding to the next step by clicking Next.
Target Selection
The target is the MySQL database that will contain the newly migrated database. The current Workbench MySQL connections will be available here, or you can choose Manage DB Connections to create a new connection.
190
Figure 10.4. MySQL Workbench migration: Target selection
Fetch Schemata List

The Schemata list is retrieved from both the source and target RDBMS. This is an automated and informational step that reports connection related errors and/or general log information. Press Next to continue.
191
Figure 10.5. MySQL Workbench migration: Fetch Schemata List
Schemata Selection
Choose the schemata you want to migrate. "Schema Name Mapping Method" options while migrating Microsoft SQL Server: Keep schemata as they are: Catalog.Schema.Table -> Schema.Table: This will create multiple databases, one per schema. Only one schema: Catalog.Schema.Table -> Catalog.Table: Merges each schema into a single database. Only one schema, keep current schema names as a prefix: Catalog.Schema.Table -> Catalog.Schema_table: Preserves the schema name as a prefix.
192
Figure 10.6. MySQL Workbench migration: Schemata Selection
Reverse Engineer Source

The source metadata is fetched from the source RDBMS, and reverse engineered. This is an automated and informational step that reports related errors and/or general log information. View the logs and then press Next to continue.
193
Figure 10.7. MySQL Workbench migration: Reverse Engineer Source
Source Objects
The discovered objects from the Reverse Engineer Source stage are revealed and made available. This includes Table, View, and Routine objects, with only the Table objects being selected by default.
194
Figure 10.8. MySQL Workbench migration: Source Objects
Migration
The migration process now converts the selected objects into MySQL compatible objects. View the logs and then proceed.
195
Figure 10.9. MySQL Workbench migration: Migration
Manual Editing
There are three sections to edit here, which are selected via the View select box on the top right. The Show Code and Messages button is available with every view, and it will show the generated MySQL code that corresponds to the selected object. Migration Problems: This will either report problems or display "No mapping problems found." It is an informational screen. All Objects: An object view that allows you to view and edit the object definitions. Double-click on a row to modify a target objects name. Column Mappings: Shows all of the table column mappings, and allows you to individually review and fix the mapping for all column types, default values, and other attributes.
196
Figure 10.10. MySQL Workbench migration: Manual Editing (All Objects)
Figure 10.11. MySQL Workbench migration: Manual Editing (Column Mappings)
Target Creation Options

The schema may be created by either adding it to the target RDBMS, creating an SQL script file, or both.
197
Figure 10.12. MySQL Workbench migration: Target Creation Options
Create Schemata
Now the schemata is created. The complete log is also available here. Figure 10.13. MySQL Workbench migration: Create Schemata
198
Create Target Results

The generated objects are listed here, along with the error messages if any exist. The migration code may also be viewed and edited here. To make changes, select an object, edit the query code, and press Apply. Repeat this process for each object that will be edited. And then, press Recreate Objects to save the results. Note The Recreate Objects operation is required to save any changes here. It will then execute the previous migration step (Create Schemata) with the modified code, and then continue the migration process. This also means that the previously saved schema will be dropped. Figure 10.14. MySQL Workbench migration: Create Target Results
Data Transfer Setup

The next steps involve transferring data from the source RDBMS to the target MySQL database. The setup screen includes the following options: Data Copy: Online copy of table data to target RDBMS: This (default) will copy the data to the target RDBMS. Create a batch file to copy the data at another time: The data may also be dumped to a file that can be executed at a later time, or be used as a backup. Options:
199
Truncate target tables before copying data: In case the target database already exists, this will delete said data. Worker tasks: The default value is 2. This is the number of tasks (database connections) used while copying the data. Enable debug output for table copy: Shows debugging information. Figure 10.15. MySQL Workbench migration: Data Transfer Setup
Bulk Data Transfer

And now the data is transferred to the target RDBMS. Optionally, view the logs to confirm.
200
Figure 10.16. MySQL Workbench migration: Bulk Data Transfer
Migration Report
And finally, the migration report is available and summarizes the entire migration process.
201
Migrating from supported databases
Figure 10.17. MySQL Workbench migration: Migration Report
Pressing Finish will close the migration window. The database may now be viewed within the MySQL Workbench SQL editor. Note If a MySQL Workbench SQL Editor tab is already opened, then the schema list within the Object Browser must be refreshed in order to view the newly imported schema.
10.2.2. Migrating from supported databases

When a supported RDBMS product is being migrated, the MySQL Workbench Migration Wizard will automatically convert as much information as it can, but you may still be required to manually edit the automatically migrated schema for difficult cases, or when the default mapping is not as desired. Generally speaking, only table information and its data are automatically converted to MySQL. Code objects such as views, stored procedures, and triggers, are not. But supported RDBMS products will be retrieved and displayed in the wizard. You can then manually convert them, or save them for converting at a later time. The following RDBMS products and versions are currently tested and supported by the MySQL Workbench Migration Wizard, although other RDBMS products can also be migrated with Section 10.2.3, Migrating from unsupported (generic) databases Microsoft SQL Server 2000 Microsoft SQL Server 2005 Microsoft SQL Server 2008
202
Migrating from unsupported (generic) databases
Microsoft SQL Server 2012 MySQL Server 4.1 and greater as the source, and MySQL Server 5.1 and greater as the target PostgreSQL 8.0 and greater Sybase Adaptive Server Enterprise 15.x and greater
10.2.3. Migrating from unsupported (generic) databases

Most ODBC compliant databases may be migrated using the generic database support. In this case, code objects will not be retrieved from the source database; only tables and data. When using the generic support, column datatypes are mapped using the following steps: 1. It searches for the first entry in the Generic Datatype Mapping Table for the source type name. If the length/scale ranges of the entry matches the source column, it will pick that type. Otherwise, it continues searching. 2. If no matches were found in the generic table, then it tries to directly map the source type to a MySQL type of the same name. 3. If the source type name doesn't match any of the MySQL datatypes, thenit will not be converted and an error is logged. You can then manually specify the target datatype in the Manual Object Editing step of the wizard.
10.3. Conceptual DBMS equivalents

Table 10.1. Conceptual equivalents between supported DBMS products and MySQL Concept Authentication Auto_Increment Backup Catalog MS SQL Sybase Server ASE Yes Yes Yes Yes Yes Yes Yes Yes PostgreSQL MySQL Yes Yes Yes Yes Yes Yes Yes N/A PostgreSQL uses sequences for Auto_Increment. See MySQL Enterprise Backup You can map a catalog into a schema and drop the , use the owner as the schema name or merge the owner and object name together. ownerobject Note
Constraints Data Dictionary Database Database Instance Dump Events Foreign Keys Full Text Search Index
Yes Yes Yes Yes Yes Yes Yes
Yes N/A Yes Yes Yes Yes Yes Yes In InnoDB as of MySQL Server 5.6, and in all versions of MyISAM mysqldump
203
Conceptual DBMS equivalents
Concept Information Schema Object Names Case Sensitivity
MS SQL Sybase Server ASE Yes No
PostgreSQL MySQL Yes Yes Mixed
Note
Depends Depends Mixed on on collation collation
MySQL: sensitivity of database, table, and trigger names OS dependent; other object names are case insensitive. PostgreSQL: as specified in the SQL-99 standard, unquoted object names are treated as case insensitive while quoted object names are case sensitive. Unlike the standard, unquoted object names are converted to lowercase instead of uppercase.
Object Naming Conventions Packages Partitioning Performance Schema Permissions Primary Key Referential Integrity Replication Role Schema
Yes N/A Yes N/A Yes Yes Yes Yes Yes Yes
Yes N/A Yes N/A Yes Yes Yes Yes Yes Yes*
Yes N/A Yes Yes Yes Yes Yes Yes Yes Yes
Yes N/A Yes Yes Yes Yes Yes Yes N/A Yes Roles are not available in MySQL at the database level. Equivalent to database in MySQL. Sybase ASE: Schemata corresponds to user names. Standalone sequence objects are not supported in MySQL. Similar functionality can be obtained with IDENTITY columns in MSSQL and AUTO_INCREMENT columns in MySQL SET_ANSI_* in MSSQL PostgreSQL itself supports and uses only one storage engine (Postgresql). Other companies have added extra storage engines to PostgreSQL. Sybase ASE: referential integrity only through triggers.
Sequences
Yes*
Yes*
Yes
Yes*
SQL Modes Storage Engines
Yes N/A N/A
Yes Yes*
Yes Yes
Stored Procedures Synonyms Table Tablespace
Yes N/A Yes Yes
Yes N/A Yes Yes*
Yes N/A Yes Yes
Yes N/A Yes N/A MSSQL groups tables in schemata (unless referring to CREATE
204
Microsoft SQL Server migration
Concept
MS SQL Sybase Server ASE
PostgreSQL MySQL
Note TABLESPACE). Sybase ASE: tables are grouped in schemata which are more like user names.
Temporary Tables Transactions Triggers UDFs Unicode Unique Key User Views
Yes Yes Yes Yes Yes Yes Yes Yes
Handling Microsoft SQL Server and MySQL structural differences A Microsoft SQL Server database is made up of one catalog and one or more schemata. MySQL only supports one schema for each database (or rather, a MySQL database is a schema) so this difference in design must be planned for. The Migration Wizard must know how to handle the migration of schemata for the source (Microsoft SQL Server) database. It can either keep all of the schemata as they are (the Migration Wizard will create one database per schema), or merge them into a single MySQL database. Additional configure options include: either remove the schema names (the Migration Wizard will handle the possible name collisions that may appear along the way), and an option to add the schema name to the database object names as a prefix.
10.4. Microsoft SQL Server migration

Introduction. The MySQL Workbench Migration Wizard is tested against the following Microsoft SQL Server versions: 2000, 2005, 2008, and 2012.
10.4.1. Preparations
To be able to migrate from Microsoft SQL Server, ensure the following: The source SQL Server instance is running, and accepts TCP connections You know the IP and port of the source SQL server instance. If you will be migrating using a Microsoft ODBC driver for SQL Server (the default in Windows), you will need to know the host and the name of the SQL Server instance. Make sure that the SQL Server is reachable from where you will be running MySQL Workbench. More specifically, check the firewall settings. Make sure that the account you will use has proper privileges to the database that will be migrated.
10.4.2. Drivers
General thoughts on the topic.
205
Drivers
10.4.2.1. Windows
Microsoft Windows XP or newer includes an ODBC driver for Microsoft SQL Server, so there are no additional actions required.
10.4.2.2. Linux
Setting up drivers on Linux.
FreeTDS
FreeTDS version 0.92 or greater is required. Note that many distributions ship older versions of FreeTDS, so it may need to be installed separately. Additionally, the FreeTDS version provided by distributions may also be compiled for the wrong ODBC library (usually to unixODBC instead of iODBC, which MySQL Workbench uses). Because of that you will probably need to build this library yourself. Important: using FreeTDS with iODBC When compiling FreeTDS for use with iODBC (the default with the official binaries), you must compile it with the --enable-odbc-wide command line option for the configure script. Failing to do so will result in crashes and other unpredictable errors. A script is provided to compile FreeTDS using the options required for MySQL Workbench You can find it in the /usr/share/mysql-workbench/extras/build_freetds.sh directory in Linux or MySQLWorkbench.app/Contents/SharedSupport/build_freetds.sh folder in the Mac. To use it, follow these steps: 1. Make sure you have the iODBC headers installed. In Linux, install the libiodbc-devel or libiodbc2-dev package from your distribution. In Mac OS X, the headers come with the system and no additional action is required for this step. 2. mkdir ~/freetds to create a directory - within the users home directory. 3. Copy the build_freetds.sh script to ~/freetds 4. Get the latest FreeTDS sources from ftp://ftp.freetds.org/pub/freetds/ and place it in the ~/freetds directory. Make sure to get version 0.92 or newer. 5. cd ~/freetds 6. Execute build_freetds.sh 7. After compilation is done, install it using make install from the path given by the script. 8. Install the driver in the ODBC Administrator, to make the ODBC subsystem to recognize it. The name of the driver file is libtdsodbc.so and is located in /usr/lib or /usr/local/lib Once the driver is installed, you should be able to create data sources for it from the ODBC Administrator GUI. Protocol version selection in FreeTDS When using FreeTDS, TDS_VERSION=7.0 is needed in the connection string. If you pick a FreeTDS specific connection method option in the connection dialog, that option is added to the connection string automatically. 206
Connection Setup
10.4.2.3. Mac OS X
See the FreeTDS setup notes for Linux.
10.4.3. Connection Setup

Using an ODBC DataSource Using Connection Parameters
10.4.4. Microsoft SQL Server Type Mapping

Table 10.2. Type mapping Source Type INT TINYINT SMALLINT BIGINT BIT FLOAT REAL NUMERIC DECIMAL MONEY SMALLMONEY CHAR MySQL Type INT TINYINT SMALLINT BIGINT TINYINT(1) FLOAT FLOAT DECIMAL DECIMAL DECIMAL DECIMAL CHAR/LONGTEXT Depending on its length. MySQL Server 5.5 and above can have CHAR columns with a length up to 255 characters. Anything larger is migrated as LONGTEXT Depending on its length. MySQL Server 5.5 and above can have VARCHAR columns with a length up to 65535 characters. Anything larger is migrated to one of the TEXT blob types. In MySQL, character set of strings depend on the column character set instead of the datatype. Depending on its length. MySQL Server 5.5 and above can have VARCHAR columns with a length up to 65535 characters. Anything larger is migrated to one of the TEXT blob types. Depending on its length. MySQL Server 5.5 and above can have VARCHAR columns with a length up to 65535 characters. Anything larger is migrated to one of the TEXT blob types. In MySQL, character set of strings depend on the column character set instead of the datatype. Precision value is used for storage size in both UNSIGNED flag set in MySQL Comment
NCHAR
CHAR/LONGTEXT
VARCHAR
VARCHAR/ MEDIUMTEXT/ LONGTEXT VARCHAR/ MEDIUMTEXT/ LONGTEXT
NVARCHAR
DATE DATETIME
DATE DATETIME
207
PostgreSQL migration
Source Type DATETIME2
MySQL Type DATETIME
Comment Date range in MySQL is '1000-01-01 00:00:00' to '9999-12-31 23:59:59'. Note: fractional second values are only stored as of MySQL Server 5.6.4
SMALLDATETIME DATETIMEOFFSET TIME TIMESTAMP ROWVERSION BINARY VARBINARY
DATETIME DATETIME TIME TIMESTAMP TIMESTAMP BINARY/MEDIUMBLOB/ Depending on its length LONGBLOB VARBINARY/ MEDIUMBLOB/ LONGBLOB VARCHAR/ MEDIUMTEXT/ LONGTEXT VARCHAR/ MEDIUMTEXT/ LONGTEXT TINYBLOB/ MEDIUMBLOB/ LONGBLOB not migrated not migrated not migrated VARCHAR(64) VARCHAR(160) TEXT Depending on its length
TEXT
Depending on its length
NTEXT
IMAGE
SQL_VARIANT TABLE HIERARCHYID UNIQUEIDENTIFIER SYSNAME XML
There is not specific support for this datatype. There is not specific support for this datatype. There is not specific support for this datatype. A unique flag set in MySQL. There is not specific support for inserting unique identifier values.
10.5. PostgreSQL migration

Native support for PostgreSQL 8.x and 9.x was added in MySQL Workbench 5.2.44. MySQL Workbench versions prior to this would migrate PostgreSQL using the generic migration support.
10.5.1. Preparations
What is required and needed. General information about the setup.
10.5.2. Drivers
General thoughts on the topic. Information specific to the psqlodb driver. If you are compiling psqlodb, first configure with the --without-libpq option.
208
Connection Setup
10.5.3. Connection Setup

Using an ODBC DataSource Using Connection Parameters
10.5.4. PostgreSQL Type Mapping

Table 10.3. Type mapping Source Type INT SMALLINT BIGINT SERIAL SMALLSERIAL BIGSERIAL BIT BOOLEAN REAL DOUBLE PRECISION NUMERIC DECIMAL MONEY CHAR MySQL Type INT SMALLINT BIGINT INT SMALLINT BIGINT BIT TINYINT(1) FLOAT DOUBLE DECIMAL DECIMAL DECIMAL(19,2) CHAR/LONGTEXT Depending on its length. MySQL Server 5.5 and above can have CHAR columns with a length up to 255 characters. Anything larger is migrated as LONGTEXT Depending on its length. MySQL Server 5.5 and above can have VARCHAR columns with a length up to 65535 characters. Anything larger is migrated to one of the TEXT blob types. In MySQL, character set of strings depend on the column character set instead of the datatype. Depending on its length. MySQL Server 5.5 and above can have VARCHAR columns with a length up to 65535 characters. Anything larger is migrated to one of the TEXT blob types. Depending on its length. MySQL Server 5.5 and above can have VARCHAR columns with a length up to 65535 characters. Anything larger is migrated to one of the TEXT blob types. In MySQL, character set of strings depend on the column character set instead of the datatype. Sets AUTO_INCREMENT in its table definition. Sets AUTO_INCREMENT in its table definition. Sets AUTO_INCREMENT in its table definition. Comment
NATIONAL CHARACTER
CHAR/LONGTEXT
VARCHAR
VARCHAR/ MEDIUMTEXT/ LONGTEXT
NATIONAL VARCHAR/ CHARACTER VARYING MEDIUMTEXT/ LONGTEXT
DATE TIME TIMESTAMP
DATE TIME DATETIME
209
MySQL migration
Source Type INTERVAL BYTEA TEXT CIDR INET MACADDR UUID XML JSON TSVECTOR TSQUERY ARRAY POINT LINE LSEG BOX PATH POLYGON CIRCLE TXID_SNAPSHOT
MySQL Type TIME LONGBLOB LONGTEXT VARCHAR(43) VARCHAR(43) VARCHAR(17) VARCHAR(36) LONGTEXT LONGTEXT LONGTEXT LONGTEXT LONGTEXT VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR
Comment
10.6. MySQL migration

Introduction Notes about copying MySQL, and what you can do with it.
10.7. Using the MySQL Workbench Migration Wizard

Introduction, and general usage notes.
10.7.1. Connecting to the databases

A connection is made to the source and target database servers.
Source Connection Setup

The Source Connection offers the MySQL, Microsoft SQL Server, and Generic RDBMS database system options. This selection determins the available Parameters and Advanced configuration options. This connection definition may be saved using the Store connection for future use as option, and there is also the Test Connection option.
Target Connection Setup

The MySQL Server that will be home to the newly migrated database.
210
Schemata Retrieval and Selection
10.7.2. Schemata Retrieval and Selection

General thoughts.
Fetch Schemata List

The names of available schemas will be retrieved from the source RDBMS. The account used for the connection will need to have appropriate privileges for listing and reading the schemas you want to migrate. Target RDBMS connection settings will also be validated. The steps that are performed include: connects to the source DBMS, checks the connection, and retrieves the schema list from the source.
Schemata Selection
Select the schemata that you want to migrate.
10.7.3. Reverse Engineering

This is an automated step, where the actions include: Connect to the source DBMS, Reverse engineer the selected schemata, and perform post-processing if needed.
10.7.4. Object Selection

By default, all table objects will be migrated. Use the Show Selection button in order to disable individual table objects from being migrated.
10.7.5. Migration
Reverse engineered objects from the source RDBMS will be automatically converted to MySQL compatible objects. Default datatype and default column value mappings will be used. You will be able to review and edit the generated objects and column definitions in the next step, which is Section 10.7.6, Manual Editing . The steps performed include Migrating the selected objects, and generating the SQL CREATE statements.
10.7.6. Manual Editing

The migrated objects may be reviewed and edited here. You can manually edit the generated SQL before applying them to the target database. Target schemas and tables may be renamed, and column definitions may be changed, by double-clicking on them. By default, the All Objects View is loaded. Other View options include Migration Problems and Column Mappings. All Objects: Shows all objects, which can also be edited by double-clicking. Migration Problem: Will list all of the migration problems, or report that no mapping problems were found. Column Mappings: Displays all of the schema columns, which may also be edited. There is an advanced Show Code and Messages option that displays the SQL CREATE script for the selected object.
10.7.7. Target Creation Options

Defines addition settings for the target schema.
211
Schema Creation
Configuration options include: Create schema in target RDBMS: Create a SQL script file: An option to keep the schemata if they already exist. Objects that already exist will not be recreated or update.
10.7.8. Schema Creation

The SQL scripts generated for the migrated schema objects will now be executed in the target database. You can monitor execution in the logs, if errors exist then they will be fixed in the next step. Table data will be migrated in a later step as well. This is an automated step, where the actions include: Create Script File, Connect to Target Database, and Create Schemata and Objects.
10.7.9. Create Target Results

Scripts to create the target schemas were executed, but the data has not yet been migrated. This step allows reviewing a creation report. If there are any errors, then you can manually fix the scripts and click Recreate Objects to retry the schema creation or return to the Manual Editing page to correct them there, and then retry the target creation. To edit, first select the object, and then the SQL CREATE Script will be shown for the selected object. Edit it there, then press Apply to save.
10.7.10. Data Migration Setup

Provides additional options for data transfer, including the ability to set up a script to automate this transfer in the future.
10.7.11. Bulk Data Transfer

The transfer is executed here.
10.7.12. Migration Report

Displays the final report, that can be reviewed to ensure a proper migration was executed.
10.8. MySQL Workbench Migration Wizard FAQ

Frequently Asked Questions with answers. Questions 10.8.1: [212] While using the Postgresql psqlodbc driver, I see the following error: ('08001', '[08001] Already connected. (202) (SQLDriverConnect)') Questions and Answers 10.8.1: While using the Postgresql psqlodbc driver, I see the following error: ('08001', '[08001] Already connected. (202) (SQLDriverConnect)') This means that PostgreSQL is not configured to accept connections from the source IP.
212
Chapter 11. Extending Workbench

Table of Contents
11.1. 11.2. 11.3. 11.4. 11.5. GRT and Workbench Data Organization ................................................................................. Modules ................................................................................................................................. Plugins .................................................................................................................................. Adding a GUI to a Plugin Using MForms ................................................................................. The Workbench Scripting Shell ............................................................................................... 11.5.1. Exploring the Workbench Scripting Shell ...................................................................... 11.5.2. The Shell Window ....................................................................................................... 11.5.3. The Files, Globals, Classes, and Modules Tabs ............................................................ 11.6. Tutorial: Writing Plugins .......................................................................................................... 213 214 215 216 217 217 218 219 220
MySQL Workbench provides an extension and scripting system that enables the developer to extend MySQL Workbench capabilities. While the core of MySQL Workbench is developed using C++, it is possible to harness this core functionality using both the Lua and Python scripting languages. MySQL Workbench also provides access to a cross-platform GUI library, MForms, which enables the creation of extensions that feature a graphical user interface. The extension system enables the following capabilities: Automate common tasks Extend the Workbench user-interface Create plugins (code which can be invoked from the Workbench menu system) Manipulate schemata Create custom Workbench features
11.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 preregistered 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)
213
Modules
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 modifying 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 Table 11.1. The main nodes in the Application Object Tree Node wb.registry wb.customData Description Application data such as plugin registry, list of editors, and options. 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). Contains some default options that are used by Workbench. Internal registry of supported RDBMS modules, known data types. The currently loaded model document. The currently loaded model object, containing the database catalog and diagrams. The database catalog for the model. Contains the list of schemata. List of schemata in the model. Individual schema can be accessed as a list: schemata[0], schemata[1] ... Lists of tables, views, routines in the schema. List of EER diagrams in the model. List of figures, layers, connections (relationships) in the diagram.
wb.options wb.rdbmsMgmt wb.doc wb.doc.physicalModels[0] wb.doc.physicalModels[0].catalog wb.doc.physicalModels[0]catalog.schemata
wb.doc.physicalModels[0].catalog.schemata[0].tables (.views, .routines, ...) wb.doc.physicalModels[0].diagrams wb.doc.physicalModels[0].diagrams[0].figures (.layers, .connections, ...)
11.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: 1. 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.
214
Plugins
2. The source file name must have the extension _grt.py; for example, my_module_grt.py. 3. 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')
4. 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, <type-or-class>). 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
11.3. Plugins
Plugins are special Modules that are exposed to the user through the Workbench GUI. This is typically done using the main menu, or the context-sensitive menu. Much of the MySQL Workbench functionality is implemented using plugins; for example, table, view, and routine editors are native C++ plugins, as are the forward and reverse engineering wizards. The Administrator facility in MySQL Workbench is implemented entirely as a plugin in Python. A plugin can be a simple function that performs some action on an input, and ends without further interaction with the user. Examples of this include auto-arranging a diagram, or making batch changes to
215
Adding a GUI to a Plugin Using MForms
objects. To create a simple plugin, the function must be located in a module and declared as a plugin using the plugin decorator of the ModuleInfo object. Plugins can have an indefinite runtime, such as when they are driven by the user through a graphical user interface. This is the case for the various object editors and wizards within MySQL Workbench. Although this latter type of plugin must be declared in the usual way, only the entry point of the plugin will need to be executed in the plugin function, as most of the additional functionality will be invoked as a result of the user interacting with the GUI. Note Reloading a plugin requires MySQL Workbench to be restarted. Declare a plugin using this syntax:
@ModuleInfo.plugin(plugin_name, caption, [input], [groups], [pluginMenu])
These parameters are defined as follows: plugin_name: A unique name for the plugin. It may contain only alphanumeric characters, dots, and underscores. caption: A caption to use for the plugin in menus. input: An optional list of input arguments. groups: Optional list of groups the plugin belongs to. Recognized values are: Overview/Utility: The Context menu in the Model Overview. Model/Utility: The menu for diagram objects. Menu/<category>: The Plugins menu in the main menu. pluginMenu: Optional name of a submenu in the Plugins menu where the plugin should appear. For example, Catalog, Objects, Utilities. This is equivalent to adding a Menu/<category> in the groups list.
11.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 crossplatform 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.
216
The Workbench Scripting Shell
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.
11.5. The Workbench Scripting Shell

The Workbench Scripting Shell provides a means for entering and executing scripts. Through the use of the scripting shell, MySQL Workbench can support new behavior and data sources using code written in Lua and Python. The shell can also be used to explore the current Workbench GRT (Generic RunTime) facilities. The scripting shell is not only useful for expanding MySQL Workbench. You can use a script file from the scripting shell command line to perform repetitive tasks programmatically. The development language can be either Python or Lua. The default programming language used in Workbench Scripting Shell is defined in the General tab of the MySQL Workbench Preferences dialog, and defaults to Python. Note Although they serve a different purpose, the MySQL Utililies are also bundled with MySQL Workbench. For more information, see Chapter 13, MySQL Utilities.
11.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.
217
The Shell Window
Figure 11.1. The Workbench Scripting Shell
11.5.2. The Shell Window

The Workbench Scripting Shell is primarily used for running Python or Lua scripts, or typing commands in these languages directly. However, you can also use it to access the Workbench Scripting Shell Scripting Library functions and global functions and objects. To see the available commands, type ?. You can also cut and paste text to and from the shell window. The Snippets tab is a scratch pad for saving code snippets. This makes it easy to reuse code and does away with the need to retype it at the command line. If you have opened script files, each will have its own tab to the right of the Snippets tab. These tabs will be labeled with the names of the script files, or Unnamed for snippets without a name. As with the Snippets tab you can cut and paste to or from any of the tabs. This gives you the opportunity to test code from the command line. Right clicking on a snippet opens a dialog with options to Execute Snippet, Send to Script Editor, or Copy To Clipboard. While individual commands can be entered into the shell, it is also possible to run a longer script, stored in an external file, using the main menu item Scripting, Run Workbench Script File. When scripts are run outside of the shell, to see the output use the main menu item View, Output. It is also possible to run script files directly from the shell. For details on running script files, type ? run at the Workbench Scripting Shell prompt. The following message is displayed:
218
The Files, Globals, Classes, and Modules Tabs
Help Topics ----------grt General information about the Workbench runtime scripting Practical information when working on scripts and modules for Workbench wbdata Summary about Workbench model data organization modules Information about Workbench module usage plugins Information about writing Plugins and Modules for Workbench Type '? [topic]' to get help on the topic. Custom Python Modules --------------------grt Module to work with Workbench runtime (grt) objects grt.root The root object in the internal Workbench object hierarchy grt.modules Location where Workbench modules are available grt.classes List of classes known to the GRT system mforms A Module to access the cross-platform UI toolkit used in some Workbench features wb Utility module for creating Workbench plugins Type 'help(module/object/function)' to get information about a module, object or function. Type 'dir(object)' to get a quick list of methods an object has. For an introductory tutorial on the Python language, visit http://docs.python.org/tutorial/ For general Python and library reference documentation, visit http://python.org/doc/
Within the Workbench Scripting Shell, there are four tabs on the top of the left side panel: Files, Globals, Classes, and Modules. Discussion of these additional tabs follows. Note An exception is thrown while attempting to use input() or read from stdin.
11.5.3. The Files, Globals, Classes, and Modules Tabs

The Workbench Scripting Shell features the Files, Globals, Classes and Modules tabs, in addition to the main Shell tab. The Files Tab Lists folders and files for user-defined (custom) script files. The categories are User Scripts, User Modules, and User Libraries. The Globals Tab At the top of the window is a list that is used to select the starting point, or root, of the GRT Globals tree displayed beneath it. By default, this starting point is the root of the tree, that is, '/'. You can expand or collapse the GRT Globals tree as desired. The GRT Globals tree is the structure in which MySQL Workbench stores document data. Clicking any item results in its name and value being displayed in the panel below the tree. The Classes Tab A class is a user-defined data type formed by combining primitive data types: integers, doubles, strings, dicts, lists, and objects. This tab shows the definitions of the classes used by the objects in the Modules tab. Clicking a class causes a brief description of the class to be displayed in a panel below the classes explorer. When the Classes tab is selected, the list displays the following items: Group by Name: Group by the object name
219
Tutorial: Writing Plugins
Group by Hierarchy: Group by inheritance Group by Package: Group by functionality The default view for this tab is Group By Name. This view shows all the different objects arranged alphabetically. Click the + icon or double-click a package to show the properties of the struct. If you switch to the hierarchical view, you will see GrtObject: the parent object from which all other objects are derived. The Modules Tab The Modules tab enables you to browse the MySQL Workbench installed modules and their functions. Clicking a module within the explorer causes its details to be displayed in a panel below the explorer. This facility is useful for exploring the available modules, and their supported functions. It is also a way to check whether custom modules have been correctly installed.
11.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
220
Tutorial: Writing Plugins
# 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.
221
222
Chapter 12. 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. There are keyboard shortcut tables for the File, Edit, View, Arrange, Model, Query, Database, Scripting, Help, and EER Diagram Mode menus. File Menu Table 12.1. File menu keyboard shortcuts Function New Model Open Model Open SQL Script Close Tab Save Model Save Script Save Model As Save Script As Forward Engineer SQL CREATE Script Keyboard Shortcut Modifier+N Modifier+O Modifier+Shift+O Modifier+W Modifier+S Modifier+S Modifier+Shift+S Modifier+Shift+S Modifier+Shift+G Context All All SQL Editor All Model SQL Editor Model SQL Editor Model Model Model EER Diagram mode only All
Forward Engineer SQL ALTER Modifier+Alt+Y Script Synchronize With SQL CREATE Script Print Exit Edit Menu Table 12.2. Edit menu keyboard shortcuts Function Undo Redo Cut Copy Paste Delete Edit Selected Edit Selected in New Window Select All Keyboard Shortcut Modifier+Z Modifier+X Modifier+C Modifier+V Modifier+Delete, Command+BackSpace (Mac OS X) Modifier+E Modifier+Shift+E Modifier+A Modifier+Shift+Y Modifier+P Modifier+Q
Context Model, EER Diagram All All All All Model, EER Diagram Model, EER Diagram EER Diagram
Modifier+Y, Modifier+Shift+Z (Mac OS X) Model, EER Diagram
223
Function Find Find Advanced Find Next Find Previous Search and Replace View Menu
Keyboard Shortcut Modifier+F Modifier+Alt+F F3 Shift+F3 Modifier+Shift+F
Context All All All All All
Table 12.3. View menu keyboard shortcuts Function Output Window Set Marker n Go to Marker n Arrange Menu Table 12.4. Arrange menu keyboard shortcuts Function Bring to Front Send to Back Model Menu Table 12.5. Model menu keyboard shortcuts Function Add Diagram Validate All Validate All (MySQL) Model Options Keyboard Shortcut Modifier+T Modifier+Alt+V Modifier+Alt+B Command+Alt+, (Shortcut available only on Mac OS X) Context Model, EER Diagram Model, EER Diagram Model, EER Diagram Model, EER Diagram Keyboard Shortcut Modifier+Shift+F Modifier+Shift+B Context EER Diagram EER Diagram Keyboard Shortcut Context
Modifier+F2, Modifier+Option+2 (Mac OS All X) Modifier+Shift+n (n is integer 1..9) Modifier+n (n is integer 1..9) EER Diagram EER Diagram
Query Menu Table 12.6. Query menu keyboard shortcuts Function Execute statement Execute statements New Tab Database Menu Table 12.7. Database menu keyboard shortcuts Function Query Database Keyboard Shortcut Modifier+U Context All Keyboard Shortcut Modifier+Return Modifier+Shift+Return Modifier+T Context SQL Editor SQL Editor SQL Editor
224
Function Reverse Engineer Forward Engineer Synchronize Model Scripting Menu
Keyboard Shortcut Modifier+R Modifier+G Modifier+Y
Context Model, EER Diagram Model, EER Diagram Model, EER Diagram
Table 12.8. Scripting menu keyboard shortcuts Function Scripting Shell Run Workbench Script File Help Menu Table 12.9. Help menu keyboard shortcuts Function Help Index Keyboard Shortcut Context Keyboard Shortcut Context
Modifier+F3, Modifier+Option+3 (on Mac All OS X) Modifier+Shift+R All
F1, Command+Option+question (on Mac All OS X)
EER Diagram Mode In the EER Diagram view, a number of other keyboard shortcuts are available. Table 12.10. EER diagram mode keyboard shortcuts Function Selection tool Hand tool Delete tool Layer tool Note tool Image tool Table tool View tool Routine Group tool Non-Identifying Relationship 1:1 Non-Identifying Relationship 1:n Identifying Relationship 1:1 Identifying Relationship 1:n Identifying Relationship n:m Relationship Using Existing Columns Keyboard Shortcut Escape H D L N I T V G 1 2 3 4 5 6
225
226
Chapter 13. MySQL Utilities

Table of Contents
13.1. Introduction ............................................................................................................................ 227 13.1.1. Introduction to MySQL Utilities ..................................................................................... 227 13.1.2. Connection Parameters ............................................................................................... 228 13.1.3. Introduction to extending the MySQL Utilities ................................................................ 229 13.2. Commands ............................................................................................................................ 235 13.2.1. mysql.utilities.command.grep Search Databases for Objects ......................... 235 13.2.2. mysql.utilities.command.proc Search Processes on Servers ......................... 236 13.3. Manual Pages ........................................................................................................................ 238 13.3.1. MySQL Utilities Overview Brief overview of command-line utilities .............................. 238 13.3.2. mut MySQL Utilities Testing .................................................................................... 240 13.3.3. mysqldbcompare Compare Two Databases and Identify Differences ........................ 243 13.3.4. mysqldbcopy Copy Database Objects Between Servers ......................................... 249 13.3.5. mysqldbexport Export Object Definitions or Data from a Database ......................... 253 13.3.6. mysqldbimport Import Object Definitions or Data into a Database .......................... 260 13.3.7. mysqldiff Identify Differences Among Database Objects ....................................... 263 13.3.8. mysqldiskusage Show Database Disk Usage ....................................................... 267 13.3.9. mysqlfailover Automatic replication health monitoring and failover ........................ 271 13.3.10. mysqlindexcheck Identify Potentially Redundant Table Indexes ........................... 277 13.3.11. mysqlmetagrep Search Database Object Definitions ............................................ 280 13.3.12. mysqlprocgrep Search Server Process Lists ....................................................... 283 13.3.13. mysqlreplicate Set Up and Start Replication Between Two Servers .................... 286 13.3.14. mysqlrpladmin Administration utility for MySQL replication ................................... 290 13.3.15. mysqlrplcheck Check Replication Prerequisites .................................................. 297 13.3.16. mysqlrplshow Show Slaves for Master Server ..................................................... 300 13.3.17. mysqlserverclone Clone Existing Server to Create New Server .......................... 303 13.3.18. mysqlserverinfo Display Common Diagnostic Information from a Server ............. 305 13.3.19. mysqluserclone Clone Existing User to Create New User ................................... 307 13.3.20. mysqluc Command line client for running MySQL Utilities ...................................... 309 13.4. Parsers .................................................................................................................................. 312 13.4.1. mysql.utilities.parser Parse MySQL Log Files ........................................................... 312 13.5. Appendix ............................................................................................................................... 314 13.5.1. MySQL Utilities FAQ ................................................................................................... 314 This chapter describes the MySQL Utilities for MySQL Workbench, a set of Python tools for working with MySQL Server.
13.1. Introduction
13.1.1. Introduction to MySQL Utilities
What are the MySQL Utilities?
It is a package of utilities that are used for maintenance and administration of MySQL servers. These utilities encapsulate a set of primitive commands, and bundles them so they can be used to perform macro operations with a single command. They can be installed via MySQL Workbench, or as a standalone package.
227
Connection Parameters
The utilities are written in Python, available under the GPLv2 license, and are extendable using the supplied library. They are designed to work with Python 2.x greater than 2.6.
How do we access the MySQL Utilities?

There are two ways to access the utilities from within the MySQL Workbench. Either use Plugins, Start Shell for MySQL Utilities from the main Workbench toolbar, or click the MySQL Utilities icon from the main Workbench page. Both methods will open a terminal/shell window, and list the available commands. Figure 13.1. Starting MySQL Utilities from Workbench
You can launch any of the utilities listed by typing the name of the command. To find out what options are available, use the option, or read the appropriate manual page.
13.1.2. Connection Parameters

To connect to a server, it is necessary to specify connection parameters such as user name, host name, password, and perhaps also port or socket. Whenever connection parameters are required, they can be specified three different ways: As a dictionary containing the connection parameters. As a connection specification string containing the connection parameters. As a Server instance. When providing the connection parameters as a dictionary, the parameters are passed unchanged to the connectors connect function. This enables you to pass parameters not supported through the other interfaces, but at least these parameters are supported:
228
Introduction to extending the MySQL Utilities
user The name of the user to connect as. The default if no user is supplied is login name of the user, as returned by getpass.getuser. passwd The password to use when connecting. The default if no password is supplied is the empty password. host The domain name of the host or the IP address. The default iIf no host name is provided is localhost. This field accepts host names, and IPv4 and IPv6 addresses. It also accepts quoted values which are not validated and passed directly to the calling methods. This enables users to specify host names and IP addresses that are outside of the supported validation mechanisms. port The port to use when connecting to the server. The default if no port is supplied is 3306 (which is the default port for the MySQL server as well). unix_socket The socket to connect to (instead of using the host and port parameters). Providing the connection parameters as a string requires the string to have the format user[:passwd]@host[:port][:socket], where some values are optional. If a connection specification string is provided, it is parsed using the options.parse_connection function.
13.1.3. Introduction to extending the MySQL Utilities

Administration and maintenance on the MySQL server can at times be complicated. Sometimes tasks require tedious or even repetitive operations that can be time consuming to type and re-type. For these reasons and more, the MySQL Utilities were created to help both beginners and experienced database administrators perform common tasks.
What are the internals of the MySQL Utilities?

MySQL Utilities are designed as a collection of easy to use Python scripts that can be combined to provide more powerful features. Internally, the scripts use the mysql.utilities module library to perform its various tasks. Since a library of common functions is available, it is easy for a database administrator to create scripts for common tasks. These utilities are located in the /scripts folder of the installation or source tree. If you have a task that is not met by these utilities or one that can be met by combining one or more of the utilities or even parts of the utilities, you can easily form your own custom solution. The following sections present an example of a custom utility, discussing first the anatomy of a utility and then what the mysql.utilities module library has available.
Anatomy of a MySQL Utility

MySQL Utilities use a three-tier module organization. At the top is the command script, which resides in the /scripts folder of the installation or source tree. Included in the script is a command module designed to encapsulate and isolate the bulk of the work performed by the utility. The command module resides in the /mysql/utilities/command folder of the source tree. Command modules have names similar to the script. A command module includes classes and methods from one or more common modules where the abstract objects and method groups are kept. The common modules reside in the /mysql/utilities/
229
common folder of the source tree. The following illustrates this arrangement using the mysqlserverinfo utility:
/scripts/mysqlserverinfo.py | +--- /mysql/utilities/command/serverinfo.py | +--- /mysql/utilities/common/options.py | +--- /mysql/utilities/common/server.py | +--- /mysql/utilities/common/tools.py | +--- /mysql/utilities/common/format.py
Each utility script is designed to process the user input and option settings and pass them on to the command module. Thus, the script contains only such logic for managing and validating options. The work of the operation resides in the command module. Command modules are designed to be used from other Python applications. For example, one could call the methods in the serverinfo.py module from another Python script. This enables developers to create their own interfaces to the utilties. It also permits developers to combine several utilities to form a macro-level utility tailored to a specified need. For example, if there is a need to gather server information as well as disk usage, it is possible to import the serverinfo.py and diskusage.py modules and create a new utility that performs both operations. Common modules are the heart of the MySQL Utilities library. These modules contain classes that abstract MySQL objects, devices, and mechanisms. For example, there is a server class that contains operations to be performed on servers, such as connecting (logging in) and running queries.
The MySQL Utilities Library

While the library is growing, the following lists the current common modules and the major classes and methods as of the 1.0.1 release:
Module ---------database dbcompare Class/Method ------------------------Database get_create_object diff_objects check_consistency format_tabular_list format_vertical_list print_list options setup_common_options add_skip_options check_skip_options check_format_option add_verbosity check_verbosity add_difftype add_engines check_engine_options parse_connection Replication Description ---------------------------------------Perform database-level operations Retrieve object create statement Diff definitions of two objects Check data consistency of two tables Format list in either GRID or delimited format to a file Format list in a vertical format to a file Print list based on format (CSV, GRID, TAB, or VERTICAL) Set up option parser and options common to all MySQL Utilities Add common --skip options Check skip options for validity Check format option for validity Add verbosity and quiet options Check whether both verbosity and quiet options are being used Add difftype option Add engine, default-storage-engine options Check whether storage engines listed in options exist Parse connection values Establish replication connection between a master and a slave
format
rpl
230
get_replication_tests server
table
tools
user
Return list of replication test function pointers get_connection_dictionary Get connection dictionary find_running_servers Check whether any servers are running on the local host connect_servers Connect to source and destination server Server Connect to running MySQL server and perform server-level operations Index Encapsulate index for a given table as defined by SHOW INDEXES Table Encapsulate table for given database to perform table-level operations get_tool_path Search for MySQL tool and return its full path delete_directory Remove directory (folder) and contents parse_user_host Parse user, passwd, host, port from user:passwd@host User Clone user and its grants to another user and perform user-level operations
General Interface Specifications and Code Practices

The MySQL Utilities are designed and coded using mainstream coding practices and techniques common to the Python community. Effort has been made to adhere to the most widely accepted specifications and techniques. This includes limiting the choice of libraries used to the default libraries found in the Python distributions. This ensures easier installation, enhanced portability, and fewer problems with missing libraries. Similarly, external libraries that resort to platform-specific native code are also not used. The class method and function signatures are designed to make use of a small number of required parameters and all optional parameters as a single dictionary. Consider the following method:
def do_something_wonderful(position, obj1, obj2, options={}): """Does something wonderful A fictional method that does something to object 2 based on the location of something in object 1. position[in] obj1[in] obj2[in] options[in] width iter ok_to_fail Position in obj1 First object to manipulate Second object to manipulate Option dictionary width of printout (default 75) max iterations (default 2) if True, do not throw exception (default True)
Returns bool - True = success, Fail = failed """
This example is typical of the methods and classes in the library. Notice that this method has three required parameters and a dictionary of options that may exist. Each method and function that uses this mechanism defines its own default values for the items in the dictionary. A quick look at the method documentation shows the key names for the dictionary. This can be seen in the preceding example where the dictionary contains three keys and the documentation lists their defaults. To call this method and pass different values for one or more of the options, the code may look like this:
opt_dictionary 'width' 'iter' 'ok_to_fail' = : : : { 100, 10, False,
231
} result = do_something_wonderful(1, obj_1, obj_2, opt_dictionary)
The documentation block for the preceding method is the style used throughout the library.
Example
Now that you are familiar with the MySQL utilities and the supporting library modules, let us take a look at an example that combines some of these modules to solve a problem. Suppose that you want to develop a new database solution and need to use real world data and user accounts for testing. The mysqlserverclone MySQL utility looks like a possibility but it makes only an instance of a running server. It does not copy data. However, mysqldbcopy makes a copy of the data and mysqluserclone clones the users. You could run each of these utilities in sequence, and that would work, but we are lazy at heart and want something that not only copies everything but also finds it for us. That is, we want a one-command solution. The good news is that this is indeed possible and very easy to do. Let us start by breaking the problem down into its smaller components. In a nutshell, we must perform these tasks: Connect to the original server Find all of the databases Find all of the users Make a clone of the original server Copy all of the databases Copy all of the users If you look at the utilities and the modules just listed, you see that we have solutions and primitives for each of these operations. So you need not even call the MySQL utilities directly (although you could). Now let us dive into the code for this example. The first task is to connect to the original server. We use the same connection mechanism as the other MySQL utilities by specifying a --server option like this:
parser.add_option("--server", action="store", dest="server", type="string", default="root@localhost:3306", help="connection information for original server in " + \ "the form: <user>:<password>@<host>:<port>:<socket>")
Once we process the options and arguments, connecting to the server is easy: Use the parse_connection method to take the server option values and get a dictionary with the connection values. All of the heavy diagnosis and error handling is done for us, so we just need to check for exceptions:
from mysql.utilities.common.options import parse_connection try: conn = parse_connection(opt.server) except: parser.error("Server connection values invalid or cannot be parsed.")
Now that we have the connection parameters, we create a class instance of the server using the Server class from the server module and then connect. Once again, we check for exceptions:
from mysql.utilities.common.server import Server
232
server_options = { 'conn_info' : conn, 'role' : "source", } server1 = Server(server_options) try: server1.connect() except UtilError, e: print "ERROR:", e.errmsg
The next item is to get a list of all of the databases on the server. We use the new server class instance to retrieve all of the databases on the server:
db_list = [] for db in server1.get_all_databases(): db_list.append((db[0], None))
If you wanted to supply your own list of databases, you could use an option like the following. You could also add an else clause which would enable you to either get all of the databases by omitting the -databases option or supply your own list of databases (for example, --databases=db1,db2,db3):
parser.add_option("-d", "--databases", action="store", dest="dbs_to_copy", type="string", help="comma-separated list of databases " "to include in the copy (omit for all databases)", default=None) if opt.dbs_to_copy is None: for db in server1.get_all_databases(): db_list.append((db[0], None)) else: for db in opt.dbs_to_copy.split(","): db_list.append((db, None))
Notice we are creating a list of tuples. This is because the dbcopy module uses a list of tuples in the form (old_db, new_db) to enable you to copy a database to a new name. For our purposes, we do not want a rename so we leave the new name value set to None. Next, we want a list of all of the users. Once again, you could construct the new solution to be flexible by permitting the user to specify the users to copy. We leave this as an exercise. In this case, we do not have a primitive for getting all users created on a server. But we do have the ability to run a query and process the results. Fortunately, there is a simple SQL statement that can retrieve all of the users on a server. For our purposes, we get all of the users except the root and anonymous users, then add each to a list for processing later:
users = server1.exec_query("SELECT user, host " "FROM mysql.user " "WHERE user != 'root' and user != ''") for user in users: user_list.append(user[0]+'@'+user[1])
Now we must clone the original server and create a viable running instance. When you examine the mysqlserverclone utility code, you see that it calls another module located in the /mysql/ utilities/command sub folder. These modules are where all of the work done by the utilities take place. This enables you to create new combinations of the utilities by calling the actual operations directly. Lets do that now to clone the server. The first thing you notice in examining the serverclone module is that it takes a number of parameters for the new server instance. We supply those in a similar way as options:
parser.add_option("--new-data", action="store", dest="new_data", type="string", help="the full path to the location "
233
"of the data directory for the new instance") parser.add_option("--new-port", action="store", dest="new_port", type="string", default="3307", help="the new port " "for the new instance - default=%default") parser.add_option("--new-id", action="store", dest="new_id", type="string", default="2", help="the server_id for " "the new instance - default=%default") from mysql.utilities.command import serverclone try: res = serverclone.clone_server(conn, opt.new_data, opt.new_port, opt.new_id, "root", None, False, True) except exception.UtilError, e: print "ERROR:", e.errmsg exit(1)
As you can see, the operation is very simple. We just added a few options we needed like --new-data, --new-port, and --new-id (much like mysqlserverclone) and supplied some default values for the other parameters. Next, we need to copy the databases. Once again, we use the command module for mysqldbcopy to do all of the work for us. First, we need the connection parameters for the new instance. This is provided in the form of a dictionary. We know the instance is a clone, so some of the values are going to be the same and we use a default root password, so that is also known. Likewise, we specified the data directory and, since we are running on a Linux machine, we know what the socket path is. (For Windows machines, you can leave the socket value None.) We pass this dictionary to the copy method:
dest_values = { "user" : conn.get("user"), "passwd" : "root", "host" : conn.get("host"), "port" : opt.new_port, "unix_socket" : os.path.join(opt.new_data, "mysql.sock") }
In this case, a number of options are needed to control how the copy works (for example, if any objects are skipped). For our purposes, we want all objects to be copied so we supply only the minimal settings and let the library use the defaults. This example shows how you can fine tune the scripts to meet your specific needs without having to specify a lot of additional options in your script. We enable the quiet option on so as not to clutter the screen with messages, and tell the copy to skip databases that do not exist (in case we supply the --databases option and provide a database that does not exist):
options = { "quiet" : True, "force" : True }
The actual copy of the databases is easy. Just call the method and supply the list of databases:
from mysql.utilities.command import dbcopy try: dbcopy.copy_db(conn, dest_values, db_list, options) except exception.UtilError, e: print "ERROR:", e.errmsg exit(1)
Lastly, we copy the user accounts. Once again, we must provide a dictionary of options and call the command module directly. In this case, the userclone module provides a method that clones one user to one or more users so we must loop through the users and clone them one at a time:
from mysql.utilities.command import userclone
234
Commands
options = { "overwrite" : True, "quiet" : True, "globals" : True } for user in user_list: try: res = userclone.clone_user(conn, dest_values, user, (user,), options) except exception.UtilError, e: print "ERROR:", e.errmsg exit(1)
We are done. As you can see, constructing new solutions from the MySQL utility command and common modules is easy and is limited only by your imagination.
Enhancing the Example

A complete solution for the example named copy_server.py is located in the /docs/intro/ examples folder. It is complete in so far as this document explains, but it can be enhanced in a number of ways. The following briefly lists some of the things to consider adding to make this example utility more robust. Table locking: Currently, databases are not locked when copied. To achieve a consistent copy of the data on an active server, you may want to add table locking or use transactions (for example, if you are using InnoDB) for a more consistent copy. Skip users not associated with the databases being copied. Do not copy users with only global privileges. Start replication after all of the users are copied (makes this example a clone and replicate scale out solution). Stop new client connections to the server during the copy.
Conclusion
If you find some primitives missing or would like to see more specific functionality in the library or scripts, please contact us with your ideas or better still, write them yourselves! We welcome all suggestions in code or text. To file a feature request or bug report, visit http://bugs.mysql.com. For discussions, visit http:// forums.mysql.com/list.php?155.
13.2. Commands
13.2.1. mysql.utilities.command.grep Search Databases for Objects
This module provides utilities to search for objects on a server. The module defines a set of object types that can be searched by searching the fields of each object. The notion of an object field is very loosely defined and means any names occurring as part of the object definition. For example, the fields of a table include the table name, the column names, and the partition names (if it is a partitioned table).
Constants
The following constants denote the object types that can be searched. mysql.utilities.command.grep.ROUTINE
235
mysql.utilities.command.proc Search Processes on Servers
mysql.utilities.command.grep.EVENT mysql.utilities.command.grep.TRIGGER mysql.utilities.command.grep.TABLE mysql.utilities.command.grep.DATABASE mysql.utilities.command.grep.VIEW mysql.utilities.command.grep.USER The following constant is a sequence of all the object types that are available. It can be used to generate a version-independent list of object types that can be searched; for example, options and help texts. mysql.utilities.command.grep.OBJECT_TYPES
Classes
class mysql.utilities.command.grep.ObjectGrep(pattern[, database_pattern=None, types=OBJECT_TYPES, check_body=False, use_regexp=False]) Search MySQL server instances for objects where the name (or content, for routines, triggers, or events) matches a given pattern. sql() string Return the SQL code for executing the search in the form of a SELECT statement. Returns: Return type: SQL code for executing the operation specified by the options. string
execute(connections[, output=sys.output, connector=mysql.connector]) Execute the search on each of the connections in turn and print an aggregate of the result as a grid table. Parameters: connections Sequence of connection specifiers to send the query to output File object to use for writing the result connector Connector to use for connecting to the servers
13.2.2. mysql.utilities.command.proc Search Processes on Servers

This module searches processes on a server and optionally kills either the query or the connection for all matching processes. Processes are matched by searching the fields of the INFORMATION_SCHEMA.PROCESSLIST table (which is available only for servers from MySQL 5.1.7 and later). Internally, the module operates by constructing a SELECT statement for finding matching processes, and then sending it to the server. Instead of performing the search, the module can return the SQL code that performs the query. This can be useful if you want to execute the query later or feed it to some other program that processes SQL queries further.
Constants
The following constants correspond to columns in the INFORMATION_SCHEMA.PROCESSLIST table. They indicate which columns to examine when searching for processes matching the search conditions.
236
mysql.utilities.command.proc Search Processes on Servers
mysql.utilities.command.proc.ID mysql.utilities.command.proc.USER mysql.utilities.command.proc.HOST mysql.utilities.command.proc.DB mysql.utilities.command.proc.COMMAND mysql.utilities.command.proc.TIME mysql.utilities.command.proc.STATE mysql.utilities.command.proc.INFO The following constants indicate actions to perform on processes that match the search conditions. mysql.utilities.command.proc.KILL_QUERY Kill the process query mysql.utilities.command.proc.KILL_CONNECTION Kill the process connection mysql.utilities.command.proc.PRINT_PROCESS Print the processes
Classes
class mysql.utilities.command.proc.ProcessGrep(matches, actions=[], use_regexp=False) This class searches the INFORMATION_SCHEMA.PROCESSLIST table for processes on MySQL servers and optionally kills them. It can both be used to actually perform the search or kill operation, or to generate the SQL statement for doing the job. To kill all queries with user mats, the following code can be used:
>>> from mysql.utilities.command.proc import * >>> grep = ProcessGrep(matches=[(USER, "mats")], actions=[KILL_QUERY]) >>> grep.execute("root@server-1.example.com", "root@server-2.example.com")
Parameters:
matches (List of (var, pat) pairs) Sequence of field comparison conditions. In each condition, var is one of the constants listed earlier that specify PROCESSLIST table fields and pat is a pattern. For a process to match, all field conditions must match.
sql([only_body=False]) Return the SQL code for executing the search (and optionally, the kill). If only_body is True, only the body of the function is shown. This is useful if the SQL code is to be used with other utilities that generate the routine declaration. If only_body is False, a complete procedure will be generated if there is any kill action supplied, and just a select statement if it is a plain search. Parameters: only_body (boolean) Show only the body of the procedure. If this is False, a complete procedure is returned.
237
Manual Pages
Returns: Return type:
SQL code for executing the operation specified by the options. string
execute(connections, ...[, output=sys.stdout, connector=mysql.connector]) Execute the search on each of the connections supplied. If output is not None, the value is treated as a file object and the result of the execution is printed on that stream. Note that the output and connector arguments must be supplied as keyword arguments. All other arguments are treated as connection specifiers. Parameters: connections Sequence of connection specifiers to send the search to output File object to use for writing the result connector Connector to use for connecting to the servers
13.3. Manual Pages

13.3.1. MySQL Utilities Overview Brief overview of command-line utilities
This is a brief overview of the MySQL command-line utilities. See their respective manual pages for further details and examples: mysqldbcompare Compare databases on two servers or the same server Compare definitions and data Generate a difference report Generate SQL transformation statements mysqldbcopy Copy databases between servers Clone databases on the same server Supports rename mysqldbexport Export metadata and/or data from one or more databases Formats: SQL, CSV, TAB, Grid, Vertical mysqldbimport Import metadata and data from one or more files Reads all formats from mysqldbexport mysqldiff Compare object definitions
238
MySQL Utilities Overview Brief overview of command-line utilities
Generate a difference report mysqldiskusage Show disk usage for databases Generate reports in SQL, CSV, TAB, Grid, Vertical mysqlfailover Performs replication health monitoring Provides automatic failover on a replication topology Uses Global Transaction Identifiers (GTID, MySQL Server 5.6.5+) mysqlindexcheck Read indexes for one or more tables Check for redundant and duplicate indexes Generate reports in SQL, CSV, TAB, Grid, Vertical mysqlmetagrep Search metadata Regexp, database search Generate SQL statement for search query mysqlprocgrep Search process information Generate SQL statement for search Kill processes that match query mysqlreplicate Setup replication Start from beginning, current, specific binlog, pos mysqlrpladmin Administers the replication topology Allows recovery of the master Commands include elect, failover, gtid, health, start, stop, and switchover mysqlrplcheck Check replication configuration Tests binary logging on master
239
mut MySQL Utilities Testing
mysqlrplshow Show slaves attached to master Can search recursively Show the replication topology as a graph or list mysqlserverclone Start a new instance of a running server mysqlserverinfo Show server information Can search for running servers on a host Access online or offline servers mysqluserclone Clone a user account, to the same or different server Show user grants mysqluc Command line client for running MySQL Utilities Allows a persistent connection to a MySQL Server Tab completion for utility names and options Allows calling the commands with shorter names, such as using "serverinfo" instead of mysqlserverinfo mut Tests for all utilities Similar to MTR Comparative and value result support Tests written as Python classes
13.3.2. mut MySQL Utilities Testing

This utility executes predefined tests to test the MySQL Utilities. The tests are located under the /mysqltest directory and divided into suites (stored as folders). By default, all tests located in the /t folder are considered the main suite. You can select any number of tests to run, select one or more suites to restrict the tests, exclude suites and tests, and specify the location of the utilities and tests. The utility requires the existence of at least one server to clone for testing purposes. You must specify at least one server, but you may specify multiple servers for tests designed to use additional servers.
240
The utility has a special test suite named performance where performance-related tests are placed. This suite is not included by default and must be specified with the --suite [242] option to execute the performance tests.
OPTIONS
mut accepts the following command-line options: --help Display a help message and exit. --do-tests=<prefix> Execute all tests that begin with prefix. --force Do not abort when a test fails. --record Record the output of the specified test if successful. With this option, you must specify exactly one test to run. --server=<server> Connection information for the server to use in the tests, in <user>[:<passwd>]@<host>[:<port>] [:<socket>] format. Use this option multiple times to specify multiple servers. --skip-long Exclude tests that require greater resources or take a long time to run. --skip-suite=<name> Exclude the named test suite. Use this option multiple times to specify multiple suites. --skip-test=<name> Exclude the named test. Use this option multiple times to specify multiple tests. --skip-tests=<prefix> Exclude all tests that begin with prefix. --sort Execute tests sorted by suite.name either ascending (asc) or descending (desc). Default is ascending (asc). --start-port=<port> The first port to use for spawned servers. If you run the entire test suite, you may see up to 12 new instances created. The default is to use ports 3310 to 3321. --start-test=<prefix> Start executing tests that begin with prefix.
241
--suite=<name> Execute the named test suite. Use this option multiple times to specify multiple suites. --testdir=<path> The path to the test directory. --utildir=<path> The location of the utilities. --verbose, -v Specify how much information to display. Use this option multiple times to increase the amount of information. For example, -v = verbose, -vv = more verbose, -vvv = debug. To diagnose test execution problems, use -vvv to display the actual results of test cases and ignore result processing. --version Display version information and exit. --width=<number> Specify the display width. The default is 75 characters.
NOTES
The connection specifier must name a valid account for the server. Any test named ???_template.py is skipped. This enables the developer to create a base class to import for a collection of tests based on a common code base.
EXAMPLES
The following example demonstrates how to invoke mut to execute a subset of the tests using an existing server which is cloned. The example displays the test name, status, and relative time:
$ python mut --server=root@localhost --do-tests=clone_user --width=70 MySQL Utilities Testing - MUT Parameters used: Display Width Sorted Force Test directory Utilities directory Starting port Test wildcard
= = = = = = =
70 True False './t' '../scripts' 3310 'clone_user%'
Servers: Connecting to localhost as user root on port 3306: CONNECTED ---------------------------------------------------------------------TEST NAME STATUS TIME ====================================================================== main.clone_user [pass] 54 main.clone_user_errors [pass] 27 main.clone_user_parameters [pass] 17 ----------------------------------------------------------------------
242
mysqldbcompare Compare Two Databases and Identify Differences
Testing completed: Friday 03 December 2010 09:50:06 All 3 tests passed.
13.3.3. mysqldbcompare Compare Two Databases and Identify Differences

This utility compares the objects and data from two databases to find differences. It identifies objects having different definitions in the two databases and presents them in a diff-style format of choice. Differences in the data are shown using a similar diff-style format. Changed or missing rows are shown in a standard format of GRID, CSV, TAB, or VERTICAL. Use the notation db1:db2 to name two databases to compare, or, alternatively just db1 to compare two databases with the same name. The latter case is a convenience notation for comparing same-named databases on different servers. The comparison may be run against two databases of different names on a single server by specifying only the --server1 [246] option. The user can also connect to another server by specifying the -server2 [246] option. In this case, db1 is taken from server1 and db2 from server2. Those objects considered in the database include tables, views, triggers, procedures, functions, and events. A count for each object type can be shown with the -vv option. The check is performed using a series of steps called tests. By default, the utility stops on the first failed test, but you can specify the --run-all-tests [246] option to cause the utility to run all tests regardless of their end state. Note: Using --run-all-tests [246] may produce expected cascade failures. For example, if the row counts differ among two tables being compared, the data consistency will also fail. The tests include the following: 1. Check database definitions A database existence precondition check ensures that both databases exist. If they do not, no further processing is possible and the --run-all-tests [246] option is ignored. 2. Check existence of objects in both databases The test for objects in both databases identifies those objects missing from one or another database. The remaining tests apply only to those objects that appear in both databases. To skip this test, use the --skip-object-compare [246] option. That can be useful when there are known missing objects among the databases. 3. Compare object definitions The definitions (the CREATE statements) are compared and differences are presented. To skip this test, use the --skip-diff [246] option. That can be useful when there are object name differences only that you want to ignore. 4. Check table row counts This check ensures that both tables have the same number of rows. This does not ensure that the table data is consistent. It is merely a cursory check to indicate possible missing rows in one table or the other. The data consistency check identifies the missing rows. To skip this test, use the --skip-rowcount [246] option. 5. Check table data consistency
243
This check identifies both changed rows as well as missing rows from one or another of the tables in the databases. Changed rows are displayed as a diff-style report with the format chosen (GRID by default) and missing rows are also displayed using the format chosen. To skip this test, use the -skip-data-check [246] option. You may want to use the --skip-xxx options to run only one of the tests. This might be helpful when working to bring two databases into synchronization, to avoid running all of the tests repeatedly during the process. Each test completes with one of the following states: pass The test succeeded. FAIL The test failed. Errors are displayed following the test state line. SKIP The test was skipped due to a missing prerequisite or a skip option. WARN The test encountered an unusual but not fatal error. The test is not applicable to this object. To specify how to display diff-style output, use one of the following values with the --difftype [245] option: unified (default) Display unified format output. context Display context format output. differ Display differ-style format output. sql Display SQL transformation statement output. To specify how to display output for changed or missing rows, use one of the following values with the -format [246] option: grid (default) Display output in grid or table format like that of the mysql monitor. csv
244
Display output in comma-separated values format. tab Display output in tab-separated format. vertical Display output in single-column format like that of the \G command for the mysql monitor. The --changes-for [245] option controls the direction of the difference (by specifying the object to be transformed) in either the difference report (default) or the transformation report (designated with the -difftype=sql [245] option). Consider the following command:
mysqldbcompare --server1=root@host1 --server2=root@host2 --difftype=sql \ db1:dbx
The leftmost database (db1) exists on the server designated by the --server1 [246] option (host1). The rightmost database (dbx) exists on the server designated by the --server2 [246] option (host2). --changes-for=server1 [245]: Produce output that shows how to make the definitions of objects on server1 like the definitions of the corresponding objects on server2. --changes-for=server2 [245]: Produce output that shows how to make the definitions of objects on server2 like the definitions of the corresponding objects on server1. The default direction is server1. You must provide connection parameters (user, host, password, and so forth) for an account that has the appropriate privileges to access all objects in the operation. If the utility is to be run on a server that has binary logging enabled, and you do not want the comparison steps logged, use the --disable-binary-logging [245] option.
OPTIONS
mysqldbcompare accepts the following command-line options: --help Display a help message and exit. --changes-for=<direction> Specify the server to show transformations to match the other server. For example, to see the transformation for transforming object definitions on server1 to match the corresponding definitions on server2, use --changes-for=server1 [245]. Permitted values are server1 and server2. The default is server1. --difftype=<difftype>, -d<difftype> Specify the difference display format. Permitted format values are unified, context, differ, and sql. The default is unified. --disable-binary-logging If binary logging is enabled, disable it during the operation to prevent comparison operations from being written to the binary log. Note: Disabling binary logging requires the SUPER privilege.
245
--format=<format>, -f<format> Specify the display format for changed or missing rows. Permitted format values are grid, csv, tab, and vertical. The default is grid. --quiet, -q Do not print anything. Return only an exit code of success or failure. --run-all-tests, -a Do not halt at the first difference found. Process all objects. --server1=<source> Connection information for the first server in <user>[:<passwd>]@<host>[:<port>][:<socket>] format. --server2=<source> Connection information for the second server in <user>[:<passwd>]@<host>[:<port>][:<socket>] format. --show-reverse Produce a transformation report containing the SQL statements to conform the object definitions specified in reverse. For example, if changes-for is set to server1, also generate the transformation for server2. Note: The reverse changes are annotated and marked as comments. --skip-data-check Skip the data consistency check. --skip-diff Skip the object definition difference check. --skip-object-compare Skip the object comparison check. --skip-row-count Skip the row count check. --verbose, -v Specify how much information to display. Use this option multiple times to increase the amount of information. For example, -v = verbose, -vv = more verbose, -vvv = debug. --version Display version information and exit. --width=<number> Change the display width of the test report. The default is 75 characters.
NOTES
The login user must have the appropriate permissions to read all databases and tables listed.
246
For the --difftype [245] option, the permitted values are not case sensitive. In addition, values may be specified as any unambiguous prefix of a valid value. For example, --difftype=d [245] specifies the differ type. An error occurs if a prefix matches more than one valid value.
EXAMPLES
Use the following command to compare the emp1 and emp2 databases on the local server, and run all tests even if earlier tests fail:
$ mysqldbcompare --server1=root@localhost emp1:emp2 --run-all-tests # server1 on localhost: ... connected. # Checking databases emp1 on server1 and emp2 on server2 WARNING: Objects in server2:emp2 but not in server1:emp1: TRIGGER: trg PROCEDURE: p1 TABLE: t1 VIEW: v1 Defn Row Data Type Object Name Diff Count Check --------------------------------------------------------------------------FUNCTION f1 pass TABLE departments pass pass FAIL Data differences found among rows: --- emp1.departments +++ emp2.departments @@ -1,4 +1,4 @@ ************************* 1. row ************************* dept_no: d002 - dept_name: dunno + dept_name: Finance 1 rows. Rows in emp1.departments not in emp2.departments ************************* 1. row ************************* dept_no: d008 dept_name: Research 1 rows. Rows in emp2.departments not in emp1.departments ************************* 1. row ************************* dept_no: d100 dept_name: stupid 1 rows. TABLE dept_manager pass pass pass
Database consistency check failed. # ...done
Given: two databases with the same table layout. Data for each table contains:
mysql> select * from db1.t1; +---+---------------+ | a | b | +---+---------------+ | 1 | Test 789 | | 2 | Test 456 | | 3 | Test 123 | | 4 | New row - db1 | +---+---------------+ 4 rows in set (0.00 sec)
247
mysql> select * from db2.t1; +---+---------------+ | a | b | +---+---------------+ | 1 | Test 123 | | 2 | Test 456 | | 3 | Test 789 | | 5 | New row - db2 | +---+---------------+ 4 rows in set (0.00 sec)
To generate the SQL statements for data transformations to make db1.t1 the same as db2.t1, use the --changes-for=server1 [245] option. We must also include the -a option to ensure that the data consistency test is run. The following command illustrates the options used and an excerpt from the results generated:
$ mysqldbcompare --server1=root:root@localhost \ --server2=root:root@localhost db1:db2 --changes-for=server1 -a \ --difftype=sql [...] # Defn Row Data # Type Object Name Diff Count Check # ------------------------------------------------------------------------# TABLE t1 pass pass FAIL # # Data transformations for direction = server1: # Data differences found among rows: UPDATE db1.t1 SET b = 'Test 123' WHERE a = '1'; UPDATE db1.t1 SET b = 'Test 789' WHERE a = '3'; DELETE FROM db1.t1 WHERE a = '4'; INSERT INTO db1.t1 (a, b) VALUES('5', 'New row - db2');
# Database consistency check failed.
# # ...done
Similarly, when the same command is run with --changes-for=server2 [245] and -difftype=sql [245], the following report is generated:
$ mysqldbcompare --server1=root:root@localhost \ --server2=root:root@localhost db1:db2 --changes-for=server2 -a \ --difftype=sql [...] # Defn Row Data # Type Object Name Diff Count Check # ------------------------------------------------------------------------# TABLE t1 pass pass FAIL # # Data transformations for direction = server2: # Data differences found among rows: UPDATE db2.t1 SET b = 'Test 789' WHERE a = '1'; UPDATE db2.t1 SET b = 'Test 123' WHERE a = '3'; DELETE FROM db2.t1 WHERE a = '5'; INSERT INTO db2.t1 (a, b) VALUES('4', 'New row - db1');
With the --difftype=sql [245] SQL generation option set, --show-reverse [246] shows the object transformations in both directions. Here is an excerpt of the results:
$ mysqldbcompare --server1=root:root@localhost \ --server2=root:root@localhost db1:db2 --changes-for=server1 \ --show-reverse -a --difftype=sql
248
mysqldbcopy Copy Database Objects Between Servers
[...] # Defn Row Data # Type Object Name Diff Count Check # ------------------------------------------------------------------------# TABLE t1 pass pass FAIL # # Data transformations for direction = server1: # Data differences found among rows: UPDATE db1.t1 SET b = 'Test 123' WHERE a = '1'; UPDATE db1.t1 SET b = 'Test 789' WHERE a = '3'; DELETE FROM db1.t1 WHERE a = '4'; INSERT INTO db1.t1 (a, b) VALUES('5', 'New row - db2'); # Data transformations for direction = server2: # Data differences found among rows: UPDATE db2.t1 SET b = 'Test 789' WHERE a = '1'; UPDATE db2.t1 SET b = 'Test 123' WHERE a = '3'; DELETE FROM db2.t1 WHERE a = '5'; INSERT INTO db2.t1 (a, b) VALUES('4', 'New row - db1');
# Database consistency check failed.
# # ...done
13.3.4. mysqldbcopy Copy Database Objects Between Servers

This utility copies a database on a source server to a database on a destination server. If the source and destination servers are different, the database names can be the same or different. If the source and destination servers are the same, the database names must be different. The utility accepts one or more database pairs on the command line. To name a database pair, use db_name:new_db_name syntax to specify the source and destination names explicitly. If the source and destination database names are the same, db_name can be used as shorthand for db_name:db_name. By default, the operation copies all objects (tables, views, triggers, events, procedures, functions, and database-level grants) and data to the destination server. There are options to turn off copying any or all of the objects as well as not copying the data. To exclude specific objects by name, use the --exclude [250] option with a name in db.*obj* format, or you can supply a search pattern. For example, --exclude=db1.trig1 [250] excludes the single trigger and --exclude=trig_ [250] excludes all objects from all databases having a name that begins with trig and has a following character. By default, the utility creates each table on the destination server using the same storage engine as the original table. To override this and specify the storage engine to use for all tables created on the destination server, use the --new-storage-engine [251] option. If the destination server supports the new engine, all tables use that engine. To specify the storage engine to use for tables for which the destination server does not support the original storage engine on the source server, use the --default-storage-engine [250] option. The --new-storage-engine [251] option takes precedence over --default-storageengine [250] if both are given. If the --new-storage-engine [251] or --default-storage-engine [250] option is given and the destination server does not support the specified storage engine, a warning is issued and the servers default storage engine setting is used instead. By default, the operation uses a consistent snapshot to read the source databases. To change the locking mode, use the --locking [250] option with a locking type value. Use a value of no-locks to turn off
249
locking altogether or lock-all to use only table locks. The default value is snapshot. Additionally, the utility uses WRITE locks to lock the destination tables during the copy. You can include replication statements for copying data among a master and slave or between slaves. The --rpl [251] option permits you to select from the following replication statements to include in the export. master Include the CHANGE MASTER statement to start a new slave with the current server acting as the master. This executes the appropriate STOP and START slave statements. The STOP SLAVE statement is executed at the start of the copy and the CHANGE MASTER followed by the START SLAVE statements are executed after the copy. slave Include the CHANGE MASTER statement to start a new slave using the current servers master information. This executes the appropriate STOP and START slave statements. The STOP SLAVE statement is executed at the start of the copy and the CHANGE MASTER followed by the START SLAVE statements follow the copy. To include the replication user in the CHANGE MASTER statement, use the --rpl-user [251] option to specify the user and password. If this option is omitted, the utility attempts to identify the replication user. In the event that there are multiple candidates or the user requires a password, the utility aborts with an error.
OPTIONS
mysqldbcopy accepts the following command-line options: --help Display a help message and exit. --default-storage-engine=<def_engine> The engine to use for tables if the destination server does not support the original storage engine on the source server. --destination=<destination> Connection information for the destination server in <user>[:<passwd>]@<host>[:<port>][:<socket>] format, where <passwd> is optional and either <port> or <socket> must be provided. --exclude=<exclude>, -x<exclude> Exclude one or more objects from the operation using either a specific name such as db1.t1 or a search pattern. Use this option multiple times to specify multiple exclusions. By default, patterns use LIKE matching. With the --regexp [251] option, patterns use REGEXP matching. This option does not apply to grants. --force Drop each database to be copied if exists before copying anything into it. Without this option, an error occurs if you attempt to copy objects into an existing database. --locking=<locking>
250
Choose the lock type for the operation. Permitted lock values are no-locks (do not use any table locks), lock-all (use table locks but no transaction and no consistent read), and snaphot (consistent read using a single transaction). The default is snapshot. --new-storage-engine=<new_engine> The engine to use for all tables created on the destination server. --quiet, -q Turn off all messages for quiet execution. --regexp, --basic-regexp, -G Perform pattern matches using the REGEXP operator. The default is to use LIKE for matching. --rpl=<dump_option>, --replication=<dump_option> Include replication information. Permitted values are master (include the CHANGE MASTER statement using the source server as the master), slave (include the CHANGE MASTER statement using the destination servers master information), and both (include the master and slave options where applicable). --rpl-user=<user[:password]> The user and password for the replication user requirement - e.g. rpl:passwd - default = rpl:rpl. --skip=<objects> Specify objects to skip in the operation as a comma-separated list (no spaces). Permitted values are CREATE_DB, DATA, EVENTS, FUNCTIONS, GRANTS, PROCEDURES, TABLES, TRIGGERS, and VIEWS. --source=<source> Connection information for the source server in <user>[:<passwd>]@<host>[:<port>][:<socket>] format, where <passwd> is optional and either <port> or <socket> must be provided. --threads Use multiple threads for cross-server copy. The default is 1. --verbose, -v Specify how much information to display. Use this option multiple times to increase the amount of information. For example, -v = verbose, -vv = more verbose, -vvv = debug. --version Display version information and exit.
NOTES
You must provide connection parameters (user, host, password, and so forth) for an account that has the appropriate privileges to access all objects in the operation. To copy all objects from a source, the user must have these privileges: SELECT and SHOW VIEW for the database, and SELECT for the mysql database.
251
To copy all objects to a destination, the user must have these privileges: CREATE for the database, SUPER (when binary logging is enabled) for procedures and functions, and GRANT OPTION to copy grants. Actual privileges required may differ from installation to installation depending on the security privileges present and whether the database contains certain objects such as views or events and whether binary logging is enabled. The --new-storage-engine [251] and --default-storage-engine [250] options apply to all destination tables in the operation. Some option combinations may result in errors during the operation. For example, eliminating tables but not views may result in an error a the view is copied. The --rpl [251] option is not valid for copying databases on the same server. An error will be generated.
EXAMPLES
The following example demonstrates how to use the utility to copy a database named util_test to a new database named util_test_copy on the same server:
$ mysqldbcopy \ --source=root:pass@localhost:3310:/test123/mysql.sock \ --destination=root:pass@localhost:3310:/test123/mysql.sock \ util_test:util_test_copy # Source on localhost: ... connected. # Destination on localhost: ... connected. # Copying database util_test renamed as util_test_copy # Copying TABLE util_test.t1 # Copying table data. # Copying TABLE util_test.t2 # Copying table data. # Copying TABLE util_test.t3 # Copying table data. # Copying TABLE util_test.t4 # Copying table data. # Copying VIEW util_test.v1 # Copying TRIGGER util_test.trg # Copying PROCEDURE util_test.p1 # Copying FUNCTION util_test.f1 # Copying EVENT util_test.e1 # Copying GRANTS from util_test #...done.
If the database to be copied does not contain only InnoDB tables and you want to ensure data integrity of the copied data by locking the tables during the read step, add a --locking=lock-all [250] option to the command:
$ mysqldbcopy \ --source=root:pass@localhost:3310:/test123/mysql.sock \ --destination=root:pass@localhost:3310:/test123/mysql.sock \ util_test:util_test_copy --locking=lock-all # Source on localhost: ... connected. # Destination on localhost: ... connected. # Copying database util_test renamed as util_test_copy # Copying TABLE util_test.t1 # Copying table data. # Copying TABLE util_test.t2 # Copying table data. # Copying TABLE util_test.t3 # Copying table data.
252
mysqldbexport Export Object Definitions or Data from a Database
# Copying # Copying # Copying # Copying # Copying # Copying # Copying # Copying #...done.
TABLE util_test.t4 table data. VIEW util_test.v1 TRIGGER util_test.trg PROCEDURE util_test.p1 FUNCTION util_test.f1 EVENT util_test.e1 GRANTS from util_test
To copy one or more databases from a master to a slave, you can use the following command to copy the databases. Use the master as the source and the slave as the destination:
$ mysqldbcopy --source=root@localhost:3310 \ --destination=root@localhost:3311 test123 --rpl=master \ --rpl-user=rpl # Source on localhost: ... connected. # Destination on localhost: ... connected. # Source on localhost: ... connected. # Stopping slave # Copying database test123 # Copying TABLE test123.t1 # Copying data for TABLE test123.t1 # Connecting to the current server as master # Starting slave #...done.
To copy a database from one slave to another attached to the same master, you can use the following command using the slave with the database to be copied as the source and the slave where the database needs to copied to as the destination:
$ mysqldbcopy --source=root@localhost:3311 \ --destination=root@localhost:3312 test123 --rpl=slave \ --rpl-user=rpl # Source on localhost: ... connected. # Destination on localhost: ... connected. # Source on localhost: ... connected. # Stopping slave # Copying database test123 # Copying TABLE test123.t1 # Copying data for TABLE test123.t1 # Connecting to the current server's master # Starting slave #...done.
13.3.5. mysqldbexport Export Object Definitions or Data from a Database

This utility exports metadata (object definitions) or data or both from one or more databases. By default, the export includes only definitions. mysqldbexport differs from mysqldump in that it can produce output in a variety of formats to make your data extraction/transport much easier. It permits you to export your data in the format most suitable to an external tool, another MySQL server, or other use without the need to reformat the data. To exclude specific objects by name, use the --exclude [255] option with a name in db.*obj* format, or you can supply a search pattern. For example, --exclude=db1.trig1 [255] excludes the single trigger and --exclude=trig_ [255] excludes all objects from all databases having a name that begins with trig and has a following character. To skip objects by type, use the --skip [257] option with a list of the objects to skip. This enables you to extract a particular set of objects, say, for exporting only events (by excluding all other types). Similarly, to skip creation of UPDATE statements for BLOB data, specify the --skip-blobs [257] option.
253
To specify how to display output, use one of the following values with the --format [256] option: sql (default) Display output using SQL statements. For definitions, this consists of the appropriate CREATE and GRANT statements. For data, this is an INSERT statement (or bulk insert if the --bulk-insert [255] option is specified). grid Display output in grid or table format like that of the mysql monitor. csv Display output in comma-separated values format. tab Display output in tab-separated format. vertical Display output in single-column format like that of the \G command for the mysql monitor. To specify how much data to display, use one of the following values with the --display [255] option: brief Display only the minimal columns for recreating the objects. full Display the complete column list for recreating the objects. names Display only the object names. Note: For SQL-format output, the --display [255] option is ignored. To turn off the headers for csv or tab display format, specify the --no-headers [256] option. To turn off all feedback information, specify the --quiet [256] option. To write the data for individual tables to separate files, use the --file-per-table [256] option. The name of each file is composed of the database and table names followed by the file format. For example, the following command produces files named db1.*table_name*.csv:
mysqldbexport --server=root@server1:3306 --format=csv db1 --export=data
By default, the operation uses a consistent snapshot to read the source databases. To change the locking mode, use the --locking [256] option with a locking type value. Use a value of no-locks to turn off locking altogether or lock-all to use only table locks. The default value is snapshot. Additionally, the utility uses WRITE locks to lock the destination tables during the copy. You can include replication statements for exporting data among a master and slave or between slaves. The --rpl [256] option permits you to select from the following replication statements to include in the export. 254
master Include the CHANGE MASTER statement to start a new slave with the current server acting as the master. This places the appropriate STOP and START slave statements in the export whereby the STOP SLAVE statement is placed at the start of the export and the CHANGE MASTER followed by the START SLAVE statements are placed after the export stream. slave Include the CHANGE MASTER statement to start a new slave using the current servers master information. This places the appropriate STOP and START slave statements in the export whereby the STOP SLAVE statment is placed at the start of the export and the CHANGE MASTER followed by the START SLAVE statements are placed after the export stream. both Include both the master and slave information for CHANGE MASTER statements for either spawning a new slave with the current servers master or using the current server as the master. All statements generated are labeled and commented to enable the user to choose which to include when imported. To include the replication user in the CHANGE MASTER statement, use the --rpl-user [256] option to specify the user and password. If this option is omitted, the utility attempts to identify the replication user. In the event that there are multiple candidates or the user requires a password, these statements are placed inside comments for the CHANGE MASTER statement. You can also use the --comment-rpl [255] option to place the replication statements inside comments for later examination. If you specify the --rpl-file [256] option, the utility writes the replication statements to the file specified instead of including them in the export stream.
OPTIONS
mysqldbexport accepts the following command-line options: --help Display a help message and exit. --bulk-insert, -b Use bulk insert statements for data. --comment-rpl Place the replication statements in comment statements. Valid only with the --rpl [256] option. --display=<display>, -d<display> Control the number of columns shown. Permitted display values are brief (minimal columns for object creation), full* (all columns), and **names (only object names; not valid for --format=sql [256]). The default is brief. --exclude=<exclude>, -x<exclude> Exclude one or more objects from the operation using either a specific name such as db1.t1 or a search pattern. Use this option multiple times to specify multiple exclusions. By default, patterns use LIKE matching. With the --regexp [256] option, patterns use REGEXP matching.
255
This option does not apply to grants. --export=<export>, -e<export> Specify the export format. Permitted format values are definitions = export only the definitions (metadata) for the objects in the database list, data = export only the table data for the tables in the database list, and both = export the definitions and the data. The default is definitions. --file-per-table Write table data to separate files. This is Valid only if the export output includes data (that is, if -export=data [256] or --export=both [256] are given). This option produces files named db_name.*tbl_name*.*format*. For example, a csv export of two tables named t1 and t2 in database d1, results in files named db1.t1.csv and db1.t2.csv. If table definitions are included in the export, they are written to stdout as usual. --format=<format>, -f<format> Specify the output display format. Permitted format values are sql, grid, tab, csv, and vertical. The default is sql. --locking=<locking> Choose the lock type for the operation. Permitted lock values are no-locks (do not use any table locks), lock-all (use table locks but no transaction and no consistent read), and snapshot (consistent read using a single transaction). The default is snapshot. --no-headers, -h Do not display column headers. This option applies only for csv and tab output. --quiet, -q Turn off all messages for quiet execution. --regexp, --basic-regexp, -G Perform pattern matches using the REGEXP operator. The default is to use LIKE for matching. --rpl=<dump_option>, --replication=<dump_option> Include replication information. Permitted values are master (include the CHANGE MASTER statement using the source server as the master), slave (include the CHANGE MASTER statement using the destination servers master information), and both (include the master and slave options where applicable). --rpl-file=RPL_FILE, --replication-file=RPL_FILE The path and file name where the generated replication information should be written. Valid only with the --rpl [256] option. --rpl-user=<user[:password]> The user and password for the replication user requirement; for example, rpl:passwd. The default is rpl:rpl. --server=<server>
256
Connection information for the server in <user>[:<passwd>]@<host>[:<port>][:<socket>] format. --skip=<skip-objects> Specify objects to skip in the operation as a comma-separated list (no spaces). Permitted values are CREATE_DB, DATA, EVENTS, FUNCTIONS, GRANTS, PROCEDURES, TABLES, TRIGGERS, and VIEWS. --skip-blobs Do not export BLOB data. --verbose, -v Specify how much information to display. Use this option multiple times to increase the amount of information. For example, -v = verbose, -vv = more verbose, -vvv = debug. --version Display version information and exit.
NOTES
You must provide connection parameters (user, host, password, and so forth) for an account that has the appropriate privileges to access all objects in the operation. To export all objects from a source database, the user must have these privileges: SELECT and SHOW VIEW on the database as well as SELECT on the mysql database. Actual privileges needed may differ from installation to installation depending on the security privileges present and whether the database contains certain objects such as views or events. Some combinations of the options may result in errors when the export is imported later. For example, eliminating tables but not views may result in an error when a view is imported on another server. For the --format [256], --export [256], and --display [255] options, the permitted values are not case sensitive. In addition, values may be specified as any unambiguous prefix of a valid value. For example, --format=g [256] specifies the grid format. An error occurs if a prefix matches more than one valid value.
EXAMPLES
To export the definitions of the database dev from a MySQL server on the local host via port 3306, producing output consisting of CREATE statements, use this command:
$ mysqldbexport --server=root:pass@localhost \ --skip=GRANTS --export=DEFINITIONS util_test # Source on localhost: ... connected. # Exporting metadata from util_test DROP DATABASE IF EXISTS util_test; CREATE DATABASE util_test; USE util_test; # TABLE: util_test.t1 CREATE TABLE `t1` ( à` char(30) DEFAULT NULL ) ENGINE=MEMORY DEFAULT CHARSET=latin1; # TABLE: util_test.t2 CREATE TABLE `t2` ( à` char(30) DEFAULT NULL ) ENGINE=MyISAM DEFAULT CHARSET=latin1;
257
# TABLE: util_test.t3 CREATE TABLE `t3` ( à` int(11) NOT NULL AUTO_INCREMENT, `b` char(30) DEFAULT NULL, PRIMARY KEY (à`) ) ENGINE=InnoDB AUTO_INCREMENT=4 DEFAULT CHARSET=latin1; # TABLE: util_test.t4 CREATE TABLE `t4` ( `c` int(11) NOT NULL, `d` int(11) NOT NULL, KEY `ref_t3` (`c`), CONSTRAINT `ref_t3` FOREIGN KEY (`c`) REFERENCES `t3` (à`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1; # VIEW: util_test.v1 [...] #...done.
Similarly, to export the data of the database util_test, producing bulk insert statements, use this command:
$ mysqldbexport --server=root:pass@localhost \ --export=DATA --bulk-insert util_test # Source on localhost: ... connected. USE util_test; # Exporting data from util_test # Data for table util_test.t1: INSERT INTO util_test.t1 VALUES ('01 Test Basic database example'), ('02 Test Basic database example'), ('03 Test Basic database example'), ('04 Test Basic database example'), ('05 Test Basic database example'), ('06 Test Basic database example'), ('07 Test Basic database example'); # Data for table util_test.t2: INSERT INTO util_test.t2 VALUES ('11 Test Basic database example'), ('12 Test Basic database example'), ('13 Test Basic database example'); # Data for table util_test.t3: INSERT INTO util_test.t3 VALUES (1, '14 test fkeys'), (2, '15 test fkeys'), (3, '16 test fkeys'); # Data for table util_test.t4: INSERT INTO util_test.t4 VALUES (3, 2); #...done.
If the database to be exported does not contain only InnoDB tables and you want to ensure data integrity of the exported data by locking the tables during the read step, add a --locking=lock-all [256] option to the command:
$ mysqldbexport --server=root:pass@localhost \ --export=DATA --bulk-insert util_test --locking=lock-all # Source on localhost: ... connected. USE util_test; # Exporting data from util_test # Data for table util_test.t1: INSERT INTO util_test.t1 VALUES ('01 Test Basic database example'), ('02 Test Basic database example'), ('03 Test Basic database example'), ('04 Test Basic database example'), ('05 Test Basic database example'), ('06 Test Basic database example'), ('07 Test Basic database example'); # Data for table util_test.t2: INSERT INTO util_test.t2 VALUES ('11 Test Basic database example'), ('12 Test Basic database example'), ('13 Test Basic database example');
258
# Data for table util_test.t3: INSERT INTO util_test.t3 VALUES (2, '15 test fkeys'), (3, '16 test fkeys'); # Data for table util_test.t4: INSERT INTO util_test.t4 VALUES #...done.
(1, '14 test fkeys'),
(3, 2);
To export a database and include the replication commands to use the current server as the master (for example, to start a new slave using the current server as the master), use the following command:
$ mysqldbexport --server=root@localhost:3311 util_test \ --export=both --rpl-user=rpl:rpl --rpl=master -v # Source on localhost: ... connected. # # Stopping slave STOP SLAVE; # # Source on localhost: ... connected. # Exporting metadata from util_test DROP DATABASE IF EXISTS util_test; CREATE DATABASE util_test; USE util_test; # TABLE: util_test.t1 CREATE TABLE `t1` ( à` char(30) DEFAULT NULL ) ENGINE=MEMORY DEFAULT CHARSET=latin1; #...done. # Source on localhost: ... connected. USE util_test; # Exporting data from util_test # Data for table util_test.t1: INSERT INTO util_test.t1 VALUES ('01 Test Basic database INSERT INTO util_test.t1 VALUES ('02 Test Basic database INSERT INTO util_test.t1 VALUES ('03 Test Basic database INSERT INTO util_test.t1 VALUES ('04 Test Basic database INSERT INTO util_test.t1 VALUES ('05 Test Basic database INSERT INTO util_test.t1 VALUES ('06 Test Basic database INSERT INTO util_test.t1 VALUES ('07 Test Basic database #...done. # # Connecting to the current server as master CHANGE MASTER TO MASTER_HOST = 'localhost', MASTER_USER = 'rpl', MASTER_PASSWORD = 'rpl', MASTER_PORT = 3311, MASTER_LOG_FILE = 'clone-bin.000001' , MASTER_LOG_POS = 106; # # Starting slave START SLAVE; #
example'); example'); example'); example'); example'); example'); example');
Similarly, to export a database and include the replication commands to use the current servers master (for example, to start a new slave using the same the master), use the following command:
$ mysqldbexport --server=root@localhost:3311 util_test \ --export=both --rpl-user=rpl:rpl --rpl=slave -v # Source on localhost: ... connected. # # Stopping slave STOP SLAVE; # # Source on localhost: ... connected. # Exporting metadata from util_test DROP DATABASE IF EXISTS util_test;
259
mysqldbimport Import Object Definitions or Data into a Database
CREATE DATABASE util_test; USE util_test; # TABLE: util_test.t1 CREATE TABLE `t1` ( à` char(30) DEFAULT NULL ) ENGINE=MEMORY DEFAULT CHARSET=latin1; #...done. # Source on localhost: ... connected. USE util_test; # Exporting data from util_test # Data for table util_test.t1: INSERT INTO util_test.t1 VALUES ('01 Test Basic INSERT INTO util_test.t1 VALUES ('02 Test Basic INSERT INTO util_test.t1 VALUES ('03 Test Basic INSERT INTO util_test.t1 VALUES ('04 Test Basic INSERT INTO util_test.t1 VALUES ('05 Test Basic INSERT INTO util_test.t1 VALUES ('06 Test Basic INSERT INTO util_test.t1 VALUES ('07 Test Basic #...done. # # Connecting to the current server's master CHANGE MASTER TO MASTER_HOST = 'localhost', MASTER_USER = 'rpl', MASTER_PASSWORD = 'rpl', MASTER_PORT = 3310, MASTER_LOG_FILE = 'clone-bin.000001' , MASTER_LOG_POS = 1739; # # Starting slave START SLAVE; #
database database database database database database database
example'); example'); example'); example'); example'); example'); example');
13.3.6. mysqldbimport Import Object Definitions or Data into a Database

This utility imports metadata (object definitions) or data or both for one or more databases from one or more files. If an object exists on the destination server with the same name as an imported object, it is dropped first before importing the new object. To skip objects by type, use the --skip [262] option with a list of the objects to skip. This enables you to extract a particular set of objects, say, for importing only events (by excluding all other types). Similarly, to skip creation of UPDATE statements for BLOB data, specify the --skip-blobs [262] option. To specify the input format, use one of the following values with the --format [261] option. These correspond to the output formats of the mysqldbexport utility: sql (default) Input consists of SQL statements. For definitions, this consists of the appropriate CREATE and GRANT statements. For data, this is an INSERT statement (or bulk insert if the --bulk-insert [261] option is specified). grid Display output in grid or table format like that of the mysql monitor. csv Input is formatted in comma-separated values format. tab
260
Input is formatted in tab-separated format. vertical Display output in single-column format like that of the \G command for the mysql monitor. To indicate that input in csv or tab format does not contain column headers, specify the --noheaders [262] option. To turn off all feedback information, specify the --quiet [262] option. By default, the utility creates each table on the destination server using the same storage engine as the original table. To override this and specify the storage engine to use for all tables created on the destination server, use the --new-storage-engine [262] option. If the destination server supports the new engine, all tables use that engine. To specify the storage engine to use for tables for which the destination server does not support the original storage engine on the source server, use the --default-storage-engine [261] option. The --new-storage-engine [262] option takes precedence over --default-storageengine [261] if both are given. If the --new-storage-engine [262] or --default-storage-engine [261] option is given and the destination server does not support the specified storage engine, a warning is issued and the servers default storage engine setting is used instead. You must provide connection parameters (user, host, password, and so forth) for an account that has the appropriate privileges to access all objects in the operation. For details, see NOTES.
OPTIONS
mysqldbimport accepts the following command-line options: --help Display a help message and exit. --bulk-insert, -b Use bulk insert statements for data. --default-storage-engine=<def_engine> The engine to use for tables if the destination server does not support the original storage engine on the source server. --drop-first, -d Drop each database to be imported if exists before importing anything into it. --dryrun Import the files and generate the statements but do not execute them. This is useful for testing input file validity. --format=<format>, -f<format> Specify the input format. Permitted format values are sql, grid, tab, csv, and vertical. The default is sql.
261
--import=<import_type>, -i<import_type> Specify the import format. Permitted format values are definitions = import only the definitions (metadata) for the objects in the database list, data = import only the table data for the tables in the database list, and both = import the definitions and the data. The default is definitions. If you attempt to import objects into an existing database, the result depends on the import format. If the format is definitions or both, an error occurs unless --drop-first [261] is given. If the format is data, imported table data is added to existing table data. --new-storage-engine=<new_engine> The engine to use for all tables created on the destination server. --no-headers, -h Input does not contain column headers. This option applies only for csv and tab output. --quiet, -q Turn off all messages for quiet execution. --server=<server> Connection information for the server in <user>[:<passwd>]@<host>[:<port>][:<socket>] format. --skip=<skip_objects> Specify objects to skip in the operation as a comma-separated list (no spaces). Permitted values are CREATE_DB, DATA, EVENTS, FUNCTIONS, GRANTS, PROCEDURES, TABLES, TRIGGERS, and VIEWS. --skip-blobs Do not import BLOB data. --skip-rpl Do not execute replication commands. --verbose, -v Specify how much information to display. Use this option multiple times to increase the amount of information. For example, -v = verbose, -vv = more verbose, -vvv = debug. --version Display version information and exit.
NOTES
The login user must have the appropriate permissions to create new objects, access (read) the mysql database, and grant privileges. If a database to be imported already exists, the user must have read permission for it, which is needed to check the existence of objects in the database. Actual privileges needed may differ from installation to installation depending on the security privileges present and whether the database contains certain objects such as views or events and whether binary logging is enabled.
262
mysqldiff Identify Differences Among Database Objects
Some combinations of the options may result in errors during the operation. For example, excluding tables but not views may result in an error when a view is imported. The --new-storage-engine [262] and --default-storage-engine [261] options apply to all destination tables in the operation. For the --format [261] and --import [262] options, the permitted values are not case sensitive. In addition, values may be specified as any unambiguous prefix of a valid value. For example, -format=g [261] specifies the grid format. An error occurs if a prefix matches more than one valid value.
EXAMPLES
To import the metadata from the util_test database to the server on the local host using a file in CSV format, use this command:
$ mysqldbimport --server=root@localhost --import=definitions \ --format=csv data.csv # Source on localhost: ... connected. # Importing definitions from data.csv. #...done.
Similarly, to import the data from the util_test database to the server on the local host, importing the data using bulk insert statements, use this command:
$ mysqldbimport --server=root@localhost --import=data \ --bulk-insert --format=csv data.csv # Source on localhost: ... connected. # Importing data from data.csv. #...done.
To import both data and definitions from the util_test database, importing the data using bulk insert statements from a file that contains SQL statements, use this command:
$ mysqldbimport --server=root@localhost --import=both --bulk-insert --format=sql data.sql # Source on localhost: ... connected. # Importing definitions and data from data.sql. #...done.
13.3.7. mysqldiff Identify Differences Among Database Objects

This utility reads the definitions of objects and compares them using a diff-like method to determine whether they are the same. The utility displays the differences for objects that are not the same. Use the notation db1:db2 to name two databases to compare, or, alternatively just db1 to compare two databases with the same name. The latter case is a convenience notation for comparing same-named databases on different servers. The comparison may be run against two databases of different names on a single server by specifying only the --server1 [265] option. The user can also connect to another server by specifying the -server2 [265] option. In this case, db1 is taken from server1 and db2 from server2. When a database pair is specified, all objects in one database are compared to the corresponding objects in the other. Any objects not appearing in either database produce an error. To compare a specific pair of objects, add an object name to each database name in db.obj format. For example, use db1.obj1:db2.obj2 to compare two named objects, or db1.obj1 to compare an object
263
with the same name in databases with the same name. It is not legal to mix a database name with an object name. For example, db1.obj1:db2 and db1:db2.obj2 are illegal. The comparison may be run against a single server for comparing two databases of different names on the same server by specifying only the --server1 [265] option. Alternatively, you can also connect to another server by specifying the --server2 [265] option. In this case, the first object to compare is taken from server1 and the second from server2. By default, the utilty generates object differences as a difference report. However, you can generate a transformation report containing SQL statements for transforming the objects for conformity instead. Use the sql value for the --difftype [265] option to produce a listing that contains the appropriate ALTER commands to conform the object definitions for the object pairs specified. If a transformation cannot be formed, the utility reports the diff of the object along with a warning statement. See important limitations in the NOTES section. To specify how to display diff-style output, use one of the following values with the --difftype [265] option: unified (default) Display unified format output. context Display context format output. differ Display differ-style format output. sql Display SQL transformation statement output. The --changes-for [265] option controls the direction of the difference (by specifying the object to be transformed) in either the difference report (default) or the transformation report (designated with the -difftype=sql [265] option). Consider the following command:
mysqldiff --server1=root@host1 --server2=root@host2 --difftype=sql \ db1.table1:dbx.table3
The leftmost database (db1) exists on the server designated by the --server1 [265] option (host1). The rightmost database (dbx) exists on the server designated by the --server2 [265] option (host2). --changes-for=server1 [265]: Produce output that shows how to make the definitions of objects on server1 like the definitions of the corresponding objects on server2. --changes-for=server2 [265]: Produce output that shows how to make the definitions of objects on server2 like the definitions of the corresponding objects on server1. The default direction is server1. For sql difference format, you can also see the reverse transformation by specifying the --showreverse [265] option. The utility stops on the first occurrence of missing objects or when an object does not match. To override this behavior, specify the --force [265] option to cause the utility to attempt to compare all objects listed as arguments.
264
OPTIONS
mysqldiff accepts the following command-line options: --help Display a help message and exit. --changes-for=<direction> Specify the server to show transformations to match the other server. For example, to see the transformation for transforming object definitions on server1 to match the corresponding definitions on server2, use --changes-for=server1 [265]. Permitted values are server1 and server2. The default is server1. --difftype=<difftype>, -d<difftype> Specify the difference display format. Permitted format values are unified, context, differ, and sql. The default is unified. --force Do not halt at the first difference found. Process all objects to find all differences. --quiet, -q Do not print anything. Return only an exit code of success or failure. --server1=<source> Connection information for the first server in <user>[:<passwd>]@<host>[:<port>][:<socket>] format. --server2=<source> Connection information for the second server in <user>[:<passwd>]@<host>[:<port>][:<socket>] format. --show-reverse Produce a transformation report containing the SQL statements to conform the object definitions specified in reverse. For example, if --changes-for [265] is set to server1, also generate the transformation for server2. Note: The reverse changes are annotated and marked as comments. --verbose, -v Specify how much information to display. Use this option multiple times to increase the amount of information. For example, -v = verbose, -vv = more verbose, -vvv = debug. --version Display version information and exit. --width=<number> Change the display width of the test report. The default is 75 characters.
NOTES
You must provide connection parameters (user, host, password, and so forth) for an account that has the appropriate privileges to access all objects to be compared.
265
The SQL transformation feature has these known limitations: When tables with partition differences are encountered, the utility generates the ALTER TABLE statement for all other changes but prints a warning and omits the partition differences. If the transformation detects table options in the source table (specified with the --changesfor [265] option) that are not changed or do not exist in the target table, the utility generates the ALTER TABLE statement for all other changes but prints a warning and omits the table option differences. Rename for events is not supported. This is because mysqldiff compares objects by name. In this case, depending on the direction of the diff, the event is identified as needing to be added or a DROP EVENT statement is generated. Changes in the definer clause for events are not supported. SQL extensions specific to MySQL Cluster are not supported. For the --difftype [265] option, the permitted values are not case sensitive. In addition, values may be specified as any unambiguous prefix of a valid value. For example, --difftype=d [265] specifies the differ type. An error occurs if a prefix matches more than one valid value.
EXAMPLES
To compare the employees and emp databases on the local server, use this command:
$ mysqldiff --server1=root@localhost employees:emp1 # server1 on localhost: ... connected. WARNING: Objects in server1:employees but not in server2:emp1: EVENT: e1 Compare failed. One or more differences found. $ mysqldiff --server1=root@localhost \ employees.t1:emp1.t1 employees.t3:emp1.t3 # server1 on localhost: ... connected. # Comparing employees.t1 to emp1.t1 # server1 on localhost: ... connected. # Comparing employees.t3 to emp1.t3 Success. All objects are the same. $ mysqldiff --server1=root@localhost \ employees.salaries:emp1.salaries --differ # server1 on localhost: ... connected. # Comparing employees.salaries to emp1.salaries # Object definitions are not the same: CREATE TABLE `salaries` ( èmp_no` int(11) NOT NULL, `salary` int(11) NOT NULL, `from_date` date NOT NULL, `to_date` date NOT NULL, PRIMARY KEY (èmp_no`,`from_date`), KEY èmp_no` (èmp_no`) - ) ENGINE=InnoDB DEFAULT CHARSET=latin1 ? ^^^^^ + ) ENGINE=MyISAM DEFAULT CHARSET=latin1 ? ++ ^^^ Compare failed. One or more differences found.
[PASS] [PASS]
[FAIL]
The following examples show how to generate a transformation report. Assume the following object definitions: Host1:
266
mysqldiskusage Show Database Disk Usage
CREATE TABLE db1.table1 (num int, misc char(30));
Host2:
CREATE TABLE dbx.table3 (num int, notes char(30), misc char(55));
To generate a set of SQL statements that transform the definition of db1.table1 to dbx.table3, use this command:
$ mysqldiff --server1=root@host1 --server2=root@host2 \ --changes-for=server1 --difftype=sql \ db1.table1:dbx.table3 # server1 on host1: ... connected. # server2 on host2: ... connected. # Comparing db1.table1 to dbx.table3 # Transformation statments: ALTER TABLE db1.table1 ADD COLUMN notes char(30) AFTER a, CHANGE COLUMN misc misc char(55); Compare failed. One or more differences found.
[FAIL]
To generate a set of SQL statements that transform the definition of dbx.table3 to db1.table1, use this command:
$ mysqldiff --server1=root@host1 --server2=root@host2 \ --changes-for=server2 --difftype=sql \ db1.table1:dbx.table3 # server1 on host1: ... connected. # server2 on host2: ... connected. # Comparing db1.table1 to dbx.table3 # Transformation statments: ALTER TABLE dbx.table3 DROP COLUMN notes, CHANGE COLUMN misc misc char(30); Compare failed. One or more differences found.
[FAIL]
To generate a set of SQL statements that transform the definitions of dbx.table3 and db1.table1 in both directions, use this command:
$ mysqldiff --server1=root@host1 --server2=root@host2 \ --show-reverse --difftype=sql \ db1.table1:dbx.table3 # server1 on host1: ... connected. # server2 on host2: ... connected. # Comparing db1.table1 to dbx.table3 # Transformation statments: # --destination=server1: ALTER TABLE db1.table1 ADD COLUMN notes char(30) AFTER a, CHANGE COLUMN misc misc char(55); # --destination=server2: # ALTER TABLE dbx.table3 # DROP COLUMN notes, # CHANGE COLUMN misc misc char(30); Compare failed. One or more differences found.
[FAIL]
13.3.8. mysqldiskusage Show Database Disk Usage

267
This utility displays disk space usage for one or more databases. The utility optionally displays disk usage for the binary log, slow query log, error log, general query log, relay log, and InnoDB tablespaces. The default is to show only database disk usage. If the command line lists no databases, the utility shows the disk space usage for all databases. Sizes displayed without a unit indicator such as MB are in bytes. The utility determines the the location of the data directory by requesting it from the server. For a local server, the utility obtains size information directly from files in the data directory and InnoDB home directory. In this case, you must have file system access to read those directories. Disk space usage shown includes the sum of all storage engine- specific files such as the .MYI and .MYD files for MyISAM and the tablespace files for InnoDB. If the file system read fails, or if the server is not local, the utility cannot determine exact file sizes. It is limited to information that can be obtained from the system tables, which therefore should be considered an estimate. For information read from the server, the account used to connect to the server must have the appropriate permissions to read any objects accessed during the operation. If information requested requires file system access but is not available that way, the utility prints a message that the information is not accessible. This occurs, for example, if you request log usage but the server is not local and the log files cannot be examined directly. To specify how to display output, use one of the following values with the --format [269] option: grid (default) Display output in grid or table format like that of the mysql monitor. csv Display output in comma-separated values format. tab Display output in tab-separated format. vertical Display output in single-column format like that of the \G command for the mysql monitor. To turn off the headers for csv or tab display format, specify the --no-headers [269] option.
OPTIONS
mysqldiskusage accepts the following command-line options: --help Display a help message and exit. --all, -a Display all disk usage. This includes usage for databases, logs, and InnoDB tablespaces. --binlog, -b 268
Display binary log usage. --empty, -m Include empty databases. --format=<format>, -f<format> Specify the output display format. Permitted format values are grid, csv, tab, and vertical. The default is grid. --innodb, -i Display InnoDB tablespace usage. This includes information about the shared InnoDB tablespace as well as .idb files for InnoDB tables with their own tablespace. --logs, -l Display general query log, error log, and slow query log usage. --no-headers, -h Do not display column headers. This option applies only for csv and tab output. --quiet, -q Suppress informational messages. --relaylog, -r Display relay log usage. --server=<server> Connection information for the server in <user>[:<passwd>]@<host>[:<port>][:<socket>] format. --verbose, -v Specify how much information to display. Use this option multiple times to increase the amount of information. For example, -v = verbose, -vv = more verbose, -vvv = debug. --version Display version information and exit. For the --format [269] option, the permitted values are not case sensitive. In addition, values may be specified as any unambiguous prefix of a valid value. For example, --format=g [269] specifies the grid format. An error occurs if a prefix matches more than one valid value.
NOTES
You must provide connection parameters (user, host, password, and so forth) for an account that has the appropriate privileges for all objects accessed during the operation.
EXAMPLES
To show only the disk space usage for the employees and test databases in grid format (the default), use this command:
269
$ mysqldiskusage --server=root@localhost employees test # Source on localhost: ... connected. # Database totals: +------------+--------------+ | db_name | total | +------------+--------------+ | employees | 205,979,648 | | test | 4,096 | +------------+--------------+ Total database disk usage = 205,983,744 bytes or 196.00 MB #...done.
To see all disk usage for the server in CSV format, use this command:
$ mysqldiskusage --server=root@localhost --format=csv -a -vv # Source on localhost: ... connected. # Database totals: db_name,db_dir_size,data_size,misc_files,total test1,0,0,0,0 db3,0,0,0,0 db2,0,0,0,0 db1,0,0,0,0 backup_test,19410,1117,18293,19410 employees,242519463,205979648,242519463,448499111 mysql,867211,657669,191720,849389 t1,9849,1024,8825,9849 test,56162,4096,52066,56162 util_test_a,19625,2048,17577,19625 util_test_b,17347,0,17347,17347 util_test_c,19623,2048,17575,19623 Total database disk usage = 449,490,516 bytes or 428.00 MB # Log information. # The general_log is turned off on the server. # The slow_query_log is turned off on the server. # binary log information: Current binary log file = ./mysql-bin.000076 log_file,size /data/mysql-bin.000076,125 /data/mysql-bin.000077,125 /data/mysql-bin.000078,556 /data/mysql-bin.000079,168398223 /data/mysql-bin.index,76 Total size of binary logs = 168,399,105 bytes or 160.00 MB # Server is not an active slave - no relay log information. # InnoDB tablespace information: InnoDB_file,size,type,specificaton /data/ib_logfile0,5242880,log file, /data/ib_logfile1,5242880,log file, /data/ibdata1,220200960,shared tablespace,ibdata1:210M /data/ibdata2,10485760,shared tablespace,ibdata2:10M:autoextend /data/employees/departments.ibd,114688,file tablespace, /data/employees/dept_emp.ibd,30408704,file tablespace, /data/employees/dept_manager.ibd,131072,file tablespace, /data/employees/employees.ibd,23068672,file tablespace, /data/employees/salaries.ibd,146800640,file tablespace, /data/employees/titles.ibd,41943040,file tablespace, Total size of InnoDB files = 494,125,056 bytes or 471.00 MB #...done.
270
mysqlfailover Automatic replication health monitoring and failover
13.3.9. mysqlfailover Automatic replication health monitoring and failover

This utility permits users to perform replication health monitoring and automatic failover on a replication topology consisting of a master and its slaves. The utility is designed to run interactively or continuously refreshing the health information at periodic intervals. Its primary mission is to monitor the master for failure and when a failure occurs, execute failover to the best slave available. The utility accepts a list of slaves to be considered the candidate slave. This utility is designed to work exclusively for servers that support global transaction identifiers (GTIDs) and have GTID_MODE=ON. MySQL server versions 5.6.5 and higher support GTIDs. See the MySQL server online reference manual for more information about setting up replication with GTIDs enabled. The user can specify the interval in seconds to use for detecting the master status and generating the health report using the --interval [273] option. At each interval, the utility will check to see if the server is alive via a ping operation followed by a check of the connector to detect if the server is still reachable. The ping operation can be controlled with the --ping [274] option (see below). If the master is found to be offline or unreachable, the utility will execute one of the following actions based on the value of the --failover-mode [273] option. auto Execute automatic failover to the list of candidates first and if no slaves are viable, continue to locate a viable candidate from the list of slaves. If no slaves are found to be a viable candidate, the utility will generate and error and exit. Once a candidate is found, the utility will conduct failover to the best slave. The command will test each candidate slave listed for the prerequisites. Once a candidate slave is elected, it is made a slave of each of the other slaves thereby collecting any transactions executed on other slaves but not the candidate. In this way, the candidate becomes the most up-to-date slave. elect This mode is the same as auto except if no candidates specified in the list of candidate slaves are viable, it does not check the remaining slaves and generates and error and exits. fail This mode produces an error and does not failover when the master is downed. This mode is used to provide periodic health monitoring without the failover action taken. For all options that permit specifying multiple servers, the options require a comma-separated list of connection parameters in the following form where the password, port, and socket are optional.:
<*user*>[:<*passwd*>]@<*host*>[:<*port*>][:<*socket*>],
The utility permits users to discover slaves connected to the master. In order to use the discover slaves feature, all slaves must use the report-host and report-port startup variables to specify the correct hostname and ip port of the slave. If these are missing or report the incorrect information, the slaves health may not be reported correctly or the slave may not be listed at all. The discover slaves feature ignores any slaves it cannot connect to. The discover slaves feature is run automatically on each interval. The utility permits the user to specify an external script to execute before and after the switchover and failover commands. The user can specify these with the --exec-before [273] and --execafter [273] options. The return code of the script is used to determine success thus each script must report 0 (success) to be considered successful. If a script returns a value other than 0, the result code is presented in an error message. The utility also permits the user to specify a script to be used for detecting a downed master or an application-level event to trigger failover. This can be specified using the --exec-fail-check [273]
271
option. The return code for the script is used to invoke failover. A return code of 0 indicates failover should not take place. A return code other than 0 indicates failover should take place. This is checked at the start of each interval if a script is supplied. The timeout option is not used in this case and the script is run once at the start of each interval. The utility permits the user to log all actions taken during the commands. The --log [273] option requires a valid path and file name of the file to use for logging operations. The log is active only when this option is specified. The option --log-age [273] specifies the age in days that log entries are kept. The default is seven (7) days. Older entries are automatically deleted from the log file (but only if the -log [273] option is specified). The format of the log file includes the date and time of the event, the level of the event (informational INFO, warning - WARN, error - ERROR, critical failure - CRITICAL), and the message reported by the utility. The interface provides the user with a number of options for displaying additional information. The user can choose to see the replication health report (default), or choose to see the list of GTIDs in use, the UUIDs in use, and if logging is enabled the contents of the log file. Each of these reports is described below. health Display the replication health of the topology. This report is the default view for the interface. By default, this includes the host name, port, role (MASTER or SLAVE) of the server, state of the server (UP = is connected, WARN = not connected but can ping, DOWN = not connected and cannot ping), the GTID_MODE, and health state. The master health state is based on the following; if GTID_MODE=ON, the server must have binary log enabled, and there must exist a user with the REPLICATE SLAVE privilege. The slave health state is based on the following; the IO_THREAD and SQL_THREADS must be running, it must be connected to the master, there are no errors, the slave delay for non-gtid enabled scenarios is not more than the threshold provided by the --max-position [274] and the slave is reading the correct master log file, and slave delay is not more than the --seconds-behind [274] threshold option. At each interval, if the discover slaves option was specified at startup and new slaves are discovered, the health report is refreshed. gtid: Display the master's list of executed GTIDs, contents of the GTID variables; @@GLOBAL.GTID_EXECUTED, @@GLOBAL.GTID_PURGED, and @@GLOBAL.GTID_OWNED. Thus, the user can toggle through four screens by pressing the 'G' key repeatedly. The display will cycle through all four screens restarting after the fourth screen. UUID: Display universally unique identifiers (UUIDs) for all servers. Log: This option is visible only if the --log [273] option is specified. Show the contents of the log file. This can be helpful to see at a later time when failover occurred and the actions or messages recorded at the time. The user interface is designed to match the size of the terminal window in which it is run. A refresh option is provided to permit users to resize their terminal windows or refresh the display at any time. However, the interface will automatically resize to the terminal window on each interval. The interface will display the name of the utility, the masters status including binary log file, position, and filters as well as the date and time of the next interval event. The interface will also permit the user to scroll up or down through a list longer than what the terminal window permits. When a long list is presented, the scroll options become enabled. The user can scroll the list up with the up arrow key and down with the down arrow key.
272
Use the --verbose [274] option to see additional information in the health report and additional messages during failover.
OPTIONS
mysqlfailover accepts the following command-line options: --help Display a help message and exit. --candidates=<candidate slave connections> Connection information for candidate slave servers for failover in the form: <user>[:<passwd>]@<host>[:<port>][:<socket>]. Valid only with failover command. List multiple slaves in comma- separated list. --discover-slaves-login=<user:password> At startup, query master for all registered slaves and use the user name and password specified to connect. Supply the user and password in the form <user>[:<passwd>]. For example, discover=joe:secret will use joe as the user and secret as the password for each discovered slave. --exec-after=<script> Name of script to execute after failover or switchover. Script name may include the path. --exec-before=<script> Name of script to execute before failover or switchover. Script name may include the path. --exec-fail-check=<script> Name of script to execute on each interval to invoke failover. --exec-post-failover=<script> Name of script to execute after failover is complete and the utility has refreshed the health report. --failover-mode=<mode>, -f <mode> Action to take when the master fails. auto = automatically fail to best slave, elect = fail to candidate list or if no candidate meets criteria fail, fail = take no action and stop when master fails. Default = auto. --force Override the registration check on master for multiple instances of the console monitoring the same master. --interval=<seconds>, -i <seconds> Interval in seconds for polling the master for failure and reporting health. Default = 15 seconds. Minimum is 5 seconds. --log=<log_file> Specify a log file to use for logging messages --log-age=<days>
273
Specify maximum age of log entries in days. Entries older than this will be purged on startup. Default = 7 days. --master=<connection> Connection information for the master server in <user>[:<passwd>]@<host>[:<port>][:<socket>] format. --max-position=<position> Used to detect slave delay. The maximum difference between the masters log position and the slaves reported read position of the master. A value greater than this means the slave is too far behind the master. Default = 0. --ping=<number> Number of ping attempts for detecting downed server. Note: on some platforms this is the same as number of seconds to wait for ping to return. --seconds-behind=<seconds> Used to detect slave delay. The maximum number of seconds behind the master permitted before slave is considered behind the master. Default = 0. --slaves=<slave connections> Connection information for slave servers in the form: <user>[:<passwd>]@<host>[:<port>][:<socket>]. List multiple slaves in comma-separated list. --timeout=<seconds> Maximum timeout in seconds to wait for each replication command to complete. For example, timeout for slave waiting to catch up to master. Default = 3. --verbose, -v Specify how much information to display. Use this option multiple times to increase the amount of information. For example, -v = verbose, -vv = more verbose, -vvv = debug. --version Display version information and exit.
NOTES
The login user must have the appropriate permissions to execute SHOW SLAVE STATUS, SHOW MASTER STATUS, and SHOW VARIABLES on the appropriate servers as well as grant the REPLICATE SLAVE privilege. The utility checks permissions for the master, slaves, and candidates at startup. At startup, the console will attempt to register itself with the master. If another console is already registered, and the failover mode is auto or elect, the console will be blocked from running failover. When a console quits, it deregisters itself from the master. If this process is broken, the user may override the registration check by using the --force [273] option.
EXAMPLES
To launch the utility, you must specify at a minimum the --master [274] option and either the -discover-slaves-login [273] option or the --slaves [274] option. The option: option can be
274
used in conjunction with the --slaves [274] option to specify a list of known slaves (or slaves that do not report their host and ip) and to discover any other slaves connected to the master. An example of the user interface and some of the report views are shown in the following examples. Note The "GTID Executed Set" will display the first GTID listed in the SHOW MASTER STATUS view. If there are multiple GTIDs listed, the utility shall display [...] to indicate there are additional GTIDs to view. You can view the complete list of GTIDs on the GTID display screens. The default interface will display the replication health report like the following. In this example the log file is enabled. A sample startup command is shown below:
$ mysqlfailover --master=root@localhost:3331 --discover-slaves-login=root MySQL Replication Monitor and Failover Utility Failover Mode = auto Next Interval = Mon Mar 19 15:56:03 2012 Master Information -----------------Binary Log File Position mysql-bin.000001 571
Binlog_Do_DB
Binlog_Ignore_DB
GTID Executed Set 2A67DE00-2DA1-11E2-A711-00764F2BE90F:1-7 [...] Replication Health Status +------------+-------+---------+--------+------------+---------+ | host | port | role | state | gtid_mode | health | +------------+-------+---------+--------+------------+---------+ | localhost | 3331 | MASTER | UP | ON | OK | | localhost | 3332 | SLAVE | UP | ON | OK | | localhost | 3333 | SLAVE | UP | ON | OK | | localhost | 3334 | SLAVE | UP | ON | OK | +------------+-------+---------+--------+------------+---------+ Q-quit R-refresh H-health G-GTID Lists U-UUIDs L-log entries
Pressing the q key will exit the utility. Pressing the r key will refresh the current display. Pressing the h key will return to the replication health report. If the user presses the g key, the gtid report is shown like the following. The first page shown is the master's executed GTID set:
MySQL Replication Monitor and Failover Utility Failover Mode = auto Next Interval = Mon Mar 19 15:59:33 2012 Master Information -----------------Binary Log File Position mysql-bin.000001 571
Binlog_Do_DB
Binlog_Ignore_DB
GTID Executed Set 2A67DE00-2DA1-11E2-A711-00764F2BE90F:1-7 [...] Master GTID Executed Set +-------------------------------------------+ | gtid | +-------------------------------------------+ | 2A67DE00-2DA1-11E2-A711-00764F2BE90F:1-7 | | 5503D37E-2DB2-11E2-A781-8077D4C14B33:1-3 | +-------------------------------------------+
275
Q-quit R-refresh H-health G-GTID Lists U-UUIDs L-log entries Up|Down-scroll
If the user continues to press the g key, the display will cycle through the three gtid lists. If the list is longer than the screen permits as shown in the example above, the scroll up and down help is also shown. In this case, if the user presses the down arrow, the list will scroll down. If the user presses the u key, the list of UUIDs used in the topology are shown.:
Binlog_Do_DB
Binlog_Ignore_DB
GTID Executed Set 2A67DE00-2DA1-11E2-A711-00764F2BE90F:1-7 [...] UUIDs +------------+-------+---------+---------------------------------------+ | host | port | role | uuid | +------------+-------+---------+---------------------------------------+ | localhost | 3331 | MASTER | 55c65a00-71fd-11e1-9f80-ac64ef85c961 | | localhost | 3332 | SLAVE | 5dd30888-71fd-11e1-9f80-dc242138b7ec | | localhost | 3333 | SLAVE | 65ccbb38-71fd-11e1-9f80-bda8146bdb0a | | localhost | 3334 | SLAVE | 6dd6abf4-71fd-11e1-9f80-d406a0117519 | +------------+-------+---------+---------------------------------------+ Q-quit R-refresh H-health G-GTID Lists U-UUIDs L-log entries
If, once the master is detected as down and failover mode is auto or elect and there are viable candidate slaves, the failover feature will engage automatically and the user will see the failover messages appear. When failover is complete, the interface returns to monitoring replication health after 5 seconds. The following shows an example of failover occurring.:
Failover starting... # Candidate slave localhost:3332 will become the new master. # Preparing candidate for failover. # Creating replication user if it does not exist. # Stopping slaves. # Performing STOP on all slaves. # Switching slaves to new master. # Starting slaves. # Performing START on all slaves. # Checking slaves for errors. # Failover complete. # Discovering slaves for master at localhost:3332 Failover console will restart in 5 seconds.
After the failover event, the new topology is shown in the replication health report.:
Binlog_Do_DB
Binlog_Ignore_DB
GTID Executed Set 2A67DE00-2DA1-11E2-A711-00764F2BE90F:1-7 [...] UUIDs +------------+-------+---------+--------+------------+---------+
276
mysqlindexcheck Identify Potentially Redundant Table Indexes
| host | port | role | state | gtid_mode | health | +------------+-------+---------+--------+------------+---------+ | localhost | 3332 | MASTER | UP | ON | OK | | localhost | 3333 | SLAVE | UP | ON | OK | | localhost | 3334 | SLAVE | UP | ON | OK | +------------+-------+---------+--------+------------+---------+ Q-quit R-refresh H-health G-GTID Lists U-UUIDs L-log entries
If the user presses the l key and the --log [273] option was specified, the interface will show the entries in the log file. Note: example truncated for space allowance.:
Binlog_Do_DB
Binlog_Ignore_DB
GTID Executed Set 2A67DE00-2DA1-11E2-A711-00764F2BE90F:1-7 [...] Log File +-------------------------+----------------------------------------- ... --+ | Date | Entry ... | +-------------------------+----------------------------------------- ... --+ | 2012-03-19 15:55:33 PM | INFO Failover console started. ... | | 2012-03-19 15:55:33 PM | INFO Failover mode = auto. ... | | 2012-03-19 15:55:33 PM | INFO Getting health for master: localhos ... | | 2012-03-19 15:55:33 PM | INFO Master status: binlog: mysql-bin.00 ... | +-------------------------+----------------------------------------- ... --+ Q-quit R-refresh H-health G-GTID Lists U-UUIDs L-log entries Up|Down-scroll\
13.3.10. mysqlindexcheck Identify Potentially Redundant Table Indexes

This utility reads the indexes for one or more tables and identifies duplicate and potentially redundant indexes. To check all tables in a database, specify only the database name. To check a specific table, name the table in db.table format. It is possible to mix database and table names. You can scan tables in any database except the internal databases mysql, INFORMATION_SCHEMA, and performance_schema. Depending on the index type, the utility applies the following rules to compare indexes (designated as idx_a and idx_b): BTREE idx_b is redundant to idx_a if and only if the first n columns in idx_b also appear in idx_a. Order and uniqueness count. HASH idx_a and idx_b are duplicates if and only if they contain the same columns in the same order. Uniqueness counts. SPATIAL idx_a and idx_b are duplicates if and only if they contain the same column (only one column is permitted).
277
FULLTEXT idx_b is redundant to idx_a if and only if all columns in idx_b are included in idx_a. Order counts. To see DROP statements to drop redundant indexes, specify the --show-drops [279] option. To examine the existing indexes, use the --verbose [279] option, which prints the equivalent CREATE INDEX (or ALTER TABLE for primary keys. To display the best or worst nonprimary key indexes for each table, use the --best [278] or -worst [279] option. This causes the output to show the best or worst indexes from tables with 10 or more rows. By default, each option shows five indexes. To override that, provide an integer value for the option. To change the format of the index lists displayed for the --show-indexes [279], --best [278], and --worst [279] options, use one of the following values with the --format [278] option: grid (default) Display output in grid or table format like that of the mysql monitor. csv Display output in comma-separated values format. tab Display output in tab-separated format. sql print SQL statements rather than a list. vertical Display output in single-column format like that of the \G command for the mysql monitor. Note: The --best [278] and --worst [279] lists cannot be printed as SQL statements.
OPTIONS
mysqlindexcheck accepts the following command-line options: --help Display a help message and exit. --best[=<N>] If --stats [279] is given, limit index statistics to the best N indexes. The default value of N is 5 if omitted. --format=<index_format>, -f<index_format> Specify the index list display format for output produced by --stats [279]. Permitted format values are grid, csv, tab, sql, and vertical. The default is grid. --server=<source> Connection information for the server in <user>[:<passwd>]@<host>[:<port>][:<socket>] format.
278
--show-drops, -d Display DROP statements for dropping indexes. --show-indexes, -i Display indexes for each table. --skip, -s Skip tables that do not exist. --stats Show index performance statistics. --verbose, -v Specify how much information to display. Use this option multiple times to increase the amount of information. For example, -v = verbose, -vv = more verbose, -vvv = debug. --version Display version information and exit. --worst[=<N>] If --stats [279] is given, limit index statistics to the worst N indexes. The default value of N is 5 if omitted.
NOTES
You must provide connection parameters (user, host, password, and so forth) for an account that has the appropriate privileges to read all objects accessed during the operation. For the --format [278] option, the permitted values are not case sensitive. In addition, values may be specified as any unambiguous prefix of a valid value. For example, --format=g [278] specifies the grid format. An error occurs if a prefix matches more than one valid value.
EXAMPLES
To check all tables in the employees database on the local server to see the possible redundant and duplicate indexes, use this command:
$ mysqlindexcheck --server=root@localhost employees # Source on localhost: ... connected. # The following indexes are duplicates or redundant \ for table employees.dept_emp: # CREATE INDEX emp_no ON employees.dept_emp (emp_no) USING BTREE # may be redundant or duplicate of: ALTER TABLE employees.dept_emp ADD PRIMARY KEY (emp_no, dept_no) # The following indexes are duplicates or redundant \ for table employees.dept_manager: # CREATE INDEX emp_no ON employees.dept_manager (emp_no) USING BTREE # may be redundant or duplicate of: ALTER TABLE employees.dept_manager ADD PRIMARY KEY (emp_no, dept_no) # The following indexes are duplicates or redundant \ for table employees.salaries: #
279
mysqlmetagrep Search Database Object Definitions
CREATE INDEX emp_no ON employees.salaries (emp_no) USING BTREE # may be redundant or duplicate of: ALTER TABLE employees.salaries ADD PRIMARY KEY (emp_no, from_date) # The following indexes are duplicates or redundant \ for table employees.titles: # CREATE INDEX emp_no ON employees.titles (emp_no) USING BTREE # may be redundant or duplicate of: ALTER TABLE employees.titles ADD PRIMARY KEY (emp_no, title, from_date)
13.3.11. mysqlmetagrep Search Database Object Definitions

This utility searches for objects matching a given pattern on all the servers specified using instances of the --server [282] option. It produces output that displays the matching objects. By default, the first nonoption argument is taken to be the pattern unless the --pattern [282] option is given. If the -pattern [282] option is given, all nonoption arguments are treated as connection specifications. Internally, the utility generates an SQL statement for searching the necessary tables in the INFORMATION_SCHEMA database on the designated servers and executes it in turn before collecting the result and printing it as a table. Use the --sql [282] option to have the utility display the statement rather than execute it. This can be useful if you want to feed the output of the statement to another application such as the mysql monitor. The MySQL server supports two forms of patterns when matching strings: SQL Simple Patterns (used with the LIKE operator) and POSIX Regular Expressions (used with the REGEXP operator). By default, the utility uses the LIKE operator to match the name (and optionally, the body) of objects. To use the REGEXP operator instead, use the --regexp [282] option. Note that since the REGEXP operator does substring searching, it is necessary to anchor the expression to the beginning of the string if you want to match the beginning of the string. To specify how to display output, use one of the following values with the --format [282] option: grid (default) Display output in grid or table format like that of the mysql monitor. csv Display output in comma-separated values format. tab Display output in tab-separated format. vertical Display output in single-column format like that of the \G command for the mysql monitor.
SQL Simple Patterns

The simple patterns defined by the SQL standard consist of a string of characters with two characters that have special meaning: % (percent) matches zero or more characters and _ (underscore) matches exactly one character. For example: 'mats%'
280
Match any string that starts with mats. '%kindahl%' Match any string containing the word kindahl. '%_' Match any string consisting of one or more characters.
POSIX Regular Expressions

POSIX regular expressions are more powerful than the simple patterns defined in the SQL standard. A regular expression is a string of characters, optionally containing characters with special meaning: . Match any character. ^ Match the beginning of a string. $ Match the end of a string. [axy] Match a, x, or y. [a-f] Match any character in the range a to f (that is, a, b, c, d, e, or f). [âxy] Match any character excepta, x, or y. a* Match a sequence of zero or more a. a+ Match a sequence of one or more a. a? Match zero or one a. ab|cd Match ab or cd. a{5} Match five instances of a.
281
a{2,5} Match from two to five instances of a. (abc)+ Match one or more repetitions of abc. This is but a brief set of examples of regular expressions. The full syntax is described in the MySQL manual, but can often be found in regex(7).
OPTIONS
mysqlmetagrep accepts the following command-line options: --help Display a help message and exit. --body, -b Search the body of stored programs (procedures, functions, triggers, and events). The default is to match only the name. --database=<pattern> Look only in databases matching this pattern. --format=<format>, -f<format> Specify the output display format. Permitted format values are grid, csv, tab, and vertical. The default is grid. --object-types=<types>, --search-objects=<types> Search only the object types named in types, which is a comma-separated list of one or more of the values procedure, function, event, trigger, table, and database. The default is to search in objects of all types. --pattern=<pattern>, -e=<pattern> The pattern to use when matching. This is required when the first nonoption argument looks like a connection specification rather than a pattern. If the --pattern [282] option is given, the first nonoption argument is treated as a connection specifier, not as a pattern. --regexp, --basic-regexp, -G Perform pattern matches using the REGEXP operator. The default is to use LIKE for matching. This affects the --database [282] and --pattern [282] options. --server=<source> Connection information for a server to search in <user>[:<passwd>]@<host>[:<port>][:<socket>] format. Use this option multiple times to search multiple servers. --sql, --print-sql, -p
282
mysqlprocgrep Search Server Process Lists
Print rather than executing the SQL code that would be executed to find all matching objects. This can be useful to save the statement for later execution or to use it as input for other programs. --version Display version information and exit.
NOTES
For the --format [282] option, the permitted values are not case sensitive. In addition, values may be specified as any unambiguous prefix of a valid value. For example, --format=g [282] specifies the grid format. An error occurs if a prefix matches more than one valid value.
EXAMPLES
Find all objects with a name that matches the pattern 't_' (the letter t followed by any single character):
$ mysqlmetagrep --pattern="t_" --server=mats@localhost +------------------------+--------------+--------------+-----------+ | Connection | Object Type | Object Name | Database | +------------------------+--------------+--------------+-----------+ | mats:*@localhost:3306 | TABLE | t1 | test | | mats:*@localhost:3306 | TABLE | t2 | test | | mats:*@localhost:3306 | TABLE | t3 | test | +------------------------+--------------+--------------+-----------+
To find all object that contain 't2' in the name or the body (for routines, triggers, and events):
$ mysqlmetagrep -b --pattern="%t2%" --server=mats@localhost:3306 +------------------------+--------------+--------------+-----------+ | Connection | Object Type | Object Name | Database | +------------------------+--------------+--------------+-----------+ | root:*@localhost:3306 | TRIGGER | tr_foo | test | | root:*@localhost:3306 | TABLE | t2 | test | +------------------------+--------------+--------------+-----------+
In the preceding output, the trigger name does not match the pattern, but is displayed because its body does. This is the same as the previous example, but using the REGEXP operator. Note that in the pattern it is not necessary to add wildcards before or after t2:
$ mysqlmetagrep -Gb --pattern="t2" --server=mats@localhost +------------------------+--------------+--------------+-----------+ | Connection | Object Type | Object Name | Database | +------------------------+--------------+--------------+-----------+ | root:*@localhost:3306 | TRIGGER | tr_foo | test | | root:*@localhost:3306 | TABLE | t2 | test | +------------------------+--------------+--------------+-----------+
13.3.12. mysqlprocgrep Search Server Process Lists

This utility scans the process lists for the servers specified using instances of the --server [285] option and selects those that match the conditions specified using the --age [284] and --match-xxx options. For a process to match, all conditions given must match. The utility then either prints the selected processes (the default) or executes certain actions on them. If no --age [284] or --match-xxx options are given, the utility selects all processes.
283
The --match-xxx options correspond to the columns in the INFORMATION_SCHEMA.PROCESSLIST table. For example, --match-command [285] specifies a matching condition for PROCESSLIST.COMMAND column values. There is no --match-time option. To specify a condition based on process time, use --age [284]. Processes that can be seen and killed are subject to whether the account used to connect to the server has the PROCESS and SUPER privileges. Without PROCESS, the account cannot see processes belonging to other accounts Without SUPER, the account cannot kill processes belonging to other accounts To specify how to display output, use one of the following values with the --format [284] option: grid (default) Display output in grid or table format like that of the mysql monitor. csv Display output in comma-separated values format. tab Display output in tab-separated format. vertical Display output in single-column format like that of the \G command for the mysql monitor.
Options
mysqlprocgrep accepts the following command-line options: --help Display a help message and exit. --age=<time> Select only processes that have been in the current state more than a given time. The time value can be specified in two formats: either using the hh:mm:ss format, with hours and minutes optional, or as a sequence of numbers with a suffix giving the period size. The permitted suffixes are s (second), m (minute), h (hour), d (day), and w (week). For example, 4h15m mean 4 hours and 15 minutes. For both formats, the specification can optionally be preceded by + or -, where + means older than the given time, and - means younger than the given time. --format=<format>, -f<format> Specify the output display format. Permitted format values are grid, csv, tab, and vertical. The default is grid. --kill-connection Kill the connection for all matching processes (like the KILL CONNECTION statement). --kill-query
284
Kill the query for all matching processes (like the KILL QUERY statement). --match-command=<pattern> Match all processes where the Command field matches the pattern. --match-db=<pattern> Match all processes where the Db field matches the pattern. --match-host=<pattern> Match all processes where the Host field matches the pattern. --match-info=<pattern> Match all processes where the Info field matches the pattern. --match-state=<pattern> Match all processes where the State field matches the pattern. --match-user=<pattern> Match all processes where the User field matches the pattern. --print Print information about the matching processes. This is the default if no --kill-connection [284] or --kill-query [284] option is given. If a kill option is given, --print [285] prints information about the processes before killing them. --regexp, --basic-regexp, -G Perform pattern matches using the REGEXP operator. The default is to use LIKE for matching. This affects the --match-xxx options. --server=<source> Connection information for a server to search in <user>[:<passwd>]@<host>[:<port>][:<socket>] format. Use this option multiple times to search multiple servers. --sql, --print-sql, -Q Instead of displaying the selected processes, emit the SELECT statement that retrieves information about them. If the --kill-connection [284] or --kill-query [284] option is given, the utility generates a stored procedure named kill_processes() for killing the queries rather than a SELECT statement. --sql-body Like --sql [285], but produces the output as the body of a stored procedure without the CREATE PROCEDURE part of the definition. This could be used, for example, to generate an event for the server Event Manager. When used with a kill option, code for killing the matching queries is generated. Note that it is not possible to execute the emitted code unless it is put in a stored routine, event, or trigger. For example, the following code could be generated to kill all idle connections for user www-data:
285
mysqlreplicate Set Up and Start Replication Between Two Servers
$ mysqlprocgrep --kill-connection --sql-body \ > --match-user=www-data --match-state=sleep DECLARE kill_done INT; DECLARE kill_cursor CURSOR FOR SELECT Id, User, Host, Db, Command, Time, State, Info FROM INFORMATION_SCHEMA.PROCESSLIST WHERE user LIKE 'www-data' AND State LIKE 'sleep' OPEN kill_cursor; BEGIN DECLARE id BIGINT; DECLARE EXIT HANDLER FOR NOT FOUND SET kill_done = 1; kill_loop: LOOP FETCH kill_cursor INTO id; KILL CONNECTION id; END LOOP kill_loop; END; CLOSE kill_cursor;
--verbose, -v Specify how much information to display. Use this option multiple times to increase the amount of information. For example, -v = verbose, -vv = more verbose, -vvv = debug. --version Display version information and exit.
NOTES
For the --format [284] option, the permitted values are not case sensitive. In addition, values may be specified as any unambiguous prefix of a valid value. For example, --format=g [284] specifies the grid format. An error occurs if a prefix matches more than one valid value.
EXAMPLES
For each example, assume that the root user on localhost has sufficient privileges to kill queries and connections. Kill all queries created by user mats that are younger than 1 minute:
mysqlprocgrep --server=root@localhost \ --match-user=mats --age=-1m --kill-query
Kill all connections that have been idle for more than 1 hour:
mysqlprocgrep --server=root@localhost \ --match-command=sleep --age=1h --kill-connection
13.3.13. mysqlreplicate Set Up and Start Replication Between Two Servers

This utility permits an administrator to start replication from one server (the master) to another (the slave). The user provides login information for the slave and connection information for connecting to the master. It is also possible to specify a database to be used to test replication.
286
The utility reports conditions where the storage engines on the master and the slave differ. It also reports a warning if the InnoDB storage engine differs on the master and slave. For InnoDB to be the same, both servers must be running the same type of InnoDB (built-in or the InnoDB Plugin), and InnoDB on both servers must have the same major and minor version numbers and enabled state. By default, the utility issues warnings for mismatches between the sets of storage engines, the default storage engine, and the InnoDB storage engine. To produce errors instead, use the --pedantic [287] option, which requires storage engines to be the same on the master and slave. The -vv option displays any discrepancies between the storage engines and InnoDB values, with or without the --pedantic [287] option. Replication can be started using one of the following strategies. Start from the current position (default) Start replication from the current master binary log file and position. The utility uses the SHOW MASTER STATUS statement to retrieve this information. Start from the beginning Start replication from the first event recorded in the master binary log. To do this, use the --startfrom-beginning [288] option. Start from a binary log file Start replication from the first event in a specific master binary log file. To do this, use the --masterlog-file [287] option. Start from a specific event Start replication from specific event coordinates (specific binary log file and position). To do this, use the --master-log-file [287] and --master-log-pos [287] options.
OPTIONS
mysqlreplicate accepts the following command-line options: --help Display a help message and exit. --master=<master> Connection information for the master server in <user>[:<passwd>]@<host>[:<port>][:<socket>] format. --master-log-file=<master_log_file> Begin replication from the beginning of this master log file. --master-log-pos=<master_log_pos> Begin replication from this position in the master log file. This option is not valid unless --master-logfile [287] is given. --pedantic, -p Fail if both servers do not have the same set of storage engines, the same default storage engine, and the same InnoDB storage engine.
287
--rpl-user=<replication_user> The user and password for the replication user, in name:passwd format. The default is rpl:rpl. --slave=<slave> Connection information for the slave server in <user>[:<passwd>]@<host>[:<port>][:<socket>] format. --start-from-beginning, -b Start replication at the beginning of events logged in the master binary log. This option is not valid unless both --master-log-file [287] and --master-log-pos [287] are given. --test-db=<test_database> The database name to use for testing the replication setup. If this option is not given, no testing is done, only error checking. --verbose, -v Specify how much information to display. Use this option multiple times to increase the amount of information. For example, -v = verbose, -vv = more verbose, -vvv = debug. --version Display version information and exit.
NOTES
The login user for the master server must have the appropriate permissions to grant access to all databases and the ability to create a user account. For example, the user account used to connect to the master must have the WITH GRANT OPTION privilege. The server IDs on the master and slave must be nonzero and unique. The utility reports an error if the server ID is 0 on either server or the same on the master and slave. Set these values before starting this utility.
EXAMPLES
To set up replication between two MySQL instances running on different ports of the same host using the default settings, use this command:
$ mysqlreplicate --master=root@localhost:3306 \ --slave=root@localhost:3307 --rpl-user=rpl:rpl # master on localhost: ... connected. # slave on localhost: ... connected. # Checking for binary logging on master... # Setting up replication... # ...done.
The following command uses --pedantic [287] to ensure that replication between the master and slave is successful if and only if both servers have the same storage engines available, the same default storage engine, and the same InnoDB storage engine:
$ mysqlreplicate --master=root@localhost:3306 \ --slave=root@localhost:3307 --rpl-user=rpl:rpl -vv --pedantic # master on localhost: ... connected. # slave on localhost: ... connected. # master id = 2 # slave id = 99
288
# # # # # # # # # # # #
Checking InnoDB statistics for type and version conflicts. Checking storage engines... Checking for binary logging on master... Setting up replication... Flushing tables on master with read lock... Connecting slave to master... CHANGE MASTER TO MASTER_HOST = [...omitted...] Starting slave... status: Waiting for master to send event error: 0: Unlocking tables on master... ...done.
The following command starts replication from the current position of the master (which is the default):
$ mysqlreplicate --master=root@localhost:3306 \ --slave=root@localhost:3307 --rpl-user=rpl:rpl # master on localhost: ... connected. # slave on localhost: ... connected. # Checking for binary logging on master... # Setting up replication... # ...done.
The following command starts replication from the beginning of recorded events on the master:
$ mysqlreplicate --master=root@localhost:3306 \ --slave=root@localhost:3307 --rpl-user=rpl:rpl \ --start-from-beginning # master on localhost: ... connected. # slave on localhost: ... connected. # Checking for binary logging on master... # Setting up replication... # ...done.
The following command starts replication from the beginning of a specific master binary log file:
$ mysqlreplicate --master=root@localhost:3306 \ --slave=root@localhost:3307 --rpl-user=rpl:rpl \ --master-log-file=my_log.000003 # master on localhost: ... connected. # slave on localhost: ... connected. # Checking for binary logging on master... # Setting up replication... # ...done.
The following command starts replication from specific master binary log coordinates (specific log file and position):
$ mysqlreplicate --master=root@localhost:3306 \ --slave=root@localhost:3307 --rpl-user=rpl:rpl \ --master-log-file=my_log.000001 --master-log-pos=96 # master on localhost: ... connected. # slave on localhost: ... connected. # Checking for binary logging on master... # Setting up replication... # ...done.
RECOMMENDATIONS
You should set read_only=1 in the my.cnf file for the slave to ensure that no accidental data changes, such as INSERT, DELETE, UPDATE, and so forth, are permitted on the slave other than those produced by events read from the master. Use the --pedantic [287] and -vv options for setting up replication on production servers to avoid possible problems with differing storage engines.
289
mysqlrpladmin Administration utility for MySQL replication
13.3.14. mysqlrpladmin Administration utility for MySQL replication

This utility permits users to perform administrative actions on a replication topology consisting of a master and its slaves. The utility is designed to make it easy to recover from planned maintenance of the master or from an event that takes the master offline unexpectedly. The act of taking the master offline intentionally and switching control to another slave is called switchover. In this case, there is no loss of transactions as the master is locked and all slaves are allowed to catch up to the master. Once the slaves have read all events from the master, the master is shutdown and control switched to a slave (in this case called a candidate slave). Recovering from the loss of a downed master is more traumatic and since there is no way to know what transactions the master may have failed to send, the new master (called a candidate slave) must be the slave that is most up-to-date. How this is determined depends on the version of the server (see below). However, it can result in the loss of some transactions that were executed on the downed master but not sent. The utility accepts a list of slaves to be considered the candidate slave. If no slave is found to meet the requirements, the operation will search the list of known slaves. The utility also provides a number of useful commands for managing a replication topology including the following. elect This command is available to only those servers supporting global transaction identifiers (GTIDs), perform best slave election and report best slave to use in the event a switchover or failover is required. Best slave election is simply the first slave to meet the prerequisites. GTIDs are supported in version 5.6.5 and higher. failover This command is available to only those servers supporting GTIDs. Conduct failover to the best slave. The command will test each candidate slave listed for the prerequisites. Once a candidate slave is elected, it is made a slave of each of the other slaves thereby collecting any transactions executed on other slaves but not the candidate. In this way, the candidate becomes the most up-to-date slave. gtid This command is available to only those servers supporting GTIDs. It displays the contents of the GTID variables, @@GLOBAL.GTID_EXECUTED, @@GLOBAL.GTID_PURGED, and @@GLOBAL.GTID_OWNED. The command also displays universally unique identifiers (UUIDs) for all servers. health Display the replication health of the topology. By default, this includes the host name, port, role (MASTER or SLAVE) of the server, state of the server (UP = is connected, WARN = not connected but can ping, DOWN = not connected and cannot ping), the GTID_MODE, and health state. The master health state is based on the following; if GTID_MODE=ON, the server must have binary log enabled, and there must exist a user with the REPLICATE SLAVE privilege. The slave health state is based on the following; the IO_THREAD and SQL_THREADS must be running, it must be connected to the master, there are no errors, the slave delay for non-gtid enabled scenarios is not more than the threshold provided by the --max-position [292] and the slave is reading the correct master log file, and slave delay is not more than the --seconds-behind [293] threshold option. reset Execute the STOP SLAVE and RESET SLAVE commands on all slaves. start Execute the START SLAVE command on all slaves. stop Execute the STOP SLAVE command on all slaves. switchover Perform slave promotion to a specified candidate slave as designated by the --newmaster [292] option. This command is available for both gtid-enabled servers and non-gtid-enabled scenarios.
290
Detection of a downed master is performed as follows. If the connection to the master is lost, wait -timeout [293] seconds and check again. If the master connection is lost and the master cannot be pinged or reconnected, the failover event occurs. For all commands that require specifying multiple servers, the options require a comma-separated list of connection parameters in the following form where the password, port, and socket are optional.:
<*user*>[:<*passwd*>]@<*host*>[:<*port*>][:<*socket*>],
The utility permits users to discover slaves connected to the master. In order to use the discover slaves feature, all slaves must use the report-host and report-port startup variables to specify the correct hostname and ip port of the slave. If these are missing or report the incorrect information, the slaves health may not be reported correctly or the slave may not be listed at all. The discover slaves feature ignores any slaves it cannot connect to. The utility permits the user to demote a master to a slave during the switchover operation. The --demotemaster [292] option tells the utility to, once the new master is established, make the old master a slave of the new master. This permits rotation of the master role among a set of servers. The utility permits the user to specify an external script to execute before and after the switchover and failover commands. The user can specify these with the --exec-before [292] and --execafter [292] options. The return code of the script is used to determine success thus each script must report 0 (success) to be considered successful. If a script returns a value other than 0, the result code is presented in an error message. The utility permits the user to log all actions taken during the commands. The --log [292] option requires a valid path and file name of the file to use for logging operations. The log is active only when this option is specified. The option --log-age [292] specifies the age in days that log entries are kept. The default is seven (7) days. Older entries are automatically deleted from the log file (but only if the -log [292] option is specified). The format of the log file includes the date and time of the event, the level of the event (informational INFO, warning - WARN, error - ERROR, critical failure - CRITICAL), and the message reported by the utility. The utility has a number of options each explained in more detail below. Some of the options are specific to certain commands. Warning messages are issued whenever an option is used that does not apply to the command requested. A brief overview of each command and its options is presented in the following paragraphs. The elect, failover, start, stop, and reset commands require either the --slaves [293] option to list all of the slaves in the topology or the --discover-slaves-login [292] option to provide the user name and password to discover any slaves in the topology that are registered to the master but are not listed in the --slaves [293] option. The options required for the health and gtid commands include the --master [292] option to specify the existing master, and either the --slaves [293] option to list all of the slaves in the topology or the -discover-slaves-login [292] option to provide the user name and password to discover any slaves in the topology that are registered to the master but are not listed in the --slaves [293] option. Use the --verbose [293] option to see additional information in the health report and additional messages during switchover or failover. The options required for switchover include the --master [292] option to specify the existing master, the --new-master [292] option to specify the candidate slave (the slave to become the new master.
291
OPTIONS
mysqlrpladmin accepts the following command-line options: --help Display a help message and exit. --candidates=<candidate slave connections> Connection information for candidate slave servers for failover in the form: <user>[:<passwd>]@<host>[:<port>][:<socket>]. Valid only with failover command. List multiple slaves in comma- separated list. --demote-master Make master a slave after switchover. --discover-slaves-login=<user:password> At startup, query master for all registered slaves and use the user name and password specified to connect. Supply the user and password in the form <user>[:<passwd>]. For example, discover=joe:secret will use joe as the user and secret as the password for each discovered slave. --exec-after=<script> Name of script to execute after failover or switchover. Script name may include the path. --exec-before=<script> Name of script to execute before failover or switchover. Script name may include the path. --format=<format>, -f <format> Display the replication health output in either grid (default), tab, csv, or vertical format. --log=<log_file> Specify a log file to use for logging messages --log-age=<days> Specify maximum age of log entries in days. Entries older than this will be purged on startup. Default = 7 days. --master=<connection> Connection information for the master server in <user>[:<passwd>]@<host>[:<port>][:<socket>] format. --max-position=<position> Used to detect slave delay. The maximum difference between the masters log position and the slaves reported read position of the master. A value greater than this means the slave is too far behind the master. Default = 0. --new-master=<connection> Connection information for the slave to be used to replace the master for switchover in the form: <user>[:<passwd>]@<host>[:<port>][:<socket>]. Valid only with switchover command.
292
--no-health Turn off health report after switchover or failover. --ping=<number> Number of ping attempts for detecting downed server. Note: on some platforms this is the same as number of seconds to wait for ping to return. --quiet, -q Turn off all messages for quiet execution. --seconds-behind=<seconds> Used to detect slave delay. The maximum number of seconds behind the master permitted before slave is considered behind the master. Default = 0. --slaves=<slave connections> Connection information for slave servers in the form: <user>[:<passwd>]@<host>[:<port>][:<socket>]. List multiple slaves in comma-separated list. --timeout=<seconds> Maximum timeout in seconds to wait for each replication command to complete. For example, timeout for slave waiting to catch up to master. Default = 3. Also used to check down status of master. Failover will wait timeout seconds to check master response. If no response, failover event occurs. --verbose, -v Specify how much information to display. Use this option multiple times to increase the amount of information. For example, -v = verbose, -vv = more verbose, -vvv = debug. --version Display version information and exit.
NOTES
The login user must have the appropriate permissions to execute SHOW SLAVE STATUS, SHOW MASTER STATUS, and SHOW VARIABLES on the appropriate servers as well as grant the REPLICATE SLAVE privilege. The utility checks permissions for the master, slaves, and candidates at startup. The --force option cannot be used with the failover command.
EXAMPLES
To perform best slave election for a topology with GTID_MODE=ON (server version 5.6.5 or higher) where all slaves are specified with the --slaves [293] option, run the following command.:
$ mysqlrpladmin --master=root@localhost:3331 \ --slaves=root@localhost:3332,root@localhost:3333,root@localhost:3334 elect # Electing candidate slave from known slaves. # Best slave found is located on localhost:3332. # ...done.
To perform best slave election supplying a candidate list, use the following command.: 293
$ mysqlrpladmin --master=root@localhost:3331 \ --slaves=root@localhost:3332,root@localhost:3333,root@localhost:3334 \ --candidates=root@localhost:3333,root@localhost:3334 elect # Electing candidate slave from candidate list then slaves list. # Best slave found is located on localhost:3332. # ...done.
To perform failover after a master has failed, use the following command.:
$ mysqlrpladmin \ --slaves=root@localhost:3332,root@localhost:3333,root@localhost:3334 \ --candidates=root@localhost:3333,root@localhost:3334 failover # Performing failover. # Candidate slave localhost:3333 will become the new master. # Preparing candidate for failover. # Creating replication user if it does not exist. # Stopping slaves. # Performing STOP on all slaves. # Switching slaves to new master. # Starting slaves. # Performing START on all slaves. # Checking slaves for errors. # Failover complete. # ...done.
To see the replication health of a topology with GTID_MODE=ON (server version 5.6.5 or higher) and discover all slaves attached to the master, run the following command. We use the result of the failover command above.:
$ mysqlrpladmin --master=root@localhost:3333 \ --slaves=root@localhost:3332,root@localhost:3334 health # Getting health for master: localhost:3333. # # Replication Topology Health: +------------+-------+---------+--------+------------+---------+ | host | port | role | state | gtid_mode | health | +------------+-------+---------+--------+------------+---------+ | localhost | 3333 | MASTER | UP | ON | OK | | localhost | 3332 | SLAVE | UP | ON | OK | | localhost | 3334 | SLAVE | UP | ON | OK | +------------+-------+---------+--------+------------+---------+ # ...done.
To view a detailed replication health report but with all of the replication health checks revealed, use the -verbose [293] option as shown below. In this example, we use vertical format to make viewing easier.:
$ mysqlrpladmin --master=root@localhost:3331 \ --slaves=root@localhost:3332,root@localhost:3333,root@localhost:3334 \ --verbose health # Getting health for master: localhost:3331. # Attempting to contact localhost ... Success # Attempting to contact localhost ... Success # Attempting to contact localhost ... Success # Attempting to contact localhost ... Success # # Replication Topology Health: ************************* 1. row ************************* host: localhost port: 3331 role: MASTER state: UP gtid_mode: ON health: OK version: 5.6.5-m8-debug-log master_log_file: mysql-bin.000001 master_log_pos: 571
294
IO_Thread: SQL_Thread: Secs_Behind: Remaining_Delay: IO_Error_Num: IO_Error: ************************* 2. row ************************* host: localhost port: 3332 role: SLAVE state: UP gtid_mode: ON health: OK version: 5.6.5-m8-debug-log master_log_file: mysql-bin.000001 master_log_pos: 571 IO_Thread: Yes SQL_Thread: Yes Secs_Behind: 0 Remaining_Delay: No IO_Error_Num: 0 IO_Error: ************************* 3. row ************************* host: localhost port: 3333 role: SLAVE state: UP gtid_mode: ON health: OK version: 5.6.5-m8-debug-log master_log_file: mysql-bin.000001 master_log_pos: 571 IO_Thread: Yes SQL_Thread: Yes Secs_Behind: 0 Remaining_Delay: No IO_Error_Num: 0 IO_Error: ************************* 4. row ************************* host: localhost port: 3334 role: SLAVE state: UP gtid_mode: ON health: OK version: 5.6.5-m8-debug-log master_log_file: mysql-bin.000001 master_log_pos: 571 IO_Thread: Yes SQL_Thread: Yes Secs_Behind: 0 Remaining_Delay: No IO_Error_Num: 0 IO_Error: 4 rows. # ...done.
To run the same failover command above, but specify a log file, use the following command.:
$ mysqlrpladmin \ --slaves=root@localhost:3332,root@localhost:3333,root@localhost:3334 \ --candidates=root@localhost:3333,root@localhost:3334 \ --log=test_log.txt failover # Performing failover. # Candidate slave localhost:3333 will become the new master. # Preparing candidate for failover. # Creating replication user if it does not exist.
295
# # # # # # # #
Stopping slaves. Performing STOP on all slaves. Switching slaves to new master. Starting slaves. Performing START on all slaves. Checking slaves for errors. Failover complete. ...done.
After this command, the log file will contain entries like the following:
2012-03-19 2012-03-19 2012-03-19 2012-03-19 2012-03-19 2012-03-19 2012-03-19 2012-03-19 2012-03-19 2012-03-19 2012-03-19 2012-03-19 2012-03-19 14:44:17 14:44:17 14:44:17 14:44:17 14:44:19 14:44:19 14:44:19 14:44:19 14:44:20 14:44:20 14:44:20 14:44:21 14:44:21 PM PM PM PM PM PM PM PM PM PM PM PM PM INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO INFO Executing failover command... Performing failover. Candidate slave localhost:3333 will become the new master. Preparing candidate for failover. Creating replication user if it does not exist. Stopping slaves. Performing STOP on all slaves. Switching slaves to new master. Starting slaves. Performing START on all slaves. Checking slaves for errors. Failover complete. ...done.
To perform switchover and demote the current master to a slave, use the following command.:
$ mysqlrpladmin --master=root@localhost:3331 \ --slaves=root@localhost:3332,root@localhost:3333,root@localhost:3334 \ --new-master=root@localhost:3332 --demote-master switchover # Performing switchover from master at localhost:3331 to slave at localhost:3332. # Checking candidate slave prerequisites. # Waiting for slaves to catch up to old master. # Stopping slaves. # Performing STOP on all slaves. # Demoting old master to be a slave to the new master. # Switching slaves to new master. # Starting all slaves. # Performing START on all slaves. # Checking slaves for errors. # Switchover complete. # ...done.
If the replication health report is generated on the topology following the above command, it will display the old master as a slave as shown below.:
# Replication Topology Health: +------------+-------+---------+--------+------------+---------+ | host | port | role | state | gtid_mode | health | +------------+-------+---------+--------+------------+---------+ | localhost | 3332 | MASTER | UP | ON | OK | | localhost | 3331 | SLAVE | UP | ON | OK | | localhost | 3333 | SLAVE | UP | ON | OK | | localhost | 3334 | SLAVE | UP | ON | OK | +------------+-------+---------+--------+------------+---------+
To use the discover slaves feature, you can omit the --slaves [293] option if and only if all slaves report their host and port to the master. A sample command to generate a replication health report with discovery is shown below. he option: option can be used in conjunction with the --slaves [293] option to specify a list of known slaves (or slaves that do not report their host and ip) and to discover any other slaves connected to the master.:
$ mysqlrpladmin --master=root@localhost:3332 --discover-slaves-login=root # Discovering slaves for master at localhost:3332 # Getting health for master: localhost:3332. health
296
mysqlrplcheck Check Replication Prerequisites
# # Replication Topology Health: +------------+-------+---------+--------+------------+---------+ | host | port | role | state | gtid_mode | health | +------------+-------+---------+--------+------------+---------+ | localhost | 3332 | MASTER | UP | ON | OK | | localhost | 3331 | SLAVE | UP | ON | OK | | localhost | 3333 | SLAVE | UP | ON | OK | | localhost | 3334 | SLAVE | UP | ON | OK | +------------+-------+---------+--------+------------+---------+ # ...done.
13.3.15. mysqlrplcheck Check Replication Prerequisites

This utility checks the prerequisites for replication between a master and a slave. These checks (called tests) are designed to ensure a healthy replication setup. The utility performs the following tests: 1. Is the binary log enabled on the master? 2. Are there binary logging exceptions (such as *_do_db or *_ignore_db settings)? If so, display them. 3. Does the replication user exist on the master with the correct privileges? 4. Are there server_id conflicts? 5. Is the slave connected to this master? If not, display the master host and port. 6. Are there conflicts between the master.info file on the slave and the values shown in SHOW SLAVE STATUS on the master? 7. Are the InnoDB configurations compatible (plugin vs. native)? 8. Are the storage engines compatible (have same on slave as master)? 9. Are the lower_case_tables_names settings compatible? Warn if there are settings for lowercase/ uppercase table names that can cause problems. See Bug #59240. 10. Is the slave behind the master? The utility runs each test in turn unless there is a fatal error preventing further testing, such as a loss of connection to the servers. Each test can complete with one of the following states: pass (the prerequisites are met), fail (the prerequisites were met but one or more errors occurred or there are exceptions to consider), or warn (the test found some unusual settings that should be examined further but may not be in error). Use the --verbose [298] option to see additional information such as server IDs, lower_case_table_name settings, and the contents of the master information file on the slave. To see the values from the SHOW SLAVE STATUS statement, use the --show-slave-status [298] option.
OPTIONS
mysqlrplcheck accepts the following command-line options: --help Display a help message and exit.
297
--master=<source> Connection information for the master server in <user>[:<passwd>]@<host>[:<port>][:<socket>] format. --master-info-file=<file> The name of the master information file on the slave. The default is master.info read from the data directory. Note: This option requires that you run the utility on the slave and that you have appropriate read access for the file. --quiet, -q Turn off all messages for quiet execution. Note: Errors and warnings are not suppressed. --show-slave-status, -s Display the values from SHOW SLAVE STATUS on the master. --slave=<source> Connection information for the slave server in <user>[:<passwd>]@<host>[:<port>][:<socket>] format. --suppress Suppress warning messages. --verbose, -v Specify how much information to display. Use this option multiple times to increase the amount of information. For example, -v = verbose, -vv = more verbose, -vvv = debug. --version Display version information and exit. --width=<number> Change the display width of the test report. The default is 75 characters.
NOTES
The login user must have the appropriate permissions to execute SHOW SLAVE STATUS, SHOW MASTER STATUS, and SHOW VARIABLES on the appropriate servers.
EXAMPLES
To check the prerequisites of a master and slave that currently are actively performing replication, use the following command:
$ mysqlrplcheck --master=root@host1:3310 --slave=root@host2:3311 # master on host1: ... connected. # slave on host2: ... connected. Test Description Status -----------------------------------------------------------------------Checking for binary logging on master [pass] Are there binlog exceptions? [pass] Replication user exists? [pass] Checking server_id values [pass] Is slave connected to master? [pass] Check master information file [pass]
298
Checking InnoDB compatibility Checking storage engines compatibility Checking lower_case_table_names settings Checking slave delay (seconds behind master) # ...done.
[pass] [pass] [pass] [pass]
As shown in the example, you must provide valid login information for both the master and the slave. To perform the same command but also display the contents of the master information file on the slave and the values of SHOW SLAVE STATUS as well as additional details, use this command:
$ mysqlrplcheck --master=root@host1:3310 --slave=root@host2:3311 \ --show-slave-status -vv # master on host1: ... connected. # slave on host2: ... connected. Test Description Status -----------------------------------------------------------------------Checking for binary logging on master [pass] Are there binlog exceptions? [pass] Replication user exists? [pass] Checking server_id values [pass] master id = 10 slave id = 11 Is slave connected to master? Check master information file # # Master information file: # Master_Log_File Read_Master_Log_Pos Master_Host Master_User Master_Password Master_Port Connect_Retry Master_SSL_Allowed Master_SSL_CA_File Master_SSL_CA_Path Master_SSL_Cert Master_SSL_Cipher Master_SSL_Key Master_SSL_Verify_Server_Cert [pass] [pass]
: : : : : : : : : : : : : :
clone-bin.000001 482 host1 rpl XXXX 3310 60 0
0 [pass] [pass] [pass]
Checking InnoDB compatibility Checking storage engines compatibility Checking lower_case_table_names settings Master lower_case_table_names: 2 Slave lower_case_table_names: 2 Checking slave delay (seconds behind master) # # Slave status: # Slave_IO_State Master_Host Master_User Master_Port Connect_Retry Master_Log_File Read_Master_Log_Pos Relay_Log_File Relay_Log_Pos : : : : : : : : : Waiting for master to send event host1 rpl 3310 60 clone-bin.000001 482 clone-relay-bin.000006 251
[pass]
299
mysqlrplshow Show Slaves for Master Server
Relay_Master_Log_File Slave_IO_Running Slave_SQL_Running Replicate_Do_DB Replicate_Ignore_DB Replicate_Do_Table Replicate_Ignore_Table Replicate_Wild_Do_Table Replicate_Wild_Ignore_Table Last_Errno Last_Error Skip_Counter Exec_Master_Log_Pos Relay_Log_Space Until_Condition Until_Log_File Until_Log_Pos Master_SSL_Allowed Master_SSL_CA_File Master_SSL_CA_Path Master_SSL_Cert Master_SSL_Cipher Master_SSL_Key Seconds_Behind_Master Master_SSL_Verify_Server_Cert Last_IO_Errno Last_IO_Error Last_SQL_Errno Last_SQL_Error # ...done.
: : : : : : : : : : : : : : : : : : : : : : : : : : : : :
clone-bin.000001 Yes Yes
0 0 482 551 None 0 No
0 No 0 0
13.3.16. mysqlrplshow Show Slaves for Master Server

This utility shows the replication slaves for a master. It prints a graph of the master and its slaves labeling each with the host name and port number. To explore the slaves for each client, use the --recurse [302] option. This causes the utility to connect to each slave found and attempt to determine whether it has any slaves. If slaves are found, the process continues until the slave is found in the list of servers serving as masters (a circular topology). The graph displays the topology with successive indents. A notation is made for circular topologies. If you use the --recurse [302] option, the utility attempts to connect to the slaves using the user name and password provided for the master. By default, if the connection attempt fails, the utility throws an error and stops. To change this behavior, use the --prompt [302] option, which permits the utility to prompt for the user name and password for each slave that fails to connect. You can also use the --numretries=n [301] option to reattempt a failed connection n times before the utility fails. An example graph for a typical topology with relay slaves is shown here:
# Replication Topology Graph:: localhost:3311 (MASTER) | +--- localhost:3310 - (SLAVE) | +--- localhost:3312 - (SLAVE + MASTER) | +--- localhost:3313 - (SLAVE)
MASTER, SLAVE, and SLAVE+MASTER indicate that a server is a master only, slave only, and both slave and master, respectively. A circular replication topology is shown like this, where <--> indicates circularity:
300
# Replication Topology Graph localhost:3311 (MASTER) | +--- localhost:3312 - (SLAVE + MASTER) | +--- localhost:3313 - (SLAVE + MASTER) | +--- localhost:3311 <--> (SLAVE)
To produce a column list in addition to the graph, specify the --show-list [302] option. In this case, to specify how to display the list, use one of the following values with the --format [301] option: grid (default) Display output in grid or table format like that of the mysql monitor. csv Display output in comma-separated values format. tab Display output in tab-separated format. vertical Display output in single-column format like that of the \G command for the mysql monitor. The utility uses of the SHOW SLAVE HOSTS statement to determine which slaves the master has. If you want to use the --recurse [302] option, slaves should have been started with the --report-host and --report-port options set to their actual host name and port number or the utility may not be able to connect to the slaves to determine their own slaves.
OPTIONS
mysqlrplshow accepts the following command-line options: --help Display a help message and exit. --format=<format>, -f<format> Specify the display format for column list output. Permitted format values are grid, csv, tab, and vertical. The default is grid. This option applies only if --show-list [302] is given. --master=<source> Connection information for the master server in <user>[:<passwd>]@<host>[:<port>][:<socket>] format. --max-depth=<N> The maximum recursion depth. This option is valid only if --recurse [302] is given. --num-retries=<num_retries>, -n<num_retries> The number of retries permitted for failed slave login attempts. This option is valid only if -prompt [302] is given. 301
--prompt, -p Prompt for the slave user and password if different from the master user and password. If you give this option, the utility sets --num-retries [301] to 1 if that option is not set explicitly. This ensures at least one attempt to retry and prompt for the user name and password should a connection fail. --quiet, -q Turn off all messages for quiet execution. This option does not suppress errors or warnings. --recurse, -r Traverse the list of slaves to find additional master/slave connections. User this option to map a replication topology. --show-list, -l Display a column list of the topology. --version Display version information and exit.
NOTES
The login user must have the REPLICATE SLAVE and REPLICATE CLIENT privileges to successfully execute this utility. Specifically, the login user must have appropriate permissions to execute SHOW SLAVE STATUS, SHOW MASTER STATUS, and SHOW SLAVE HOSTS. For the --format [301] option, the permitted values are not case sensitive. In addition, values may be specified as any unambiguous prefix of a valid value. For example, --format=g [301] specifies the grid format. An error occurs if a prefix matches more than one valid value.
EXAMPLES
To show the slaves for a master running on port 3311 on the local host, use the following command:
$ mysqlrplshow --master=root@localhost:3311 # master on localhost: ... connected. # Finding slaves for master: localhost:3311 # Replication Topology Graph localhost:3311 (MASTER) | +--- localhost:3310 - (SLAVE) | +--- localhost:3312 - (SLAVE)
As shown in the example, you must provide valid login information for the master. To show the full replication topology of a master running on the local host, use the following command:
$ mysqlrplshow --master=root@localhost:3311 --recurse # master on localhost: ... connected. # Finding slaves for master: localhost:3311 # Replication Topology Graph localhost:3311 (MASTER)
302
mysqlserverclone Clone Existing Server to Create New Server
| +--- localhost:3310 - (SLAVE) | +--- localhost:3312 - (SLAVE + MASTER) | +--- localhost:3313 - (SLAVE)
To show the full replication topology of a master running on the local host, prompting for the user name and password for slaves that do not have the same user name and password credentials as the master, use the following command:
$ mysqlrplshow --recurse --prompt --num-retries=1 \ --master=root@localhost:3331 Server localhost:3331 is running on localhost. # master on localhost: ... connected. # Finding slaves for master: localhost:3331 Server localhost:3332 is running on localhost. # master on localhost: ... FAILED. Connection to localhost:3332 has failed. Please enter the following information to connect to this server. User name: root Password: # master on localhost: ... connected. # Finding slaves for master: localhost:3332 Server localhost:3333 is running on localhost. # master on localhost: ... FAILED. Connection to localhost:3333 has failed. Please enter the following information to connect to this server. User name: root Password: # master on localhost: ... connected. # Finding slaves for master: localhost:3333 Server localhost:3334 is running on localhost. # master on localhost: ... FAILED. Connection to localhost:3334 has failed. Please enter the following information to connect to this server. User name: root Password: # master on localhost: ... connected. # Finding slaves for master: localhost:3334 # Replication Topology Graph localhost:3331 (MASTER) | +--- localhost:3332 - (SLAVE) | +--- localhost:3333 - (SLAVE + MASTER) | +--- localhost:3334 - (SLAVE)
13.3.17. mysqlserverclone Clone Existing Server to Create New Server

This utility permits an administrator to clone an existing MySQL server instance to start a new server instance on the same host. The utility creates a new datadir (--new-data [304]), and starts the server with a socket file. You can optionally add a password for the login user account on the new instance.
OPTIONS
mysqlserverclone accepts the following command-line options: --help Display a help message and exit.
303
mysqlserverclone Clone Existing Server to Create New Server
--mysqld=<options> Additional options for mysqld. To specify multiple options, separate them by spaces. Use appropriate quoting as necessary. For example, to specify --log-bin=binlog and --general-logfile="mylogfile", use:
--mysqld="--log-bin=binlog --general-log-file='my log file'"
--new-data=<path_to_new_datadir> The full path name of the location of the data directory for the new server instance. If the directory does not exist, the utility will create it. --new-id=<server_id> The server_id value for the new server instance. The default is 2. --new-port=<port> The port number for the new server instance. The default is 3307. --quiet, -q Turn off all messages for quiet execution. --root-password=<password> The password for the root user of the new server instance. --server=<source> Connection information for the server to be cloned in <user>[:<passwd>]@<host>[:<port>][:<socket>] format. --verbose, -v Specify how much information to display. Use this option multiple times to increase the amount of information. For example, -v = verbose, -vv = more verbose, -vvv = debug. --version Display version information and exit. --write-command=<file_name>, -w<file_name> Path name of file in which to write the command used to launch the new server instance.
EXAMPLES
The following command demonstrates how to create a new instance of a running server, set the root user password and enable binary logging:
$ mkdir /source/test123 $ mysqlserverclone --server=root:pass@localhost \ --new-data=/Users/cbell/source/test123 --new-port=3310 \ --root-password=pass --mysqld=--log-bin=mysql-bin # Cloning the MySQL server running on localhost. # Creating new data directory... # Configuring new instance... # Locating mysql tools...
304
mysqlserverinfo Display Common Diagnostic Information from a Server
# # # # # #
Setting up empty database and mysql tables... Starting new instance of the server... Testing connection to new instance... Success! Setting the root password... ...done.
13.3.18. mysqlserverinfo Display Common Diagnostic Information from a Server

This utility displays critical information about a server for use in diagnosing problems. The information displayed includes the following: Server connection information Server version number Data directory path name Base directory path name Plugin directory path name Configuration file location and name Current binary log coordinates (file name and position) Current relay log coordinates (file name and position) This utility can be used to see the diagnostic information for servers that are running or offline. If you want to see information about an offline server, the utility starts the server in read-only mode. In this case, you must specify the --basedir [306], --datadir [306], and --start [306] options to prevent the utility from starting an offline server accidentally. Note: Be sure to consider the ramifications of starting an offline server on the error and similar logs. It is best to save this information prior to running this utility. To specify how to display output, use one of the following values with the --format [306] option: grid (default) Display output in grid or table format like that of the mysql monitor. csv Display output in comma-separated values format. tab Display output in tab-separated format. vertical Display output in single-column format like that of the \G command for the mysql monitor. To turn off the headers for csv or tab display format, specify the --no-headers [306] option. To see the common default settings for the local servers configuration file, use the --showdefaults [306] option. This option reads the configuration file on the machine where the utility is run, not the machine for the host that the --server [306] option specifies.
305
mysqlserverinfo Display Common Diagnostic Information from a Server
To run the utility against several servers, specify the --server [306] option multiple times. In this case, the utility attempts to connect to each server and read the information. To see the MySQL servers running on the local machine, use the --show-servers [306] option. This shows all the servers with their process ID and data directory. On Windows, the utility shows only the process ID and port.
OPTIONS
mysqlserverinfo accepts the following command-line options: --help Display a help message and exit. --basedir=<basedir> The base directory for the server. This option is required for starting an offline server. --datadir=<datadir> The data directory for the server. This option is required for starting an offline server. --format=<format>, -f<format> Specify the output display format. Permitted format values are grid, csv, tab, and vertical. The default is grid. --no-headers, -h Do not display column headers. This option applies only for csv and tab output. --port-range=<start:end> The port range to check for finding running servers. This option applies only to Windows and is ignored unless --show-servers [306] is given. The default range is 3306:3333. --server=<server> Connection information for a server in <user>[:<passwd>]@<host>[:<port>][:<socket>] format. Use this option multiple times to see information for multiple servers. --show-defaults, -d Display default settings for mysqld from the local configuration file. It uses my_print_defaults to obtain the options. --show-servers Display information about servers running on the local host. The utility examines the host process list to determine which servers are running. --start, -s Start the server in read-only mode if it is offline. With this option, you must also give the -basedir [306] and --datadir [306] options. --verbose, -v
306
mysqluserclone Clone Existing User to Create New User
Specify how much information to display. Use this option multiple times to increase the amount of information. For example, -v = verbose, -vv = more verbose, -vvv = debug. --version Display version information and exit. For the --format [306] option, the permitted values are not case sensitive. In addition, values may be specified as any unambiguous prefix of a valid value. For example, --format=g [306] specifies the grid format. An error occurs if a prefix matches more than one valid value.
EXAMPLES
To display the server information for the local server and the settings for mysqld in the configuration file with the output in a vertical list, use this command:
$ mysqlserverinfo --server=root:pass@localhost -d --format=vertical # Source on localhost: ... connected. ************************* 1. row ************************* server: localhost:3306 version: 5.1.50-log datadir: /usr/local/mysql/data/ basedir: /usr/local/mysql-5.1.50-osx10.6-x86_64/ plugin_dir: /usr/local/mysql-5.1.50-osx10.6-x86_64/lib/plugin config_file: /etc/my.cnf binary_log: my_log.000068 binary_log_pos: 212383 relay_log: None relay_log_pos: None 1 rows. Defaults for server localhost:3306 --port=3306 --basedir=/usr/local/mysql --datadir=/usr/local/mysql/data --server_id=5 --log-bin=my_log --general_log --slow_query_log --innodb_data_file_path=ibdata1:778M;ibdata2:50M:autoextend #...done.
13.3.19. mysqluserclone Clone Existing User to Create New User

This utility uses an existing MySQL user account on one server as a template, and clones it to create one or more new user accounts with the same privileges as the original user. The new users can be created on the original server or a different server. To list users for a server, specify the --list [308] option. This prints a list of the users on the source (no destination is needed). To control how to display list output, use one of the following values with the -format [308] option: grid (default) Display output in grid or table format like that of the mysql monitor. csv Display output in comma-separated values format. tab
307
mysqluserclone Clone Existing User to Create New User
Display output in tab-separated format. vertical Display output in single-column format like that of the \G command for the mysql monitor.
OPTIONS
mysqluserclone accepts the following command-line options: --help Display a help message and exit. --destination=<destination> Connection information for the destination server in <user>[:<passwd>]@<host>[:<port>][:<socket>] format. --dump, -d Display the GRANT statements to create the account rather than executing them. In this case, the utility does not connect to the destination server and no --destination [308] option is needed. --format=<list_format>, -f<list_format> Specify the user display format. Permitted format values are grid, csv, tab, and vertical. The default is grid. This option is valid only if --list [308] is given. --force Drop the new user account if it exists before creating the new account. Without this option, it is an error to try to create an account that already exists. --include-global-privileges Include privileges that match base_user@% as well as base_user@host. --list List all users on the source server. With this option, a destination server need not be specified. --quiet, -q Turn off all messages for quiet execution. --source=<source> Connection information for the source server in <user>[:<passwd>]@<host>[:<port>][:<socket>] format. --verbose, -v Specify how much information to display. Use this option multiple times to increase the amount of information. For example, -v = verbose, -vv = more verbose, -vvv = debug. --version Display version information and exit.
308
mysqluc Command line client for running MySQL Utilities
NOTES
You must provide connection parameters (user, host, password, and so forth) for an account that has the appropriate privileges to access all objects in the operation. The account used to connect to the source server must have privileges to read the mysql database. The account used to connect to the destination server must have privileges to execute CREATE USER (and DROP USER if the --force [308] option is given), and privileges to execute GRANT for all privileges to be granted to the new accounts. For the --format [308] option, the permitted values are not case sensitive. In addition, values may be specified as any unambiguous prefix of a valid value. For example, --format=g [308] specifies the grid format. An error occurs if a prefix matches more than one valid value.
EXAMPLES
To clone joe as sam and sally with passwords and logging in as root on the local machine, use this command:
$ mysqluserclone --source=root@localhost \ --destination=root@localhost \ joe@localhost sam:secret1@localhost sally:secret2@localhost # Source on localhost: ... connected. # Destination on localhost: ... connected. # Cloning 2 users... # Cloning joe@localhost to user sam:secret1@localhost # Cloning joe@localhost to user sally:secret2@localhost # ...done.
The following command shows all users on the local server in the most verbose output in CSV format:
$ mysqluserclone --source=root@localhost --list --format=csv -vvv # Source on localhost: ... connected. user,host,database joe,localhost,util_test rpl,localhost, sally,localhost,util_test sam,localhost,util_test joe,user,util_test
13.3.20. mysqluc Command line client for running MySQL Utilities

The mysqluc utility provides a command line environment for running MySQL Utilities, and exists as of MySQL Utilities 1.1.0. The mysqluc utility, hence console, allows users to execute any of the currently installed MySQL Utilities command. The option is used to provide a path to the MySQL Utilities if the location is different from when the utility is executed. The console has a list of console or base commands. These allow the user to interact with the features of the console itself. The list of base commands is shown below along with a brief description.:
Command ---------------------help utilities help <utility> help | help commands exit | quit set <variable>=<value> show options Description --------------------------------------------------Display list of all utilities supported. Display help for a specific utility. Show this list. Exit the console. Store a variable for recall in commands. Display list of options specified by the user on
309
show variables <ENTER> <ESCAPE> <DOWN> <UP> <TAB> <TAB><TAB>
launch. Display list of variables. Press ENTER to execute command. Press ESCAPE to clear the command entry. Press DOWN to retrieve the previous command. Press UP to retrieve the next command in history. Press TAB for type completion of utility, option, or variable names. Press TAB twice for list of matching type completion (context sensitive).
One of the most helpful base commands is the ability to see the options for a given utility by typing 'help <utility>'. When the user types this command and presses ENTER, the console will display a list of all of the options for the utility. The console provides tab completion for all commands, options for utilities, and user-defined variables. Tab completion for commands allows users to specify the starting N characters of a command and press TAB to complete the command. If there are more than one command that matches the prefix, and the user presses TAB twice, a list of all possible matches is displayed. Tab completion for options is similar. The user must first type a valid MySQL Utility command then types the first N characters of a command and presses TAB, for example verb<TAB>. In this case, the console will complete the option. For the cases where an option requires a value, the console will complete the option name and append the '=' character. Tab completion for options works for both the full name and the alias (if available). If the user presses TAB twice, the console will display a list of matching options. Pressing TAB twice immediately after typing the name of a MySQL Utility will display a list of all options for that utility. Tab completion for variables works the same as that for options. In this case, the user must first type the '$' character then press TAB. For example, if a variable $SERVER1 exists, when the user types server= $SER<TAB>, the console will complete the $SERVER variable name. For cases where there are multiple variables, pressing TAB twice will display a list of all matches to the first $+N characters. Pressing TAB twice after typing only the $ character will display a list of all variables. Note: the console does not require typing the 'mysql' prefix for the utility. For example, if the user types 'disku<TAB>' the console will complete the command with 'diskusage '. Executing utilities is accomplished by typing the complete command and pressing ENTER. The user does not have to type 'python' or provide the '.py' file extension. The console will add these if neeeded. The user can also run commands using the option. The value for this option is a semi-colon separated list of commands to execute. These can be base commands or MySQL Utility commands. The console will execute each command and display the output. All commands to be run by the console must appear inside a quoted string and separated by semi-colons. Commands outside of the quoted string will be treated as arguments for the mysqluc utility itself and thus ignored for execution. Note: if there is an error in the console or related code, the console will stop executing commands at the point of failure. Commands may also be piped into the console using a mechanism like 'echo <commands> | mysqluc. The console also allows users to set user-defined variables for commonly used values in options. The syntax is simply 'set VARNAME=VALUE'. The user can see a list of all variables by entering the 'show variables' command. To use the values of these variables in utility commands, the user must prefix the value with a '$'. For example, server=$SERVER1 will substitute the value of the SERVER1 user-defined variable when the utility is executed. Note: user-defined variables have a session lifetime. They are not saved from one execution to another of the users console.
310
User-defined variables may also be set by passing them as arguments to the mysqluc command. For example, to set the SERVER1 variable and launch the console, the user can launch the console using this command.:
$ mysqluc SERVER1=root@localhost
The user can provide any number of user-defined variables but they must contain a value and no spaces around the '=' character. Once the console is launched, the user can see all variables using the 'show variables' command.
OPTIONS
--version show program's version number and exit --help show the program's help page --verbose, -v control how much information is displayed. For example, -v = verbose, -vv = more verbose, -vvv = debug --quiet suppress all informational messages --execute <commands>, -e <commands> Execute commands and exit. Multiple commands are separated with semi-colons. Note: some platforms may require double quotes around command list. --utildir <path> location of utilities --width <number> Display width
NOTES
Using the option or piping commands to the console may require quotes or double quotes (for example, on Windows).
EXAMPLES
To launch the console, use this command:
$ mysqluc
The following demonstrates launching the console and running the console command 'help utilities' to see a list of all utilities supported. The console will execute the command then exit.:
$ mysqluc -e "help utilities" Utility Description
311
Parsers
---------------mysqlindexcheck mysqlrplcheck mysqluserclone mysqldbcompare mysqldiff mysqldbcopy mysqlreplicate mysqldbexport mysqldbimport mysqlmetagrep mysqlprocgrep mysqldiskusage mysqlserverinfo mysqlserverclone
--------------------------------------------------------check for duplicate or redundant indexes check replication clone a MySQL user account to one or more new users compare databases for consistency compare object definitions among objects where the difference is how db1.obj1 differs from db2.obj2 copy databases from one server to another establish replication with a master export metadata and data from databases import metadata and data from files search metadata search process information show disk usage for databases show server information start another instance of a running server
The following demonstrates launching the console to run several commands using the option to including setting a variable for a server connection and executing a utility using variable substitution. Note: it may be necessary to escape the '$' on some platforms (for example, Linux). Output below is an excerpt and is representational only.:
$ mysqluc -e "set SERVER=root@host123; mysqldiskusage --server=\$SERVER" # Source on host123: ... connected. NOTICE: Your user account does not have read access to the datadir. Data sizes will be calculated and actual file sizes may be omitted. Some features may be unavailable. # Database totals: +--------------------+--------------+ | db_name | total | +--------------------+--------------+ ... | world | 0 | ... +--------------------+--------------+ Total database disk usage = 1,072,359,052 bytes or 1022.00 MB #...done.
The following demonstrates launching the console using the commands shown above but piped into the console on the command line. The results are the same as above.:
$ echo "set SERVER=root@host123; mysqldiskusage --server=\$SERVER" | mysqluc
The following demonstrates launching the console and setting variables via the command line.:
$ mysqluc SERVER=root@host123 VAR_A=57 -e "show variables" Variable -------SERVER VAR_A Value ----------------------------------------------------------------root@host123 57
13.4. Parsers
13.4.1. mysql.utilities.parser Parse MySQL Log Files
This module provides classes for parsing MySQL log files. Currently, Slow Query Log and General Query Log are supported.
312
mysql.utilities.parser Parse MySQL Log Files
Classes
class mysql.utilities.parser.GeneralQueryLog(stream) This class parses the MySQL General Query Log. Instances are iterable, but the class does not provide multiple independent iterators. For example, to read the log and print the entries:
>>> general_log = open("/var/lib/mysql/mysql.log") >>> log = GeneralQueryLog(general_log) >>> for entry in log: ... print entry
Parameters:
stream (file type) a valid file type; for example, the result of the built-in Python function open()
version Returns: Return type: program Returns: Return type: port Returns: Return type: socket Returns: Return type: start_datetime Returns: Return type: lastseen_datetime Returns: Return type: Date and time of the last read log entry datetime.datetime Date and time of the first read log entry datetime.datetime Full path of the MySQL server Unix socket str TCP/IP port on which the MySQL server was listening int Full path of the MySQL server executable str Version of the MySQL server that produced the log tuple
class mysql.utilities.parser.SlowQueryLog(stream) This class parses the MySQL Slow Query Log. Instances are iterable, but the class does not provide multiple independent iterators. For example, to read the log and print the entries:
313
Appendix
>>> slow_log = open("/var/lib/mysql/mysql-slow.log") >>> log = SlowQueryLog(slow_log) >>> for entry in log: ... print entry
Parameters:
stream (file type) a valid file type; for example, the result of the built-in Python function open()
version Returns: Return type: program Returns: Return type: port Returns: Return type: socket Returns: Return type: start_datetime Returns: Return type: lastseen_datetime Returns: Return type: Date and time of the last read log entry datetime.datetime Date and time of the first read log entry datetime.datetime Full path of the MySQL server Unix socket str TCP/IP port on which the MySQL server was listening int Full path of the MySQL server executable str Version of the MySQL server that produced the log tuple
13.5. Appendix
13.5.1. MySQL Utilities FAQ
Frequently Asked Questions with answers. Questions 13.5.1.1.1: [314] Are these utilities present in the community version of MySQL? 13.5.1.2.1: [315] Can the utilities be used with MyISAM or CSV? Questions and Answers 13.5.1.1.1: Are these utilities present in the community version of MySQL?
314
MySQL Utilities FAQ
They are included in the community version of MySQL Workbench, and available from Launchpad. 13.5.1.2.1: Can the utilities be used with MyISAM or CSV? Yes. There are no storage engine specific limitations in using the utilities. There are some features written specifically for InnoDB so those may not apply but in general no utility is storage engine specific. For example, the mysqldiskusage utility shows exact sizes for MyISAM and InnoDB files but uses estimated sizes for any other storage engine based on number of rows and row size.
315
316
Appendix A. Third Party Licenses

Table of Contents
A.1. .NET Flat TabControl License .................................................................................................. 318 A.2. ANTLR 3.4 License ................................................................................................................. 319 A.3. Bitstream Vera License ............................................................................................................ 319 A.4. Boost Library License .............................................................................................................. 320 A.5. Cairo License .......................................................................................................................... 321 A.6. CTemplate (Google Template System) License ......................................................................... 321 A.7. cURL (libcurl) License ........................................................................................................ 322 A.8. DockPanel Suite License ......................................................................................................... 322 A.9. Dojo Toolkit v1.7.0b1 License .................................................................................................. 323 A.10. GLib License (for MySQL Workbench) .................................................................................... 323 A.11. Glitz License .......................................................................................................................... 323 A.12. GNU Lesser General Public License Version 2.1, February 1999 ............................................. 324 A.13. HtmlRenderer (System.Drawing.Html) ..................................................................................... 332 A.14. iODBC License ...................................................................................................................... 332 A.15. Libiconv License .................................................................................................................... 333 A.16. Libintl License ........................................................................................................................ 334 A.17. Libxml2 License ..................................................................................................................... 334 A.18. Libzip License ........................................................................................................................ 335 A.19. Lua (liblua) License ............................................................................................................... 335 A.20. Paramiko License .................................................................................................................. 336 A.21. PCRE License ....................................................................................................................... 336 A.22. Pixman License ..................................................................................................................... 337 A.23. PyCrypto License ................................................................................................................... 339 A.24. PyODBC License ................................................................................................................... 339 A.25. Python License ...................................................................................................................... 340 A.26. Scintilla License ..................................................................................................................... 350 A.27. ScintillaNET License .............................................................................................................. 352 A.28. TinyXML License ................................................................................................................... 352 A.29. TreeViewAdv for .NET License ............................................................................................... 353 A.30. VSQLite++ License ................................................................................................................ 353 A.31. zlib License ........................................................................................................................ 354 Use of any of this software is governed by the terms of the licenses that follow.
MySQL Workbench
Section A.1, .NET Flat TabControl License Section A.2, ANTLR 3.4 License Section A.3, Bitstream Vera License Section A.4, Boost Library License Section A.5, Cairo License Section A.6, CTemplate (Google Template System) License Section A.7, cURL (libcurl) License
317
.NET Flat TabControl License
Section A.8, DockPanel Suite License Section A.9, Dojo Toolkit v1.7.0b1 License Section A.10, GLib License (for MySQL Workbench) Section A.11, Glitz License Section A.12, GNU Lesser General Public License Version 2.1, February 1999 Section A.13, HtmlRenderer (System.Drawing.Html) Section A.14, iODBC License Section A.15, Libiconv License Section A.16, Libintl License Section A.17, Libxml2 License Section A.18, Libzip License Section A.19, Lua (liblua) License Section A.20, Paramiko License Section A.21, PCRE License Section A.22, Pixman License Section A.23, PyCrypto License Section A.24, PyODBC License Section A.25, Python License Section A.26, Scintilla License Section A.27, ScintillaNET License Section A.28, TinyXML License Section A.29, TreeViewAdv for .NET License Section A.30, VSQLite++ License Section A.31, zlib License
A.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
318
ANTLR 3.4 License
A.2. ANTLR 3.4 License

The following software may be included in this product: ANTLR 3.4 This product was build using ANTLR, which was provided to Oracle under the following terms: Copyright (c) 2010 Terence Parr 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 author 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.
A.3. 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
319
Boost Library License
"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.
A.4. 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.
320
Cairo License
A.5. Cairo License

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 A.12, GNU Lesser General Public License Version 2.1, February 1999.
A.6. CTemplate (Google Template System) License

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

cURL (libcurl) Use of any of this software is governed by the terms of the license below: COPYRIGHT AND PERMISSION NOTICE Copyright (c) 1996 - 2009, Daniel Stenberg, <daniel@haxx.se>. All rights reserved. Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Except as contained in this notice, the name of a copyright holder shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization of the copyright holder.
A.8. DockPanel Suite License

DockPanel Suite The MIT License Copyright (c) 2007 Weifen Luo (email: weifenluo@yahoo.com) Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
322
Dojo Toolkit v1.7.0b1 License
A.9. Dojo Toolkit v1.7.0b1 License

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.
A.10. GLib License (for MySQL Workbench)

GLib You are receiving a copy of the GLib library in both source and object code in the following folder: C:\Program Files (x86)\MySQL\MySQLWorkbench 5.2\ on Windows and MySQLWorkbench.app/Contents/Frameworks on Mac OS X. The terms of the Oracle license do NOT apply to the GLib library; it is licensed under the following license, separately from the Oracle programs you receive. If you do not wish to install this library, you may go to the folder C:\Program Files (x86)\MySQL\MySQL Workbench 5.2\ and remove or replace the libglib-2.0-0.dll, libgmodule-2.0-0.dll, libgobject-2.0-0.dll and libgthread-2.0-0.dll files if present on Windows or go to the folder MySQLWorkbench.app/Contents/Frameworks and remove or replace the files libglib-2.*.dylib, libgmodule-2.*.dylib and libgthread-2.*.dylib on Mac OS X, but the Oracle program might not operate properly or at all without the library.
A.11. Glitz License

323
GNU Lesser General Public License Version 2.1, February 1999
Glitz Copyright 2004 David Reveman, Peter Nilsson Permission to use, copy, modify, distribute, and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the names of David Reveman and Peter Nilsson not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. David Reveman and Peter Nilsson makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty. DAVID REVEMAN AND PETER NILSSON DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL DAVID REVEMAN AND PETER NILSSON BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
A.12. 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
324
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
325
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.
326
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.
327
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
328
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
329
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
330
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. <one line to give the library's name and a brief idea of what it does.> Copyright (C) <year> <name of author> 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
331
HtmlRenderer (System.Drawing.Html)
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. <signature of Ty Coon>, 1 April 1990 Ty Coon, President of Vice That's all there is to it!
A.13. HtmlRenderer (System.Drawing.Html)

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

iODBC
332
Libiconv License
In accordance with the terms of the iODBC licensing scheme set forth below, Oracle is hereby making the election to license iODBC under the BSD license. iODBC Driver Manager Copyright (C) 1995 by Ke Jin <kejin@empress.com> Copyright (C) 1996-2009 by OpenLink Software <iodbc@openlinksw.com> All Rights Reserved. This software is released under either the GNU Library General Public License (see LICENSE.LGPL) or the BSD License (see LICENSE.BSD). Note that the only valid version of the LGPL license as far as this project is concerned is the original GNU Library General Public License Version 2, dated June 1991. While not mandated by the BSD license, any patches you make to the iODBC may be contributed back into the iODBC project at your discretion. Contributions will benefit the Open Source and Data Access community as a whole. Submissions may be made at http://www.iodbc.org. LICENSE.BSD: Copyright (C) 1995-2009, OpenLink Software Inc and Ke Jin. 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 OpenLink Software Inc. nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL OPENLINK 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.
A.15. Libiconv License

Libiconv You are receiving a copy of the GNU LIBICONV Library. The terms of the Oracle license do NOT apply to the GNU LIBICONV Library; it is licensed under the following license, separately from the Oracle programs you receive. If you do not wish to install this program, you may delete iconv.dll or libiconv.* files.
333
Libintl License
A.16. Libintl License

The following software may be included in this product: libintl
Copyright (C) 1994 X Consortium 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 X CONSORTIUM BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Except as contained in this notice, the name of the X Consortium shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization from the X Consortium. FSF changes to this file are in the public domain. Copyright 1996-2007 Free Software Foundation, Inc. Taken from GNU libtool, 2001 Originally by Gordon Matzigkeit <gord@gnu.ai.mit.edu>, 1996 This file is free software; the Free Software Foundation gives unlimited permission to copy and/or distribute it, with or without modifications, as long as this notice is preserved. You are receiving a copy of the libintl library. The terms of the Oracle license do NOT apply to the libintl library; it is licensed under the following license, separately from the Oracle programs you receive. If you do not wish to install this program, you may delete the intl.dll or libintl.* files.
A.17. Libxml2 License

Libxml2 Except where otherwise noted in the source code (e.g. the files hash.c, list.c and the trio files, which are covered by a similar licence but with different Copyright notices) all the files are: Copyright (C) 1998-2003 Daniel Veillard. All Rights Reserved.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation
334
Libzip License
the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE DANIEL VEILLARD BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Except as contained in this notice, the name of Daniel Veillard shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization from him.
A.18. Libzip License

libzip Copyright (C) 1999-2008 Dieter Baron and Thomas Klausner The authors can be contacted at <libzip@nih.at> Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The names of the authors may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE AUTHORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
A.19. Lua (liblua) License

Lua (liblua)
335
Paramiko License
Copyright 19942008 Lua.org, PUC-Rio. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
A.20. Paramiko License

Paramiko You are receiving a copy of Paramiko in both source and object code. The terms of the Oracle license do NOT apply to the Paramiko program; it is licensed under the following license, separately from the Oracle programs you receive. If you do not wish to install this program, you may delete the Paramiko folder and all its contents.
A.21. 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
336
Pixman License
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
A.22. Pixman License

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 Copyright Copyright Copyright Copyright Copyright Copyright 1987, 1988, 1989, 1998 The Open Group 1987, 1988, 1989 Digital Equipment Corporation 1999, 2004, 2008 Keith Packard 2000 SuSE, Inc. 2000 Keith Packard, member of The XFree86 Project, Inc. 2004, 2005, 2007, 2008, 2009, 2010 Red Hat, Inc. 2004 Nicholas Miell
337
Pixman License
Copyright Copyright Copyright Copyright Copyright Copyright Copyright Copyright Copyright
2005 Lars Knoll & Zack Rusin, Trolltech 2005 Trolltech AS 2007 Luca Barbato 2008 Aaron Plattner, NVIDIA Corporation 2008 Rodrigo Kumpera 2008 Andr Tupinamb 2008 Mozilla Corporation 2008 Frederic Plourde 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 Copyright Copyright Copyright Copyright Copyright Copyright Copyright Copyright Copyright Copyright Copyright Copyright Copyright Copyright Copyright 1987, 1988, 1989, 1998 The Open Group 1987, 1988, 1989 Digital Equipment Corporation 1999, 2004, 2008 Keith Packard 2000 SuSE, Inc. 2000 Keith Packard, member of The XFree86 Project, Inc. 2004, 2005, 2007, 2008 Red Hat, Inc. 2004 Nicholas Miell 2005 Lars Knoll & Zack Rusin, Trolltech 2005 Trolltech AS 2007 Luca Barbato 2008 Aaron Plattner, NVIDIA Corporation 2008 Rodrigo Kumpera 2008 Andr Tupinamb 2008 Mozilla Corporation 2008 Frederic Plourde 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:
338
PyCrypto License
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.
A.23. PyCrypto License

PyCrypto - The Python Cryptography Toolkit =================================================================== Distribute and use freely; there are no restrictions on further dissemination and usage except those imposed by the laws of your country of residence. This software is provided "as is" without warranty of fitness for use or suitability for any purpose, express or implied. Use at your own risk or not at all. =================================================================== Incorporating the code into commercial products is permitted; you do not have to make source available or contribute your changes back (though that would be nice). --amk (www.amk.ca) /********************************************************************\ * FILE: rmd160.c * CONTENTS: A sample C-implementation of the RIPEMD-160 hash-function. * TARGET: any computer with an ANSI C compiler * AUTHOR: Antoon Bosselaers, Dept. Electrical Eng.-ESAT/COSIC * DATE: 1 March 1996 VERSION: 1.0 ********************************************************************** * Copyright (c) Katholieke Universiteit Leuven 1996, All Rights Reserved * The Katholieke Universiteit Leuven makes no representations concerning * either the merchantability of this software or the suitability of this * software for any particular purpose. It is provided "as is" without * express or implied warranty of any kind. These notices must be retained * in any copies of any part of this documentation and/or software. \********************************************************************/
A.24. PyODBC License

PyODBC 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. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
339
Python License
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.
A.25. Python License

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 from Year Owner GPLcompatible? (1) yes yes no no yes (2) no yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes
0.9.0 thru 1.2 1.3 thru 1.5.2 1.6 2.0 1.6.1 2.1 2.0.1 2.1.1 2.2 2.1.2 2.1.3 2.2.1 2.2.2 2.2.3 2.3 2.3.1 2.3.2 2.3.3 2.3.4 2.3.5 2.4 2.4.1 2.4.2
1.2 1.5.2 1.6 1.6 2.0+1.6.1 2.0+1.6.1 2.1+2.0.1 2.1.1 2.1.1 2.1.2 2.2 2.2.1 2.2.2 2.2.2 2.3 2.3.1 2.3.2 2.3.3 2.3.4 2.3 2.4 2.4.1
1991-1995 1995-1999 2000 2000 2001 2001 2001 2001 2001 2002 2002 2002 2002 2003 2002-2003 2002-2003 2002-2003 2002-2003 2004 2005 2004 2005 2005
CWI CNRI CNRI BeOpen.com CNRI PSF PSF PSF PSF PSF PSF PSF PSF PSF PSF PSF PSF PSF PSF PSF PSF PSF PSF
340
Python License
2.4.3 2.5 2.5.1 2.5.2 2.5.3 2.6 2.6.1 2.6.2 2.6.3 2.6.4 2.7
2.4.2 2006 PSF 2.4 2006 PSF 2.5 2007 PSF yes 2.5.1 2008 PSF yes 2.5.2 2008 PSF yes 2.5 2008 PSF yes 2.6 2008 PSF yes 2.6.1 2009 PSF yes 2.6.2 2009 PSF yes 2.6.3 2010 PSF yes 2.6 2010 PSF yes
yes 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.
341
Python License
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 ---------------------------------------
342
Python License
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
343
Python License
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,
344
Python License
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 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. 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|
/ | | | | | | | | | | | | | | | | | | |
345
Python License
| | | | | | | | | | | |
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 <ghost@aladdin.com>. 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 <purschke@bnl.gov>. 1999-05-03 lpd Original version. Asynchronous socket services ============================ The asynchat and asyncore modules contain the following notice:
346
Python License
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 <timo@alum.mit.edu> 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.
347
Python License
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
348
Python License
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 MERCHANTABILITY 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:
349
Scintilla License
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 `ÀS 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. * ***************************************************************/
A.26. Scintilla License

Scintilla License for Scintilla and SciTE Copyright 1998-2003 by Neil Hodgson <neilh@scintilla.org> 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
350
Scintilla License
AND FITNESS, IN NO EVENT SHALL NEIL HODGSON BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Scintilla includes some files copyright Adobe Systems Incorporated: Copyright (c) 2007 Adobe Systems Incorporated Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. ---Scintilla includes some files copyright Apple Computer, Inc.: Disclaimer: IMPORTANT: This Apple software is supplied to you by Apple Computer, Inc. ("Apple") in consideration of your agreement to the following terms, and your use, installation, modification or redistribution of this Apple software constitutes acceptance of these terms. If you do not agree with these terms, please do not use, install, modify or redistribute this Apple software. In consideration of your agreement to abide by the following terms, and subject to these terms, Apple grants you a personal, non-exclusive license, under Apple's copyrights in this original Apple software (the "Apple Software"), to use, reproduce, modify and redistribute the Apple Software, with or without modifications, in source and/or binary forms; provided that if you redistribute the Apple Software in its entirety and without modifications, you must retain this notice and the following text and disclaimers in all such redistributions of the Apple Software. Neither the name, trademarks, service marks or logos of Apple Computer, Inc. may be used to endorse or promote products derived from the Apple Software without specific prior written permission from Apple. Except as expressly stated in this notice, no other rights or licenses, express or implied, are granted by Apple herein, including but not limited to any patent rights that may be infringed by your derivative works or by other works in which the Apple Software may be incorporated. The Apple Software is provided by Apple on an "AS IS" basis. APPLE MAKES NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, REGARDING THE APPLE SOFTWARE OR ITS USE AND OPERATION ALONE OR IN COMBINATION WITH YOUR PRODUCTS. IN NO EVENT SHALL APPLE BE LIABLE FOR ANY SPECIAL, INDIRECT, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) ARISING IN ANY WAY OUT OF THE USE, REPRODUCTION, MODIFICATION AND/OR DISTRIBUTION OF THE APPLE SOFTWARE, HOWEVER CAUSED AND WHETHER UNDER THEORY OF CONTRACT, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY OR
351
ScintillaNET License
OTHERWISE, EVEN IF APPLE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Copyright (c) 2002 Apple Computer, Inc., All Rights Reserved
A.27. ScintillaNET License

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 <gserack@gmail.com> 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 <neilh@scintilla.org> 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.
A.28. TinyXML License

The following software may be included in this product: TinyXML
TinyXML is released under the zlib license: This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any
352
TreeViewAdv for .NET License
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.
A.29. TreeViewAdv for .NET License

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.
A.30. VSQLite++ License

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

The following software may be included in this product: zlib Oracle gratefully acknowledges the contributions of Jean-loup Gailly and Mark Adler in creating the zlib general purpose compression library which is used in this product.
zlib.h -- interface of the 'zlib' general purpose compression library Copyright (C) 1995-2004 Jean-loup Gailly and Mark Adler zlib.h -- interface of the 'zlib' general purpose compression library version 1.2.3, July 18th, 2005 Copyright (C) 1995-2005 Jean-loup Gailly and Mark Adler zlib.h -- interface of the 'zlib' general purpose compression library version 1.2.5, April 19th, 2010 Copyright (C) 1995-2010 Jean-loup Gailly and Mark Adler 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. Jean-loup Gailly jloup@gzip.org Mark Adler madler@alumni.caltech.edu
354
Appendix B. MySQL Workbench FAQ

Frequently Asked Questions with answers. Questions B.1: [355] How does MySQL Workbench increase import performance? B.2: [355] MySQL Workbench 5.0 appears to run slowly. How can I increase performance? B.3: [356] I get errors when creating or placing objects on an EER Diagram. I am using OpenGL rendering, AMD processor, and ATI graphics hardware. B.4: [356] What do the column flag acronyms (PK, NN, UQ, BIN, UN, ZF, AI) in the MySQL Workbench Table Editor mean? Questions and Answers B.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;
B.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.
355
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. B.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. B.4: What do the column flag acronyms (PK, NN, UQ, BIN, UN, ZF, AI) in the MySQL Workbench Table Editor mean? Checking these boxes will alter the table column by assigning the checked constraints to the designated columns. Hover over an acronym to view a description, and see the MySQL Workbench Table Editor and MySQL CREATE TABLE documentation for further information.
356
Appendix C. MySQL Workbench and Utilities Change History

Table of Contents
C.1. MySQL Workbench Change History ......................................................................................... C.1.1. Changes in MySQL Workbench 5.2 ............................................................................... C.1.2. Changes in MySQL Workbench 5.1 ............................................................................... C.1.3. Changes in MySQL Workbench 5.0 ............................................................................... C.2. MySQL Utilities Change History ............................................................................................... C.2.1. Changes in Release 1.1 ............................................................................................... C.2.2. Changes in Release 1.0 ............................................................................................... This appendix lists the changes from version to version in the MySQL Workbench and MySQL Utilities source code. Note that we tend to update the manual at the same time we make changes to MySQL. If you find a recent version of the MySQL Workbench or Utilities listed here that you can't find on our download page (http:// dev.mysql.com/downloads/), it means that the version has not yet been released. The date mentioned with a release version is the date of the last Bazaar ChangeSet on which the release was based, not the date when the packages were made available. The binaries are usually made available a few days after the date of the tagged ChangeSet, because building and testing all packages takes some time. The manual included in the source and binary distributions may not be fully accurate when it comes to the release changelog entries, because the integration of the manual happens at build time. For the most upto-date release changelog, please refer to the online version instead. 357 357 455 473 489 489 489
C.1. MySQL Workbench Change History

The following sections outline the changes between versions for MySQL Workbench.
C.1.1. Changes in MySQL Workbench 5.2

C.1.1.1. Changes in MySQL Workbench 5.2.45 (Not yet released)
This section documents all changes and bug fixes applied to MySQL Workbench since the release of 5.2.44. This version adds support for MySQL Server 5.6. Functionality Added or Changed Models: Copy, Cut, and Paste options were added to the context menu (right-click) of the Columns list in the models table editor. These options can be used between models. (Bug #13029519, Bug #62503) A Copy Selected button was added to the Server Status panel of the Server Administration window. It copies the query of the selected connection to the clipboard. (Bug #14799336, Bug #66728) The Control + / keyboard shortcut was added to comment/uncomment lines while editing SQL queries. (Bug #14803414, Bug #67002) An Import Recordset from CSV File option was added to the SQL Editor and model insert tabs. This import functionality parses a file with comma-separated values. (Bug #14207773, Bug #65592)
357
Changes in MySQL Workbench 5.2
Bugs Fixed Linux: Right-dragging saved connections, models, and MySQL Server instances on the home screen could crash MySQL Workbench. (Bug #14812457) Linux: Executing MySQL Workbench from the command-line would print stdout twice. (Bug #14565095, Bug #66590) Mac OS X: The results window from executing an SQL query could be empty. A workaround was to resize the results window. (Bug #14520361, Bug #66446) Mac OS X: Closing MySQL Workbench after executing and making changes with the Alter Table tool would not prompt the user with the save dialog. (Bug #14456136) Mac OS X: On Mac OS X, the default column name and column type model preferences did not function. Note that this feature does not function on Linux. (Bug #14399236, Bug #66090) Mac OS X: The ability to select multiple columns in the models table editor did not function on Mac OS X. It is now possible to use Shift, Command, and mouse dragging. (Bug #11766291, Bug #59372) Models: Microsoft Windows: After opening and then closing a model file from the file manager, attempts to open a different model file would fail to load the model. (Bug #14791573, Bug #67312) Models: Microsoft Windows: Model files (*.mwb) would not load MySQL Workbench after being double-clicked in Windows Explorer. (Bug #14521111) Microsoft Windows: Pressing Control + A in the table editor on a table field would select all table entities instead of the text in the field. (Bug #15884658, Bug #67610) Microsoft Windows: Clicking on the Schema and Schema Objects column headers within Server Administration, Data Export would properly sort in descending order, but would not sort in ascending order when clicked again. (Bug #15849616, Bug #67518) Microsoft Windows: The Enter key would not create newlines within the table column comment dialogue. (Bug #14829617, Bug #67320) Microsoft Windows: Queries surrounded by parenthesis would not display results in the view tab. (Bug #14651969, Bug #66887) Microsoft Windows: Right-clicking on a database name in the schema browser and choosing Set as Default Schema would add a strikethrough to the chosen database name. (Bug #14663690, Bug #66930) Microsoft Windows: The Explain button would not display the results in the Explain tab. (Bug #14702591, Bug #67059) Microsoft Windows: The Id and Time columns within the Server Administration, Server Status, Connections panel would not sort properly, as they were sorted as ASCII values instead of numerically. (Bug #14612413, Bug #66768) Microsoft Windows: A model would fail to load when opened from the Microsoft Windows 7 taskbar if a different model was already open. (Bug #14621880, Bug #66799) Microsoft Windows: Control + H did not invoke the replacement function. (Bug #14520920, Bug #66422) Microsoft Windows: After using the schema search filter in the object browser, right-clicking on a filtered schema would generate a context menu with invalid options. (Bug #14521006, Bug #66346)
358
Microsoft Windows: Find and Replace would not function properly while using '_' as a replacement character. (Bug #14499088, Bug #66390) Microsoft Windows: The Explain Current Statement option would not function. A workaround is to manually prepend EXPLAIN to your query. (Bug #14483518, Bug #66157) Microsoft Windows: Control + A would not always select data from cells in the query results tab. (Bug #13891109, Bug #64723) Microsoft Windows: The default plugin directory in the configuration tab was set as a Linux style path such as "/usr/", but it is now based on the OS aware BASEDIR value. (Bug #11764440, Bug #57271) MySQL Server 5.6: The SHA-256 Authentication Plugin is now supported. (Bug #14786561, Bug #67155) MySQL Server 5.6: MySQL Workbench would alter the mysql.* system tables for tasks such as account management, instead of using the corresponding account manipulation statements. This would conflict with GTID usage as of MySQL Server 5.6. (Bug #14786531, Bug #67150) MySQL Server 5.6: The MySQL 5.6 ALTER USER ... PASSWORD EXPIRE option is now supported. An expired password indicator, and an Expire Password button to expire the current password, were added. (Bug #14786564, Bug #67157) MySQL Server 5.6: MySQL Workbench now supports MySQL Server 5.6 configuration options. (Bug #14786556, Bug #67153) MySQL Server 5.6: The SQL Editor would emit invalid syntax errors with MySQL 5.6 queries. For example, GET DIAGNOSTICS queries would return "syntax error, unexpected IDENT_QUOTED, expecting ':'". (Bug #14786599, Bug #14786604, Bug #14786615, Bug #67163, Bug #67164, Bug #67168) MySQL Server 5.6: MySQL Workbench would not allow passwords to be created or changed for user accounts that utilize the SHA-256 Authentication Plugin, which exists as of MySQL Server 5.6.6. (Bug #14786567, Bug #14786558, Bug #67158, Bug #67154) MySQL Server 5.6: The partition count definition was limited to 1-10 as a drop-down selector in MySQL Workbench. This option is now a text field, which accommodates the 8192 partition limit in MySQL Server 5.6. (Bug #14786614, Bug #67166) MySQL Server 5.6: A DDL related parsing error would be generated while attempting to update an existing routine that contained a DateTime variable type with precision. This feature is specific to MySQL Server 5.6. (Bug #14684874, Bug #14545075) MySQL Server 5.6: The MySQL Workbench UI now supports the extended TIMESTAMP and DATETIME features that MySQL Server 5.6 offers. Both the initial and on-update values can now be defined for these types, and the fractional-second granularity is also now supported. (Bug #67165, Bug #67169, Bug #14786605, Bug #14786616) MySQL Server 5.6: All MySQL Server 5.6 system variables were listed under the Other tab instead of their proper location. For example, gtid_done is now listed under the Replication tab. (Bug #67170, Bug #14786569) MySQL Server 5.6: Creating a standard MySQL Server 5.6 user account in MySQL Workbench would fail, and emit an error related to the msyql_native_auth plugin. (Bug #67151, Bug #14786542) MySQL Server 5.6: The creation of a username and password will now utilize the Password Validation Plugin in MySQL 5.6. This option is available within the Server Administration section, under the Security Options tab. (Bug #67152, Bug #67161, Bug #14786551, Bug #14786626)
359
Migration: Migrating a Microsoft SQL Server database would fail if nvarchar(max) was used. These are now converted to LONGTEXT. (Bug #14780416, Bug #67289) Migration: Migrating from MySQL Server 5.0 to MySQL Server 5.6 could fail. The migration tool now supports MySQL Server 4.1 and above as the source database. MySQL Server 5.1 and above are supported as the target database. (Bug #14647426, Bug #66861) Models: Switching from a table column tab to a different tab, and then back to the column tab, would add an empty column named "tablenamecol". This empty column would be added to the table unless Escape was pressed. (Bug #14768685, Bug #67235) Models: Model notes could not be saved. The Apply Changes button is available again. (Bug #14813462, Bug #67211) Models: Synchronizing a model with a database could crash MySQL Workbench by causing a segmentation fault. (Bug #14588524, Bug #66707) Models: While executing the Synchronize Model with Database wizard, invalid trigger related errors could be emitted even though the definitions were correct. (Bug #14498358, Bug #65982) Models: Forward Engineering a model with users and roles could generate invalid SQL, because the username was not escaped within the generated GRANT statements. (Bug #14396930, Bug #66070) Models: The File, Import, Import DBDesigner4 Model feature would fail to function. (Bug #13548113, Bug #63878) Models: Sometimes a modified stored procedure would not be flagged as modified while synchronizing a model. (Bug #13364922, Bug #62595) Models: The ability to open model files from older versions of MySQL Workbench has been improved. (Bug #12747012, Bug #61703) Models: When editing an EER diagram, the Cut context menu option follows Delete behavior by also deleting the schema object. It will now only remove it from the EER canvas. And a new Remove option was added that also only removes an object from the EER canvas. (Bug #11761492, Bug #53994) Having sql_mode set to PAD_CHAR_TO_FULL_LENGTH causes the routine functionality to fail, as MySQL Workbench is not designed for this setting. A connection specific sql_mode option was added, and it can be set from the Advanced tab in the Connection Editor. It defaults to "". (Bug #14845656) Added DbMySQLQuery->affectedRows, fixed MySQLResult->firstRow, and added a Splitter control to the Python binding for mforms. (Bug #14799403, Bug #66804) MySQL Workbench would fail to interpret C-style comments, such as /*! MySQL-specific code */. For more information about comment usage in MySQL, see Comment Syntax. (Bug #14807602, Bug #67203) Opening a connection using Open connection to Start Querying from the MySQL Workbench home screen could crash MySQL Workbench. (Bug #14803527, Bug #67074) A model could not be synchronized if a field contained a comment with a single quote. (Bug #14582241, Bug #66680) A crash could occur after switching tables in the EER Diagram tab while the Privileges was open, or while adding roles to the active table. (Bug #14645542, Bug #66869) In the MySQL Workbench Scripting Shell, an exception is now thrown while attempting to use input() or read from stdin. (Bug #14520741, Bug #66452)
360
The non-functional comments box was removed from the schema editor. (Bug #14548126, Bug #66553) An exception would be generated when executing Forward Engineer without a MySQL Server connection. (Bug #14574987, Bug #66648) Lower level changes, such as a newly created TRIGGER, would not be visible after the object browser was refreshed. (Bug #14551801, Bug #66549) The mouse scroll would not function while viewing the Options File in the Server Administration panel. (Bug #14388344) Unlike the Server Administration panel (since 5.2.35), the SQL Editor did not support syntax that utilized the authentication plugins. (Bug #14356470) The Server Access Management interface would not allow a password to be set as an empty string. (Bug #14278189, Bug #65739) The Limit Connectivity to Hosts Matching option did not allow an IP with a Subnet Mask because "/" was considered an invalid character. (Bug #14207793, Bug #65583) Multiple instances of MySQL Workbench will no longer open the same database model file. Doing so caused problems with features such as auto save and file locking. (Bug #13864687, Bug #64639) An SSL connection required a client certificate. (Bug #13851229, Bug #61266) A new General, SQL Editor option was added. Enabling Create new tabs as Query tabs instead of File (disabled by default) causes new SQL Editor tabs to default as Query tabs instead of SQL File tabs. File tabs include additional options, and prompt to be saved when the tab closed. (Bug #13492434, Bug #14541178, Bug #62929, Bug #66541) The Start Command Line Client feature would fail to connect with SSH connections. (Bug #12612343, Bug #61325) A Refresh Rate option was added to the Server Administration, Server Status window. The refresh rate defaults to "Don't Refresh" and includes options ranging from 0.5 to 30 seconds. (Bug #11926869, Bug #60546) It was not possible to sort schemas for exporting. (Bug #11926862, Bug #60566) Changes to the DEFINER clause were not detected by the Alter Table wizard when altering this clause was the only change. (Bug #11829867, Bug #60164) Attempting to open MySQL Doc Library while it was already opened would generate an error. (Bug #11763691, Bug #56432) The ALTER ROUTINE functionality would not detect stored procedure changes when only the case changed. This check was case-insensitive. (Bug #65277, Bug #14136994)
C.1.1.2. Changes in MySQL Workbench 5.2.44 (2012-09-27)

This section documents all changes and bug fixes applied to MySQL Workbench since the release of 5.2.43. This version adds native PostgreSQL and Sybase ASE support to the Database Migration Wizard. Functionality Added or Changed Updated the bundled MySQL Utilities to version 1.1.0, which includes the new mysqluc console.
361
Added native migration support for PostgreSQL and Sybase ASE. Bugs Fixed After right-clicking on a non-empty field in the SQL editor, and choosing Copy Row Content, pasting the row into an empty row (by right-clicking and choosing Paste Row) would not increment the row id when it was appropriate to do so. (Bug #14587186, Bug #66668) When a table from Microsoft SQL Server was migrated to MySQL, TEXT columns were mapped to VARCHAR(16). They are now mapped to LONGTEXT because Microsoft SQL Server TEXT columns have a maximum length of 2^31 - 1. (Bug #14556732, Bug #66584) The MySQL Workbench Data Export feature would fail to recognize tables that contained accented characters in the table's name. (Bug #14504342, Bug #66421) The object browser would not update the column order after a table was altered. (Bug #14495629, Bug #66232) On Mac OS X systems with the Retina display, the mouse cursor would register incorrect mouse coordinates. (Bug #14396939, Bug #65607) Entering the caret ("^") character inside the SQL editor, followed by any other character, could cause MySQL Workbench to hang. This was a Scintilla bug that is now fixed. (Bug #13930994, Bug #64848) After choosing Alter Table, pressing Apply would cause MySQL Workbench to display "Preparing..." in the output panel, but it now displays "No changes detected." (Bug #13497239, Bug #63604) When synchronizing a model to a database after changing a field definition from NOT NULL DEFAULT x to NULL DEFAULT NULL, the model synchronization would correctly generate the SQL. But after executing this SQL and resynchronizing, MySQL Workbench would report that the table needed to be updated. (Bug #12756728, Bug #61720)

This section documents all changes and bug fixes applied to MySQL Workbench since the release of 5.2.42. Functionality Added or Changed The default object/relationship notation for new models will now be taken from the last notation selected by the user. This is chosen via Model, Relationship Notation. (Bug #49997, Bug #11757883) Bugs Fixed It was possible for a custom plugin to cause MySQL Workbench to crash. (Bug #14595613, Bug #65817) After editing and closing an EER diagram, double-clicking on one of the diagram tables could generate an exception. (Bug #14587490, Bug #66699) MySQL Workbench would sometimes crash at startup due to a race condition. The logged error included "Invoke or BeginInvoke cannot be called on a control until the window handle has been created." (Bug #14526134, Bug #66130) Clicking Browse after the Target Creation Options stage of the database migration wizard would generate an error. (Bug #14520838, Bug #66271) Passing in the -nologo argument while starting MySQL Workbench would cause a crash. (Bug #14527014)
362
Right-clicking and choosing Edit Table Data while multiple schemas are selected could cause the activity animation icon to remain active and/or crash MySQL Workbench. (Bug #14524139, Bug #66022) A semicolon at the end of a single lined SQL comment would be treated as a delimiter, and cause the SQL query to not execute. (Bug #14529811, Bug #66505) Dropping multiple objects at the same time was not possible. Selecting multiple objects, right-clicking on one of the selected objects, and then choosing the Drop n Object option would generate SQL that deleted only one of the selected objects. (Bug #14538863) Migrating a Microsoft SQL Server table that contained both NULL and non-null values in a DATETIME column would fail to import properly. (Bug #14509484, Bug #66359) Migrating from a remote SQL Server 2008 database to a local MySQL database would fail at the Fetch Schemata List stage of the database migration wizard, as it was unable to connect to the source database. (Bug #14498549, Bug #66030) On Mac OS X, code signing was added to MySQL Workbench so it will now load when this condition is required. (Bug #14457847, Bug #66052) The object browser did not display foreign keys. A workaround was to view them via the Alter Table interface. (Bug #14483668, Bug #66226) Objects in the schema tree, such as tables, were not listed alphabetically after edits were made. (Bug #14483610, Bug #66209) Selecting a view in the object browser would sometimes insert the view into the table listing. (Bug #14483526, Bug #66158) On Linux, the mysql-workbench-bin executable is no longer installed under /usr/bin/ because it cannot be executed directly. It was moved to /usr/lib*/mysql-workbench/. (Bug #14485725, Bug #66322) On Microsoft Windows, MySQL Workbench would crash after attempting to export a model as a PNG, SVN, or PDF. (Bug #14483735, Bug #66298) On Fedora 17, autoconf would not detect the altlr which is antlr3-C version 3.4. (Bug #14495924, Bug #66325) The database export feature would not always export the correct databases if some database names were clicked while others checked the selection checkbox. This feature now only takes into account the checkboxes. (Bug #14495660, Bug #66376) Under certain conditions, synchronizing a model would generate SQL statements that dropped a schema before altering it. (Bug #14495165, Bug #66083) Right-clicking on a table and selecting Copy Insert Statement would generate SQL with the columns sorted in alphabetical order. The SQL is now generated in the order listed in the database. (Bug #14508845, Bug #66419) With the Slovenian keyboard layout chosen, pressing Control + / would not toggle commenting. (Bug #14504877, Bug #66131) Synchronizing a model could crash if the model had an invalid foreign key. (Bug #14498436, Bug #66020) Synchronizing a restored EER model with the Model and Database Differences, Update Model Only configuration option enabled for all tables would cause MySQL Workbench to crash. (Bug #14510962, Bug #66436)
363
The Select Schemata step of the Reverse Engineer Database wizard would not display the underscore character correctly. Instead it would appear as an underline to the next character. (Bug #14467930, Bug #66248) On Microsoft Windows, the behavior of Control + Enter was changed back to the previous behavior, which is to execute the statement that contains the cursor, instead of the last statement in the SQL editor, or the current statement if the cursor is at the beginning. (Bug #14396992, Bug #66025) After exporting a schema, and unselecting the schema, exporting a new schema would export both the current and previously exported schema. (Bug #14388355) On a table with a multiple field foreign key, attempts to remove one of these fields would fail. The associated checkboxes can now be used with success. (Bug #14415483, Bug #66171) Expanding a view object from within the schema viewer would immediately collapse, and it would only expand with subsequent attempts. (Bug #14404189) A warning message was added when a user attempts to delete an index that belongs to a foreign key. (Bug #14359329, Bug #65972) The default database while applying changes to users and privileges is now set to mysql. (Bug #14359266, Bug #65959) Exporting a table that contained views could fail to export. (Bug #14359349, Bug #65780) The --enable-maintainer-mode autoconf option was not available. (Bug #14329365, Bug #65900) MySQL Workbench could execute queries from the wrong tab after tabs were moved (reordered). (Bug #14221754, Bug #65557) The vertical scrollbar in the table definition window would appear incorrect after clicking a NN (Not Null) checkbox on one of the column definitions. (Bug #14221022, Bug #65500) Choosing the Edit in New Window context menu on a routine would not open a new window. (Bug #14171776, Bug #65520) On Linux, pressing the Enter key after typing a file name would not save the file while doing so in the SQL editor file save dialogue. (Bug #14124900, Bug #64945) On Mac OS X, new tabs could not be closed (via the [x]) if ten or more tabs were already open, and if the total MySQL Workbench window width exceeded around 1200px. (Bug #14127281, Bug #65186) Executing from mysql.utilities.parser import GeneralQueryLog from within the MySQL Workbench scripting shell would result in an error. (Bug #14128312) The MySQL Export wizard would not escape hardcoded newlines in the generated SQL, but they are now escaped. For example, a \n now remains as \n in the exported query, when before it was expanded. (Bug #14124914, Bug #65222) On Linux, tables that are present are now marked with a black point in the diagram editor. (Bug #14107656, Bug #65210) On Mac OS X, hiding a window pane (such as the snippets) would cause the window pane to remain hidden, even after restarting MySQL Workbench. (Bug #14017268, Bug #65138) The Plugins, Objects, Create Multiple Tables feature did not function on Microsoft Windows, and only created one table on Linux. (Bug #14026694, Bug #14026709) Exported "Excel Spreadsheet" files were exported with the ".xls" extension, instead of the ".xml" extension. (Bug #13970552, Bug #64955)
364
MySQL Workbench was unable to edit the lc_time_names variable. (Bug #13939985, Bug #64880) Under certain conditions, MySQL Workbench would generate invalid SQL when dealing with foreign keys. (Bug #13865784, Bug #14486006, Bug #64601, Bug #66285) While editing a model, right-clicking on a user and choosing Copy SQL to Clipboard would not not function. (Bug #13742855) After setting an EER diagram marker, modifying the zoom, and then setting a marker, the markers would not be created. (Bug #13742896) On Linux, the WB_FORCE_SYSTEM_COLORS environment variable was added. Enabling this variable (with a value of 1) will disable MySQL Workbench from using its own color scheme. Example usage: export WB_FORCE_SYSTEM_COLORS=1. This is useful for certain conditions, like when using the HighContrastInverse or GnomishDark system themes. (Bug #13608244, Bug #64013) MySQL Workbench would yield incorrect results while displaying results from the MAX function on a bit field. (Bug #13496747, Bug #63457) Table data could not be edited if the primary key was a binary field. (Bug #13418610, Bug #63198) Multiple objects would remain selected after adding a new table within the Create new EER Model wizard. (Bug #12933282) The Forward Engineering wizard did not utilize the Use Default Schema setting that is set in the Manage Connections configuration table. (Bug #12757331, Bug #61786) Passwords are now removed if they are no longer used by other connections when a particular connection is deleted. (Bug #12627613, Bug #61322) Deleting a connection would not immediately delete the connection from MySQL Workbench. (Bug #12642474, Bug #61445) The Treat BINARY/VARBINARY as nonbinary character string preference for SQL Queries did not function. (Bug #12612409) When a routine contained CONCAT with a number as an argument, MySQL Workbench would return it as a BLOB. (Bug #11763872, Bug #56642) On Mac OS X, the Server Status tool would fail to find the server. (Bug #11766286, Bug #59365) MySQL Workbench would not export data when using a remote server connection through SSL with certificates. (Bug #11766196, Bug #59249) On Mac OS X, the window to set up a Standard TCP/IP over SSH connection contained incorrect descriptions. And the dialogue now behaves more intelligently. (Bug #11761555, Bug #54061) The error icon would continue to be displayed in the SQL editor after deleting a character to create the error, and then adding it back. This only affected multiline SQL statements. (Bug #11763319, Bug #56015) The Tab key would not navigate field values in the Set remote configuration parameters dialogue of the Server Administration panel. (Bug #11757375, Bug #49413) Closing MySQL Workbench while an unsaved model was open would prompt the user with a "MySQL Workbench has stopped working" error, with a Close button. MySQL Workbench now prompts to either save or close. (Bug #61802, Bug #12912241) While using the Forward Engineer wizard, any change detected in a connection option now clears the "Stored connection" field. (Bug #49921, Bug #11757818)
365

This section documents all changes and bug fixes applied to MySQL Workbench since the release of 5.2.41. Bugs Fixed The Reformat DDL for Views configuration option would generate invalid SQL syntax if the expression contained an even number of parts that were very long. (Bug #14396953, Bug #66068) There was a typographical error in the "Rename" dialogue that prompts a user to rename unsupported foreign key names that originate from old model files. (Bug #14399185, Bug #66113) The Search on server button would create an additional Search on server button each time it was pressed. (Bug #14395153) Data modeling would not allow table edits, and repeated attempts to do so would crash MySQL Workbench. (Bug #14374169, Bug #66013) After upgrading to MySQL Workbench 5.2.41, MySQL Workbench would freeze if the initial load involved a connection without a saved password. (Bug #14383570, Bug #66016) MySQL Workbench would sometimes crash after populating a model. (Bug #14211444, Bug #65423) On Microsoft Windows XP, the width of the line number column would display a maximum of four characters. It now displays additional characters, such as the number "10000". (Bug #14079497, Bug #65259) Undoing the last four changes via the history tab would only undo the last three changes. (Bug #14026666) Entering the caret ("^") character inside the SQL editor, followed by any other character, could cause MySQL Workbench to hang. This was a Scintilla bug that is now fixed. (Bug #13930994, Bug #64848) On Microsoft Windows, the Enter key would not create newlines within the table column comment dialogue. This was a Scintilla bug that is now fixed. (Bug #13891121, Bug #64714) On Microsoft Windows, certain conditions would allow the model overview pane to shrink, and only display a small portion of the diagram information. (Bug #13877323, Bug #64640) Synchronizing a model after adding a column to the model would not add the new column to the syncronized database. (Bug #13891063, Bug #63938) Models that were temporarily saved as "Unsaved models" could not be deleted. (Bug #13742833) On Mac OS X, attempts to store a password into the keychain could result in an error. (Bug #13387025, Bug #62279) A signal statement in a stored procedure was not supported, and would report a syntax error. (Bug #11763874, Bug #56644) Using \func would prevent the Apply changes to data option to function, and instead "Pending changes" error message windows would be displayed. (Bug #62061, Bug #12844298) On Ubuntu 12.04 64-bit, MySQL Workbench could freeze. (Bug #65331, Bug #14120708) Expanding the tree view for a database with a large number of tables (tested 30,000) would crash MySQL Workbench. (Bug #66036, Bug #14383521)
366
In the SQL Editor, the cursor would inappropriately flash. This was fixed while moving to the native Scintilla control. (Bug #61752, Bug #12757202)

This section documents all changes and bug fixes applied to MySQL Workbench since the release of 5.2.40. This version contains the initial release of the Database Migration Wizard. Functionality Added or Changed Added a new Data Import/Restore option to select the default schema to import to, and a button to create a new schema in case a dump is being imported from a single file. (Bug #13539030, Bug #63853) A word wrapping option was added to the SQL Editor. (Bug #11765583, Bug #58566) The Diagram object tooltip now displays the column comments. (Bug #11765060, Bug #57977) A Global Privileges tab was added to the Server Administration interface. It allows adding and editing individual global user privileges. (Bug #11761628, Bug #54141) Basic code completion functionality has been implemented. (Bug #11760500, Bug #13813099, Bug #52917, Bug #64525) The model wizards now remember the last connection that was added. (Bug #56515, Bug #11763761) MySQL Workbench added a migration wizard, which will migrate ODBC compliant databases to MySQL. (Bug #54731, Bug #11762168) Bugs Fixed The Search on Server option would not function, and instead it generated errors when searching MySQL Server 5.1. This option is now only available when connecting to MySQL Server 5.5 or greater. (Bug #14404138) MySQL Workbench was not compatable with alocal versions greater than 1.11.1. Compiling would generate errors related to AC_RUN_IFELSE usage, as opposed to the preferred AC_LANG_SOURCE. (Bug #14329354, Bug #65898) A snippets file could not be created. (Bug #14278287, Bug #65734) On Microsoft Windows 64-bit, closing MySQL Workbench from within the SQL editor could cause a crash. (Bug #14307316) The option to control specific user privileges is now available with MySQL Workbench. Before it was only possible to edit the roles (e.g., DBManager) but now the specific privileges (e.g., RELOAD) can also be modified. (Bug #14226955, Bug #65677) It is now possible to select a range of rows using the shift key. And on Mac OS X, the command key will now allow the selection of individual rows (Bug #14177386, Bug #65569) Comments and collation controls are now disabled until a column in the column editor is selected. Before it was always available, so invalid entries would attempt to be created, which would result in an error. (Bug #14177412, Bug #65574) MySQL Workbench would not load with Ubuntu 11.10. (Bug #14058886, Bug #63626) An orphaned privileges tab would be shown in the table editor when switching tables. Now only the current privilege tab is displayed. (Bug #14102537, Bug #65182)
367
The Edit, Find, Find and Replace operation was slow. (Bug #14079480, Bug #65262) Having a schema without a name in a model would cause MySQL Workbench to crash. (Bug #14017357, Bug #65119) Several exposed DbMySQL methods (such as makeSQLExportScript) were problematic, and have been replaced by the DbMySQLRE and DbMySQLFE modules. (Bug #13971951, Bug #62596) MySQL Workbench would fail to compile with automake 1.11.2 or greater, due to the pkglib_DATA reference. (Bug #13972001, Bug #63898) Using the '%' character within environment variables could cause MySQL Workbench to crash. (Bug #13989371, Bug #65056) The SQL Beautifier feature would remove DISTINCT from inner queries. (Bug #13970596, Bug #64932) Creating and then synchronizing a table in a model with a DOUBLE typed column would generate invalid SQL, thus generating an "Invalid SQL syntax" error. (Bug #13970484, Bug #64990) MySQL Workbench would crash while multiple model routines were opened. (Bug #13970497) The SQL Beautifier would delete WITH ROLLUP if it was contained within a subquery. (Bug #13919924, Bug #64796) The Replace All option would not function when the replacement string was empty. (Bug #13919875, Bug #64818) A new Copy Row (tab separated) option was added to the result set context menu within the SQL editor. A comma separated variant of this option already existed. (Bug #13884753, Bug #64724) Certain conditions would cause privilege related problems and emit errors such as "Incorrect Value Entered" when creating a table in one tab, altering it in another, then going back to the original tab. (Bug #13877873, Bug #64591) Passing a grt.classes.db_query_EditableResultset object to getattr() could cause a crash. (Bug #13893388, Bug #64777) On Linux and Mac OS X, it was not possible to select/copy multiple rows from within the result set grid. (Bug #13895191) Input elements are now correctly disabled until an editable row in the column editor is selected. Therefore, invalid values are no longer set in the model. (Bug #13812811, Bug #64550) Inputting invalid SQL would remain designated as such, even after the SQL was corrected. (Bug #13820997, Bug #64481) Internal log tables are now excluded while exporting a the MySQL database. The excluded tables are mysql.schema, mysql.apply_status, mysql.general_log, and mysql.slow_log. (Bug #13837725) Using Paste Row after Copy Row Data within the SQL editor would insert rows with extra apostrophes. For example, 'hello' would become ''hello''. (Bug #13840070, Bug #64630) Closing an SQL Editor tab that had a Find/Replace dialog box open, then subsequently closing the Find/Replace dialog box would crash MySQL Workbench. (Bug #13816167, Bug #64569) Changing the Default Collation of a schema after changing its name would reset the schema name to "new_schema". (Bug #13799456, Bug #64259)
368
The Edit table data SQL editor option would not properly display or save Unicode characters. (Bug #13790645, Bug #64447) On Mac OS X, the color dropdown in the object tool would not display the color properly. It instead showed the color code, and would not apply the color to the object. (Bug #13742905) All editor tabs now prompt to save data when these tabs are closed. Before, only the main tabs (like the SQL Editor) would prompt for to save. (Bug #13788071, Bug #64462) Opening the Scripting Shell window, followed by selecting then closing the snippet tab, would cause MySQL Workbench to crash. (Bug #13744364) If Plugins, Utilities, Indent Selected Lines is used while a row is selected, then MySQL Workbench would delete the selected row. (Bug #13744346) The Match Case search option did not function. (Bug #13790397) On Mac OS X, the Option key did not behave like a standard Mac OX application. For example, Option + Delete would delete one character instead of one word. (Bug #13702376, Bug #64217) Added version dependent keyword list support for syntax highlighting. Supports MySQL Server 5.0, 5.1, 5.5, and 5.6 (Bug #13699804) On Mac OS X, and while working with mixed-case table names, a foreign key could not be assigned to link two InnoDB tables together. (Bug #13639162, Bug #64109) Quickly executing the same query multiple times would cause MySQL Workbench to use an excessive amount of memory and CPU. (Bug #13642999, Bug #64077) After right-clicking on a value in the SQL editor and choosing Open Value in Viewer, selecting the text would insert extra new lines into the clipboard. (Bug #13538942, Bug #63753) The Model, Model Options, Diagram, Hide Captions option could not be altered (disabled) and would remain checked (enabled). (Bug #13571857, Bug #63937) MySQL Workbench would allow the creation of multiple foreign keys across multiple tables but with the same foreign key name. Synchronization would then emit a "Can't create table" error. (Bug #13548236, Bug #13500447, Bug #63642, Bug #62960) The Object Browser now manages procedures and functions separately, when before they could not co-exist with the same name. They remain under the routines group but have separate icons and menu options. (Bug #13548213, Bug #13730415, Bug #63849) Plugins, Utilities, Execute query would freeze MySQL Workbench if the query resulted in 1000 or more rows. (Bug #13470781) The Server Administration, Server logs, General Log Table option would not function, and only show a Try again button. (Bug #13530413) While editing in the Edit Table tab, Control + A would also select diagram objects. (Bug #13519852, Bug #63758) A "Removed corrupt column definition for Foreign key" error would sometimes be emitted while editing a table with foreign keys. (Bug #13519797, Bug #63772) OpenGL determination at startup has been disabled, and instead this check is performed while creating diagrams. The system could fail at startup, so now MySQL Workbench avoids this startup trouble and can better fall back to software rendering if necessary.
369
MySQL Workbench would also silently fail to load if "Microsoft Visual C++ 2010 Redistributable Package" was not available. This is now checked and reported to the user. (Bug #13512714, Bug #61969) The Open Value in Editor SQL editor option did not work with INT or NULL values. (Bug #13492493, Bug #62934) The Move to a group context option for database connections would cause saved connections below the target connection (that is being added to a group) to disappear. (Bug #13470318) After synchronizing a database, refreshing a model would not refresh the stored procedure information. (Bug #13418563, Bug #62879) The info and session tabs within the MySQL connection interface would not display any information. (Bug #13466537) The Options tab within the SQL Editor would always display an empty AUTO_INCREMENT value for tables using InnoDB. (Bug #13463458, Bug #63464) After making changes to a model, then closing the window, clicking Cancel on the unsaved changes warning/dialogue would close MySQL Workbench. Now the model window remains open. (Bug #13463465, Bug #63460) On Mac OS X, Command + A would not select all results from the result set. (Bug #13463374, Bug #63461) A query such as "SELECT * FROM SomeTable PROCEDURE analyse()" would only work if "limit rows" was disabled in the preferences. The MySQL Workbench query parsing has been extended to support this type of query. (Bug #13344686, Bug #62964) The MySQL Workbench bug reporting form (MySQL Bugs: Report) did not allow pasting content into the form. (Bug #13344751, Bug #62928) "MariaDB" has been change to "Aria" within MySQL Workbench. (Bug #13252479, Bug #62903) On Microsoft Windows, Server Administration, Server logs, Slow Log File would display an error instead of showing the slow query log. (Bug #13026572) Routine groups on the diagram was not updated after adding new routines to the group. (Bug #13029520, Bug #62496) Right-clicking on Catalog tree within the Model, Diagram context would display an empty line. (Bug #13025389) MySQL Workbench would crash after clicking EER links and options multiple times. (Bug #13024949) Clicking between routines with different comments would not update the description editor with information from the selected object. (Bug #13025359) The Connection Method option within the Edit Table Data window was partially hidden. (Bug #13025670) Detection of a connection to the local machine based on the IP address has been removed. There is now a selection between localhost, remote host, and db host on the initial New Server Instance page. Selecting localhost will let the wizard know that it is local, as otherwise the full path is now required, which for example allows 127.0.0.1 to be used as a remote host to support port forwarding. (Bug #12890503, Bug #62119)
370
The View, Home option did not function. (Bug #12879850) The sorting options within the Inserts Editor window did not function. (Bug #12884134) The MySQL Workbench window can now be resized to 1024x710. (Bug #12632406, Bug #60762) A confirmation dialog was added that warns users about attempts to edit stub tables, and it describes why these will be ignored by both synchronization and forward engineering. The dialog includes an option to either keep editing it as stub object, or to clear the stub flag and make the table appear in generated SQL. (Bug #12616360, Bug #61309) User Defined Types (UDT) could not be deleted when they were not referenced elsewhere. (Bug #12671629, Bug #61530) The synchronization wizard now allows the possibility to force synchronization of schemas that are thought to have been renamed. Otherwise, MySQL Workbench will recreate the schema from scratch. (Bug #12565644, Bug #61211) The EER Diagram zoom feature would not function. (Bug #12346981, Bug #60807) The Partitions tab within the Alter table context menu would not show all of the available partitions. (Bug #11933015, Bug #60235) On Mac OS X, having a large number of databases (1,000+) could cause performance issues where MySQL Workbench would load in several minutes, as opposed to a few seconds. (Bug #11869432, Bug #60420) MySQL Workbench would not allow a user to delete a saved server instance that contained an incorrect password. This incorrect password can now be deleted. (Bug #11765337, Bug #58295) The Synchronize Model operation would use an excessive amount of memory. (Bug #11762726, Bug #55355) MySQL Workbench would freeze while attempting to search and replace with a large number of strings, such as over 100,000. (Bug #11762890, Bug #55539) A new Model: MySQL preference was added for Forward Engineering and Synchronization to configure SQL_MODE. (Bug #11761659, Bug #54173) The Synchronization wizard has been changed to allow forcing synchronization of schemas that have the same name but an unexpected "last known name", which would cause a confusing scenario of the target database being recreated from scratch. (Bug #11756969, Bug #48962) Under certain conditions, adding a foreign key could generate invalid SQL code. (Bug #64539, Bug #13872284) A crash would occur if trigger code referred to tables in a schema different from the one where it is contained. (Bug #60041, Bug #13611382) On Mac OS X, MySQL Workbench would crash when changing database engines if a database included a table with uppercase characters. (Bug #65376, Bug #14117038) The Copy Column Names to Clipboard option could crash MySQL Workbench. (Bug #64881, Bug #13970600) MySQL Workbench now respects case-sensitivity when lower_case_table_names = 2. (Bug #60618, Bug #11926851) Closing MySQL Workbench while editing SQL Scripts will now prompt the user to save the edits. (Bug #61037, Bug #62959, Bug #12546710, Bug #13344705)
371
The zoom feature (in or out) could cause a fatal error. (Bug #65247, Bug #14136870) On Microsoft Windows, MySQL Workbench would ignore the system's font setting, but now uses it when MySQL Workbench is initialized. (Bug #62105, Bug #12872840) On Ubuntu 12.04, MySQL Workbench would not load. (Bug #64956, Bug #14180754) MySQL Workbench would sometimes repeat a warning during a successful action that followed the action with the warning. (Bug #62454, Bug #13014873) Deleting an EER diagram would cause MySQL Workbench to hang. (Bug #65174, Bug #14102990) While editing an EER diagram, and click-dragging the mouse cursor, the cursor now remains in the same place it was originally clicked. (Bug #64487, Bug #13813199) New or updated trigger content would disappear from the SQL Editor GUI, as it was required to reopen the table editor to see the changes. (Bug #65411, Bug #14137775) Loading large files (over 100MB) using File, Open SQL Script... would fail to load the script, and throw an out of memory exception while halting operation. Now, MySQL Workbench warns users if a file exceeding 100MB is attempted to be loaded, and no longer crashes when running out of memory but instead reports that the file was unable to be loaded. (Bug #55312, Bug #60780, Bug #61363, Bug #64186, Bug #11762687, Bug #12339717, Bug #12627645, Bug #13790375) If a view contains a row that is too long to be represented as a table column, it will now be substituted with an alias column in a placeholder table, similar to how mysqldump behaves. Before it could generate invalid SQL, and fail to synchronize the model. (Bug #63807, Bug #13538955) Using File, Export, Forward Engineer SQL CREATE Script would remove delimiters statements if the Omit Schema Qualifier in Object Names option was selected. (Bug #63742, Bug #13520528) MySQL Workbench now uses the MySQL Server limit for maximum comment lengths while using the forward engineering wizard. Before it would truncate comments to 60 characters, which was a MySQL Server limit before version 5.5.3. From the MySQL Server 5.5.3 changelog: the maximum length of table comments was extended from 60 to 2048 characters. The maximum length of column comments was extended from 255 to 1024 characters. Index definitions now can include a comment of up to 1024 characters. (Bug #62207, Bug #12904170) Adding a trigger with the Alter Table, Trigger interface now warns the user if the inputted trigger statement was invalid. Before, MySQL Workbench would output "No changes to object were detected." if the SQL was valid, but without a CREATE TRIGGER statement. (Bug #61712, Bug #12908810) Synchronizing a model would drop, and then re-add, indexes and foreign keys if the order of these indexes and foreign keys were different. This could happen because MySQL Workbench would add UNIQUE indexes in the order added by the user, whereas the MySQL Server puts them first. (Bug #60230, Bug #11829807) When altering a table with uppercase letters in the table name, MySQL Workbench would automatically convert the table name to lowercase. (Bug #64072, Bug #13639292)

This section documents all changes and bug fixes applied to MySQL Workbench since the release of 5.2.39.
372
Functionality Added or Changed The File, Export, Forward Engineer SQL ... wizards now have the option to use the same configuration settings from the last time Forward Engineer SQL ... was used. (Bug #34977, Bug #11748058) The SQL editor tab now displays the selected database in the header. (Bug #50932, Bug #11758694) Bugs Fixed On Microsoft Windows, the mysqlrplshow MySQL Utility was missing. (Bug #13773189) Within the SQL Editor, MySQL Workbench would freeze after choosing Replace All when the find field was empty. (Bug #13744385) On Microsoft Windows XP, performing a database export could cause MySQL Workbench to crash while using the Export to Self-Contained File option with a UNC path. (Bug #13701996, Bug #64267) On Mac OS X, the schema sidebar was missing a horizontal scrollbar. (Bug #13596326, Bug #64000) Inserting a snippet into the SQL Editor could insert incorrect characters. (Bug #13466559) MySQL Workbench would generate invalid SQL while using the Partitioning tab when altering a table. (Bug #64396, Bug #13788180) The Data Export option would not use the current date in the folder name containing the exported data. (Bug #63893, Bug #13571760) Database, Synchronize Model would not update the view after a new field was added. (Bug #62569, Bug #13051152) On Microsoft Windows, the MySQL Workbench installer would sometimes not detect where VISUAL C+ + 2010 was installed. A workaround is to append CPP_100_RUNTIMES to the eCustomProperties property in the .msi file. (Bug #62141, Bug #12872805) After a connection has timed out, clicking Reconnect to DBMS would freeze MySQL Workbench. (Bug #64467, Bug #13840041) On Mac OS X, expanding the schema for a remote database from within the SQL Editor tab would crash, if the SQL editor tab was closed before the tables were done being fetched. (Bug #63589, Bug #13500242) On Mac OS X, when viewing the results of a query that would normally exceed the window width, the last column would have a width of one character if the column type was numeric. (Bug #62588, Bug #13365052) Within the Database, Synchronize With Any Source wizard, synchronizing a model from a Live Database Server source to a Model Schemata destination would crash after the Retrieve Object Information step. (Bug #64553, Bug #13812932) Password-based SSH authentication would still check the key-based authentication files within .ssh/ before prompting for a password. (Bug #60024, Bug #12672238) The minimum size of the MySQL Workbench window has been lowered to 980x600 pixels, although officially the minimum screen resolution requirement remains at 12801024. (Bug #63519, Bug #13463411) 373
MySQL Workbench would not build with GLib 2.3x+, as only glib.h can be included directly. (Bug #63705, Bug #13500364) Copying SQL to the clipboard could cause MySQL Workbench to hang or crash if the table comments contained Unicode characters that exceeded the buffer size. (Bug #64611, Bug #13840045) While using MySQL Workbench to adjust a Users and Privileges role with a MySQL Server version prior to 5.1.6, an unhandled exception would result from MySQL Workbench attempting to access the mysql.event table. (Bug #63149, Bug #13496657) A query like SELECT foo+1 FROM bar could cause a crash. (Bug #64051, Bug #13629089) Scrolling the mouse wheel now only scrolls the focused window. (Bug #61480, Bug #12661387) On Fedora Linux version 16 and greater, the service command is now used to start and stop the MySQL Server, instead of /etc/init.d/mysqld. (Bug #63777, Bug #13519817) MySQL Workbench would prompt a user for the password to reconnect to a MySQL server that had lost the connection, and this password dialogue would not have focus yet still showed as the top window with a blinking cursor. To reduce confusion, this password window is no longer the top window. (Bug #62003, Bug #12918370) On Windows XP, attempts to copy values from multiple cells would fail, and not insert values into the clipboard. (Bug #64281, Bug #13726466) The Open value in viewer window did not open with SELECT queries that used the cast function. (Bug #63874, Bug #13548148) The following sequence would crash MySQL Workbench: Database, Reverse Engineer to generate an EER diagram, then Database, Synchronize with Any Source, and then a mouse-click would cause the crash. (Bug #61876, Bug #12912593) The following sequence could crash MySQL Workbench: "Open a model", "Synchronize the model with a remote database", "Modify the model", and then "Synchronize the model" a second time. (Bug #63943, Bug #13779239) The Control + a key combination would not select all of the text within a window. (Bug #63752, Bug #13511244) SELECT queries could crash MySQL Workbench during the validation stage of the SQL Editor. (Bug #64435, Bug #13788133) The _idx suffix is now added to foreign keys as they are created. And MySQL Workbench checks for duplicate named foreign keys if a document is loaded from a previous version of MySQL Workbench. And if duplicates are found, then the user is given the choice of renaming them. (Bug #60705, Bug #12621452) Queries that explicitly set RESTRICT will now synchronize properly with those that do not, because RESTRICT is the default behavior in MySQL. (Bug #62432, Bug #13491535)

This release updates the bundled MySQL Utilities to version 1.0.5. It contains no other new features or bug fixes. Functionality Added or Changed Updated the bundled MySQL Utilities to version 1.0.5.
374

This section documents all changes and bug fixes applied to MySQL Workbench since the release of 5.2.37. Functionality Added or Changed The width of the "Reference column" drop-down selector is now set to the widest entry. (Bug #53278, Bug #11760835) Bugs Fixed On Linux, the result set window would not display properly. (Bug #13615255) While editing Limit Connectivity to Host Matching within the Server Administration, Users and Privileges, Login window, the Apply button would not be available until one of the other three Users and Privileges fields was changed. (Bug #13470424) Comments that spanned multiple lines and included stored procedures with comments that were surrounded by conditional comments would not be handled properly, as MySQL Workbench would end the outer comment unconditionally when the first inner comment was finished. (Bug #13490118) On Microsoft Windows with the "classic mode" theme set, MySQL Workbench buttons were difficult to read. (Bug #13470583) Generating a DBDoc report with both HTML Detailed Frames and Include DDL code for objects enabled would cause MySQL Workbench to stall. (Bug #13471637) The Plugins, Utilities, Execute Query Into Text Output feature would duplicate the first column, and fill it with NULL values. (Bug #13470770) Scripting Shell would fail to continue running after a breakpoint. Clicking Execute Script after a breakpoint now continues execution of the script. (Bug #13470397) The Scripting shell window lost focus after opening and closing a tab. (Bug #13470451) On Microsoft Windows, using the Manage Server Instances menu to delete server instances could cause MySQL Workbench to generate an internal error while closing the Manage Server Instances window. (Bug #13466083) For Microsoft Windows, the Download Prerequisites link within the MySQL Workbench installer now directly links to the prerequisites manual page. (Bug #13448582) On Linux, MySQL Workbench .mwb files would be detected as Zip files. (Bug #13466584) The SQL Editor Execute the Explain Command... feature did not function properly, and would return zero results. (Bug #13466571) Using the Open Connection to Start Querying dialog with a new (not stored) connection would cause MySQL Workbench to crash. (Bug #13028855) The editor tabs would not update after a user was added. (Bug #12884776) On Linux, while saving a new model with a note, the Save to File dialogue would not prompt to name the file. (Bug #12933345) It was possible for MySQL Workbench to generate a pop-up window underneath a different pop-up window, thus requiring a restart of MySQL Workbench when the bottom pop-up was required to be closed first. (Bug #12927510)
375
Under the File menu, using the Print to PDF... and Print to PS File... options for a model would crash MySQL Workbench. (Bug #12884845) Dumping a schema via the Data export and restore option now prompts for a correct password, as needed. Before it would simply fail to export. (Bug #12903967) Opening a Server Administration tab for a server instance that has remote management via SSH enabled would result in an error, and fail to load. (Bug #63857, Bug #13655999) Within Server Administration, Users and Privileges, selecting Add Account after sorting the users would insert the new user into the list alphabetically, yet open the bottom user entry into the editor. (Bug #63951, Bug #13702340) On Linux, the Object Info panel within the SQL editor would not show information about the object, and would instead remain empty. (Bug #63960, Bug #13608228) On Linux and Mac OS X, the Replace All search feature would hang, and not function properly. (Bug #63764, Bug #13520443) Query, Commit Result Edits and Query, Discard Result Edits could result in "Unrecognized command" errors, and not function properly. (Bug #63744, Bug #13511195) On Microsoft Windows, tab titles were difficult to read on systems with dark backgrounds. (Bug #63715, Bug #13500349) The search box within the MySQL Workbench toolbar did not perform searches. (Bug #61825, Bug #12757354) On Microsoft Windows, the Open in viewer menu could be blank while viewing results. (Bug #63873, Bug #13548115) Closing a tab could result in an unhandled exception. (Bug #64152, Bug #13655860) Choosing the Open value in Editor option would scroll the result set to the top. Selecting this option no longer refreshes the results, so the selected row remains intact. (Bug #63860, Bug #13539049) Executing a query after reordering multiple editor tabs would make the inactive editor tab active, and execute that query. (Bug #63866, Bug #13542154) On Microsoft Windows, changing or deleting a row or column within a model, could cause a crash. (Bug #63056, Bug #13344572) The object editor could leak memory and crash MySQL Workbench while handling notifications. (Bug #63025, Bug #13492608) MySQL Workbench would highlight the MySQL 5.6 reserved words name, type, and types. (Bug #62775, Bug #13252599) Clicking the foreign keys tab within the Alter table context could crash MySQL Workbench. (Bug #63050, Bug #13492730) Recovery of the last state using either the Auto-save feature, or the Save snapshot of open editors on close option, would sometimes load improperly by creating an empty schema and/or crash while closing opened SQL editor tabs. (Bug #61950, Bug #12917371) Exporting a model to a CSV file could crash MySQL Workbench. (Bug #63883, Bug #13685708) Double-clicking on a table within the EER diagram editor would sometimes crash MySQL Workbench. (Bug #62451, Bug #13014823)
376
Selecting and editing multiple indexes or foreign keys would crash MySQL Workbench. (Bug #61863, Bug #62057, Bug #12757370, Bug #13013715) On Mac OS X 10.7+, the "Open File" panel would attempt to show hidden files, which would fail and cause no files to be shown. MySQL Workbench no longer attempts to display hidden files on Mac OS X. (Bug #62172, Bug #12912085) Pressing the Control + Enter key combination within the SQL editor would generate a recoverable error. (Bug #62169, Bug #12927292) If the charset/collation is set to use the default value, then DEFAULT will now be inserted as the charset/ collation name within generated queries. (Bug #61202, Bug #12622649) Plugins, Utilities, Reformat SQL Query would mangle queries by removing the first SELECT statement if a subquery clause was present. (Bug #60311, Bug #12613662) Pasting a query with \r line endings instead of \r\n or \n could cause MySQL Workbench to mangle the query. Line endings are now normalized after pasting, like they already were while loading files. (Bug #56334, Bug #11763603) On Microsoft Windows, rapidly repeating a query could emit an error. (Bug #56776, Bug #11763997) The main schema information found within the object browser now updates after a table is altered, and collapses the expanded details. And selecting an object now reloads the data, which means the current (altered) data is displayed. (Bug #63828, Bug #13538990) MySQL Workbench would not work with paramiko 1.7+. (Bug #63750, Bug #13519860) MySQL Workbench did not test for and use the gl.pc pkgconfig files if present, to determine the location of GL/{gl,glx}.h and libGL.so. (Bug #63818, Bug #13538964) MySQL Workbench would fail to compile under certain PCRE setups, like when pcre.h existed within / usr/include/pcre/. (Bug #63819, Bug #13538971) Moving the placeholder row (an empty row) around within the table editor would crash MySQL Workbench. The placeholder row can no longer be moved. (Bug #64122, Bug #13629953) Choosing the Close All But This option within the routines manager would freeze MySQL Workbench. (Bug #64133, Bug #13630602) When viewing the foreign key definition window of the Alter Table editor, the restrict foreign key option did not display for either the update or delete actions, and instead the value would appear empty. (Bug #63978, Bug #13596254) On Mac OS X, opening files saved from previous versions of MySQL Workbench would result in an empty window, without data being loaded. (Bug #63932, Bug #13571842) On Microsoft Windows, the Routines editor would insert extra line endings. (Bug #55006, Bug #11762414) The Server Status window would incorrectly sort options. Numeric fields are now sorted numerically (e.g., 1300 is now after 500). (Bug #61659, Bug #12698865) The File, Open SQL Script, Files of Type dialogue would incorrectly give the option to open files with the .dbquery suffix, instead of .qbquery. (Bug #63861, Bug #13541769) A query similar to the following would crash MySQL Workbench: select c.* from actor c where actor_id=38 (Bug #63940, Bug #13582514)
377
The Beautify Query feature incorrectly formatted statements containing the UNION clause, which left the query with syntax errors. (Bug #64120, Bug #13629967) After clicking Apply to alter a table where changes are not being made, the output window says "Preparing..." and does not automatically change to "No changes detected" until the window is clicked. (Bug #63842, Bug #13548232) MySQL Workbench would freeze when a SELECT statement was executed on a table without private keys, and that included at least one UNIQUE NOT NULL column. (Bug #63867, Bug #13542546) On Linux, right-clicking on a table and choosing the Alter Table feature would perform no function. A workaround was to delete all XML nodes from /usr/share/mysql-workbench/modules/data/ editor_mysql_table_live.glade like:
<child internal-child="selection"> <object class="GtkTreeSelection" id="treeview-selection5"/> </child>
(Bug #62686, Bug #13491865) Queries containing a UNION are now excluded from the automatic addition of the LIMIT clause, when the Limit Rows preference is enabled. (Bug #62524, Bug #13029474) After a connection has timed out, clicking Reconnect to DBMS would freeze MySQL Workbench. (Bug #61722, Bug #12725314) The Beautify Query wizard would remove spaces from MySQL date function parameter values that contain INTERVAL. (Bug #61021, Bug #12546864) MySQL Workbench would crash while opening an existing EER model, after a file failed to open. (Bug #63841, Bug #13539006) Individual model settings are now respected. Before they would be ignored in favor of the global settings. (Bug #61771, Bug #12757255) While attempting to synchronize a database to any source, the Execute button to perform the synchronization was missing. Only the Go Back and Close buttons were shown. The Execute button is now standardized for all database synchronization options. (Bug #62130, Bug #12872823) On Microsoft Windows, and when called from the home screen, opening and immediately closing the Manage Server Instances window would result in an unhandled exception. (Bug #63927, Bug #13571816) On Mac OS X, exporting a database that has a stored procedure resulted in an unhandled exception. (Bug #63653, Bug #13476062) A pop-up window is no longer generated when selecting an inactive server from within the Server Administration panel. (Bug #61810, Bug #12757347) On Microsoft Windows, using Alt based key shortcut combinations would not always work. (Bug #54119, Bug #11761607) The dialog windows now remain in front, even when another part of MySQL Workbench is clicked. (Bug #48692, Bug #11756737) MySQL Workbench now detects duplicated trigger names while using the Model,Validation, (MySQL)>Validate all and Model, Validation (MySQL), Check integrity sequences. (Bug #44063, Bug #11752780)
378
Running a SELECT statement and attempting to alias the only column selected would result in a crash. (Bug #64123, Bug #13629962) When right-clicking on a table that has triggers, and then choosing Create Statement to either send the statement to the clipboard or SQL editor, the trigger creation statement is written before the table creation statement. (Bug #61698, Bug #12756722) MySQL Workbench would crash after the following sequence: Synchronize Model With Database, Fetch Object Info, Continue. (Bug #63746, Bug #13591854) MySQL Workbench would emit an error (error code: 1064) with queries using WITH ROLLUP. (Bug #57178, Bug #11764355) MySQL Workbench would not behave correctly with ON UPDATE CURRENT_TIMESTAMP as a default value, while synchronizing models, and would update the field. (Bug #61087, Bug #12546735) When a table had columns like DOUBLE(M,D), the data model synchronization would discard the (M,D) specification, and convert the columns to DOUBLE(11). (Bug #61165, Bug #12565933) Tables without an engine set were treated as though they were unable to support foreign keys. Therefore, the foreign key declaration would be missing after forward engineering these tables. A workaround is to explicitly set the table engine to InnoDB. (Bug #63934, Bug #13562926)

This section documents all changes and bug fixes applied to MySQL Workbench since the release of 5.2.36. Functionality Added or Changed The SQL editor now automatically fetches table data. (Bug #63590, Bug #13500202) Bugs Fixed Under Server Administration, the location of the configuration file was not visible. It is now shown within the configuration file label. (Bug #14017264, Bug #65033) The SQL editor would open a table in read-only mode when opened from either the Edit Table Data link via the home screen, or if the schema tree was not expanded. (Bug #13466131) On Mac OS X, the File, Open Recent feature would open the incorrect script. (Bug #13028666) Viewing the Server Logs on a MySQL server after it has been stopped, resulted in an unhandled exception. (Bug #12908134) Pasting from the clipboard would not work in the hostname and related fields. Users are now able to paste values into these fields. (Bug #11753997, Bug #45528) Options unrelated to the SQL Editor would be available under the View menu while a SQL editor window was open. (Bug #11763150, Bug #55830) On Mac OS X, clicking Apply within the Alter Table dialogue on a table with foreign constraints would crash MySQL Workbench. (Bug #62042, Bug #12844307) Invalid SQL was generated when a schema name contained a dot. Table names are now enclosed in quotes. (Bug #63710, Bug #13500360) MySQL Workbench required the Andale Mono font. (Bug #61782, Bug #12757325)
379
The export feature would sometimes fail when exporting tables with stored procedures, and with Dump Stored Procedures checked. And also having Export as Dump Project Folder selected would result in an unhandled exception. (Bug #57500, Bug #11764642) The Help, Check for Updates feature did not function properly. (Bug #63534, Bug #13463399) The SQL editor would not load under certain circumstances. The check for restoring split positions was corrected to solve this issue. (Bug #63582, Bug #13490891) The password prompt dialog is no longer the topmost window over all open applications on a system, but now it's only the topmost MySQL Workbench window. (Bug #63499, Bug #13496347) MySQL Workbench now quotes table names in generated SQL queries, when the table name contains characters that would break the SQL statement. (Bug #63600, Bug #13497088) Generating a list of tables and views was slow, when compared to the previous MySQL Workbench version. (Bug #63633, Bug #13485667) The field editor would hang when large text values were shown. (Bug #63606, Bug #13485779) MySQL Workbench would sometimes be unable to save changes that were only to comments. It used a hard limit, but now uses the MySQL Server limit for maximum comment lengths. For example, it would compare the first 60 characters of a table comment change, and generate an error if the change did not affect the first 60 characters. From the MySQL Server 5.5.3 changelog: the maximum length of table comments was extended from 60 to 2048 characters. The maximum length of column comments was extended from 255 to 1024 characters. Index definitions now can include a comment of up to 1024 characters. (Bug #61626, Bug #12694146) MySQL Workbench would generate an exception after editing and then closing a table tab within the EER diagram window. (Bug #63591, Bug #13463991) Creating a foreign key using the Place a relationship using existing columns EER option would crash MySQL Workbench. (Bug #63629, Bug #13480328) Exporting a database that has a stored procedure, resulted in an unhandled exception. (Bug #63653, Bug #13476062) The user administration panel did not fit on systems using a 1024x768 screen resolution. (Bug #62341, Bug #12967541) Changing a schema name with routines present would prepend and append invalid delimiters. (Bug #63624, Bug #13470435) MySQL Workbench could freeze while importing a dump. (Bug #63669, Bug #13485795) Case changes to ENUM values were not recognized by MySQL Workbench. (Bug #60478, Bug #11889204) Database synchronization would sometimes confuse similar table and routine names. (Bug #61028, Bug #12656879) Altering the case of a table name caused an error, when that was the only change and the SQL Identifiers are Case Sensitive option was set to true. (Bug #58808, Bug #11765806) The Forward engineering feature now preserves case for schema names, even on case-insensitive systems. Before it would create lowercase variants of the schema names on these systems. (Bug #56237, Bug #11763520)
380
Within the Database, Forward Engineer dialogue for a Model, the DROP Objects Before Each CREATE Object option was ignored if the Export MySQL Table Objects option was not selected. (Bug #59200, Bug #11766157) The Forward engineer feature would sometimes create invalid SQL syntax for old MySQL Workbench files with deleted routines and roles. (Bug #53973, Bug #11761473)

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

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)
387
The Copy Insert Template to Clipboard option was added to the Model View. For more information, see Figure 7.8, A Table on an EER Diagram. (Bug #54887, Bug #11762310) The query history is now saved between Workbench sessions. (Bug #51388, Bug #11759102) Usernames and schemas can now be sorted. (Bug #55318, Bug #11762692) Bugs Fixed The Administrator now allows various authentication plugins (such as Windows Auth, PAM) to create user accounts. The dropdown for the authentication method will only be displayed if MySQL Workbench detects that additional authentication plugins are enabled by the server. (Bug #12899893) 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) On Mac OS X, disabling the Enable data changes commit wizard preference setting would not disable the wizard. (Bug #61354, Bug #12616314) MySQL Workbench would not load the configuration options with MariaDB due to version number differences between MariaDB and MySQL. (Bug #61219, Bug #12605404) Closing MySQL Workbench would not prompt to save SQL Editor scratch tabs. (Bug #58899, Bug #11765889) The is_enabled() method was added to the mforms View class. (Bug #62140, Bug #12860149) The database connection splash screen would freeze after opening a server administration instance. It would work perfectly the second time. (Bug #61693, Bug #12756623) It was not possible to drop multiple selected tables or schemas. (Bug #55688, Bug #11763027) 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) MySQL Workbench crashed with a segmentation fault after the connection step of a model synchronization. (Bug #61822, Bug #12742008) Under certain circumstances, closing a query window would not prompt to save the query. (Bug #61160, Bug #12565971) Create EER Model, Schema Privileges, Add Role, Privileges, and then Uncheck All Privileges caused MySQL Workbench to crash. (Bug #61308, Bug #12613935) 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 MySQL Workbench SE MySQL Bug Reporter linked to bugs.mysql.com instead of support.oracle.com. (Bug #60364, Bug #11872318) The Synchronize with Any Source option reversed the 'destination' and 'source' database names within the generated SQL statement. (Bug #62189, Bug #12921676)
388
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) 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) The SQL Editor Output, History window contained escaped characters. For example, a "'" was written as "'". (Bug #61345, Bug #12605093) 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) 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) 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 Linux, the Reverse Engineer Database, Select Objects to Reverse Engineer dialogue contained a menu titled label. (Bug #61327, Bug #12600868) MySQL Workbench would not compile with GNU C Compiler (GCC) version 4.6. (Bug #60603, Bug #12617226) The Find Plugin in Web Repository option was removed from the MySQL Doc Library action. (Bug #61305, Bug #12613922) 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) The Management, Server Logs, Slow Query Log view resulted in an unhandled exception after the initial Newest button usage. (Bug #58810, Bug #11765808) The SQL Editor Overview tab did not refresh after a schema was deleted. (Bug #61314, Bug #12616355) The Object Browser now automatically refreshes after an object is changed. (Bug #56704, Bug #11763930) 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 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) 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)
389
Viewing the Admin Management option Server Logs with an empty TABLE resulted in an unhandled exception. (Bug #61523, Bug #12674989) On Ubuntu Linux, MySQL Workbench crashed with a segmentation fault when executing the View, Output combination twice. (Bug #61303, Bug #12601189) The query beautifier added superfluous identifier quote characters to the end of some queries. (Bug #60576, Bug #11926859)

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

This section documents all changes and bug fixes applied since the release of 5.2.33. Bugs Fixed
394
Creating a relationship broke the model file due to the index and foreign key having the same name. (Bug #60564, Bug #11926856) Attempting to open a saved model produced this error:
Error unserializing GRT Data. db.mysql.Table. Expected Type db.mysql.Column, but got
(Bug #60369, Bug #11840427)

This section documents all changes and bug fixes applied since the release of 5.2.32. Bugs Fixed The Reformat SQL Query option would sometimes fail, and emit an error. (Bug #58856, Bug #11765852) MySQL Workbench would incorrectly report that the MySQL server had stopped. (Bug #51146, Bug #11758886) The query beautifier failed for queries containing subqueries. (Bug #58835, Bug #11765832) The ability to synchronize non-model sources was added. (Bug #60009, Bug #11766805) It was not possible to forward engineer a model, or synchronize it with a live model. (Bug #60396, Bug #11850052) In the Administrator, when Manage Security was selected, an error message was displayed in the status bar. It was not then possible to see and therefore manage user privileges. (Bug #60370, Bug #11840439) In the Users and Privileges task of the Administrator, it was not possible to sort the users alphabetically. (Bug #56456, Bug #11763710)

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)
395
Dropping a table from the Object Browser did not remove the table's icon. (Bug #52878, Bug #11760462) Primary and foreign keys are now displayed with different icons. (Bug #53503, Bug #11761049) MySQL Workbench crashed when closing the query results tab in the SQL Editor. (Bug #59774, Bug #11766626) In the SQL Editor, switching between query tabs did not switch the associated results panel. (Bug #57486, Bug #11764628) 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) When deleting a recursive foreign key constraint, the primary key was also mistakenly deleted. (Bug #59668, Bug #11766538) 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) 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) 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) 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 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) 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'
396
(Bug #59559, Bug #11766448) When a model was forward engineered, the primary keys were not created in the generated script. (Bug #58926, Bug #11765913) When exporting a model, if the Skip Creation of FOREIGN KEYS option was selected, indexes were not created. (Bug #56389, Bug #11763649) 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 Administrator, when making a backup with the --single-transaction option enabled, the -lock-tables option was erroneously still enabled. (Bug #58562, Bug #11765579) 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) 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) 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) 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) 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) 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) 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)
397
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) 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 geschtzten Speicher zu lesen oder zu schreiben. Dies ist hufig ein Hinweis darauf, dass anderer Speicher beschdigt ist.
(Bug #58554, Bug #11765571) 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) Attempting to create a new user with MySQL Workbench failed with this error:
Unhandled exception: Error adding account accountName@%:
(Bug #59000) 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) 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) Running the version of mysqldump supplied with the MySQL Server package resulted in this error:
Operation failed with exitcode -1073741819
(Bug #59411) SQL Editor did not load certain text files correctly, and inserted erroneous empty lines between text. (Bug #58850)
C.1.1.16. Changes in MySQL Workbench 5.2.31a (2010-12-13)

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 398
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 SQL Editor did not load certain text files correctly, and inserted erroneous empty lines between text. (Bug #58850) 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< <template-parameter-1-1> >::operator->() const [with T = Sql_editor]: Assertion `px != 0' failed. Aborted
(Bug #58833) 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) An unexpected error was generated when attempting to modify the script created in the Forward Engineer to Database wizard. (Bug #58893)

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

This section documents all changes and bug fixes applied since the release of 5.2.29. Functionality Added or Changed 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)
404
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) Bugs Fixed 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) 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) After a query was executed, MySQL Workbench crashed when the Export button was clicked to export the result set to a file. (Bug #57379) 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) 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) 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) 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) 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) The default settings for the Export Directory Path in the Workbench Preferences dialog used mixed file path delimiters (both '/' and '\'). (Bug #57944) 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) 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 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)
405
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) 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) Foreign keys were not updated when a referenced column was deleted. (Bug #55219) 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) The safe updates option on the SQL Editor tab of the Preferences dialog required a MySQL Workbench restart to take effect. (Bug #56159) 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)

This section documents all changes and bug fixes applied since the release of 5.2.28. Functionality Added or Changed The Autosave feature was added. (Bug #50044, Bug #11757926) An open model that has not been saved is now automatically saved after a user-settable period. On loading a model file, MySQL Workbench will notify the user if the file was not previously saved correctly, due to a crash or power failure. MySQL Workbench can then attempt to recover the last auto-saved version. Note that for automatic recovery to be available for a new file, it will have to have been saved by the user at least once. (Bug #56718) Bugs Fixed Security Fix: Bug #57080 was fixed. Scripts could successfully be executed on the MySQL Server failed to execute in the MySQL Workbench SQL Editor. (Bug #56833) In the Model View, MySQL Workbench crashed when the Output tab was reopened after previously being closed. (Bug #57150) Screen areas in the Administrator did not redraw correctly. It was necessary to move the main window to force a redraw. (Bug #55490) If an EER diagram was created and then closed, attempting to reopen it caused MySQL Workbench to display an unexpected error dialog. (Bug #57259) In the Administrator, clicking the Data Dump tab generated the error Error updating DB: float division and schemata were not displayed. (Bug #56658) In the SQL Editor, if some table data was edited, and then the connection to the server was lost, clicking the Apply changes to data toolbar button caused MySQL Workbench to crash.
406
Now MySQL Workbench shows an error message in the Output tab when a connection is lost. Once the connection is back up, clicking Apply changes to data re-establishes the connection and sends the changes to the server. (Bug #56170) If a foreign key was set to RESTRICT for On Delete and On Update on the Foreign Keys tab of the Table Editor, MySQL Workbench generated SQL code to drop and add this key on every subsequent synchronization attempt. (Bug #55155) Clicking the Inserts tab of the Table Editor resulted in the MySQL Workbench Unexpected Error dialog being displayed. (Bug #57346) Changes made to a server instance were not saved. In particular, changing installation type to Custom was not saved, and changes to the sudo command were also not saved. (Bug #57026) It was only possible to connect to a MySQL server for administration using an SSH connection. (Bug #56874) Attempting to open the Table Editor in the SQL Editor multiple times for a table that contained no primary key caused MySQL Workbench to crash. (Bug #57139) In the Alter Table dialog of the SQL Editor, attempting to create a new index in the Index tab was not actioned when the Apply button was clicked. The dialog reported that no changes to object were detected. (Bug #56906) When synchronizing a model to a live database, if a database was deselected in the wizard, a DROP statement for that database was generated in the SQL code to prevent it from being part of the synchronization process. This caused that database to be dropped from the live database, with corresponding loss of all data. (Bug #56938) When attempting to open an EER Diagram by double-clicking it in the Model Overview, MySQL Workbench generated this unexpected error:
Cannot access a disposed object. Object Name: ModelDiagramForm.
(Bug #56963) Folding of iteration statement blocks, such as WHILE, REPEAT, and LOOP, did not work correctly in the SQL Editor. The loop end constructs such as END WHILE, END REPEAT, and END LOOP were not recognized as expected. (Bug #55358) If a table containing a User Defined Type based on VARCHAR was forward engineered, the resulting SQL did not correctly quote the VARCHAR value, resulting in a server error. For example, this code was generated:
CREATE TABLE IF NOT EXISTS `x`.`tabley` (`customstring` VARCHAR(10)); INSERT INTO `x`.`tabley` (ìd_customstring`) VALUES (example);
The correct INSERT statement should be:

INSERT INTO `x`.`tabley` (ìd_customstring`) VALUES ('example');
(Bug #56710)

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

This section documents all changes and bug fixes applied since the release of 5.2.26. Functionality Added or Changed Several changes were made to the Synchronize Model With Database wizard: The wizard shows all schemata in a model, regardless of whether they exist in the live database. The wizard shows a list of schemata that exist in the model but are missing from the live server, with a note recommending the use of the Forward Engineering wizard. The wizard does not auto-select schemata names that are in the model but not in the live database. (Bug #54748) Bugs Fixed
410
When the Alter Table dialog for an InnoDB table was displayed in an SQL Editor session, the Foreign Key Options Index showed INVALID when a foreign key in the Foreign Keys tab was clicked. (Bug #54471) When an attempt was made to synchronize a model with a live database, no schemata were listed as available in the Synchronize Model with Database wizard. This happened when the name of the schema in the model and the schema on the live server differed only in lettercase. (Bug #55147) At startup, these warnings were generated in the Workbench Scripting Shell:
Starting Workbench...Registered 147 GRT classes. WARNING: Could not load wb.mysql.validation.grt.dylib: Invalid module /Applications/MySQLWorkbench.app/Contents/PlugIns/wb.mysql.validation.grt.dylib WARNING: Could not load wb.validation.grt.dylib: Invalid module /Applications/MySQLWorkbench.app/Contents/PlugIns/wb.validation.grt.dylib
(Bug #54929) When an attempt was made to synchronize a modified exported script with the current model, using File, Export, Synchronize with SQL Create Script, the model was not updated. (Bug #54501) After dropping a schema from the list in the Object Browser, the schema that was dropped remained, but with the name of the schema that followed it. Refreshing the list of available schemata produced an unhandled exception:
An unhandled exception has occurred: Invalid node index
(Bug #55861) MySQL Workbench crashed when using the Export recordset to an external file command button on the result pane of the SQL Editor. (Bug #55554) When using the Edit Table Data wizard (launched from Home screen), if a database with a single table was connected to, after selecting the table, the Finish button remained grayed out. (Bug #54942) In the SQL Editor, right-clicking a routine name in the Object Browser caused MySQL Workbench to exit unexpectedly. (Bug #55822) If a table was copied in the EER Diagram view, and then the model was synchronized with the live database, the synchronize functionality did not recognize the copied table as a new table and overwrote the original table. (Bug #55566) Renaming a column with a foreign key resulted in an invalid script being generated on forward engineering or synchronization with a live database. (Bug #55502) The second attempt to save a read-only model file produced this error:
Couldn't backup existing file name-of-the-file.mwb: No such file or directory
(Bug #55439) When a table was being edited in the Table Editor, and its name was changed, the name change was not reflected on the Table Editor's table tab. (Bug #55338) It was not possible to add the LOCK TABLES privilege when assigning a new role in the Model Overview because that privilege was missing from the available options. (Bug #55186) Selecting the Check Duplicated Identifiers (Additions) operation from the Validation (SQL) submenu of the Model menu produced this error message:
411
Type mismatch: expected object of type db.Schema, but got workbench.physical.Model
(Bug #54968) The schema collation was not saved after being changed in the Table Editor. (Bug #55152) Selecting Validate (SQL) from the Model menu and then selecting the Validate All option reported no errors. Selecting Forward Engineer from the Database menu and selecting Run Validations also reported no errors. However, executing the SQL script resulted in this error:
ERROR: Error 1005: Can't create table 'xxx' (errno:150)
(Bug #54985) MySQL Workbench crashed when using the Partitioning tab of the Table Editor. (Bug #55761) Forward engineering a model to a live database caused MySQL Workbench to crash. (Bug #56009) MySQL Workbench crashed in the foreign key editor. The Microsoft Visual C++ Runtime Library runtime error generated prior to the crash was:
R6025 - pure virtual function call
(Bug #55910) The Dump tab did not display the target folder before the dump was performed. (Bug #55945) Dumping tables or schemata without the LOCK TABLE privilege produced this error:
mysqldump: Got error: 1044: Access denied for user 'wwroot'@'%' to database db' when doing LOCK TABLES
(Bug #55019) Selecting "Dump views" for a backup produced this error:
Unhandled exception: global name 'views_by_schema' is not defined
It was necessary to restart the Administrator to enable the dump facility again. (Bug #55833) If the sidebar was placed on the right hand side, using the option in Workbench Preferences, this Unexpected Error was generated when Add Diagram was double-clicked:
SplitterDistance value is invalid (-52)
(Bug #55902) Attempts to restore a backup of selected tables resulted in this error:
File "C:\Program Files\MySQL\MySQL Workbench 5.2 CE\modules\wb_admin_export.py", line 841, in start logmsg = "Restoring %s (%s)" % (schema, table) NameError: global name 'schema' is not defined
(Bug #56020) MySQL Workbench caused Windows XP to reboot if launched from Start, Programs, MySQL, MySQL WorkBench 5.2 OSS.
412
If a MySQL Workbench model file (.mwb) was opened directly, an error dialog titled Microsoft Visual C+ + Runtime Library was displayed with the message:
R6034 An application has made an attempt to load the C runtime library incorrectly. Please contact the application's support team for more information.
The dialog's only option was OK. After clicking OK, two more instances of the same dialog were displayed. After clicking OK for all three, MySQL Workbench opened with the model file displayed. On Windows 7 x64, the same runtime error (R6034) occurred. (Bug #52949) When using MySQL Workbench to report a bug, it was not possible to attach a file using the Choose File button because the button had no effect. (Bug #55112) In the SQL Editor, executing statements designed for MySQL Server 5.5 generated syntax or syntax highlighting errors. (Bug #55867, Bug #55891) Opening an SQL Editor connection for a remote server produced this error:
OverviewBE::get_node:invalid node 0.0.0.
(Bug #52648)

This section documents all changes and bug fixes applied since the release of 5.2.25. Functionality Added or Changed A validation module (a SE feature only) has been added. It sends an alert if foreign keys are being used in or to a partitioned table. Note: partitioned tables do not support foreign keys. (Bug #44273, Bug #11752933) When using the MySQL Workbench table properties to add a foreign key, the size of a new foreign key field will now update to match the size of the corresponding primary key. (Bug #55083, Bug #11762482) Added the default value of CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP to context menu of column editor for TIMESTAMP columns. (Bug #54987) Bugs Fixed When using su -user instead of sudo, rather than requesting the password of the user for invoking the su command, MySQL Workbench requested the root password and attempted to invoke the sudo command. (Bug #53740) In the Administrator, if the MySQL server configuration file was modified to enable skip-innodb, and the server was restarted, InnoDB was still active. (Bug #55030) On the Snippets tab, the tooltip for the Insert selected snippet to cursor position in the active SQL editor button contained the misspelling selected. (Bug #55026) If the Start Server button was clicked twice in MySQL Workbench, the server would stop. (Bug #49588) In the list view of the physical schemata, clicking a list column heading failed to sort the items by that column. (Bug #38863) When connecting to a server, MySQL Workbench prompted for a password, even if one had not been set for that account. (Bug #52826)
413
MySQL Workbench crashed when executing LOAD DATA LOCAL INFILE as a query in the SQL Editor. (Bug #49694) In the Overview tab of the SQL Editor, if there was a large number of schemata, using the arrow buttons in the interface to scroll through them caused MySQL Workbench to crash, usually on the last schema in the list. (Bug #54891) MySQL Workbench crashed if minimized while loading a model. (Bug #54918) In the Synchronize Model with Database wizard, the list of schemata was not drawn correctly on the Select Schemata page, if Back was clicked from the Fetch Object Info page. (Bug #55174) Importing a DBDesigner model caused MySQL Workbench to crash. (Bug #55300) After creating a server instance and double-clicking it on the Home screen, the Administrator took an excessively long time to load (over 10 minutes). (Bug #52530) When a model was synchronized with a live database, CHAR(N) columns were always synchronized as CHAR(1). (Bug #55334) Complex queries with multiple newlines did not fit well in the Action column of the Output tab of the SQL Editor. This prevented any query error messages from being read. (Bug #55117) When using the SQL Editor and issuing a query containing SQL_CALC_FOUND_ROWS and a subsequent FOUND_ROWS() query, FOUND_ROWS() returned zero instead of the number of matching rows without a LIMIT applied. (Bug #54868) Multi-statement syntax did not work in the SQL Editor. If the delimiter was set to a character other than the default semicolon, the SQL Editor should still have recognized semicolon as a valid delimiter for multi-statements, but it did not. (Bug #54831) In the SQL Editor, if a column's comment contained a Chinese word, then in the Object Browser, if the context-sensitive menu item Send to SQL Editor, Create Statement was selected, incomplete script code was sent to the SQL Query tab. (Bug #54822) In an EER Diagram, the circles at each end of a relationship line were drawn in different sizes. (Bug #54663) In forward engineering a model to a database, the PRIMARY index was not reordered correctly when columns were reordered. (Bug #54176) When a model was forward engineered to a database, insert statements associated with binary data were not present in the generated code. As a result, binary data was not forwarded to the database. (Bug #54680) In the Reverse Engineer Database wizard, using a pattern mask to filter tables being imported caused a subsequent MySQL Workbench crash. (Bug #55076) The Configuration section of the MySQL Workbench Administrator did not copy configuration variables from the my.cnf file that contained an underscore character. (Bug #54933) MySQL Workbench would not compile on RHEL 5. This was due to the calls to the function set_opacity in library/form/gtk/src/lf_utilities.cpp (line 661) and library/forms/ gtk/src/lf_popup.cpp (line 64). The set_opacity function was not available in GTK 2.10. (Bug #54844) When forward engineering an SQL ALTER script, the generated code attempted to recreate all foreign keys. (Bug #54363)
414
On the Home screen, the saved connections previously listed in the Workspace were no longer visible. (Bug #55484) When zooming in and out of the EER Diagram view, MySQL Workbench generated an unknown error. (Bug #52829, Bug #55390)
C.1.1.23. Changes in MySQL Workbench 5.2.25 (2010-06-30, 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 MySQL Workbench displayed instability after an SSH connection to the server was closed, resulting in hanging or crashing behavior. (Bug #50554) 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) 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) 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) If the Alter Routine dialog was maximized in the SQL Editor, the dialog buttons were no longer visible. (Bug #53734) 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) 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) 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) 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)
415
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) 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) 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) 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 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) 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) 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) 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) Printing or previewing an EER Diagram in Landscape/Tabloid produced blank output. (Bug #54240, Bug #54601)

This section documents all changes and bug fixes applied since the release of 5.2.23. Functionality Added or Changed
416
A Kill Query button has been added to the Connections tab of the Administrator. (Bug #54409) Bugs Fixed 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) 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, 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) 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) 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)
C.1.1.25. 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. Version 5.2.23 has no changelog entries.

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

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

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)
425
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 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) 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) 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) In the SQL Editor, field data of type VARBINARY viewed using the Open Value in Viewer contextsensitive menu item was displayed only up to the first null byte (\0). (Bug #52954) 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 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) 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) 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) 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
426
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) 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) If multiple SQL Editor tabs were opened, closing the last one caused MySQL Workbench to crash. (Bug #53061) Selecting multiple tables at the same time in the Overview tab of the SQL Editor caused MySQL Workbench to crash. (Bug #52922) 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) 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 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 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) 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) 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) 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) The MySQL Workbench make targets, with the exception of make all, were broken by the file ext/ ctemplate/Makefile. (Bug #51024) The MySQL Workbench configure.in configure script contained a construct incompatible with NetBSD. The script used test == instead of test =. (Bug #53175) 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) 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)
427
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 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) 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 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) 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) MySQL Workbench failed to compile from source due to a missing #include <stdarg.h> statement in the file library/sql-parser/include/myx_sql_tree_item.h. (Bug #52919) 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) 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) 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) 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) 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) The MySQL Workbench dependency on libmysql has changed to use version 16 of the library rather than 15. (Bug #52682) 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)

428
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, 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 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) 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) MySQL Workbench crashed when carrying out most tasks in the SQL Editor including adding tables, adding columns, and altering tables. (Bug #52789) 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) 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) 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 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) 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) 429
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) 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) MySQL Workbench crashed when creating a foreign key relationship in the EER Diagram view. (Bug #51602) The Assigned Privileges list on the Privileges tab in the View Editor lacked default grant options such as SELECT, UPDATE, and DROP. (Bug #42157) Double-clicking a model file (*.mwb) to open it caused MySQL Workbench to crash. (Bug #52838) 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) In the SQL Editor, when altering a routine, if the Apply SQL Script button was clicked, MySQL Workbench froze. (Bug #52853)

This section documents all changes and bug fixes applied since the release of 5.2.17. Functionality Added or Changed MySQL Workbench now features the ability to copy field data in the SQL Editor results tab in quoted or unquoted mode. (Bug #51041) Bugs Fixed The Connection Information panel in the SQL Editor did not display information for the User field. (Bug #52560) In the Alter Table dialog of the SQL Editor, in the columns or indexes tab, the first right-click in the dialog central area failed to display the context-sensitive menu. However, it was displayed on subsequent clicks. (Bug #51796) In the SQL Editor, it was not possible to export a result set, if the result set was not the first result set. For example, if there were two result sets, it would be possible to export the first one created, but not the second result set. (Bug #51595) In the Alter Routine dialog of the SQL editor, there was inconsistency between the operation of the close dialog button ('X') on the top right of the window, and the Close button on the bottom right. When
430
using the close dialog button you were prompted to save changes, regardless of whether you actually changed the routine or not. When using the Close button, the user was not prompted, even if the routine had changed. (Bug #51518) When editing a row in the SQL Editor, if a column was NOT NULL and had a default value, and a value was not entered for it, then after changing another column if changes were applied an error would be generated. This was because the editor attempted to set the NOT NULL column to NULL, rather than to its default value. (Bug #50781) The Triggers tab in the Alter Table dialog of the SQL Editor erased all entered code, when an attempt was made to copy and paste text within the tab. (Bug #52587) In the SQL Editor, if in the Alter Routine dialog, the user had a routine that contained an error, the routine would be lost if an attempt was made to close the Alter Routine dialog using the close button, and then click Yes to apply changes. (Bug #51921) In the SQL Editor, in the results editor, it was not possible to edit or copy data containing multiple lines of text. Further, lines containing new lines were displayed as if the new lines did not exist. MySQL Workbench now includes a blob editor. This can be accessed by right-clicking in the field to edit and selecting Open Value in Editor. (Bug #51561) In the SQL Editor, right-clicking a row in the results editor (after double-clicking a table), and selecting delete from the context-sensitive menu, did not have any effect. (Bug #51361) In the SQL Editor, if a routine was altered in the routine editor, it was possible to close the editor without the editor prompting you to save any changes made, and so changes were lost. (Bug #52728) The Log text area in the Reverse Engineer SQL Script wizard was inactive, preventing the log message from being scrolled. (Bug #50758) On the Linux platform, no context-sensitive menu was displayed when right-clicking a schema tab in the Physical Schemata section of the MySQL Model page. (Bug #49429) In the EER Diagram view, when a table with a name containing underscores was right-clicked, the context-sensitive menu displayed menu items containing the table name without the underscores. (Bug #49314) In the MySQL Model page it was not possible to delete a schema by using the context sensitive menu in the Physical Schemata section. (Bug #48055) MySQL Workbench crashed if No in the Delete Object dialog was clicked when attempting to delete a view from an EER Diagram. (Bug #52310) MySQL Workbench crashed when an attempt was made to create an EER Diagram from a database containing a large number of tables (1500+). (Bug #52500) The Data Dump facility in the Administrator exported the entire schema into a single file when the Dump Views option was selected. Further, if tables were selected and the Dump stored routines option selected, the routines would be stored in their own file, but with the DROP PROCEDURE IF EXISTS statements missing. (Bug #52579) During the import procedure of the Data Dump facility in the Administrator, stored routines were not imported. (Bug #52577) When using the Forward Engineer SQL Script wizard, the wizard did not terminate DROP procedure IF EXISTS statements with a semicolon. This caused SQL syntax errors if the script was executed on a server. (Bug #52743)
431
The scrollable boxes on the Home screen did not respond to mouse wheel events. (Bug #51213) The model Navigator did not redraw itself correctly. The Navigator worked correctly for the first model loaded into MySQL Workbench, but not for subsequently loaded models. (Bug #50580, Bug #50622) In the Object Explorer of the Sidebar, if an existing table was right-clicked, the context-sensitive menu displayed the option Create Table.... However, selecting this option appeared to have no effect. (Bug #51570) The Message Log text area in the Forward Engineer to Database wizard was in active, preventing scrolling of the message when an error occurred. (Bug #51417) When editing a table in the SQL Editor, the context sensitive menu items did not affect the row under the cursor, but a previously selected row. This potentially led to the unintentioned deletion of a row. (Bug #50113)

This section documents all changes and bug fixes applied since the release of 5.2.16. Functionality Added or Changed 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) 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) 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) The WeifenLuo library was removed. This was the cause of difficult to trace application crashes. (Bug #50706) 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) 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) 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) A description column has been added to the snippets table. (Bug #51010) In the SQL Editor, the Comments tab in the Create View dialog has been removed. (Bug #49270) Bugs Fixed 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)
432
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) It was not possible to connect to the MySQL server with MySQL Workbench if using sockets. (Bug #51419, Bug #51460) 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 EER Diagram view, when zooming in or out of the diagram the screen was not redrawn correctly. (Bug #48020, Bug #48032, Bug #34505) If, in the EER Diagram view, an attempt was made to edit two tables, MySQL Workbench crashed. (Bug #52158) 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 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) 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) 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) 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) 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 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 Output tab, causing the Response column to be unacceptably narrow. (Bug #51550) 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)
433
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, 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) 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) 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, 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) 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) 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 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) MySQL Workbench crashed while attempting to edit code in the SQL Editor. (Bug #51815) If a connection was opened for querying and then Control+W quickly pressed to close the connection, MySQL Workbench would crash. (Bug #51685) MySQL Workbench crashed when synchronizing a model to a live server. (Bug #51892) 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) 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) 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:
434
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) 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) Building MySQL Workbench from source failed if LDFLAGS="-Wl,--as-needed" option was specified. (Bug #51469) MySQL Workbench crashed if objects were sequentially selected in the EER Diagram view. (Bug #51573) 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) 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, 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) 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) When opening the ip2nation.sql file MySQL Workbench crashed. (Bug #51606, Bug #51531) After exporting a schema to disk, importing the schema did not restore the tables. (Bug #51261) 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& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& 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) An Out of Range exception occurred when switching from the Table Editor to the Home screen. (Bug #50980, Bug #51030)
435
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) In the Inserts tab of the Table Editor, if a row was right-clicked and Delete selected rows selected, MySQL Workbench crashed. (Bug #51584) 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) When the MySQL Workbench source was configured, the package gnome-keyring-1 was not found. (Bug #51090) 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 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) 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) 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) 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 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 <value1> ; <value2> ; ... ; <valueN>. (Bug #15245, Bug #11745436)

436
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) 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 data dump facility, used for exporting data to disk, has been modified to enable the --singletransaction 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) 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) 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) The second invocation of File, Print caused MySQL Workbench to crash. (Bug #50885) In the SQL Editor the text Parsing SQL ... displayed in the status bar remained once the parsing was complete.
437
MySQL Workbench has been changed to display No errors found once parsing has successfully completed. (Bug #50833) 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 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) 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) Using File, Export, Forward Engineer ALTER Script to export a model resulted in MySQL Workbench generating the exception AccessViolationException. (Bug #51053) 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 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) 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 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) 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)
438
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) 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) 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) 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 nonEnglish systems. (Bug #50050, Bug #50635, Bug #50966, Bug #50873, Bug #51008) 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) 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) 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) 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) Expanded Schemata Palettes in the SQL Editor would collapse when switching between SQL Editor tabs. (Bug #50815) 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) 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 the toolbar button to execute SQL statements was missing.
439
MySQL Workbench also now includes a new toolbar button to execute a single statement. (Bug #50791) 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) 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 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) 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 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) 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) 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) 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) 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) 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) 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)
440
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 Data Dump facility of the Administrator it was not possible to import a file where the path contained a space. (Bug #50609, Bug #50007) 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) 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) 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) 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) MySQL Workbench did not support SSH keys that required a passphrase to be entered. (Bug #49418) 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) 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) 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) 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)
441
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)

This section documents all changes and bug fixes applied since the release of 5.2.14. Functionality Added or Changed The GRT Shell exhibited various issues and could generate exceptions in some circumstances. The GRT Shell has been updated and is now implemented as a standalone dialog known as the Workbench Scripting Shell. (Bug #49298) Bugs Fixed In the SQL Editor, if an attempt was made to change the number of partitions in a table, using Alter Table, the SQL code produced did not contain the necessary ALTER TABLE statement to effect this change. (Bug #49054) If a model contained a table which used a user defined type for a column, then when the model was forward engineered an erroneous COLUMN CHANGE statement was generated for the column. This only happened for user defined types without additional arguments. For example, a user defined type using INTEGER(11) would not create a COLUMN CHANGE statement, but using INTEGER would. (Bug #45834) If the MySQL Server was stopped outside of MySQL Workbench then the server status displayed in the Administrator did not update correctly until the Startup tab was clicked. The log file did however correctly note the change in status. (Bug #48966) If text was entered into the search bar in the SQL Editor, and the sidebar button clicked twice, MySQL Workbench crashed. This only happened on Mac OS X. (Bug #50560) With an EER Diagram open, the File, Page Setup menu item was unavailable. (Bug #49863) The Synchronize Model with Database wizard generated a script that erroneously dropped schemata that had been selected to be ignored. (Bug #49587) The Portrait and Landscape icons were missing from the Page Setup dialog. (Bug #50529) On an EER Diagram, when a relationship was placed using the toolbar button Place a Relationship using Existing Columns, if the relationship was subsequently checked in the Foreign Keys tab of the Table Editor, it was found to contain incorrect values for foreign key names, for example, fk_%dcolumn%1. It was apparent that the placeholder had not had its value correctly substituted. (Bug #50492) When working through the Manage DB Connections wizard, the prompt to Enter SSH password appeared as a sheet behind the modal dialog box for the wizard. In some situations, it was not possible to see the Enter SSH password sheet, and it was not possible to click any buttons on, or close, the modal wizard. This meant the user had to move the modal dialog box to see the Enter SSH password sheet, but is was not obvious that this was possible because the window decorations indicated that the modal dialog could not be focused. MySQL Workbench now uses a dialog rather than a wizard used for Manage DB Connections when creating a new connection. (Bug #49810)
442
When exporting a model to a single file using File, Export, Export as Single Page PDF or Export as Single Page Postscript File, the table positions contained in the file were incorrect. (Bug #47384) Double-clicking any main tab, just below the main menu toolbar, caused MySQL Workbench to generate an exception. (Bug #50562) It was not possible to print EER Diagrams or schemata. The File, Print option was grayed out, and Control+P did not have any effect. (Bug #50528) MySQL Workbench reported the remote server as being down, in the Database Server Status section of the Administrator, even though the server was in fact running, and queries could be successfully run against the database using MySQL Workbench. (Bug #50453) When performing a data dump in the Administrator, the operation failed with an exit code 7. MySQL Workbench has been changed so that it will generate an error if the mysqldump executable cannot be found. (Bug #50184) On the General tab of the configuration file editor, if a value was set for Temp directory, and the changes applied, the value set was not displayed in the preview, implying it would not be set in the server configuration file. (Bug #49423) In the Administrator, when an attempt was made to import multiple tables from the same project folder, MySQL Workbench only imported the first table and then stopped, reporting the import process as finished. (Bug #49217) In the Columns tab of the Table Editor, attempting to change the column data type using the list caused MySQL Workbench to crash. (Bug #50546, Bug #50598, Bug #50527) When the menu item File, Page Setup was selected from the main menu, MySQL Workbench crashed. (Bug #50315) When a MySQL Workbench unhandled exception occurred and the exception dialog was displayed, if the user clicked Quit, and there were unsaved changes, a new dialog was displayed, warning of unsaved changes. If Cancel was clicked on this dialog, MySQL Workbench would exit, which was not the expected behavior because changes would then be lost. If Yes was clicked on this dialog, to save changes, MySQL Workbench crashed. Overall, the behavior of the dialogs was confusing. A new error dialog has been introduced that changes the handling. It presents the user options to go to the bug report page, copy debug information to the clipboard and to close the dialog. (Bug #49304) Client-side sorting always sorted on an alpha basis, regardless of data type. This meant numeric values were not sorted into the order expected. (Bug #50158)

This section documents all changes and bug fixes applied since the release of 5.2.13. Bugs Fixed In the Physical Schemata section of the MySQL Model tab, the tables were not displayed in alphabetic order. (Bug #47143) In the SQL Editor, the Alter Table dialog created incorrect DDL for changes to the partitioning. (Bug #49055) 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)
443
C.1.1.35. Changes in MySQL Workbench 5.2.13 (Not released)

C.1.1.36. Changes in MySQL Workbench 5.2.12 (Not released)


This section documents all changes and bug fixes applied since the release of 5.2.10. Functionality Added or Changed 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.3, Live Editing Tabsheets. (Bug #38600) 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) 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) The AUTHORS file in the MySQL Workbench distribution was empty. (Bug #49341) In the Create new server instance wizard, on the MySQL Config File page, clicking the Check path button generated an exception. (Bug #49228) 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 SQL Editor the SQL Statements area could only display ten lines of code and was not resizeable. (Bug #49788) 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
444
reverted to its value prior to editing. However, other cell values that had been edited were correctly saved. (Bug #49301) 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) 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) 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) When using the Create a new server instance wizard, the panel used to enter the SSH password was hidden by the wizard. (Bug #49416) 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) In the Document Properties dialog the created date and last changed date values were reversed. (Bug #48104) 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) 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 Overview tab of SQL Editor, the toolbar buttons representing large icons, small icons, list, add, and delete did not function correctly. (Bug #49239) 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) 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 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)
445
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) When using the Reverse Engineer SQL Script to import the Sakila script file, sakila-data.sql, MySQL Workbench occasionally crashed. (Bug #49381) In the SQL Editor, when editing live table data, there was no right-click menu item to delete a row. (Bug #49300) 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 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) 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) 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) 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) 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) In the Schemata Palette of the SQL Editor the default schema selector did not work if the schema name contained a '.' character. (Bug #49373) 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) 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) 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 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) 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 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
446
user was working with transactional tables, the commit and rollback toolbar buttons appeared to work, although they had no effect. (Bug #49462) 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) 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) 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 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) 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 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) 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)

This section documents all changes and bug fixes applied since the release of 5.2.9. Functionality Added or Changed 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) 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) Bugs Fixed
447
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) 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 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 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) 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) 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) 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) 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 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) 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) 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) 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)
448
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 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 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) 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)

Internal release. This section documents all changes and bug fixes applied since the release of 5.2.8. Version 5.2.9 has no changelog entries.
C.1.1.40. Changes in MySQL Workbench 5.2.8 (2009-11-18, 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 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) 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) 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)
449
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 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) 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) Once a default value had been set for a column in the Table Editor, it was not possible to remove it. (Bug #47085) 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)


This section documents all changes and bug fixes applied since the release of 5.2.5. Bugs Fixed After using the Forward Engineer to Database wizard, MySQL Workbench would crash if an attempt was subsequently made to exit the application. (Bug #47276) If a foreign key relationship was altered to point to a column in a different table, the foreign key was updated correctly but the EER diagram was not redrawn to reflect the new relationship. (Bug #47807)
450
When editing a trigger, the trigger editor would automatically insert a delimiter during a pause in typing, and also relocate the cursor. (Bug #45929)
C.1.1.43. 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.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 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) 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) Clicking the Test Connection button in DB Connection Editor wizard did not appear to have any effect. (Bug #47083) 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 -> '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) On Mac OS X using cmd + backspace to delete a column in the table editor did not work. (Bug #46613) In the Query Editor, when an attempt was made to expand a schema and select a table, this exception was generated:
************** Exception Text **************
451
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) 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) When a model was synchronized, this incorrect SQL was generated:
CREATE TABLE IF NOT EXISTS `synthescom`.àdx_clienti` (
ìd` INT(11) UNSIGNED NOT NULL AUTO_INCREMENT , `citta` VARCHAR(100) NULL DEFAULT NULL , `provincia` VARCHAR(100) NULL DEFAULT NULL , PRIMARY KEY (ìd`) 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) 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)

This section documents all changes and bug fixes applied since the release of 5.2.2. Functionality Added or Changed 452
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 During Forward Engineering, clicking the Copy to Clipboard button generated code that contained an extra newline per line. (Bug #45579) 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) 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 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 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) It was not possible to assign columns to indexes because the Column check boxes did not respond to mouse events. (Bug #45260) When a connection was selected in the DB Connection Editor it appeared to flicker a number of times before MySQL Workbench crashed. (Bug #46065) 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) MySQL Workbench crashed on launch on Mac OS X 10.6.0. (Bug #46953) 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)
453
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) 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 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) 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) On Mac OS X, it was not possible to resize a Text Object on the EER Diagram canvas. (Bug #45472) References: See also Bug #39887. 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) 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> 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)

This section documents all changes and bug fixes applied since the release of 5.2.1. Bugs Fixed The UML relationship notation was incorrect. When setting a Foreign Key to NULLable, the table referenced by the Foreign Key should be marked as optional. However, MySQL Workbench marked the table containing the Foreign Key itself as optional. (Bug #45069) If MySQL Workbench gave the message that the MySQL Server was no longer available (because of timeout due to inactivity) then MySQL Workbench crashed when the user tried to reconnect. (Bug #45123) The Synchronize Model with Database wizard contain a spelling mistake. The word synchronization was mispelled as synchronizatiob. (Bug #45939)
454
MySQL Workbench 5.1.16 failed to create INSERTs in the exported DDL for some tables. (Bug #45920) If a user added a LIMIT clause to a query, the automatically added LIMIT 0,1000 clause caused a syntax error. (Bug #45051) MySQL Workbench crashed at startup on Mac OS X. (Bug #45869) The new SQL IDE, introduced in 5.2, did not support returning results from procedures. When any routine was called, there were no results displayed in the query editor window. However, the log contained the message Response: OK. When another query was run on the same connection, the log message was:
Error Code: 2014 Commands out of sync; you can't run this command now
(Bug #44910)

C.1.1.48. Changes in MySQL Workbench 5.2.0 (2009-04-30, Alpha)

This is the first alpha release of 5.2.0. Version 5.2.0 has no changelog entries.

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) 455

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 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) 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) 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) 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) When editing a trigger, the trigger editor would automatically insert a delimiter during a pause in typing, and also relocate the cursor. (Bug #45929) 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) Clicking the Test Connection button in DB Connection Editor wizard did not appear to have any effect. (Bug #47083) 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) 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}' <object workbench.Workbench> key=owner could not
456
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) 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) MySQL Workbench crashed on launch on Mac OS X 10.6.0. (Bug #46953) 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) 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) The DBDoc documentation generation system did not support facilities for Stored Routines, Views and Triggers. (Bug #41589) 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)
457
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) 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) 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) 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 updated correctly. This only happened in MySQL Workbench 5.1.17. (Bug #46940) 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) 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) The DDL was generated without foreign keys, regardless of whether the Skip generation of foreign keys option was turned on. (Bug #46875)

This section documents all changes and bug fixes applied since the release of 5.1.16. Functionality Added or Changed 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) 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) 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)
458
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 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) Bugs Fixed During Forward Engineering, clicking the Copy to Clipboard button generated code that contained an extra newline per line. (Bug #45579) 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) Foreign Key checks were not enabled before the standard inserts section of the script started. (Bug #35180) 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 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) 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) 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) The Microsoft Windows version of MySQL Workbench leaked GDI objects, resulting in a drop in performance. (Bug #46101)
459
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) MySQL Workbench crashed and also lost procedure objects when attempting to synchronize with a live database. (Bug #45773) 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) 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 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) Relationship lines were not always drawn on the EER Diagram. (Bug #45583) 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) 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 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 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) 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 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) 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) 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
460
(Bug #46562) 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, 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) 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) 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' <object GrtObject> key=owner could not be resolved ** Message: item_activated: 0xadbb608 -> 'plugin:wb.file.newDocument' ** Message: unhandled message 4: wb.file.newDocument finished in 0.34s ** Message: item_activated: 0xaacbea8 -> '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) 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) 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) 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 writing code in the Routine Editor it appeared that the code was lost if the Routine Editor was closed. (Bug #46049) 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->type != GTK_SELECTION_MULTIPLE' failed ** Message: item_activated: 0x30d4920 -> 'plugin:db.plugin.database.rev_eng' ** Message: unhandled message 4: db.plugin.database.rev_eng finished in 0,00s
(Bug #46078) 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.
461
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) 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 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) 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) 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) 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 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) 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) 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)
462
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) On Mac OS X, it was not possible to resize a Text Object on the EER Diagram canvas. (Bug #45472) References: See also Bug #39887. 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) 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> 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) 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) 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) The Synchronize Model with Database wizard contain a spelling mistake. The word synchronization was mispelled as synchronizatiob. (Bug #45939) 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) 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)

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)
463
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 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 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) When zooming an EER Diagram, the text in a table would sometimes extend beyond the edge of the table box. (Bug #35407) 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) 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) 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) 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) 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) 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
464
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) 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) 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) 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) 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)

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 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) MySQL Workbench Synchronize 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) 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) Selecting Database, Generate Catalog Diff Report from the main menu caused MySQL Workbench to crash. (Bug #45652) 465
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) 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)

This section documents all changes and bug fixes applied since the release of 5.1.13. Bugs Fixed When synchronizing a model with a database, rather than synchronizing only the selected tables, all tables were synchronized. (Bug #43485) When right-clicking an item that was not selected, such as a table or routine, in the MySQL Model tab, the item was selected without the other items being deselected. The expected behavior for applications in both Windows and Linux is that right-clicking an item that has not been selected, should deselect all other items. Right-clicking an already selected item should not alter any of the selections. (Bug #44268) On Mac OS X, MySQL Workbench crashed when creating a new document after another one had been worked on. If editing a document, and then selecting to create a new document and not saving the current document when prompted, MySQL Workbench crashed when the save dialog closed. (Bug #45519) Printing an EER diagram crashed MySQL Workbench. (Bug #45518)

This section documents all changes and bug fixes applied since the release of 5.1.12. Bugs Fixed When trying to synchronize a model to a database, tables defining some columns as FLOAT or DOUBLE prevented the synchronization SQL script from working. The SQL generated used the syntax FLOAT(256) or DOUBLE(256) which was rejected by MySQL Server 5.0.51a. Editing the generated script manually to use just FLOAT or DOUBLE worked. However, MySQL Workbench then assumed the target table was not correctly synchronized, and prompted the user accordingly. (Bug #40169) 466
In the table editor, when a column was added with a data type of TIMESTAMP, and the default value of 0 entered, MySQL Workbench erroneously added quotation marks around the 0. Any generated SQL script therefore contained errors, and would subsequently fail. (Bug #44006) MySQL Workbench frequently crashed with an unknown exception in Wb.h at line 1010. This occurred while working on tables within EER diagrams on a design consisting of more than 190 tables and 20 EER diagrams. (Bug #41325) In the table editor the VARBINARY data type was not listed in the list for columns. (Bug #44023) When tables with relationship connectors were dragged or copied from one EER diagram to another, the connectors were not always drawn. (Bug #38545) MySQL Workbench did not limit foreign key name length. This meant that an exported SQL script was invalid and MySQL Server generated an error on attempting to import it:
1059 - ER_TOO_LONG_IDENT
(Bug #45139) Changing a relationship's visibility had no effect. If a relationship was right-clicked in the EER diagram, Edit Relationship selected, and then the Relationship tab selected, the visibility radio buttons were displayed. However, if the visibility settings were changed there was no effect. (Bug #44988) When a relationship was fully visible in the EER diagram, if the user chose to have it drawn split, or hidden, MySQL Workbench behaved as expected. However, if the relationship was hidden, and the user chose to have it drawn split, or fully visible again, the relationship was not properly redrawn. The user had to move either of the tables involved in the relationship to have the relationship redrawn. (Bug #40015) It was not possible to rename a table created using Add Table, by copying text into its text field. (Bug #44913) MySQL Workbench appeared not to display table rows in an EER diagram for tables that had more than 20 columns. MySQL Workbench now includes the ability to manually resize the table, besides automatically limiting the number of columns to a user selectable value, by order of appearance, regardless of being key columns or not. (Bug #44675) Invisible characters in a reverse engineered script caused errors to be generated when the same script was forward engineered. The problem was due to the reverse engineered script containing a mixture of \n, \r and \r\n line endings. These are now normalized to \n in the reverse engineering code. The validation process now also checks SQL code objects to ensure valid line endings. (Bug #41254) When synchronizing a model with a database, using the Synchronize Model with Database wizard, the data type translation resulted in errors. (Bug #42728) When working in the Routines tab of the Routine Group editor, the Routine tab did not appear to save changes to routine code. If code was copied from an external application into the Routine tab, then the model saved and MySQL Workbench exited, then on restarting MySQL Workbench, any changes to the routine code were lost. (Bug #40885)
467
Foreign key names must be unique. However, MySQL Workbench default generated foreign key names were sometimes identical, causing Forward Engineer SQL CREATE Script to fail. (Bug #45027) When in the Columns tab of the Table Editor, if an attempt was made to change a column data type to INTEGER(n) this would have no effect and the column data type would remain unchanged. However, if INT(n) was entered this was accepted and the data type changed accordingly. (Bug #44552) The Forward Engineer SQL Script wizard would write over an existing file without prompting the user for confirmation. (Bug #44437) On Mac OS X, an application window's red close button should contain a solid circle if the current document is unsaved. However, for MySQL Workbench this did not work correctly. Although the circle was initially shown, it was not displayed after subsequent edits to the model. (Bug #44435) The Copy SQL to Clipboard menu item, which was normally available when right-clicking a table in MySQL Workbench, was not displayed. (Bug #44254) When editing a column's type in the Columns tab of the Table Editor, the list for selecting the data type displayed BOOL. However, once that had been selected the data type was displayed as BOOLEAN. Further, if a column data type was set by entering INTEGER in the Datatype column, it then changed to INT on pressing return. (Bug #41934) Synchronization of the model with an external database failed to report errors. This meant there was the possibility of an incomplete synchronization, without the developer being informed. (Bug #45024) On the Linux version of MySQL Workbench it was not possible to rename a layer by double-clicking it in the Layers window (which is typically docked to the right hand side of the screen). A layer editor has now been added to the Linux version of MySQL Workbench. This can be activated by double-clicking the layer's title. (Bug #44972) Using the Foreign Keys tab of the Table Editor, it was not possible to correctly create multiple foreign key relationships. (Bug #44701) In the Workbench Preferences dialog, on the Diagram tab, in the Tables panel, the check boxes Show Column Types and Show Column Flags did not work correctly. Selecting or deselecting Show Column Types only had an effect when MySQL Workbench was restarted. Selecting Show Column Flags had no effect at all, and the flags were never displayed. (Bug #44586) The Forward Engineer SQL Script wizard did not emit table INSERT statements in the generated script when requested to do so. (Bug #43799, Bug #44385) On Ubuntu Linux, the following MySQL Workbench menu items did not work: Page Setup, Print Preview and Print. If those menu items were selected, these console messages were generated:
** Message: item_activated: 0xaa44bf0 -> 'builtin:wb.page_setup' ** Message: show_progress_becb not implemented ** Message: unhandled message 4: wb.print.setup finished in 0,00s ** Message: show_progress_becb not implemented create font Helvetica 0 0 11,000000 (200)** Message: item_activated: 0xa4c9800 -> 'plugin:wb.print.printPreview' ** Message: show_progress_becb not implemented ** (mysql-workbench-bin:11732): WARNING **: Could not open editor shared object '/usr/lib/mysql-workbench/plugins/'
468
** Message: unhandled message 4: wb.print.printPreview finished in 0,00s ** ** ** ** Message: Message: Message: Message: show_progress_becb not implemented item_activated: 0xa4cec08 -> 'plugin:wb.print.print' show_progress_becb not implemented unhandled message 4: wb.print.print finished in 0,00s
** Message: show_progress_becb not implemented create font Helvetica 0 0 11,000000 (300)
(Bug #44524) When editing a foreign key in the Foreign Keys tab of the Table Editor, and then removing the corresponding relationship from the EER Diagram canvas, the Foreign Keys tab remained open and populated, instead of being cleared and closed. (Bug #39478) When Workbench:copyToClipboard() was used from within a plugin, only garbage characters were copied to the Windows clipboard. This affected the operation of plugins. When a plugin attempted to output the string abcdefghijklmnopqrstuvwxyz0123456789!$%&/()= a runtime exception was generated. (Bug #44461) On Mac OS X, if the mouse pointer was used to select an entity and then Command+Delete was pressed before the tooltip appeared, MySQL Workbench crashed when the delete was confirmed. (Bug #45042) When attempting to delete an existing EER diagram, MySQL Workbench crashed. The origin of the diagram seemed to have no bearing on whether the crash occurred because it happened both with diagrams created from reverse engineering and those created independently. (Bug #44407) When using the Generate Catalog Diff Report wizard, the Stored Connection information was not automatically populated when a previously defined Stored Connection was selected. (Bug #45234) On Mac OS X, using the Forward Engineer to Database, or Forward Engineer SQL Script wizards caused MySQL Workbench to generate this error message:
The application MySQLWorkbench quit unexpectedly after it was relaunched.
(Bug #45229) When using the Forward Engineer SQL Script wizard, the SQL Object Export Filter step displayed duplicate items. (Bug #45241) When defining a primary key with a user-defined data type, it was not possible to set the auto-increment (AI) attribute. Clicking the AI check box had no effect. To circumvent this problem it was possible to temporarily change the data type of the column to a builtin data type such as INT, set the AI attribute and then change the data type back to the desired userdefined data type. The model could then be saved. However, if this model was reopened and File, Export, Forward Engineer SQL CREATE Script used to generate a script, MySQL Workbench would crash. (Bug #45165) Adding Insert records for a table worked correctly. However, there was no way to remove the records once the Open Editor facility has been used to add them. (Bug #45233) On Ubuntu Linux, MySQL Workbench crashed with a segmentation fault when an attempt was made to save the model. (Bug #44974)
469
On Debian Linux (Lenny), after adding a second table and selecting AI on the first column element, MySQL Workbench generated a segmentation fault. (Bug #44612) Deleting or cutting a Relation from an EER diagram crashed MySQL Workbench. (Bug #44340) When a Routine Group was renamed, this was not immediately updated in the EER diagram. (Bug #44503) In the Flags box, which is located in the Column Details panel in the Table Editor, the same flags were not listed as available for both the INT and INTEGER data types. INT has both UNSIGNED and ZEROFILL listed, but these were not listed for the column if it was of type INTEGER. Also, the AI check box was not selectable for columns defined as INTEGER. (Bug #44872) When a new index was created in the Indexes tab for a table that already had indexes, the previously displayed index field remained selected. This caused concern that the newly created index would be on the wrong field. (Bug #44532) The Forward Engineer SQL Script wizard did not permit the SQL script text to be copied using the keyboard shortcut. Only the mouse could be used to select and copy the text. (Bug #44531) If the order of columns was changed in the Columns tab, this was not reflected in the EER diagram. (Bug #44240) When exiting MySQL Workbench with unsaved changes, you are given the choices Save, Don't Save and Cancel. When Cancel was clicked, MySQL Workbench exited without saving, rather than returning to the application without making any changes. This only happened when clicking the main application Close button, in the upper right corner. It did not happen if the application was exited by selecting File, Exit from the main menu. (Bug #44267) Omit Schema Qualifiers did not omit schema for foreign keys. When using File, Export, Forward Engineer SQL CREATE Script and selecting the Omit Schema Qualifiers check box, the schema for foreign keys were not omitted. (Bug #42328) When Relations were deleted using the Foreign Keys tab, MySQL Workbench intermittently generated an exception:
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous) at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args) at System.Windows.Forms.Control.Invoke(Delegate method) at MySQL.GUI.Workbench.Plugins.ObjectEditorPlugin.RefreshFormDataInvoke() at MySQL.Grt.DelegateSlot0<void\,void>.cpp_callback() at sigc.pointer_functor0<void>.()(pointer_functor0<void>* ) at sigc.adaptor_functor<sigc::pointer_functor0<void> >.()(adaptor_functor<sigc::pointer_functor0<void> >* ) at sigc.internal.slot_call0<sigc::pointer_functor0<void>,void>.call_it(slot_rep* rep) at MySQL.Grt.Db.TableEditorBE.remove_fk(NodeId fk) at MySQL.GUI.Workbench.Plugins.DbMysqlTableEditor.deleteSelectedFKsToolStripMenuItem_Click(Ob ject sender, EventArgs e) at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e) at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e) at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e) at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e) at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met) at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType
470
met) at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea) at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ScrollableControl.WndProc(Message& m) at System.Windows.Forms.ToolStrip.WndProc(Message& m) at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
(Bug #44326)

This section documents all changes and bug fixes applied since the release of 5.1.11. Bugs Fixed In the Foreign Key tab of the Relationship Editor, the two buttons labeled Edit Table... were inactive. Clicking them had no effect. (Bug #45391) It was not possible to change the Default Collation for any schema. (Bug #44220) When running on Ubuntu Linux the edit window in MySQL Workbench was not expanded horizontally by default. When editing existing routines, the horizontal scroll-bar covered 100% of the visible area, no matter how long any of the rows are. This meant that if a row expanded outside the visible area, it was not possible to scroll sideways to see the rest of the row. All of the row was there, but the right part was not visible. (Bug #44296)


This section documents all changes and bug fixes applied since the release of 5.1.9. Bugs Fixed In the EER Diagram view, if the Tables folder was expanded in the Catalog Palette, and then a table dragged onto the EER Diagram, the expanded Tables folder immediately collapsed. (Bug #41922) An attempt to edit a table resulted in this error:
The plugin db.mysql.editors.mwbplugin does not contain the published object DbMysqlTableEditor
This only happened if the project was opened immediately after MySQL Workbench was started. (Bug #43863) Soon after MySQL Workbench was launched, error popup dialogs were generated with this message: 471
"AXDocument" attribute unsupported by <some component>
This occurred on the Mac OS X version of MySQL Workbench, when a third-party usage monitoring utility was running. This error was due to the fact that custom exception reporting was disabled by default. (Bug #43872) If a MySQL Workbench project file was opened, all tabs closed, and then File, New selected, MySQL Workbench crashed with this error message:
Unknown exception caught in c:\users\tax\documents\visual studio 2008\projects\wb 5.1\workbench\backend\windows\wbprivate.wr\src\Wb.h at line 994.
(Bug #43850) If an attempt was made to use the undo feature after having first saved a project, MySQL Workbench crashed. (Bug #43849) It was not possible to edit the cardinality of existing relations using the MAC OS X version of MySQL Workbench. Attempting to change the cardinality using the radio buttons had no effect. For example, it was not possible to change a relation from one-to-many to one-to-one. (Bug #44043) When a foreign key was created, a column was selected in the original table, but no column was selected in the foreign table. If the project was saved and an attempt was made to reload it, this error message was generated:
Unserializing GRT data - Inserting null value to not null list
This error prevented MySQL Workbench from opening the project file, resulting in all model data being inaccessible. (Bug #43997) Data entered using the Inserts tab in the Table Editor was not displayed in the Inserts tab, but was saved to the MWB file when the project was saved. The data could be viewed in MySQL Workbench running on platforms other than Mac OS X, but the Mac OS X version of MySQL Workbench did not display the data entered using the Inserts tab. (Bug #43907) When creating a new 1:n link MySQL Workbench froze. (Bug #43812) Using the Navigator to zoom in and out of an EER diagram view caused MySQL Workbench to crash. (Bug #43782) When a plugin was installed using the Tools, Install Plugin/Module File... menu option, MySQL Workbench copied the selected plugin and reported:
'Copied module /Users/tilman/Desktop/SymfonyYmlExport.grt.lua to '/Users/tilman/Library/Application Support/MySQL/Workbench/modules/SymfonyYmlExport.grt.lua' Please restart Workbench for the change to take effect.'
When restarted, MySQL Workbench crashed. MySQL Workbench could only be fully restarted by first removing the installed file from the modules directory. (Bug #43906) When a nonstandard port was specified in Database, Forward Engineer..., such as 3307, MySQL Workbench still attempted to connect to port 3306. (Bug #44014) The name of the table displayed on the tab in the Table Editor did not update when the table name was changed in the editor. (Bug #43960) The Many-to-Many Table generated by MySQL Workbench was of engine type Server Default. It should have been of type InnoDB. (Bug #43776)
472
On opening a diagram the file tables layout was broken. All tables were placed in the top left corner. It appeared that MySQL Workbench stored the diagram layout in the MWB file correctly but it was not retrieved correctly on file load. (Bug #43455)
C.1.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.0.29. Bugs Fixed If a model contained a View that was using a Function, and an attempt was made to Synchronize the database, an error was generated such as:
Error 1305: FUNCTION `bleble` does not exist
A similar error was also generated if the Forward Engineer SQL CREATE Script wizard was used. (Bug #40846) The Forward Engineer SQL ALTER Script wizard produced an erroneous script. If Forward Engineer SQL CREATE Script was used to generate a script and this was then used as an input to Forward Engineer SQL ALTER Script, without having made any changes to the model, then an ALTER script with no changes should be produced. However, the ALTER script showed many changes, even though no changes had been made to the model. (Bug #37709)
473
Introducing a UserType into a model caused the File, Export, Forward Engineer SQL CREATE Script wizard to crash. Further, performing a Plugins, Objects, Copy SQL to Clipboard operation also caused MySQL Workbench to crash. (Bug #42085) MySQL Workbench crashed when the mouse wheel was used. If you scrolled the Options tab of the Table Editor, closed the Table Editor and then used the mouse wheel again on the MySQL Model page, MySQL Workbench crashed. (Bug #42847) The Forward Engineer SQL CREATE Script wizard failed to generate a script correctly. This happened when using the File, Export, Forward Engineer SQL CREATE Script facility. If, in the wizard, Object of type MySQL table was selected, and then all tables added to the Exclusion Masks pane, before moving back the required table to the Objects to Process pane, the script was generated for the entire database rather than the selected table. (Bug #41475) When a diagram was renamed, the history displayed:
Rename 'new name' to 'new name
It should have instead displayed:

Rename 'old name' to 'new name'
(Bug #41355) The viewport, which is the combobox in the top right corner of Workbench, did not scale to less than 40%. However, resizes above 40% worked fine. (Bug #39607)

This section documents all changes and bug fixes applied since the release of 5.0.28. Bugs Fixed 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) 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) In the EER Diagram view an icon was not displayed for Not-NULL items. (Bug #41326) Workbench crashed when objects other than tables were moved out of a layer. (Bug #41358)

This section documents all changes and bug fixes applied since the release of 5.0.27. Bugs Fixed 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)
474
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) A complex EER diagram threw an exception whenever an action was performed 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& m, MouseButtons button, Int32 clicks) System.Windows.Forms.Control.WndProc(Message& m) System.Windows.Forms.ScrollableControl.WndProc(Message& m) System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
(Bug #39360) 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) 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)

This section documents all changes and bug fixes applied since the release of 5.0.26. 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 475
The Copy SQL to Clipboard action (right-click menu on table) did not use Windows-compatible line endings. (Bug #39476) If a trigger was renamed, and the design then synched with a database instance, the generated SQL created a trigger with the new name and then dropped the trigger with the old name. This resulted in this error:
Error 1235: This version of MySQL doesn't yet support 'multiple triggers with the same action time and event for one table'
(Bug #39989) When a column had a data type BOOLEAN and it was exported using Forward Engineer SQL ALTER, the exported type was BOOLEAN(2) instead of BOOLEAN. (Bug #39257) When a stored routine was edited, the edit cursor jumped back to the start of the page unless typing was constant. (Bug #40426) When a DBDesigner model with 333 tables was imported into Workbench the RAM usage went up to approximately 1GB. Workbench then crashed with this exception:
Error creating cairo context: out of memory
(Bug #37178) Workbench application performance was poor, with slow loading times and excessive memory usage. (Bug #38439) When using the Copy Insert to Clipboard menu item the generated SQL code was incorrect. The S was missing from VALUES and the data was not included. This resulted in SQL code such as:
INSERT INTO `table1` (`table1_id`, `descr`) VALUE ();
(Bug #40041)

This section documents all changes and bug fixes applied since the release of 5.0.25. Bugs Fixed The script generated by the Export, Forward Engineer SQL CREATE Script menu item contained invalid statements when using two schemata. (Bug #39211) Exported SQL code containing a trigger that called a procedure would fail when an INSERT activated the trigger. (Bug #39088) When attempting to export a model using the File, Export, Forward Engineer SQL CREATE Script menu item, Workbench crashed on clicking the wizard's Finish button. (Bug #39578) Renaming a table and then selecting Forward Engineer SQL ALTER Script did not result in a RENAME statement. Instead, DROP and CREATE statements were generated. (Bug #39256) The Copy Insert to Clipboard action generated SQL with lowercase keywords. This was not consistent with the behavior of the Copy SQL to Clipboard action. (Bug #39477)

476
Bugs Fixed 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) When you loaded a UTF-8 encoded script file into Workbench, the embedded SQL editor replaced international characters with the ? symbol. (Bug #38783) If any DEFAULT properties were defined for a model, they appeared to be lost after saving the model and restarting Workbench. (Bug #38825) 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 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) Foreign keys referencing a deleted table were not removed. (Bug #39150) The Triggers tab would always enable Insert mode when opened. (Bug #39118) If the user closed all tabs and then quit, Workbench crashed. (Bug #39346) 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) 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)

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 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 autoincrement flag for the changed column. (Bug #36085)
477
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) 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) It was not possible to synchronize a model to an external database, if the model contained triggers. (Bug #38436) Errors were generated in SQL code during Forward Engineer Schema for Inserts data in TIMESTAMP columns. (Bug #37059) When synchronizing the database, table comments were not updated. However, column comments worked as expected. (Bug #37686) Workbench crashed when using the Model, Validation(MySQL), Validate All menu item on a model that contained a dangling foreign key index. (Bug #38115) When resizing the comment column under Physical Schemata view in column format, the column resize was reverted when switching between schemas. (Bug #38431) When a DBDesigner 4 XML file was imported into Workbench the INSERT statements were incorrectly converted. (Bug #38196) An attempt to copy a table and then paste it into a new schema resulted in an Unknown Exception being generated. (Bug #38429) 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) Importing a script that specified an incorrect data type required Workbench to close. (Bug #38146) 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) 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 using the Forward Engineer SQL CREATE Script, columns marked as NOT NULL were generated as NOT NULL DEFAULT NULL. (Bug #37385) 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) Foreign key options (onDelete, onUpdate) are not imported from DBDesigner schema. (Bug #37794) Running Help, Update... crashes Workbench when the wizard comes to the point where it is trying to close Workbench. (Bug #37665)

478
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 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) 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) 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) The behavior of the Synchronize wizard was inconsistent when cancelled and re-run. (Bug #36177) 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 creating a Schema Diff Report from the local model to a live database, the wizard crashed with an unhandled exception. (Bug #35878) When a new column was added to a table Inserts data was deleted. (Bug #37192) Workbench was failing to correctly export Trigger DDLs. (Bug #37432) 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) Mouse wheel does not work when you double-click a table and select the Options tab. (Bug #36374) 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) 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) The script generated by the File, Export, Forward Engineer SQL ALTER Script menu item contains syntax errors. (Bug #36889)
479
Several windows and tabs have fields which are either not completely visible or are obscured by labels that overlap the field. (Bug #36115) 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) When File, Export, Forward Engineer SQL ALTER Script menu item is selected it causes an ALTER Script Generation (Script Synchronization) error. (Bug #36355) 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) 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) The export filter did not properly filter tables. (Bug #36739) 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)

This section documents all changes and bug fixes applied since the release of 5.0.21. Bugs Fixed 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) The script generated by database synchronize contained errors. (Bug #35644) When columns are added to, or removed from a table, Workbench deletes all Inserts data. (Bug #37008) The script generated by the File, Export, Forward Engineer SQL CREATE Script menu item contains a spurious quotation mark. (Bug #36753) Can not add values for TIMESTAMP columns in the Inserts editor. (Bug #37009) The Copy to SQL operation caused a crash. (Bug #36184) The enabled/disabled status of items in the Edit menu was not updated properly. (Bug #35962) Relationships were drawn over tables. (Bug #35867) View renaming in overview did not work properly and has been disabled. (Bug #36202) Dragging objects out of a layer did not work properly. (Bug #36053)
480
Setting up foreign key relationships across multiple schemas did not work. (Bug #34546) Trigger definition auto-formatting resulted in malformed code. (Bug #36815, Bug #37685) 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) 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) Scrollbars now appear correctly when editor windows are reduced in height. (Bug #32454) Table partitioning information was not exported properly. (Bug #32226)

This section documents all changes and bug fixes applied since the release of 5.0.20. Bugs Fixed When a schema used InnoDB, and then was switched to use MyISAM, the script generated by Forward Engineer SQL CREATE Script still contained InnoDB-only syntax. (Bug #35947) The undo operation did not completely undo a relationship between two tables. It removed only the line drawn between two tables, but did not undo the fields and keys. (Bug #36645) Forward Engineer wizard failed to create a table, but did not show any error messages. (Bug #35874) The Copy Connection nn menu item on the context menu of a connection does not have a complementary Paste Connection menu item. The Edit menu has a greyed-out Paste Connection menu item. (Bug #36166) The scripts generated by the File, Export, Forward Engineer SQL ALTER Script and File, Export, Forward Engineer SQL CREATE Script include unnecessary SQL code. (Bug #36170) When making a column a primary key and this column has NULL as default value, this default value is not changed. When the table gets synchronized back to the database Workbench creates a statement such as:
ALTER TABLE `test_defhan`.`table1` CHANGE COLUMN ìd_table1` ìd_table1` INT(11) NOT NULL DEFAULT NULL, ...
This leads to an error: Error 1067: Invalid default value for 'id_table1' (Bug #32972) Saving a file restores the column widths of the list view to default under Physical Schemata. (Bug #35718) Double-clicking a column-heading separator in Find results caused a crash. (Bug #36266)
481

This section documents all changes and bug fixes applied since the release of 5.0.19. Bugs Fixed The message log on the Forward Engineer Progress/Results Advanced dialog had no scroll bar. (Bug #36192) Re-creating a deleted relationship caused a crash. (Bug #36385)

This section documents all changes and bug fixes applied since the release of 5.0.18rc. Bugs Fixed Forward Engineer SQL CREATE Script wizard generated no output script. Further, no error or warning messages appeared to be generated that might explain this. The error message in this case was displayed in the Advanced Log, which was not visible to the user. MySQL Workbench was changed so that the Advanced Log appeared to the user if it received an error message. (Bug #34430) The HTML Basic Single Page DBDoc report from the Model -> DBDoc -> Model Reporting menu option was missing the schema and table numbers. (Bug #36060)
C.1.3.13. Changes in MySQL Workbench 5.0.18rc (not released)

This section documents all changes and bug fixes applied since the release of 5.0.17rc. Version 5.0.18rc has no changelog entries.
C.1.3.14. Changes in MySQL Workbench 5.0.17rc (2008-04-07)

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

This section documents all changes and bug fixes applied since the release of 5.0.15rc. Functionality Added or Changed Options and configuration options that affect models can now be set on a model by model basis. Choose Options from the Model menu and choose the Diagram tab. (Bug #34610) Bugs Fixed A 1:m relation in a diagram would fail to be generated properly when exported as a PDF. (Bug #32882) When double-clicking the row in a column as a primary key, the primary key property would be toggled. The editor will now permit you to edit the value when you click a data row on the table. (Bug #35613) When disabling global options on an individual model would fail to honor the model specific options would be ignored. (Bug #35516) Placing an image on to the canvas could crash the application. For images larger than the canvas, the image is automatically reduced so that it is properly visible on the canvas for editing. (Bug #33179) Opening the Indexes portion of a table would generate a unhandled exception error. (Bug #35598) When placing a 1:n relation, an index out of range error could be raised. This could further result in operation on NULL object: Invalid value errors when trying to edit the relation. (Bug #35447) Printing an HTML version of the schema would produce a fatal error. (Bug #35400) Setting the value of a numeric column to a negative value was not supported. (Bug #35442) The OK and Cancel buttons for the Diagram Size dialog would not be initialized properly. (Bug #34808) When copying multiple table definitions from one schema to another, only the first table in the selection would be pasted into the new schema. (Bug #34483) When exporting a diagram to PDF, some additional lines would be added to the generated PDF. (Bug #33586) The Draw Line Crossing option would fail to be recognized correctly. You can also now set this on an individual model basis using the Options option in the Model menu. (Bug #34248) Copying an existing module to the plugins directory would trigger a double registration of the modulem, and produce an error. (Bug #34134) When using print preview on a diagram, clicking the Print button would send a blank page to the printer. (Bug #34630) The Undo and Redo options would not be applied properly when making modifications to partition definitions. (Bug #32279)

This section documents all changes and bug fixes applied since the release of 5.0.14abeta. Bugs Fixed
484
Editing a primary key column within a model on Microsoft Vista could cause a crash. (Bug #34922) 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) 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) 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) 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) Editing an existing diagram could cause an unhandled exception on Windows Vista. (Bug #33477) When scrolling through a schema, the tables in the schema were not redrawn correctly. (Bug #32835) Deleting objects within the overview pane when the corresponding editor pane for those objects is open would cause a crash. (Bug #35186) 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) When saving an existing model, the MySQL Model overview panel would scroll to the top of the model definition. (Bug #34975) 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) 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) 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) 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) 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) A foreign key relationship to the source table (a reflexive relationship) gives a bad representation in the entity model diagram. (Bug #35237, Bug #34810) 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) 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) Incorrect ALTER statements are created during the synchronization process if you add foreign keys to an existing or imported model. (Bug #34897) 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)
485
Using Undo on a relationship within a model would cause an exception. (Bug #35243) Identifiers (tables, column, index, triggers and other data types) could be created with names longer than the maximum support by MySQL Server. (Bug #33265) 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) 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) 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) 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) The application crashed when attempting to export an SQL CREATE script. (Bug #33263) The Properties palette was not cleared when a new project was started. It retained the properties of the last selected object. (Bug #34433) Attempting to move a table on an EER diagram after deleting a relationship, caused the application to crash. (Bug #34816) After importing a DB Designer schema, the following error occurred: "Cairo error: input string not valid UTF-8." (Bug #34987) 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) On the MySQL Model page, when the large icons view was selected, the Add Table icon disappeared. (Bug #34904) Changing the drawSplit property of a connection from the Properties palette did not updated the Visibility section of the connection editor. (Bug #34934) Printing a model when there is no printer connected could result in an application exception. (Bug #32320) On an EER diagram 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)
C.1.3.17. Changes in MySQL Workbench 5.0.14abeta (2008-02-28)

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) References: See also Bug #34847.
486
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) 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) Repeatedly changing the object notation crashed Workbench. This is no longer repeatable. (Bug #34499) When clicking the Browse button in the image editor, the default file name was openFileDialog1. This now defaults to an empty string. (Bug #34622)
C.1.3.18. Changes in MySQL Workbench 5.0.14beta (2008-02-25)

This section documents all changes and bug fixes applied since the release of 5.0.13beta. Workbench Improvements in this Version The GRT inspector has been improved to support new types. Namely: text longtext bool color file This makes it much easier to change object properties manually. Multiple selection support has also been improvedyou can easily change a value for several selected objects at once. Because of serious performance and display issues Workbench no longer uses Mesa. For those users who don't have native OpenGL support, Workbench now uses the Windows GDI API. The command line switch for using this mode is -swrendering. For more information about running Workbench from the command line see Section 3.3.2, Launching MySQL Workbench on Windows. An Export as SVG menu option has been added under the File, Export menu option. A System Information menu option has been added to the Help menu. This option displays information about your system that is useful when reporting a big. A Fit Objects to Contents option has been added under the Arrange menu option. This option expands an object on an EER diagram. For example, if a table has a long column name that is not fully displayed, using this menu option will expand the table making the column name visible. Expand All and Collapse All menu options have been added under the Arrange menu. The Expand All option expands all objects on an EER. This option will display a table's columns if the object notation supports expansion. Indexes will not automatically be expanded unless they were previously expanded and have been collapsed using the Collapse All menu option. Some object notations, such as Classic, do not permit expansion or contraction. Collapse All undoes the operation performed by Expand All. Bugs Fixed After placing related tables on an EER diagram and then removing them using the Undo menu option, the connection lines between related tables no longer showed up. (Bug #34601)
487
When exporting an SQL CREATE script it was possible to create two tables in the same schema with the same name. (Bug #34668) It was not possible to resize a table that used the Workbench (Default) object notation. This was problematic for a number of reasons: Long table names make the table very wide. Column definitions that are long relative to the table name, are truncated. Even if you trimmed column names using the Diagram tab of the Workbench Options the names were sometimes truncated bled over the table border. This has been corrected. (Bug #32981) When there were many tables on an EER diagram, constant screen refreshing made the application unusable. The performance of the software rendering mode has been improved. (Bug #33646) Setting a column to AUTO_INCREMENT caused the application to crash. (Bug #34418) A table with many columns did not display properly. When the table was expanded on an EER diagram it was impossible to scroll down and view all the columns. Improved rendering has helped solve this problem. However, for very large tables you may have to increase the size of an EER. To do this use the Model, Diagram Size ... menu option. (Bug #33367) When a table's expanded property was set to 0, the connection line between related tables, appeared at a diagonal orientation. A connection line is now docked on the sides of a table even when the expanded property is set to 0. (Bug #34249) It was reported that you could not add a primary key to a table imported from a MySQL CREATE script. This was not true but did highlight the fact that the method for adding a primary key was not obvious. Now, in addition to adding a primary key by double-clicking the icon to the left of a column in the table editor view, you can also add a primary key by checking the PRIMARY KEY check box in the Column Details section of the table editor. (Bug #34408) If there was a relationship between table A and table B and also one between table B and table A, the connection lines appeared on top of each other. Connection lines now appear attached at the related columns. (Bug #34543) When choosing the Export as PNG menu option the file dialogue box file type was All Filesinstead of PNG. The same was true for Export as singlePage PDF and Export as singlePage PS. The default is now the appropriate file type. (Bug #34548) When there were multiple tables with long identifiers the Physical Schemata section of the MySQL Model page was messy. Table names were obscured and sometimes overlapped. Also, the position of the Add Table icon was not optimal. Now the space between table names is adjusted to the largest entry and the Add Table icon is fixed in the upper left corner. (Bug #34536) When returning to the SQL Export Filter page after using the Back button, filters were no longer selected. Selections now persist. (Bug #34503) The export filters were applied more than once when forward engineering an SQL CREATE script. This happened if you exported the script after using the Back button on the SQL Export Filter page. (Bug #34501) Creating a new foreign key did not update an EER diagram. An EER diagram is now updated immediately. (Bug #34206)
488
MySQL Utilities Change History
When multiple objects on an EER diagram were selected and deleted, Workbench crashed. This happened when both connections and tables were selected. (Bug #34434) Users failed to be created when exporting an SQL CREATE script. (Bug #34342) Copying a table from the MySQL Model page to an EER diagram canvas created a duplicate table with the same name as the original. This table did not show up in the Catalog palette or in the appropriate schema in thePhysical Schemata section of the MySQL Model page. (Bug #34230) When changing the foreign key column of a table on an EER diagram, the foreign key did not change color and Workbench crashed when attempting to save the MWB file. The application no longer crashes and the foreign key is updated. (Bug #33139) When the object notation was Workbench Classic the width of a table on an EER diagram could not be less than the widest column. If there was an enum column with many options, this made for a disproportionately wide table. Table width can now be less than the widest column. (Bug #34496) When using the menu option Generate Schema Diff Report an exception was thrown. A new tree-less version of the Diff report plugin resolves this problem. (Bug #34396) It was not possible to drag or resize tables on an EER diagram. Tables can now be manually resized. To revert a table to automatic sizing use the Property palette and set manualSizingto True. (Bug #32549) When there were two schemata and two EER diagrams tables did not show up on the EER diagram if tables from different schemata were added to different EER diagrams. This was caused by defective software rendering. (Bug #32588) The display turned black when the application was resized. This happened when viewing the MySQL Model page or when viewing an EER diagram. (Bug #23959) When forward engineering to a live database, objects not selected on the Select Objects page were still created. This applied to tables, routines, and users. (Bug #32578)
C.2. MySQL Utilities Change History

The following sections outline the changes between versions for MySQL Utilities.
C.2.1. Changes in Release 1.1

C.2.1.1. Changes in MySQL Utilities 1.1.0 (2012-09-27)
This section documents all changes and bug fixes applied since the release of 1.0.5. The version adds the mysqluc console. Functionality Added or Changed Added the mysqluc command, which is a command line client for running MySQL Utilities.
C.2.2. Changes in Release 1.0

489
Changes in Release 1.0
It is now possible for the mysqlserverclone utility to clone a downed server. Before, it was only able to clone a running server. (Bug #13698224) Arguments for the utilities are no longer case-sensitive. And arguments now accept prefixed values, such as g or gr representing grid when passed to --format. The --format and --help arguments have been standardized across all utilities. And as such, -h no longer represents --help. (Bug #13554556) Added replication support to the mysqldbexport, mysqldbimport, and mysqldbcopy utilities. This adds the following options to the mysqldbexport and mysqldbcopy utilities: --rpl, --rplfile, --rpl-user, and --comment-rpl. And adds the --skip-rpl option to the mysqldbimport utility. Added the mysqlrpladmin utility, which allows administration and recovery of the replication topology. Added the mysqlfailover utility, which provides replication health monitoring. It relies on Global Transaction Identifiers (GTIDs) so requires MySQL Server 5.6.5 or greater. Bugs Fixed The mysqlserverinfo utility would fail when used with an offline version of MySQL Server 5.6. (Bug #13916903) The following utilities would not always exit properly, when executed from within MySQL Workbench: mysqlindexcheck, mysqlmetagrep, mysqlprocgrep, mysqlreplicate, mysqlrplcheck, mysqlrplshow, mysqlserverclone. (Bug #13721467) The --copy-dir option was removed from the mysqluserclone and mysqldbcopy utilities. (Bug #13576571) The MySQL Utilities Testing tool (mut) --sorted option had no function. It now accepts either asc or desc, with asc remaining the default. (Bug #13592147) When executing a diff operation with the mysqldiff utility on a single server between two databases with missing objects, an invalid warning would be issued that did not show the correct servers involved. (Bug #13554750)

This section documents all changes and bug fixes applied since the release of 1.0.3. Functionality Added or Changed Added the --write-command option to the mysqlserverclone utility, which saves the command used to launch the new server instance. This command may also be shown while generated, depending on the -verbose level. (Bug #13082771) Added the --locking option to the mysqldbcopy and mysqldbexport utilities, which now allows for table locking. Added the --regexp option, which changes the --exclude option behavior to use REGEXP instead of LIKE for its matching. This change affects the mysqldbcopy and mysqldbexport utilities. The mysqldbcompare utility can now generate SQL statements for synchronizing the objects and data for the compared databases. This adds the --difftype, --changes-for, and --show-reverse options.
490
Also, enabling the --quiet option will now only generate the diff output for runs when the --difftype option is set, but not as =sql. And only output the SQL statements when --difftype is set to =sql. Added a parser for the slow and general logs, within the new mysql.utilities.parser module that contains the SlowLog, SlowLogEntry, GeneralLog, and GeneralLogEntry classes. Bugs Fixed Installation would alter the permissions of /etc/profile.d/mysql-utilities.sh before creating the file. The order of operations has been corrected. (Bug #13115052) Optimized the mysqldbexport utility performance, namely for the _table.get_column_metadata() and table.get_column_string() methods. (Bug #13082780) The setup.py command would not generate all manual pages. (Bug #12988064) Refactored conditions to use list within the mysqldbexport and mysqldbimport utilities. (Bug #12945167) The mysqldbcopy utility would crash when any of the data contained an apostrophe. (Bug #63145, Bug #13418634)

This section documents all changes and bug fixes applied since the release of 1.0.2. Functionality Added or Changed Added the following options to the mysqlreplicate utility: --start-from-beginning, --masterlog-file, and --master-log-pos Added the mysqlrplshow utility, which is used to show replication slaves. Bugs Fixed Added the --all option to the mysqldbcopy and mysqldbexport utilities. (Bug #12885004) The mysqlreplicate utility no longer executes FLUSH TABLE WITH READ LOCK before obtaining the master's status. (Bug #12887948) server.connect_servers would force the source and destination to be of the same type. (Bug #12871032) While using the mysqldbcopy utility, the % symbol within routines would be changed to %%. (Bug #12757358)

This section documents all changes and bug fixes applied since the release of 1.0.1. Functionality Added or Changed Added the --new-storage-engine and --default-storage-engine options to the mysqldbcopy and mysqldbimport utilities. (Bug #12632010) Refactored the exception handling in the python library for MySQL Utilities to be more granular, and divided them into classes and errors types.
491
Refactored the MySQL Utilities library to make the server connection use a variety of connection parameters. Refactored the MySQL Utilities library to remove optional parameter lists, and replaced them with an options dictionary. Bugs Fixed Exporting a database with tables containing a single column and a mixed set of storage engines could result in the wrong storage engine being used. (Bug #12631924) Several parts of the code referred to the incorrect postal address of the Free Software Foundation. (Bug #12614037) Attempting to connect to a host name containing hyphens using any of the python based command line utilities would truncate the host name at the hyphen. (Bug #60252, Bug #11829755) Refactored the MySQL Utilities tree to remove extraneous files, fix test locations, and make mut resemble MTR's folder structure. Added the mysqldbcompare utility, which is used to compare two databases. Added the mysqlrplcheck utility, which is used to check replication prerequisites.

This section documents all changes and bug fixes applied since the release of 1.0.0. Functionality Added or Changed mysqlserverclone did not print out the connection information. (Bug #59095) With mysqluserclone, the --destination option is now optional, and defaults to the connection information provided by --source. Before, both options were required even when the values were identical. (Bug #59096) Added the mysqldiff utility, which is used to check database definition differences. Added the mysqldiskusage utility, which is used to show disk usage information. Added the mysqlserverinfo utility, which is used to show MySQL server information. Bugs Fixed Fixed a typo within the mysqldiskusage help page. (Bug #11854150) Diff related mut unit tests would fail with Python 2.7+. (Bug #11854512) The mysqldbexport, mysqlimport, and mysqldbcopy utilities would not form correct user@host pairings with remote access privileges. (Bug #59478) mysqldiskusage did not work. A workaround was to fix the hashbang. (Bug #60852) mysqlreplicate would fail when the two servers had the same port number. (Bug #59477, Bug #11766376) The MySQL utilities unit tests would fail under MySQL 5.5, due to INFORMATION_SCHEMA changes. (Bug #60008)
492
There were several installation related problems, including: everything was installed under /usr/local on Ubuntu (scripts not found), setuptools is used by utilities but not for c/Python (library not found), not all files were written while using --record during installation, and the required dependencies were not clarified in the README. (Bug #59083) The format_tabular_list() method in mysql.utilities.common.format.py did not properly print a single-column list. (Bug #59265, Bug #11766207)

First release of the MySQL Utilities. Functionality Added or Changed Added the mysqlreplicate utility, which is used to quickly set up replication. Added the mysqlindexcheck utility, which is used for index checking. Added the mysqlprocgrep utility, which is used to find and operate on processes. Added the mysqluserclone utility, which is used to clone users. Added the mut unit test framework. Added the mysqlserverclone utility, which is used to clone server instances. Added the mysqlmetagrep utility, which is used to search database object definitions. Added the documentation build system, which is based on sphinx. Added the mysqldbimport and mysqldbexport utilities, which are used to import and export data. Added the mysqldbcopy utility, which is used to copy databases.
493
494

Workbench en

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Workbench en

Uploaded by

Copyright:

Available Formats

MySQL Workbench

7.2. 7.3. 7.4. 7.5.

Preface and Legal Notices

Chapter 1. MySQL Workbench Introduction

Chapter 2. MySQL Workbench Editions

Chapter 3. Installing and Launching MySQL Workbench

3.1. Hardware Requirements

3.2. Software Requirements

Starting MySQL Workbench

3.3. Starting MySQL Workbench

Installing MySQL Workbench on Windows

--quit-when-done: Quits MySQL Workbench after --script or --run finishes.

3.3.1. Installing MySQL Workbench on Windows

3.3.2. Launching MySQL Workbench on Windows

Uninstalling MySQL Workbench on Windows

3.3.3. Uninstalling MySQL Workbench on Windows

Installing MySQL Workbench on Linux

3.3.4. Installing MySQL Workbench on Linux

3.3.5. Launching MySQL Workbench on Linux

This will display the available command-line options:

3.3.6. Uninstalling MySQL Workbench on Linux

Installing MySQL Workbench on Mac OS X

To uninstall a Debian package, use this command:

Uninstalling RPM packages To uninstall an RPM package, use this command:

This command does not remove the configuration files.

3.3.7. Installing MySQL Workbench on Mac OS X

3.3.8. Launching MySQL Workbench on Mac OS X

Uninstalling MySQL Workbench on Mac OS X

It is also possible to start MySQL Workbench from the command line:

A model file must be specified.

3.3.9. Uninstalling MySQL Workbench on Mac OS X

Chapter 4. Getting Started Tutorial

4.1. Administering a MySQL Server

Administering a MySQL Server

Figure 4.1. Getting Started Tutorial - Home Window

Administering a MySQL Server

Figure 4.2. Getting Started Tutorial - Specify Host Machine

Administering a MySQL Server

Figure 4.3. Getting Started Tutorial - Database Connection

Administering a MySQL Server

Figure 4.4. Getting Started Tutorial - Connection Test

Administering a MySQL Server

Figure 4.5. Getting Started Tutorial - Management and OS

Administering a MySQL Server

Figure 4.6. Getting Started Tutorial - SSH Configuration

Administering a MySQL Server

Figure 4.7. Getting Started Tutorial - Windows Management

Administering a MySQL Server

Figure 4.8. Getting Started Tutorial - Test Host Settings

Administering a MySQL Server

Figure 4.9. Getting Started Tutorial - Review Settings

Administering a MySQL Server

Figure 4.10. Getting Started Tutorial - Instance Name

Administering a MySQL Server

Figure 4.11. Getting Started Tutorial - Home Window Instance

Figure 4.12. Getting Started Tutorial - Admin Startup

4.2. Creating a Model

Figure 4.13. Getting Started Tutorial - Home Window

Figure 4.14. Getting Started Tutorial - New Schema

Column Name movie_title release_date

Data Type VARCHAR(45) DATE (YYYY-MM-DD)

Column Properties NN None