Hello everybody,
I expirienced some unresolvable problems using mysql workbench.
I started using 5.2.35.1 on a Window 7 (32 Bit) machine. It worked okay but crashed really often. I could provoke a crash when editing a table in a diagram when another table (bottom of the screen) was already opened.
That problem wasn't so bad that I couldn't find a workaround. I just closed the bottom pane before opening another one.
Later I wanted to install the same version on another Windows 7 (32 Bit) machine. Mysql workbench was unusable there. All the time popups occured "an external component has thrown an exception" (translated from my german error message). I could hardly close the application because I had to press space repeatedly and then try to close the window.
I tried to install the same version under Ubuntu Linux Oneiric (11.10). The version I downloaded was made for 10.04..). The splash screen appeared and then nothing happend. That could be a problem of incompatibility.
On the windows maschine where 5.2.35.1 did not run I installed 5.2.37 (32 Bit) and encountered the same error message all the time.
For my suprise the 5.2.37 version now runs under linux so I was able to edit my database.
I made tiny changes an exported the sql again. I realized that some constraints (foreign keys) were not exported. I did not (and never..) check "Skipt in SQL generation" or something like that.
So i tried to create a new database model and imported the old sql script into that model. Everything worked fine an all constraints were there. When I exported the sql the same constraints were missing again..
I than changed to manually edit my files.
I was wondering about all these errors that I encountered. Am I doing something wrong or is mysql workbench a bit too untested before a release?
Does anybody know a solution for the constraint problems?
Thanks and regard
Frederik
I expirienced some unresolvable problems using mysql workbench.
I started using 5.2.35.1 on a Window 7 (32 Bit) machine. It worked okay but crashed really often. I could provoke a crash when editing a table in a diagram when another table (bottom of the screen) was already opened.
That problem wasn't so bad that I couldn't find a workaround. I just closed the bottom pane before opening another one.
Later I wanted to install the same version on another Windows 7 (32 Bit) machine. Mysql workbench was unusable there. All the time popups occured "an external component has thrown an exception" (translated from my german error message). I could hardly close the application because I had to press space repeatedly and then try to close the window.
I tried to install the same version under Ubuntu Linux Oneiric (11.10). The version I downloaded was made for 10.04..). The splash screen appeared and then nothing happend. That could be a problem of incompatibility.
On the windows maschine where 5.2.35.1 did not run I installed 5.2.37 (32 Bit) and encountered the same error message all the time.
For my suprise the 5.2.37 version now runs under linux so I was able to edit my database.
I made tiny changes an exported the sql again. I realized that some constraints (foreign keys) were not exported. I did not (and never..) check "Skipt in SQL generation" or something like that.
So i tried to create a new database model and imported the old sql script into that model. Everything worked fine an all constraints were there. When I exported the sql the same constraints were missing again..
I than changed to manually edit my files.
I was wondering about all these errors that I encountered. Am I doing something wrong or is mysql workbench a bit too untested before a release?
Does anybody know a solution for the constraint problems?
Thanks and regard
Frederik
