MySQL Workbench was developed to be the next-generation visual database design application that can be used to efficiently design, manage and document database scheme.
MySQL Workbench is a cross-platform, visual database design tool developed by MySQL. It is the highly anticipated successor application of the DBDesigner4 project.
Here are some key features of "MySQL Workbench":
· Syntax highlighting and code folding, supported is the full set of reserved words for MySQL.
· Single and Multi Statement Execution, including detailed execution log and query history. More than one connection at a time can be established and used.
· Embedded resultsets, with a splittable view to allow for optimal work area.
· Dynamic Error Parsing while typing, not only for correct identifier syntax but also full MySQL syntax.
· Convenience features, which simply make life easier. This includes quick zoom-in and -out for large text (use ⌘ + scroll wheel, ctrl + wheel for non-Mac platforms), loading and saving from/to files, collapsible editor parts (query and result set area).
Requirements:
· Net 2.0 framework
What's New in This Release: [ read full changelog ]
Functionality Added or Changed:
· The SQL editor tab now displays the selected database in the header. (Bug #50932, Bug #11758694)
· The File, Export, Forward Engineer SQL ... wizards now have the option to use the same configuration settings from the last time Forward Engineer SQL ... was used. (Bug #34977, Bug #11748058)
Bugs Fixed:
· Within the SQL Editor, MySQL Workbench would freeze after choosing Replace All when the find field was empty. (Bug #13744385)
· MySQL Workbench would generate invalid SQL while using the Partitioning tab when altering a table. (Bug #64396, Bug #13788180)
· The Data Export option would not use the current date in the folder name containing the exported data. (Bug #63893, Bug #13571760)
· Database, Synchronize Model would not update the view after a new field was added. (Bug #62569, Bug #13051152)
· On Microsoft Windows, the MySQL Workbench installer would sometimes not detect where VISUAL C++ 2010 was installed.
· A workaround is to append CPP_100_RUNTIMES...