I tried to use MySQL as the repository server for Servoy, instead of Firebird, but I can’t seem to get it working. I did the following:
Install Servoy R2, but without the FireBird database.
I’ve created a new database in MySQL
Created a new user in MySQL that has access to that database.
Started Servoy Developer
Under the Edit Menu, I went to the preferences.
I’ve selected the DB servers tab
Clicked on the Auto Setup Server option
Filled in the neccesary details
Clicked on OK
So far, so good, but there I got the message that the repository can only be created with on a transactional database system. The manual however states that MySQL can be used as the repository server.
I’m running the latest version of Servoy R2 on Windows 2000 SP2. The version of MySQL I’m running is version 4.0.14.
But i never had a repository on mysql (only data databases), so i tested it and there was another error because we tried to create varchar column above the size of 255. I corrected this now but you need a new build (after RC5)
Just tested this, and I got it working fine. A few gotchas though before I got it working:
Download the latest JDBC driver from the MySQL website, and put the jar file in the Servoy drivers directory. Why are you including the older version of the driver by the way?
If you want to use the server, and you just created the repository, make sure you close the Servoy Developer program otherwise, the properties file in the user home directory is not updated with the right information. It surprises me a bit that this is not done when the preferences dialog box is closed.
If you use MySQL as the repository server, you will not be able to import the example solutions. I get SQL errors all the time, but unfortunately, I couldn’t figure out why exactly.
For the rest, it works just fine, and really fast actually with MySQL as the repository server.
We can’t ship the newer driver of mysql because the 3.x driver is GPL and GPL can’t be distributed with non OS programs (it is very unclear what you can or can’t do so we are playing it save with the 2.0 drivers)
The problem with the sample solution is that those solutions had types that are not really compartible with mysql (like a varchar columns > 255) We will try to fix this with comming releases.. (map it to other types ect)