In MySQL 5.7, the Optimizer Team has been doing great work in
refactoring as well as innovation with the new Cost Model. The
improved Visual Explain enables the DBA to now get deeper
insights into Optimizer decision making, for improved performance
tuning of queries. The UI was also improved to allow easier
navigation in large query plans.

Streamlined Query Results Panel

The query results panel was updated to centralize the many
features related to result sets into a single location. Result
Grid, Form …

MySQL 5.7 will include much awaited GIS support for InnoDB
tables. To make it easier to
quickly visualize spatial/geometry data in geographic
context, Workbench 6.2 includes a viewer for
resultsets containing that type of data. The viewer will render
data from each row as a separate clickable element. When clicked,
you can view the rest of the data from that row in the
textbox. If you have multiple queries with geometry data,
you can overlay them in the same map.

MySQL Workbench has an option to view MySQL server variables
divided into groups [img. 1], for example: Binlog, General,
Keycache, Performance, etc. This is okay if we just wanted to
look around, but it can become overwhelming as sometimes we only
want to monitor specific variables from different groups.

img.1. Server Variables main view

In MySQL Workbench 6.1, we solve this by implementing Custom
Groups. It’s a special group that can be created by the user. At
the end of the Category List, there is already one …

The SQL Editor in MySQL Workbench 6.1 adds a new interface for
query results. This addition offers 4 new views to your
query results, 2 for the result data itself and 2 for
meta-information about the query that was executed.

Query Result Set Grid

The traditional result set grid. Run a SELECT query on a table
with a primary key and you can edit the data. You must click the
Edit button to enter edit mode.

Note: Until Workbench 6.1.1, the check was being done
automatically for every SELECT query, but …

MySQL Workbench have one nice feature which is probably a
stranger for some of us. The name of this feature is vertical
query output, it help in situations where the standard Workbench
output will not be very useful. This functionality is very
easy to use and in this post I’ll try to visualize some of it’s
benefits.

First we need to know how to use it, so we’ve provided you two
options to execute the query with vertical output. One of them is
the menu bar where you can find item named Execute
vertically, you’ll also find hint about the shortcut for
that option it’s CTRL+ALT+RETURN.

Do you know this scenario: you are writing down a stored
procedure but you can’t for the life of you remember the exact
syntax of that CASE statement? Has it to end
with CASE or not? Can I use more than one
WHEN part and how should that be written?
Usually you end up opening a web page and read through the
excellent MySQL online docs. However, this might cost too much
time if you quickly need different statements and other detail
info. Here’s where MySQL Workbench’s context help jumps in.

One of the new features of MySQL Workbench 6.0 is Table Data
Search. The main purpose of this was to ease data searching
through the whole instance. Previously, we needed to use some
tricks to get the query to run over all schemas that we’ve got on
the server. Now it’s easy to find the searched term with
much less hassle. This functionality is easy to use and
provides searching through all columns and even all types.
However, we …

With the first beta of MySQL Workbench 6.0 just released, we’ll
go through the list of improvements we’ve made since 5.2.47

New Home Screen

The Home screen went through a renovation and now has a
modernized look. As part of the SQL Editor and Administration GUI
unification, there’s now a single list for MySQL connections.
Recently opened model files and other major features are also
accessible from it.

You can organize different connections into “folders” by right
clicking on a connection and selecting “Move to Group…” in the
context menu.

MySQL Workbench 5.2.36 is now out and brings a lot of
improvements across the board, with special focus on the Query
Editor. We’ll cover some of that here:

Redesigned Query Editor

The log of executed commands and server responses is now
always visible while resultset grids and the query editor can
be resized according to your needs. Resultsets are also
grouped in the same tab as the query editor that generated
them.

SELECT queries are now analyzed as in the old MySQL Query
Browser tool and, if possible, its resultset can be edited in
the grid. If the resultset cannot be edited, you can place
the mouse …

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.