Once upon a time, there was a policy in MySQL not to add new features after the beta stage.
To my surprise, MySQL Workbench 5.2.30 introduces a new feature, the query formatter. I gave it a try. The results are not extremely encouraging. Granted, it's a plugin and not a feature in the core application, but nonetheless one would expect something more stable in a GA release, especially since the plugin features are displayed in the main menu, and unless you have read the announcement, you couldn't easily tell the core from the plugins.
This is what I have got in just a few minutes:

Bug #58356: beautify function fails on CREATE TABLE
Bug #58357: beutify function erases statement on CREATE …

If you want to clear local session status variables this is easy, simply execute FLUSH STATUS.  Unfortunately doing the same for global status variables is not as easy.

That is until now.  In the Drizzle7 beta release 2010-11-08 is a new command: FLUSH GLOBAL STATUS

I created this command to fulfil a Rackspace feature request but it appears this has also been a MySQL feature request in the past.  The implementation would be very different in MySQL since the status variables and sessions work differently, but it would certainly be good to see in a future release, and it appears patches already exist for it.

…

This is a new release of HeidiSQL, the result of 331 changes done after the previous 5.1 release. HeidiSQL 6.0 introduces many new features of which I'll list the most important ones here:
- Tabs for multiple batch results or multiple procedure results in a query tab.
- Multiple connections in one application instance
- Editable query results
- Rewritten user manager, using GRANT and REVOKE syntax now
- Rewritten "Copy table" dialog and logic, supporting WHERE filters now
- Rewritten "Load text file" dialog and logic, supports client side parsing for situations where LOAD DATA is not allowed
- Rewritten SQL help dialog
- Query profiling in query tabs
- Introduce "Run current query" action (Shift+Ctrl+F9)
- Enhance detection of Unicode text files
- Server details hint when mouse over version status panel
- Internal image previewer for BLOBs
- LaTeX and Wiki markup …

We’re proud to announce the next release of MySQL Workbench, version 5.2.30. This is a maintenance release focusing on general product improvement and usability. In addition to that, we have added a small set of Text-Formatting-Plugins to the SQL Editor to help format/structure your SQL Queries.

As always, we want to thank everyone for the great feedback we have received. This helps us to continuously improve the functionality and stability of MySQL Workbench – we appreciate all your ideas for improving MySQL Workbench.  Please keep sending us your ideas!

About the Query-Formatter

In the Edit->Format menu of Workbench’s SQL Editor you will see a set of functions that assist in reformatting your SQL Queries, for example “Beautify Query”, “UPCASE Keywords”, etc.

MySQL Workbench 5.2 GA

• Data Modeling
• Query (replaces the old MySQL Query Browser)
…

While I was optimizing an old mysql table copy script, I found the PIPESTATUS Shell Variables in the bash manual.
PIPESTATUS is an array with the status / exit codes of the last pipelined commands. ( A pipeline is a sequence of one or more commands separated by the character | (pipe).)

The following example script uses PIPESTATUS to check the exit code of mysqldump and mysql. If one of these commands fails, the script will exit and print an error message.

#!/bin/sh

dbname="testdb"
tables="table1 table2 table3"

for table in $tables
do
       mysqldump $dbname $table | mysql -h $dest_servername $dbname
       for a in  "${PIPESTATUS[@]}"
       do
                  if [ $a -gt 0 ]; then
                                echo -e "n\tError: mysqldump or mysql returned $a\n"
                                exit 1
                 fi
       done
done

Related Posts:

• …

As some of you already know, I too have recently left the MySQL Support Team at Oracle.

However, I am happy to report that I have joined SkySQL!

So I’ll remain in the MySQL Community, and will still be providing support for MySQL.

I am grateful to everyone I’ve worked with and to everyone who has had a hand in improving MySQL (no matter how small or large) over the years! It’s been a blast working with such dedicated and passionate people, and I look forward to many more years of the same now at SkySQL!

I have decided to “officially” retire Hack MySQL, which is to say that the web site (pages, tools, etc.) will no longer be maintained. The MySQL universe has changed significantly since 2004 when I began writing tools. Similarly, my professional and personal lives have changed, too. I don’t think Hack MySQL is needed or relevant any longer, and I certainly do not have the time to maintain it.

The web site will remain online for perhaps another year (since Media Temple has always provided free hosting for this site–thanks!), then I will remove it or archive it somewhere else.

For further MySQL resources, see Planet MySQL. That aggregate is, imho, the pulse of the MySQL community.

I know some people have used mymonitor on and off over the years, but it was a long ago since I created it, and things has moved on and changed. Among the things that didn't work well was the build process, and the fact that there were a few bugs in the normalization of SQL statements. Now this is fixed.

If you have NOT used MyMonitor, it is a small ncurses based tool for monitoring SQL statements in your server, and work by polling the PROCESSLIST and the normalizing and sorting and grouping the result. What is "normalizing" then? It's the term I use to describe the process where a statement has all the literals replaced with ? in them, so I can see that:
SELECT * FROM mytable WHERE id = 861
is actually the same statement as
SELECT * FROM mytable WHERE id = 387
And by the way, this is also the same statement as
SELECT * FROM mytable WHERE id = 177

MyMonitor can look like this in …

The highlights of this release are:

* A brand new helper function interface: We have implemented an easy-form based interface for customizing helper functions. Any customization of helper functions or user defined functions being used with earlier versions have to be migrated manually to this version. From this version and onwards a GUI-’conflict resolver’ will guide the users very similar to how it works for customized counters.

* Apply settings to all servers of a specific tag: MONyog now has an option to apply a group of settings to all the servers with a specific tag. (Please note: New servers registered later with the same tag are not considered)

* Enhanced readability of MONyog logs: MONyog logs from now on contain the server name along with error making it easy to backtrack.

* Earlier multiple alerts for same issue would be sent …