MySQL Workbench 5.1 OSS Goes Beta

We are proud to announce the release of the first official Beta of MySQL Workbench 5.1, the next highly anticipated version of our database GUI tool – MySQL Workbench. For the first time we are making an announcement for all our major platforms at the same time: OSX, Linux and Windows.

MySQL Workbench 5.1 has some major improvement over our current 5.0 release, many of them might not be that visible when looking at the UI only. We did a major overhaul under the hood in addition to enhance usability and adding some features. On top of it, we moved some features to 5.1 OSS, that were only available in SE edition for 5.0 (like different notation styles i.e.). The editors have been tuned to startup more quickly, and some of them also got face lifted. All Wizards have been revamped using our new mForms library.

Please keep in mind that this is the first beta release of MySQL Workbench 5.1, and it’s not supposed to be used on production level files! There is still work to do to get it to GA production quality, but we’re working hard on that to deliver the next, improved beta versions in a short release cycle. So please fetch the shiny new files right from our Download Mirrors and give us a heads up on any issues you might find on your platform, what you like, and what can be improved. Have fun!

22 thoughts on “MySQL Workbench 5.1 OSS Goes Beta”

  1. remi: thanks for the extra packages.

    As for the bug, that’s very strange, none of us has ever saw that. Will try testing in Fedora with your binaries.

  2. Hi, just to let you know this is barely runnable in windows 7 x64, gets stuck for almost every action (opening a file, placing relationships, importing from a sql file, etc.) Using the no-installer version; I have the 5.0.30 no-installer version running smoothly.

  3. Thanks for the update.

    I have over 8 years of active DB Designer diagrams that I would like to migrate to my MAC OSX version of Workbench and it would be nice to have the import DB Designer 4 model option enabled.

  4. jgarifuna: Hi
    It seems we overlooked a packaging problem with the Mac beta. You can enable DBD4 import by running a couple of commands from the Terminal shell:

    cd /Applications/MySQLWorkbench.app/Contents/PlugIns
    ln -s modules/* .

    Assuming WB is in /Applications.

  5. Using Fedora rawhide:

    In file included from mdc_algorithms.h:5,
    from mdc_algorithms.cpp:2:
    mdc_common.h: In member function ‘std::string mdc::Size::str() const’:
    mdc_common.h:61: error: ‘snprintf’ was not declared in this scope
    mdc_common.h: In member function ‘std::string mdc::Point::str() const’:
    mdc_common.h:81: error: ‘snprintf’ was not declared in this scope
    In file included from mdc_algorithms.h:5,
    from mdc_algorithms.cpp:2:
    mdc_common.h: In member function ‘std::string mdc::Rect::str() const’:
    mdc_common.h:120: error: ‘snprintf’ was not declared in this scope
    make[4]: *** [mdc_algorithms.lo] Error 1
    make[4]: Leaving directory `/home/greg/Download/mysql-workbench-oss-5.1.9/library/canvas/src’
    make[3]: *** [all-recursive] Error 1
    make[3]: Leaving directory `/home/greg/Download/mysql-workbench-oss-5.1.9/library/canvas’
    make[2]: *** [all-recursive] Error 1
    make[2]: Leaving directory `/home/greg/Download/mysql-workbench-oss-5.1.9/library’
    make[1]: *** [all-recursive] Error 1
    make[1]: Leaving directory `/home/greg/Download/mysql-workbench-oss-5.1.9′
    make: *** [all] Error 2

  6. People with trouble with model layout:

    It seems the bug is that floating pointer number parsing is depending on locale, so 1.345+E03 is being parsed as 1,345 which gets rounded to 1. The model is then interpreted as having size 1×1 when loaded.

    If you start with with the LC_NUMERIC environment variable set to C or with an english locale, it should work fine. However, if you saved the model after reloading the model into a broken state, the file will be saved with size 1×1. So, if you find this problem DO NOT SAVE back.
    If you already did, please comment here and I can try making some Python script to restore the file, although if the model was saved with broken layout, it cannot be restored back automatically.

  7. On the Mac version , table editor won’t start, is that yet not included in the beta version or there is a way I could make it work ?

    It’s kind of an hassle switching to XP on VMWare Fusion just to use this great piece of software, and I just can’t wait for a fully working versione of the application.

    Thanks for making this port!

  8. Same problems on MAC OSX as the alpha version…
    This is what i get when i click each menu:

    “An unhandled exception has occurred. The stack trace is being written to the log”
    “AXSubrole” attribute unsupported by:

    I have Leopard 10.5.6…

    anybody has the solution?

    thank you!

  9. kgaramszegi:

    Thanks to my friend http://www.ExtremeAmbient.net the problem with the lose of diagram layout in Ubuntu can be solved easily.

    Edit /usr/bin/mysql-workbench and force to use English as locales for this application.

    After basedirname=$(cd “$bindirname/..”;pwd)

    Add this two lines:

    defaultLANG=$LANG
    export LANG=”en_GB.UTF-8″

    And at the last line add

    export LANG=$defaultLANG

    So in case you run mysqlworkbench via command the original language would be set at the end of the execution.

  10. jakecool, do you have any software enabled that might interact with other applications? Or maybe some accessibility related option turned on in OSX?

  11. akojima I’m also having problems editing tables on a Mac the errors I get are:

    3/30/09 10:56:55 PM MySQLWorkbench[430] opening plugin /Applications/MySQLWorkbench.app/Contents/PlugIns/db.mysql.editors.mwbplugin [DbMysqlTableEditor initWithModule:GRTManager:arguments:…]

    3/30/09 10:56:55 PM MySQLWorkbench[430] plugin class DbMysqlTableEditor was not found in bundle /Applications/MySQLWorkbench.app/Contents/PlugIns/db.mysql.editors.mwbplugin/Contents/Frameworks/db.mysql.editors.wbp.dylib

  12. phoose: that can be worked around by opening the model from the Recent Files menu

    patrik: tables with too many columns are truncated to keep the diagram layout sane. You can change the number of columns shown in Preferences, tho

Leave a Reply