MySQL Forums
Forum List  »  MySQL Workbench

Collecting ideas for MySQL Workbench 6.x-7.x Roadmap - SQL IDE
Posted by: Michael G. Zinner
Date: March 19, 2008 06:34AM

Hi MySQL Tools Users,

I would like to start collecting ideas of what you would like to see in the MySQL Workbench 6.x-7.x Roadmap over the 2009-2010 timeframe.

In the short term (April-June 2009), MySQL Workbench 5.2 will deliver a completely next-generation (developed from scratch) Query Browser. Please think of it as an improved, extended MySQL Query Browser embedded right into the MySQL Workbench framework.

Screenshots for new Query Browser:

My vision is to turn MySQL Workbench into a complete SQL IDE including the next generation of SQLBrowser, SQLBuilder, SQLEditor, SQLRefactor. The single tool a MySQL database developer needs to start up to do all his database work.

A few key points that come to my mind.
* Database schema design, creation and maintenance (already there)
* Default data management ("CREATE INSERTS", already there, can be improved)
* Database SQL querying
* Result set handling (like in QB, but improved)
* Visual query builder (I liked the Oracle XE web-based query builder)
* Improved SQL code editing (syntax highlighting, auto completion, ...)
* Stored Procedures debugger
* Full scripting and plugin support
* Exchange with Netbeans IDE
* ...

Please add your own points here and also provide input how you would like to see the features implemented.

References to other tools, e.g. Oracle SQL Developer (project Raptor), MSSQL Query Analyzer, SQLyog, ... are welcome. Please point out what you like about their querying interface and how we could improve upon that.

I am looking forward to your input,

Edited 6 time(s). Last edit at 01/28/2009 11:44AM by Edwin DeSouza.

Options: ReplyQuote

Written By
Collecting ideas for MySQL Workbench 6.x-7.x Roadmap - SQL IDE
March 19, 2008 06:34AM
February 06, 2009 07:30AM
March 12, 2009 01:38AM

Sorry, you can't reply to this topic. It has been closed.

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.