The Lua plugin support has been finally fixed and will be working in the next release. Together with a few other improvements, it’s now possible to write your own commands to do all kinds of tasks. Documentation for the plugin system is not yet written (and the previous one is outdated), but it should be straightforward to copy the supplied Lua plugin and change it to do something else. All you need is to know a little Lua (which is a simple scripting language) and explore Workbench internals using the GRT Shell (View -> Advanced -> GRT Shell).The sample Lua plugin is located in the modules folder. You can copy it to the custom plugins folder which is shown in the GRT Shell at startup and change things like the module name and add your own functions. I’ll write more about how to write such functions in a future post, like after the next WB is actually released.There are a few ways that plugins can be accessed, including just calling them from the GRT Shell, from the main menus (which you can change in the main_menu.xml file or in a menu editor when its written) or from context menus for the objects that the plugin supports. In fact, most functionality of Workbench works the same way as plugins, so there’s a lot that can be done.
The team was on vacation during the holidays (a well deserved one I hope) and today is the first day the full team is back. Our plan is to keep our main focus on bug fixes and also start working on the plugin-writing/scripting tutorials. We also have to add more hooks at various places in the tool so people interested can add their stuff wherever it needs to be added.
Starting on the 14th of January we will travel to the MySQL company meeting and we will try hard to get a new release out before that – including as many bugfixes as possible.
We just unleashed version 5.0.11 Beta of MySQL Workbench. We fixed the nasty bug, that prevented us from releasing .11 earlier. To find out what’s new take a look at this page (You can trace all changes in detail here).
Although the filenames say 5.0.11a (notice the trailing ‘a’), what’s actually inside the packages is our official 5.0.11 beta release. That’s because we had already uploaded the files to our mirrors when we found that index-related bug on monday – so the fastest way for this release was, to add the suffix.
Please fetch the new release right away and keep up your good work with testing and reporting bugs.
Apart from more than 60 bug fixes the upcoming MySQL Workbench 5.0.11 release will contain a few major improvements in respect to the last release two weeks ago.
- The partitioning settings are now fully supported during reverse engineering of SQL scripts and live database and CREATE / ALTER generation for synchronizations. We had a preliminary implementation but this has been replaced by full parser support.
- Addition of Standard Insert grid input. Instead of having to type in the full INSERT statements the initial/test data can now be entered by using a data grid.
- Improved formatting of generated SQL output.
- Improved GRT Shell console. This is in preparation of the upcoming tutorials on the scripting- and plugin writing possibilities
The show-stopper bug that is holding back the release is now fixed. We will run detailed tests tomorrow and if nothing else comes up will upload to the mirrors then. Standard Edition Beta Testers will get an email notifying them about the new download addresses.
I prepared the release builds for 5.0.11 yesterday evening and they have been uploaded to the mirrors. All automated tests passed without error and my initial manual tests showed everything working. Nevertheless Tax found a show-stopper bug later today following our manual testing procedures.
The problem is located in the SQL generation code for tables. We introduced a new internal index type for foreign key index columns that is maintained automatically by the tool. This new type caused the generated SQL to be corrupt. We tried a simply fix today but were not able to fully solve it. We will take time tomorrow to properly fix the issue and I will trigger new build after that. Then it will take about 20h till the mirrors have catched up and we can announce the new release.
Sorry for the delay.
For all new contributors devoted to quality, FAQ was slightly updated with new section.
We are working hard on the next release of MySQL Workbench and are trying to follow our plan of getting a release out every second week. A lot of things have already been addressed, some new things came up. But we are clearly moving into the right direction and our investments in unit tests and UI tests seems to pay off as expected. More details in a post later this week.
I just sent out the mail to the mailing lists to officially announce the 5.0.10 release. I have added an additional page that will keep track of the changes we make and it is available here. The change log file is included in the source package as well of course.
I am curious how the level of regression bugs will be. For Workbench we have a unit testing framework in place as well as an ever expanding suite of UI tests. We are using TestComplete and as long as the tool does not crash itself (which happens quite a lot, sadly) it is quite useful to automated the UI testing.
Please keep testing and reporting bugs. We will keep working hard to fix reported issues as fast as possible.
We are just in the process of running the final 5.0.10 builds. If Johannes does not discover any last-minute major bug we are going to upload to the mirrors soon and the release will be available tomorrow. The complete build and packaging process is now fully scripted.
The community did an amazing job in reporting bugs – there were a lot of issues that slipped through the first release. And so did the team. 75 bugs were closed since the 5.0.9 release in just 9 days. If we can keep that pace we will reach RC even sooner than I expected.
A lot of P1 and P2 bugs have been closed, we still have a load of P3 + P4 to go and I hope the stream of bugs keeps getting in, so we discover all issues soon. My biggest concern is about some threading issues we seem to have in the core which causes “random” crashes. We will run stress tests to trace those down during the next weeks.
Ok, builds have finished, now the last QA test are taking place.
As most of you probably know now, Workbench supports two visualization modes: hardware & software based. Unfortunately automatic switcher was not in place by the time when beta version came out (will be fixed in a week), so some of you, who don’t have video subsystem supporting OpenGL v1.5, will encounter error on start when trying to run hardware based configuration. Note v1.5 is a minimum required version of OpenGL needed to start Workbench. You can get detailed information about your video subsystem using one of these tools: OpenGL-Extension-Viewer or GPU-Caps-Viewer