MySQL Lists are EOL. Please join:

List:General Discussion« Previous MessageNext Message »
From:daniel.horecki Date:April 19 2018 1:36pm
Subject:MySQL Workbench 8.0.11-rc has been released
View as plain text  
Dear MySQL users,

The MySQL developer tools team announces 8.0.11 as our release candidate (RC) for
MySQL Workbench 8.0.

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

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

The release is now available in source and binary form for a number 
ofplatforms from our download pages at:

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

Enjoy!

Changes in MySQL Workbench 8.0.11 (2018-04-19, Release Candidate)


      * Functionality Added or Changed

      * Bugs Fixed

Functionality Added or Changed


      * Visual SQL editor: The context help has been enhanced to
        eliminate the requirement of having a valid MySQL
        connection to view the help topics. In addition, the help
        content now can be updated with each release of MySQL
        Workbench and the formatting of help topics has been
        improved. (Bug #25918509)

      * Microsoft .NET Framework version 4.5 replaced version
        4.5.2 as the minimum requirement for installing MySQL
        Workbench with MySQL Installer. (Bug #25837944)

      * All links to MySQL and Oracle web pages from within MySQL
        Workbench now use the HTTPS protocol. (Bug #25531365)

      * Geometry fields displayed in the result grid now include
        a context-menu item that opens the geometry point in a
        browser. The selected point opens in openstreetmap.org by
        default, but the URL is configurable. (Bug #25517676)

      * The MySQL Workbench prerequisites web page was updated to
        include links to the latest Microsoft downloads.
        (Bug #25408896, Bug #25840902, Bug #85820)

      * The SSH Connect Timeout preference now can be configured,
        whereas in previous versions, this preference was set
        statically to 10 seconds. (Bug #18663250)

      * The following infrastructure changes were made:

           + ANTLR4 as the backend parser.

           + A new code-completion engine that works with object
             editors (triggers, views, stored procedures, and
             functions) in the visual SQL editor and in models.

           + Support for new language features in MySQL 8.0, such
             as common-table expressions and roles.

           + Grammar updates that synchronize with the latest
             MySQL servers.

      * Platform support for Microsoft Windows Server 2016 was
        added.

      * Administration tabs were modified to include the latest
        configuration options available from servers up to and
        including the MySQL 8.0 release series.

      * Character sets and collations are now rendered
        consistently across connections, models, and all editors
        (schema, table, and column).

      * MySQL Workbench now supports the caching_sha2_password
        authentication plugin introduced in MySQL 8.0 (see
        Caching SHA-2 Pluggable Authentication
       
(http://dev.mysql.com/doc/refman/8.0/en/caching-sha2-pluggable-authentication.html)).
        A user account can be reset to use the other available
        authentication types for making a connection.

      * MySQL Workbench source code has been reformatted
        according to Google style.

      * MySQL Workbench now uses C++14 (replaces C++11 in
        6.3.10).

      * Support for invisible indexes was added for use when the
        active server supports the feature and the index is
        neither a primary key index nor a unique column (see
        Invisible Indexes
        (http://dev.mysql.com/doc/refman/8.0/en/invisible-indexes.html)).
        A new option in the Indexes subtab of the table
        editor (for both the SQL and modeling editors) provides
        index visibility when it is selected.

      * MySQL Workbench now provides a simple way to enable or
        disable the persisted global system variable settings
        introduced in MySQL 8.0 (see SET Syntax for Variable
        Assignment
        (http://dev.mysql.com/doc/refman/5.7/en/set-variable.html)).
        For variables that can be persisted, a new check box
        enables configuration changes at runtime that also
        persist across server restarts, and applies the persisted
        value if one exists. Persistent system variables can be
        reset (to not persist) individually or collectively.

      * The layout and behavior of the graphical elements within
        all administration tabs now are consistent across the
        tabs. In addition, the sidebar Management secondary tab
        was renamed to Administration to match the title of the
        workspace tabs that open when accessing the operations
        listed in the Management, Instance, Performance, and
        MySQL Enterprise sections.

Bugs Fixed


      * Several tooltips within the Administration - Users and
        Privileges tab had inaccurate text that was corrected by
        this fix. (Bug #27392119, Bug #89256)

      * Columns of a table that followed a column containing a
        fractional seconds part did not appear within the tab
        opened by using Alter Table. (Bug #27314770, Bug #89053)

      * MySQL Workbench generated an error when the valid
        encryption instruction was improperly identified, but the
        query executed as expected. (Bug #27239353)

      * A differences report generated during the compare schemas
        operation for models could not be saved to a file.
        (Bug #27187659)

      * The on-screen buttons that enable saving a script to a
        file or copying it to the clipboard were missing from the
        review step of the forward-engineering operation on macOS
        hosts. (Bug #27162920, Bug #88612)

      * A UNION query with valid syntax produced an error
        message. (Bug #27113889, Bug #88456)

      * Some MySQL 8.0 keywords within a query were improperly
        identified as syntax errors. (Bug #27036620)

      * Importing a JSON document with the Table Data Import
        Wizard was unsuccessful. (Bug #27036381, Bug #25983728,
        Bug #86148)

      * Recorded rules were not found after the Mode option in
        the Firewall tab was properly configured for a valid user
        account. (Bug #27003240)

      * The manual editing step of the MySQL Migration wizard
        generated an exception when an object was selected for
        editing. (Bug #26986326)

      * The version of gtkmm30 that shipped with Red Hat
        Enterprise Linux 7.4 was incompatible with the version
        that MySQL Workbench compiled against. The version
        mismatch caused MySQL Workbench to close unexpectedly.
        (Bug #26797891)

      * The DBDoc Model Reporting feature omitted comments from
        the detailed HTML report using frames when processing a
        model based on a database with valid table comments and
        the Include DDL code for Objects option selected.
        Generating the report also caused MySQL Workbench to exit
        unexpectedly. (Bug #26436291)

      * The Table Data Import wizard ignored the user's column
        selection and always generated tables containing the full
        set of columns. Deselected columns were populated with
        NULL values after the import operation. (Bug #26194914,
        Bug #86577)

      * When typing text in the search box related to an EER
        diagram, MySQL Workbench became unresponsive or exited
        unexpectedly. (Bug #26025177, Bug #86225, Bug #26678740,
        Bug #87522)

      * A table or stored procedure with the ENCRYPTION
        table-level option in the definition prevented Workbench
        from parsing the definition, regardless of whether or not
        encryption was actually enabled. (Bug #25961450,
        Bug #25447637)

      * The SQL editor did not highlight syntax errors in
        statements as expected. (Bug #25861352)

      * Workbench closed unexpectedly when the Compare and Report
        Differences in Catalogs wizard attempted to save the
        differences report to a file. (Bug #25860643)

      * With a default schema properly selected and with the
        Create View icon (from the menu bar in an active
        connection tab) selected to open a new_view - View tab, a
        valid statement returned errors and then dynamically
        appended _SYNTAX_ERROR to the view name. For example,
        new_view was changed to new_view_SYNTAX_ERROR.
        (Bug #25860621)

      * When a new procedure on a MySQL model was created, the
        parser incorrectly generated a syntax error.
        (Bug #25851441)

      * After restarting the server from MySQL Workbench and then
        attempting to refresh the server log from the
        Administration - Server Logs tab, an error message
        appeared indicating that a garbage packet was received.
        (Bug #25760560)

      * An error message appeared when MySQL Workbench was
        started that improperly identified the operating system
        as unsupported. (Bug #25736096)

      * The forward engineering wizard did not launch when the
        operation was selected from the MySQL Workbench menu on
        hosts running macOS. (Bug #25701117, Bug #85398)

      * Changes made to a view or stored procedure associated
        with a model were not detected after the model was
        synchronized without first closing or deselecting the
        editor. (Bug #25671681, Bug #85246)

      * Using Alter Stored Procedure from the context menu to
        rename a stored procedure did not remove the original
        stored procedure after renaming it. (Bug #25645222,
        Bug #85229)

      * Two program entries were created for MySQL Workbench
        6.3.9 on Windows when installed or upgraded with MySQL
        Installer. Only one of the programs listed in the Start,
        All Programs menu was a valid executable file.
        (Bug #25584877, Bug #85083)

      * All SQL options were missing during the SQL Export
        Options step of the Forward Engineering SQL Script wizard
        when a valid model was exported. (Bug #25559175,
        Bug #85012, Bug #25833972, Bug #84965)

      * Object rights, DDL rights, and other rights related to
        schema privileges set for a user account were not visible
        from the Administration - Users and Privileges tab on the
        Windows platform. (Bug #25527029, Bug #84923)

      * Labels and icons associated with the tables, views, and
        routines of an EER diagram were missing from within the
        Catalog tab. (Bug #25519411, Bug #84892)

      * The generated UPDATE statement was incorrect when the
        query included a row with a unique index, had multiple
        columns, and one column had the NULL value.
        (Bug #25510537, Bug #84856)

      * Browsing for files on a remote server using a valid SSH
        connection returned an error and did not display the
        remote files. (Bug #25495895)

      * After backing up server connections to a file on a Linux
        host, attempting to restore those connections from the
        backup file generated errors and was unsuccessful.
        (Bug #25492082)

      * Clicking Start Server within the Administration - Startup
        / Shutdown tab did not start the server on macOS hosts.
        (Bug #25489098)

      * The layout of Firewall Rules within the Administration -
        Users and Privileges tab obscured some graphical
        elements. This fix improves the usability.
        (Bug #25487997)

      * Source objects could not be viewed within the setup step
        when using the MySQL Workbench Migration Wizard to
        prepare for a database migration. (Bug #25487312)

      * The spinning circular icon on the query tab that appears
        when a query executes and replaces the X on the tab was
        absent on hosts running Linux. (Bug #25482378)

      * An exception was returned when the Continue execution
        until next break point button was used on a script
        executing within the Scripting Shell. (Bug #25476250)

      * When a new snippet was saved within the Scripting Shell,
        the save operation did not save the snippet properly and
        the snippet could not be reused after MySQL Workbench was
        restarted. (Bug #25471491)

      * The Run Script File action could be selected from the
        Scripting menu without an available script to execute.
        This fix disables the submenu item unless there is a
        script to run. (Bug #25462195)

      * Migrating a table to a database generated an incomplete
        definition for a binary field that was NOT NULL.
        (Bug #25404308, Bug #84519)

      * Altering a stored procedure that contained double
        dollar-sign characters ($$) as part of a variable name
        produced an error parsing DDL message. (Bug #25377145,
        Bug #84466)

      * Single quotes in string columns were not escaped properly
        during the database migration operation. (Bug #24939843)

      * When multiple queries were executed, only the first query
        was displayed in the history output area or written to
        the sql_history log file. (Bug #24622889, Bug #82929)

      * The invalid syntax indicator that appears on each line of
        the SQL editor did not change after the syntax was
        corrected or completed. This fix ensures that the editor
        re-evaluates each change. (Bug #24528088, Bug #82741,
        Bug #24901911, Bug #83395, Bug #24901911, Bug #83395)

      * With large text enabled on the host, some option groups
        were not visible to select within the forward-engineering
        wizard. (Bug #24486726, Bug #82633)

      * For a table with existing indexes (and
        SQL_MODE=ANSI_QUOTES), the Indexes tab within the table
        editor (opened with the wrench button in the Schemas tab
        of the sidebar) did not show the indexes as expected.
        Columns, Foreign Keys, Triggers, and Partitioning tabs
        were also missing objects defined in the table.
        (Bug #24349382, Bug #80483)

      * Unless the default syntax checker was set to
        SQL_MODE=ANSI_QUOTES, all double-quoted string literals
        were highlighted as syntax errors by the SQL editor.
        (Bug #24329515, Bug #82293)

      * After executing a query, MySQL Workbench often quit
        working or exited unexpectedly without writing to the log
        file. This fix improves the overall stability of the SQL
        editor. (Bug #24291775, Bug #82187)

      * The SQL editor underlined some keywords and reserved
        words in statements, indicating a syntax error, but
        executed the statements successfully. (Bug #23346980,
        Bug #24345217, Bug #82331)

      * Attempting to store a password in the vault from the
        Manage Server Connections window on a Windows host caused
        MySQL Workbench to become unresponsive. (Bug #23308198,
        Bug #81470)

      * When executing Explain Current Statement (Ctrl+Alt+X)
        from the menu on an UPDATE statement, a query plan
        generation error was displayed and the operation failed.
        (Bug #23098982, Bug #81068)

      * The Reverse Engineer Database wizard excluded tables in
        which the WITH PARSER clause was present. (Bug #22940775,
        Bug #80760)

      * A column with the STORED keyword could not be generated
        by using the EER Diagram or MySQL Model tabs on macOS
        hosts. This fix updates all of the relevant tabs to
        include the missing STORED option for generating a column
        or for editing generated columns. (Bug #22645321,
        Bug #80211)

      * Table rows were not generated properly when a valid
        Microsoft SQL Server table was migrated using the MySQL
        Migration wizard. (Bug #22200194, Bug #77933)

      * The forward engineering operation passed the default
        collation when a custom collation was defined for a
        schema. (Bug #22148986, Bug #79115)

      * When synchronizing a MySQL model that contained a table
        with JSON columns, the operation attempted to create a
        new table instead of fetching the table from the
        database. (Bug #22060787)

      * Columns with custom collation were reset to the default
        collation when the model containing the table was
        exported. (Bug #22006966, Bug #78817)

      * Models synchronized with existing databases produced an
        error message if any of the tables within a model had
        comments enclosed between /* and */ characters in
        triggers. (Bug #21551643, Bug #76176)

      * Generated queries were incomplete for models that
        included table columns of type VARCHAR with partitioning
        enabled. (Bug #21104120, Bug #76489)

      * Some fields within the Table Data Import wizard were
        misaligned and difficult to use. (Bug #20956767)

      * If the SCHEMAS tree was refreshed during a long query,
        MySQL Workbench became unresponsive until the query
        finished. (Bug #20896682, Bug #76594)

      * An error message was displayed when the delete operation
        was performed on an existing connection in the Manage
        Server Connections window. (Bug #20652117, Bug #76153)

      * The mouse pointer did not always change shape to match
        the area it was moved to within the visual SQL editor.
        (Bug #20588048, Bug #75993)

      * A complex IF, ELSEIF, ELSE structure when used to create
        a stored procedure within the new procedure - Routine tab
        produced a syntax error message as clause 45 was added
        and for each clause that followed. (Bug #18972055,
        Bug #72991)

      * Code completion did not provide a suggestion reliably for
        instructions included in the server dictionary, such as
        statements or system variables. In addition, types like
        TIMESTAMP were completed with the wrong type values.
        (Bug #18445589, Bug #27386829, Bug #89222, Bug #26897612,
        Bug #87907, Bug #18871688, Bug #72812)

      * Attempting to access the MySQL Enterprise Backup
        interface caused MySQL Workbench to stop working.
        (Bug #18019469)

      * An on-screen label with inaccurate text was corrected.
        (Bug #16808557)

      * Erroneous input at the beginning of the line in the SQL
        editor generated an error marker that continued to
        display after the wrong input was corrected or removed.
        (Bug #13820997, Bug #64481)

      * Popular Windows themes did not always render as expected,
        especially when color themes were selected on Windows
        hosts. In particular, some areas persisted a white
        background regardless of the setting. (Bug #11760110,
        Bug #52485)

      * When out-of-range index, unique index, or primary key
        values were define in the source, no warning was provided
        to indicate that the code produced could not be executed
        by the MySQL server. (Bug #11745588, Bug #17509)

On Behalf of Oracle/MySQL Release Engineering Team,

Daniel Horecki

Thread
MySQL Workbench 8.0.11-rc has been releaseddaniel.horecki19 Apr