Users of the latest builds now have a GUI way to display a detailed query profile for the executed SQL in a query tab. Just check the Query profile tree node in the newly introduced "helpers" tree and run some query.



This is basically what SHOW PROFILE in MySQL 5.0.37 and later releases does. HeidiSQL just adds colored bars and a conveniant checkbox to accomplish that.

You may also have noticed that the tree replaces a tabbed list box, which was not able to hold a 5th tab for the profile stuff without overcrowding the GUI. Converting this to a tree makes the helpers more user friendly and look more like a standard GUI for developers.

Looks like Oracle is continuing to invest heavily in MySQL and the storage engine eco-system.  They've announced a full MySQL Sunday at the upcoming Oracle Open World Sunday September 19, in San Francisco.  Registration is only $75 which is a bargoon.  I expect this will be bigger than any MySQL conference held to date.  And there's also the JavaOne developer conference and the rest of the Oracle Open World show.

Ok, technically things actually start at noon, but knowing the MySQL crowd, I am sure there will be parties that go well past midnight.  Helan gar!

• Oracle Open World: …

This is for users who don't like HeidiSQL to store usernames and passwords somewhere:

Activating this new checkbox will ask you for username and password on demand, each time you connect to this session. Both previously stored username and password are taken as the default credentials when prompting.

Dear MySQL Users,

We’re pleased to announce the release of MySQL Workbench 5.2.25  This release is GA (Generally Available). We hope you will make MySQL Workbench your preferred tool for Design, Development, and Administration of your MySQL database applications.

Special thanks go to all the great MySQL Beta Testers that provided valuable ideas, insights, and bug reports to the Workbench Team. Your beta feedback truly helped us improve the product.

MySQL Workbench 5.2 GA provides:
• Data Modeling
• Query (replaces the old MySQL Query Browser)
• Administration (replaces the old MySQL Administrator)

Please get your copy from our Download site. Sources and binary packages are available for several platforms, including Windows, Mac OS X and Linux.

To get started quickly, please take a look at …

Dear MySQL Users,

We’re happy to announce the 3rd Release Candidate (RC) of MySQL Workbench.
Version 5.2.24 includes fixes for more than 70 issues.

MySQL Workbench 5.2 RC provides:

• Data Modeling
• Query (replaces the old MySQL Query Browser)
• Administration (replaces the old MySQL Administrator)
if you are a current user of MySQL Query Browser or MySQL Administrator, we look forward to your feedback on all the new capabilities we are delivering in a single unified MySQL Workbench
As always, you will find binaries for the various platforms on our download pages.

Please get your copy from our Download

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

To get started quickly, please take a look at this short tutorial.

MySQL Workbench 5.2 RC Tutorial

…

Users of the latest HeidiSQL build file will find a new option when rightclicking a data grid: "Copy selected rows as LaTeX table". Same applies to the "Export grid data ..." which is capable of storing rows in LaTeX format to a file.

Thanks to brampton for the patch!

Now there are 5 different text formats supported in grid exports: CSV, HTML, XML, SQL and LaTeX. Probably you know some more reasonable file formats to support?

From time to time dialogs need some usability refactoring. So happened with the good old Copy table dialog in HeidiSQL. New features:
- Select specific indexes or foreign keys to be created in the new table
- An editor for a WHERE clause, for cases in which you only need a subset of the original row data in the target table
- A menu for recently used WHERE clauses, so you don't need to keep them all in mind
- Prompts for overwriting if the new table exists



Thanks to Daniel for ideas and feature request number 2,000.

Users of HeidiSQL 3.x may have missed this feature since grid and BLOB editing was rewritten for v4: A preview area for images. Now it's even more powerful than before: it detects and loads various kinds of images (JPG, PNG, GIF, BMP, PSD, TIF and more). Also, the new preview area does not take valuable space when you're in some grid, as it's placed below the database tree:

After having updated to the latest build via Help > "Check for updates" you will be able to see more than only the result of the last SELECT query in any "Query" tab. By default, HeidiSQL displays up to 10 result sets in subtabs. In case you want more just go to

Tools > Preferences > Data

and increase this value in Maximum number of query results. Different than before, these are the first result sets from your SQL code.



Please note that HeidiSQL still does not separate multiple results from a stored procedure. Will be the next thing to implement soon.

Also a minor new feature is the hint on the lower statusbar when hovering over the MySQL version. You will see various connection, server and client related details here.

In the last few months we’ve got couple of bugs with the PBXT read/write locking code. One of the problems was directly in the lock/grant algorithm. It was strange to find such kind of error after quite long time of various testing and real-life usage. From the point of view of QA it was clear that manual code review was not efficient in this case.

Given all this I decided to try formal verification of the code. The specifics of the PBXT locking code is that it’s relatively small (about 100 LOC) but quite complex. The algorithm itself is not that trivial but the major source of complexity is concurrent execution of its parts. So if I had to manually create a finite state table for it then it would be essentially a cartesian product of states of all concurrent threads. In numbers that is if there is about 20-30 states per thread and there are 3 threads (empirically I estimated that threads beyond 3 don’t add more states) then I would …