MySQL Workbench 6.2.3 GA has been released

Dear MySQL users,

The MySQL developer tools team announces 6.2.3 as our GA release for
MySQL Workbench 6.2.

MySQL Workbench 6.2 is the new version for the official MySQL
graphical development tool .

MySQL Workbench 6.2 focuses on support for innovations released in MySQL
5.6 and MySQL 5.7 DMR (Development Release) as well as MySQL Fabric 1.5,
with features such as:

  • A new spatial data viewer, allowing graphical views of result sets
    containing GEOMETRY data and taking advantage of the new GIS
    capabilities in MySQL 5.7.
  • Support for new MySQL 5.7.4 SQL syntax and configuration options.
  • Metadata Locks View shows the locks connections are blocked or waiting on.
  • MySQL Fabric cluster connectivity – Browsing, view status, and connect
    to any MySQL instance in a Fabric Cluster.
  • MS Access migration Wizard – easily move to MySQL Databases.

Other significant usability improvements were made, aiming to raise
productivity for advanced and new users:

  • Direct shortcut buttons to commonly used features in the schema tree.
  • Improved results handling. Columns have better auto-sizing and their
    widths are saved. Fonts can also be customized. Results “pinned” to
    persist viewing data.
  • A convenient Run SQL Script command to directly execute SQL scripts,
    without loading them first.
  • Database Modeling has been updated to allow changes to the formatting
    of note objects and attached SQL scripts can now be included in forward
    engineering and synchronization scripts.
  • Integrated Visual Explain within the result set panel.
  • Visual Explain drill down for large to very large explain plans.
  • Shared SQL snippets in the SQL Editor, allowing multiple users to
    share SQL code by storing it within a MySQL instance.
  • And much more.

The list of provided binaries was updated and MySQL Workbench binaries
now available for:

  • Windows 7 32 and 64bits
  • Mac OS X Lion or newer
  • Ubuntu 12.04 LTS and Ubuntu 14.04 64bits
  • Fedora 20 64bits
  • Oracle Linux 6.5 64bits
  • Oracle Linux 7 64bits
  • Sources for building in other Linux distributions. Pre-compiled binaries
    are no longer provided for 32bit Linux distributions, although users may
    still download and build from sources.

Note: Workbench for Windows requires Visual C++ Redistributable for
Visual Studio 2013, which can be downloaded from:

http://www.microsoft.com/en-us/download/details.aspx?id=40784

For the full list of changes in this revision, visit
http://dev.mysql.com/doc/relnotes/workbench/en/changes-6-2.html

For discussion, join the MySQL Workbench Forums:
http://forums.mysql.com/index.php?151

Download MySQL Workbench 6.2.3 now, for Windows, Mac OS X 10.7+, Oracle
Linux 6 and 7, Fedora 20, Ubuntu 12.04 and Ubuntu 14.04 or sources,
from:

http://dev.mysql.com/downloads/tools/workbench/

10 thoughts on “MySQL Workbench 6.2.3 GA has been released”

  1. I tried to install this version on my Debian Sid but it failed with

    mysql-workbench-community depends on libcairo2 (>= 1.13.0~20140204); however:
    Version of libcairo2:amd64 on system is 1.12.16-5.
    mysql-workbench-community depends on libproj0; however:
    Package libproj0 is not installed.

    However the latest version of cairo is 1.12.16. Is 1.13 unreleased software?

    http://cairographics.org/releases/

  2. Sounds like you’re using the package for Ubuntu 14.04, all the dependencies there are from Ubuntu. If you can’t install/upgrade libcairo, then I suppose your best bet would be to build from sources (or use Ubuntu 🙂
    The source build instructions were updated in the INSTALL file.

  3. Dear Release Team – Thank you for the new features! Workbench Rocks!! Thank you for all the hard work that goes into each release of Workbench.

    I’m looking forward to using 6.2.3 I am currently experiencing a minor setback.

    The ubuntu software center (USC) barked at me on the 14.04 64bit deb file. Some of the Lintian checks (uptight package checks) failed. Most are warnings, but a few were classified as errors.

    Is it OK to install the deb file with dpkg -i instead of using the USC for the install?

    Here are the lintian errors just in case its helpful.

    Here’s the command used to produce the lintian warnings list below:
    lintian mysql-workbench-community-6.2.3-1ubu1404-amd64.deb

    ***————***
    E: mysql-workbench-community: embedded-library usr/lib/mysql-workbench/libgdal.so.1.16.2: tiff
    E: mysql-workbench-community: embedded-library usr/lib/mysql-workbench/libgdal.so.1.16.2: libjpeg
    E: mysql-workbench-community: binary-or-shlib-defines-rpath usr/lib/mysql-workbench/libiodbcadm.so.2.1.19 /local/home/mysqldev/linux-res-6.2/usr/lib
    E: mysql-workbench-community: embedded-library usr/lib/mysql-workbench/libmysqlclient.so.18.1.0: zlib
    E: mysql-workbench-community: embedded-library usr/lib/mysql-workbench/libmysqlclient.so.18.1.0: libmysqlclient
    W: mysql-workbench-community: hardening-no-relro usr/lib/mysql-workbench/libmysqlclient.so.18.1.0
    E: mysql-workbench-community: embedded-library usr/lib/mysql-workbench/mysql: zlib
    E: mysql-workbench-community: embedded-library usr/lib/mysql-workbench/mysql: libmysqlclient
    W: mysql-workbench-community: hardening-no-relro usr/lib/mysql-workbench/mysql
    E: mysql-workbench-community: embedded-library usr/lib/mysql-workbench/mysqldump: zlib
    E: mysql-workbench-community: embedded-library usr/lib/mysql-workbench/mysqldump: libmysqlclient
    W: mysql-workbench-community: hardening-no-relro usr/lib/mysql-workbench/mysqldump
    W: mysql-workbench-community: wrong-bug-number-in-closes l407:#nnnn
    W: mysql-workbench-community: old-fsf-address-in-copyright-file
    E: mysql-workbench-community: copyright-file-contains-full-gpl-license
    W: mysql-workbench-community: extra-license-file usr/share/doc/mysql-workbench/COPYING.gz
    W: mysql-workbench-community: binary-without-manpage usr/bin/mysql-workbench
    W: mysql-workbench-community: binary-without-manpage usr/bin/mysql-workbench-bin
    W: mysql-workbench-community: binary-without-manpage usr/bin/wbcopytables
    W: mysql-workbench-community: pkg-not-in-package-test mysql-workbench usr/share/menu/mysql-workbench-community
    W: mysql-workbench-community: script-not-executable usr/share/mysql-workbench/extras/build_freetds.sh

    Thanks again for all the work on this release. Your efforts are appreciated.

  4. After upgrade to community workbench 6.2.3
    I could not open model files
    after some checks I found that the reason was
    an hebrew letters in my file path
    in the previous version it was not a problem

  5. Thanks for your work on this release (6.2.4)

    The Ubuntu 14.04 package installer is balking on the install file. Here are the lintian errors.

    Command to see the lintian errors:
    lintian mysql-workbench-community-6.2.4-1ubu1404-amd64.deb

    E: mysql-workbench-community: embedded-library usr/lib/mysql-workbench/libgdal.so.1.16.2: libjpeg
    E: mysql-workbench-community: embedded-library usr/lib/mysql-workbench/libgdal.so.1.16.2: tiff
    E: mysql-workbench-community: binary-or-shlib-defines-rpath usr/lib/mysql-workbench/libiodbcadm.so.2.1.19 /local/home/mysqldev/linux-res-6.2/usr/lib
    E: mysql-workbench-community: embedded-library usr/lib/mysql-workbench/libmysqlclient.so.18.1.0: libmysqlclient
    E: mysql-workbench-community: embedded-library usr/lib/mysql-workbench/libmysqlclient.so.18.1.0: zlib
    E: mysql-workbench-community: embedded-library usr/lib/mysql-workbench/mysql: libmysqlclient
    E: mysql-workbench-community: embedded-library usr/lib/mysql-workbench/mysql: zlib
    E: mysql-workbench-community: embedded-library usr/lib/mysql-workbench/mysqldump: libmysqlclient
    E: mysql-workbench-community: embedded-library usr/lib/mysql-workbench/mysqldump: zlib
    E: mysql-workbench-community: copyright-file-contains-full-gpl-license

  6. dears
    i use the Centos in VMware ,,and i have mysql workbench on my windows 7 ,i want to ask if i made a database on mysql workbench how can i use it in centos inside the vmware

Leave a Reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload CAPTCHA.