HeidiSQL 4.0 RC1 released
I am not sure how many MySQL developers are using HeidiSQL for development but I am sure those who are using it will be fan of some of it's features.!
I have been using HeidiSQL tool for my php/mySQL development for a while now. (more than a year and half..!). Before few months I have upgraded to newer version of HeidiSQL which is 4.1 RC1. It has got quite new and exciting features, looks and skins are improved.
The Good has got better...
1. Better UI:
As we can see in the image below that HeidiSQL 4.0 is packed with new icon set. Size of each database and tables are being displayed just next to object name in the left panel.
Also shows up database objects size next to objects (tables, databases).
2. Type In Search for Variables, Status and Process List:
We can search through system variable from the list on the fly and at the same time by just double clicking on it.
3. Improved Filter and Filter Editor:
As we can see data filter has improved and we can see and edit that filter to anything manually. In previous versions it was just filtering data on all table columns and we didn't have any control on modifying those filter but now we can filter data on completely custom conditions. We just need to specify conditions we use after <WHERE> clause.
We can save applied filter by saving that "Perspective" and specifying appropriate name for it, so that we can revert back to that view of data anytime in future.
4. Better User Management control:
User authentication and privilage control has improved and we can provide rights very easily till column level for any the object of any database.
We can pick what rights a User can have and at the same time multi-table / column rights on multiple db and all that with variety of rights on each table or it's column.
5. Export Data:
Export with different type of Compatibility options.
What is bad/missing?
While dealing with database with hundreds of tables and size reaching few hundred megabytes it seems to be slower than commercial competitor like Navicat. Although Navicat seems to be falling behind in user interface but works faster than HeidiSQL. Not sure what is keeping Heidi behind in this matter.
Export and Import needs to be improved while dealing with bulk of data. As many a times extended SQL export creates problem while importing. MySQL Dump work faster comparatively;
3. Support for Stored Procedures / Triggers / Functions:
Looking desperately to get support for Stored Procedures, Triggers, Functions. Although Toad for MySQL is there but it seems bit more heavy and HeidiSQL is so lightweight to play with.
4. Inline data editing while Querying data:
In 3.x versions of HeidiSQL it was possible to edit data from query result-set itself but now you have to go and filter data from filter tab itself. Even in Data tab now it asks for confirmation although it is to make sure users don't mess up data accidentally but it just takes some more time to edit. Anyway I don't complaint much about this data editing in Data tab/view for tables but I am going to miss this feature in Query tab as I can't edit my data resultset grid.
Looking forward to see better HeidiSQL with Final Release of 4.0 as it seems to be they are working hard to get it right. As we can see nightly build for every day on the download section but RC1 has been out for sometime now.