[prev in list] [next in list] [prev in thread] [next in thread]
List: mysql
Subject: MySQL Workbench 8.0.12 has been released
From: Balasubramanian Kandasamy <balasubramanian.kandasamy () oracle ! com>
Date: 2018-07-27 17:30:26
Message-ID: 7fc4f58c-88d3-313a-2f7a-0c0c5f4b9757 () oracle ! com
[Download RAW message or body]
Dear MySQL users,
The MySQL developer tools team announces 8.0.12 as our first general
availability (GA) 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 of
platforms from our download pages at:
http://dev.mysql.com/downloads/tools/workbench/
Enjoy!
Changes in MySQL Workbench 8.0.12 (2018-07-27, General Availability)
Known limitation of this release: Importing spatial data into
a MySQL 8.0 server does not work currently, due to an
outstanding library update. Older versions of the server are
not affected.
* Installation Notes
* Functionality Added or Changed
* Bugs Fixed
Installation Notes
* Because the Microsoft Visual C++ 2017 Redistributable
installer deletes the Microsoft Visual C++ 2015
Redistributable registry keys that identify its
installation, standalone MySQL MSIs may fail to detect
the Microsoft Visual C++ 2015 Redistributable if both it
and the Microsoft Visual C++ 2017 Redistributable are
installed. The solution is to repair the Microsoft Visual
C++ 2017 Redistributable via the Windows Control Panel to
recreate the registry keys needed for the runtime
detection. Unlike the standalone MSIs, MySQL Installer
for Windows contains a workaround for the detection
problem. (Bug #28345281, Bug #91542)
Functionality Added or Changed
* Important Change: MySQL model files last saved before
MySQL Workbench 6.3 are no longer supported unless the
models can be upgraded for use with the 6.3 release
series.
* All editions of MySQL Workbench and the bundled libraries
were upgraded to use OpenSSL 1.0.2o. (Bug #27829782, Bug
#28326884)
* libgnome-keyring was depreciated and replaced with
libsecret in this release on Linux platforms. Some users
with existing stored passwords will be prompted to enter
a password after upgrading. (Bug #27635281, Bug #89898,
Bug #20291538, Bug #75345)
* SSH tunneling support was added to the MySQL Workbench
Migration Wizard and also to the wbcopytables
command-line utility for copying data. (Bug #27556268,
Bug #89671)
* Performing multiple data export operations while the
Administration - Data Export tab stays open now preserves
custom file paths, rather than switching to the default
paths for re-export operations. Exported files are
automatically renamed with an incremental numeric suffix
to enable repeated export.
In addition, a new dialog box prompts for confirmation
before overwriting an existing exported file when the
same path and file names are reused. (Bug #27029840)
* OGRFree() was deprecated and replaced with CPLFree().
Thanks to Christian Hesse for the patch. (Bug #26086599,
Bug #86339)
* The SWIG prerequisite listed in the INSTALL document
provided with source distributions was updated to the
latest version. (Bug #25811732, Bug #85717)
* Support for the --incremental-with-redo-log-only option
was added to create backups directly from the redo log.
(Bug #24960233)
* The option to skip secure authorization is no longer
available in the advanced options that apply to data
import and export operations. The --skip-secure-auth
option was removed in the MySQL 5.7 release. (Bug
#21697062, Bug #78060)
* The character set and collation pairings available after
selecting Create a new schema in the connected server
(from the main toolbar) now are sorted alphabetically in
lists. (Bug #21681041, Bug #78079)
* A new SQL export option in the Forward Engineering SQL
Script wizard sorts tables alphabetically in the
generated script, rather than sorting tables according to
foreign-key references by default. (Bug #18551598, Bug
#72289)
* MySQL Workbench now supports the Chinese character set
gb18030. (Bug #18547307)
* The SQL editor supports online renaming of indexes with
the ALTER TABLE statement. For example:
ALTER TABLE `sakila`.`actor` RENAME INDEX `idx_actor_last_name`
TO `id
x_actor_last_xxxx`;
(Bug #18547288)
* MySQL Workbench now uses utf8mb4 as the connection and
client character set, replacing utf8mb3.
Bugs Fixed
* Some of the controls and data were not shown within the
Administration-Users and Privileges tab. (Bug #28246905,
Bug #91414)
* An attempt to add a column to an existing multicolumn
index (primary key) of a table caused MySQL Workbench to
stop working. (Bug #28244024, Bug #91371)
* On Windows platforms, pasting valid content into the SQL
editor was followed by the operating system becoming
unresponsive. (Bug #28184916, Bug #91249)
* A query containing SELECT COUNT(*) FROM DUAL, when saved
to a script file and then opened, caused MySQL Workbench
to exit. (Bug #28101684, Bug #91070)
* With code completion enabled, defining a custom variable
within a subquery caused an unexpected exit. (Bug
#28040983, Bug #90915)
* With an active MySQL 8.0.11 server connection, MySQL
Workbench displayed an error message when a valid attempt
was made to open Performance Reports or Performance
Schema Setup. (Bug #28034685, Bug #90889)
* Attempting to open a new query tab from the home screen
(File, New Query Tab from the menu) returned an error
message and closed MySQL Workbench. (Bug #28032431, Bug
#90885, Bug #27781092)
* The binlog-format option was not listed as expected
within the Administration - Options File tab. (Bug
#28008041)
* When Alter Stored Procedure was selected from the context
menu, MySQL Workbench stopped working. (Bug #28006985,
Bug #90830, Bug #23259608, Bug #81334)
* The advanced option, $internal$show-internal-schemas,
within the Administration - Data Export tab did not
expose internal schemas as expected. (Bug #27938719, Bug
#90665)
* MySQL Workbench stopped working when the CHANGE MASTER TO
statement was typed directly into the SQL editor,
followed by options. (Bug #27910024, Bug #90568)
* A stored procedure without a parameter direction (IN or
OUT) caused MySQL Workbench to exit when it attempted to
create or alter the procedure. (Bug #27908753, Bug
#90555)
* The source-database connection password used to
reverse-engineer a database was not requested and the
connection failed if the password was not stored in the
vault. (Bug #27882813)
* With SSH enabled, all new connections were made to the
same MySQL server instance, regardless of the port number
specified. (Bug #27882278)
* The operation that synchronizes tables with the MySQL
database produced an error message when an existing
column was moved to a position after a newly added
column. This fix ensures that ADD COLUMN always precedes
CHANGE COLUMN within the script when both are used
together. (Bug #27871632, Bug #90459)
* The table editor did not apply any changes made in the
order of an index to the generated ALTER TABLE statement.
(Bug #27868813)
* Snippet execution finished with an error when the
scripting shell was used. (Bug #27746883)
* An unclear error message was displayed during the
table-export operation when the file path was invalid or
left empty. (Bug #27746585)
* The shell script for copying bulk data was not generated
as expected. Instead, an error message was displayed.
(Bug #27745372)
* Setting a valid command-line path for remote-server
access using SSH tunneling in MySQL Enterprise Backup (on
Linux) caused the validation step to fail when both the
SSH and sudo users were the same. (Bug #27745200)
* MySQL Workbench model files (.mwb) did not open as
expected when double-clicked from File Explorer on
Windows platforms. (Bug #27739848)
* MySQL Workbench editors displayed text from the standard
exception in the action output, rather than using an
error message when SQL syntax errors were discovered.
(Bug #27730102)
* Two terminals opened when Start Command Line Client was
selected from the context menu on the home screen
(right-click an existing MySQL connection). (Bug
#27721918)
* Text objects when double-clicked within an EER diagram
caused MySQL Workbench to stop working. (Bug #27711642,
Bug #90119)
* The shell script created during the Data Transfer Setup
step of the migration process from a MySQL local
connection to a MySQL SSH connection produced errors that
prevented the copying of data from outside MySQL
Workbench. (Bug #27670242)
* Modifying the column order within an existing index on a
table caused MySQL Workbench to exit unexpectedly. (Bug
#27627986, Bug #89886)
* The Audit Inspector cache process failed when the
connection was within a group. (Bug #27567546)
* When using the 'OmitSchemata':1 parameter in a Python
script to generate a schema from an .mwb file
automatically, the resulting SQL script still included
the schema in each table name. This fix introduces the
OmitSchemas option, which replaces both the UseShortNames
and OmitSchemata options, to eliminate the schema name as
expected. (Bug #27557537, Bug #84390)
* The work area within an EER diagram was hidden after
double-clicking one of the table objects to open the
table editor. (Bug #27436624)
* When two schemas were compared with Synchronize Models
(from the Database menu), differences were reported
consistently for stored procedures and functions even
though the compared items were identical. (Bug #27436115,
Bug #82151)
* An existing MySQL model file, when selected from the home
screen, generated an error (Error unserializing GRT data
string too long) and did not open. (Bug #27420297, Bug
#89257)
* The sidebar panel of the EER diagram editor was cut off,
making the leftmost subtabs inaccessible and forcing the
diagram-zoom area to shift to the right. (Bug #27330971,
Bug #89072)
* An incorrect INSERT statement was generated when a value
was inserted into a BIT column. This fix now prefixes all
BIT data-type values with the character b (for example:
b'0'). (Bug #27320396, Bug #89068)
* When using the Reverse Engineer Database wizard, the
objects selected during the Select Objects step could not
then be deselected. (Bug #27319905, Bug #89064)
* Column-collation changes, when made using the table
editor, could not be applied. Instead, a message
indicating that no changes were detected was displayed.
(Bug #27297634, Bug #88985)
* The tls_version option was not listed as expected within
the Administration - Options File tab. (Bug #27272808,
Bug #87964)
* Syntax errors typed into the SQL editor are highlighted
and each one can provide usage information within a
tooltip while the pointer device hovers over the error.
On hosts running macOS, the tooltip remained visible when
the pointer device was moved off the highlighted error.
(Bug #27255488)
* When only one role in a model was assigned to a user
account, the role could not be removed. (Bug #27054771)
* Right-clicking within a new or existing script file that
was opened with the Workbench Scripting Shell did not
display the context menu as expected. (Bug #27037750)
* The edit dialog box did not open when an existing snippet
from SQL Additions was double-clicked. (Bug #27036975)
* The on-screen progress of a full backup operation never
changed from Starting. The correct progress was indicated
in the log. (Bug #27011013)
* Creating an MySQL model from a script, with the imported
objects added to a diagram, caused MySQL Workbench to
exit. (Bug #27010684)
* 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, Bug #26705113, Bug #87380)
* Catalog objects for an EER diagram were not listed,
although the tables were visible in the diagram. (Bug
#26747931, Bug #87662)
* The JSON tab of the Edit Data for Value dialog box
displayed large column values as negative numbers when
the numbers were positive. (Bug #26741970, Bug #87646)
* Some on-screen text within Workbench Preferences (Fonts &
Colors) wrapped around to new lines rather than filling
the open space on the same line. (Bug #26448300, Bug
#85961)
* The filter arrows that select objects for forward or
reverse engineering within wizards generated an error
instead of moving the objects as expected. (Bug
#26435349, Bug #26922638, Bug #87980, Bug #25921645, Bug
#86013, Bug #25852505, Bug #85837)
* The SQL editor returned an error when valid characters
were used with the utf8mb4 character set. (Bug #26142347,
Bug #86454)
* An error was reported during an attempt to back up
encrypted tables using MySQL Enterprise Backup. This fix
introduces the Encrypt Password option in the Options
subtab for a new job within the Administration - Online
Backup tab. Setting an encryption password is required to
perform backup and restore operations on encrypted
tables. (Bug #26135245)
* With multiple connection tabs opened, selecting Close All
But This from the context menu (right-click a connection
tab) closed tabs at random. (Bug #25983146, Bug #86144)
* Attempting to alter a table in MySQL Workbench produced
an error message when the table was previously altered
using a command-line client with the ENCRYPTION option
set to Y or N. (Bug #25929075, Bug #86021)
* When synchronizing a model with a database, none of the
buttons for the Select Changes to Apply step were
visible. In addition, some frames and options were
hidden. (Bug #25906359, Bug #85963, Bug #25527078, Bug
#84924, Bug #25747524, Bug #85500, Bug #26128307, Bug
#86426)
* Time stamps representing the elapsed time of backup
operations were miscalculated. (Bug #25820146, Bug
#85764)
* Long comments in tables were truncated with too few
characters when pasted into the SQL editor after using
Copy SQL to Clipboard from the context menu within an EER
diagram or the MySQL Model tab. This fix extends the
threshold. (Bug #25760721, Bug #85568)
* The attribute in source code that set the program name
('MySQLWorkbench') was omitted from Unix and Linux
distributions. Thanks to Daniël van Eeden for
contributing to the fix. (Bug #25725077, Bug #85460)
* Double-clicking areas within the spatial view caused
MySQL Workbench to become unresponsive. (Bug #25723306,
Bug #85443)
* The height and width of object-selection lists within the
Administration - Data Export tab were improperly
proportioned for the content of the lists and could not
be resized. A scroll bar now enables access to all listed
objects. (Bug #25716077, Bug #85308)
* A message displayed during the startup sequence indicated
that some valid operating systems were unsupported. For
current platform information, see
https://www.mysql.com/support/supportedplatforms/workbench.html.
(Bug #25602334, Bug #85087)
* A model exported as an SQL script could not be saved to
disk when using either the Forward Engineer to Database
or the Synchronize With Any Source wizard. (Bug
#25569529, Bug #85030)
* The buttons associated with renaming a diagram (OK and
Cancel) were partially concealed. (Bug #25557678, Bug
#85011)
* The progress bar and Abort button were partially
concealed on the screen when changes were being applied
to stored procedures. (Bug #25532963, Bug #84927)
* Each connection to an incompatible or nonstandard server
opened a dialog box with a valid warning, but without an
option to suppress the warning for subsequent
connections. Thanks to Christian Hesse for the patch.
(Bug #25519446, Bug #84885)
* A connection made with an improper file did not return an
SSL error as expected when the connection was tested.
(Bug #25517237)
* An explicit collation set on a column was reverted to the
default collation each time the column specification was
modified with the table editor. (Bug #25504264, Bug
#84815)
* The process running MySQL Workbench did not end on exit.
(Bug #25496663)
* The MySQL Workbench Migration Wizard returned an error
message after failing to get a row count from source
tables, which caused the wbcopytables utility to exit.
(Bug #25496622)
* Starting MySQL Workbench from the command line was
unsuccessful on hosts running the Fedora 25 operating
system. (Bug #25495120)
* Custom settings made before executing the data export
operation were not persisted if the operation was
executed again (by clicking Start Export a second time).
Instead, the custom settings were discarded and replaced
by the default settings. (Bug #25488234)
* Overlapping text boxes covered the full name entered for
the Create a New Table option within the Select
Destination step of the Table Data Import Wizard. (Bug
#25476103)
* The Copy and Copy Details operations from the Server Logs
context menu (right-click a row in the log) were swapped.
The Copy operation copied the details and the Copy
Details operation performed a simple copy. (Bug
#25469694)
* The Copy as PHP Code (Iterate SELECT Results) command
(select Tools and then Utilities from the menu) was
unexpectedly disabled for valid query results. (Bug
#25466399)
* On Linux platforms, right-clicking Tables within the
Catalog Tree for a valid EER diagram displayed an empty
context menu. This fix minimizes the size of the empty
menu. (Bug #25463963)
* Exporting a schema from the Administration - Data Export
tab returned an error when the server was configured for
use within an InnoDB cluster. (Bug #25444837)
* After maximizing and then reducing MySQL Workbench, some
screen options were improperly sized or no longer visible
on Linux platforms. (Bug #25415064)
* The set of default target schemas available to choose
from within the Administration - Data Import/Restore tab
showed each schema listed twice on Windows platforms.
(Bug #25239261, Bug #84161)
* The table editor did not display generated columns within
a user-defined table and the Alter Table operation
returned an error message when an attempt was made to
modify any of the nonvisible columns. (Bug #25209591, Bug
#84078)
* An error message was returned when an attempt was made to
inspect a partitioned table using either the information
icon or the context menu. (Bug #24973171, Bug #83605)
* A single MySQL connection tab could not be closed unless
a second connection tab was opened first. (Bug #24751859,
Bug #83194)
* With a connection made to a remote MySQL server, some
context-menu functionality stopped working. For example,
right-clicking a valid stored procedure from the Schemas
list and selecting Alter Stored Procedure or Create
Stored Procedure did not open a tab in the editor as
expected. (Bug #24506578, Bug #82659)
* On occasion, using sudo with a valid password to open a
log file produced an exception. (Bug #24297921)
* A variety of error messages were returned when attempts
were made to open the Output panel (or when using Help,
System Info from the menu) with older versions of MySQL
Workbench. System Info was removed from the menu. (Bug
#23584746)
* The print-preview operation (File, Print Preview from the
menu) did not work, or return an error message, on some
Linux platforms. (Bug #23467065)
* Executing separate queries (each in its own connection
tab) caused MySQL Workbench to exit. (Bug #23305283, Bug
#81480)
* The PROJ.4 library (libproj) was not found, which
prevented the initialization of Spatial Viewer. (Bug
#22931452, Bug #80710)
* A model diagram could not be reduced in size by clicking
to the grid or by adjusting its value with the input
controls. Attempts to reduce the size made the diagram
larger. (Bug #22929861, Bug #80730)
* Read-only tables, such as those having an index but no
primary key, could be selected for update. However, the
invalid update operation caused MySQL Workbench to become
unresponsive before the operation finished. (Bug
#22735577, Bug #80378)
* An active connection to MySQL server was closed
unexpectedly with the DBMS connection read time out (in
seconds) preference option set to zero, which should keep
the connection open. (Bug #22618750, Bug #80188)
* Performance Schema instrumentation was not reset from the
dashboard on Windows, even though confirmation of the
change was provided. (Bug #22557320, Bug #80021)
* When using the keyboard shortcut to comment selected
lines within the SQL editor and with the cursor wrapped
around to the beginning of the next line, the entire
unselected next line was also commented. (Bug #22282406,
Bug #77143)
* A second view was created unexpectedly when an existing
view was renamed using ALTER VIEW syntax. (Bug #22170451,
Bug #79176)
* An error message (Operation failed with exitcode 7) was
generated during the dump operation when an attempt was
made to export data running on a remote server. (Bug
#22093554, Bug #78937)
* The MySQL Server start and stop management operations
generated unhandled exceptions. (Bug #21861171)
* Stored procedures, when added to a model and synchronized
with a database, were not listed in the Navigator area of
the sidebar panel. New functions were not represented in
the Catalog Tree after synchronization, although each
function did appear in the Navigator area and in source.
(Bug #21443566, Bug #76368)
* Tabs separating multiple schemas within the Physical
Schemas area of the MySQL Model tab were not visible.
(Bug #21356922, Bug #77451)
* The on-screen description of the myisam-repair-threads
system variable was incomplete. It now indicates that the
(default) value of 1 disables parallel repair (see the
MyISAM tab in Administration - Option File). (Bug
#20667496, Bug #76200)
* Unexpected differences were displayed after using the
Forward Engineer to Database wizard and then
synchronizing the model and database. (Bug #20631631)
* The keyboard shortcut to open the Find and Replace dialog
box (or Edit, Replace from the menu) did not work from
within the Workbench Scripting Shell. (Bug #20630325)
* When importing data from a CSV file, some rows of data
were not shown until Apply was clicked. This fix replaces
the import functionality with a wizard. All rows now
display correctly in the Configure Import Settings step
of the Table Data Import wizard. Note that when no column
header is provided, the first row of data is used as the
header. (Bug #20630193)
* The template supplied for the Create a Table Like
operation (right-click Tables within the schema tree) was
not complete enough to use without custom modifications.
(Bug #20578595)
* The wb.log file did not rotate to a new file (for
example, wb.log to wb.1.log) as expected on startup. In
addition, all queries were written to the
sql_actions_unconnected.log file, instead of to an
individual log file for each connection. (Bug #20356293,
Bug #75496)
* The Zoom + icon in the spatial view toolbar produced
deteriorating resolution as an image was enlarged. For
better results, use the Zoom to area icon to recompute a
portion of the whole shape, instead of simply magnifying
the visible area with the Zoom + tool. (Bug #20279644,
Bug #75318)
* A newly created SSH connection could not be used to
synchronize a model with a MySQL database. (Bug
#20144296, Bug #75102)
* Expired root passwords were not supported by MySQL
Workbench and could not be changed during the first
attempt to make a connection to the server where the
password was expired. (Bug #19654005)
* Keywords in stored procedures and triggers were not
highlighted consistently within the SQL editor and code
blocks with keywords did not expand or collapse as
expected. (Bug #19000092, Bug #72677)
* Selecting Server and then Backup Recovery from the menu
generated an unhandled exception when the server was
stopped. (Bug #18492268)
* Returned rows of a column in the result grid did not
reliably sort by ascending and descending order when the
column label was clicked. (Bug #18454325)
* The Delete key did not function within EER diagrams. (Bug
#18445600)
* With both a MySQL model and EER diagram open, pressing
the CTRL+W keyboard shortcut twice closed the diagram,
but not the model file. (Bug #18445598)
* On Linux platforms before the home screen was redesigned,
attempting to drag and drop a connection from within a
group caused the group to move instead of the connection.
(Bug #18445563)
* When editing an EER diagram, the icons within the editor
overlapped on Linux platforms. (Bug #18426867)
* Schema transfer and migration operations did not support
SSH connections and produced error messages when the
operations were attempted. (Bug #18138798, Bug #71295)
* The Use defaults from global settings model option
(Model, Model Options from the menu in the MySQL Model
tab) when selected did not override the target MySQL
version (set in Model Options) with the default target
version (set in Workbench Preferences). (Bug #18130160,
Bug #71429)
* Attempting to edit a corrupted MySQL model (.mwb) file
resulted in an unpredicted shutdown. (Bug #17456147, Bug
#70334)
* The Save and Save As dialog boxes did not show the file
type of a model or SQL script. (Bug #17300401)
* On macOS platforms, the database-migration operation
returned various error messages when an attempt was made
to migrate valid data into MySQL. (Bug #17299915, Bug
#17299925, Bug #17408230)
* Selecting multiple objects (tables, views, and so on) in
a model, and then deleting all of them at once, removed
only the first object from the model. (Bug #14821928, Bug
#67214)
* When an output message in the Action Area panel consisted
of multiple lines, only the first line was visible. This
fix provides an information box that appears briefly when
a pointer device hovers over the truncated message. (Bug
#14802567, Bug #66988)
* The Workbench Scripting Shell window on hosts running the
GNOME Shell lacked the controls to resize or close the
window. (Bug #14768677, Bug #66810)
* The context menus associated with tables in the schema
tree did not function when the schema list was filtered.
(Bug #14690217, Bug #67001)
* The combination of Ubuntu with language-pack-tr and
LANG=tr_TR.UTF-8 produced an error message when columns
of type INT were parsed during operations that altered
existing tables. (Bug #13971992, Bug #63872)
* Chinese characters in the file path of an existing MySQL
model were misrepresented and rendered the file
inaccessible. (Bug #11757843, Bug #49950)
* EER diagrams with long names wrapped around to a second
line in the Model Overview area and were not fully
visible when the host was Microsoft Windows. This fix
inserts a vertical scroll bar into the Model Overview to
accommodate long names. (Bug #11749931, Bug #40103)
On Behalf of Oracle/MySQL Release Engineering Team,
Balasubramanian Kandasamy
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic