I would like to know if somebody is using MySQL 5.1. I am considering using it but I am not sure. I don’t think that it hasn’t been tested in large scale production environments (Google is still on 5.0). Can anybody tell me about it? I am particular interested in the row-based replication feature that 5.1 offers
BTW, Google is probably not a good example.
BYW, I want to make a clarification: Google does not store its search index in MySQL. Google uses MySQL for his Ads Application (AdWords).
AdWords is Google’s lead advertising product and main source of revenue. The AdWords system runs on top of MySQL. Google, as I learned in MySQL World 2009, has no plans to migrate to MySQL 5.1 anytime soon. If it does, it is sufficient proof that MySQL 5.1 is a stable enough product.
In MySQL World I met Monty (the creator of MySQL). I asked him about Google position regarding 5.1. He just said that “if you are a new user trying out MySQL for the first time, you should use MySQL 5.1, so you learn all the new features.” This scares me a little bit. I just wasn’t expecting the caveat “if you are a new user” bit.
If you have used MySQL 5.1, what’s your experience with it?
I was setting up a server today and I tried using Servoy with MySQL 5.1 with no success. Lots of transaction errors when importing a solution, then shuts down the service. I’m now going back to 5.0
I was just about to install 5.1. I wasn’t really thinking about using it as the repository for Servoy’s solutions. I really appreciate your input in this regard. I’ll give it a try in one year or so.
jcarlos:
I was just about to install 5.1. I wasn’t really thinking about using it as the repository for Servoy’s solutions. I really appreciate your input in this regard. I’ll give it a try in one year or so.
We’ve been running 5.1 for some time now without Db created issues so far!
Servoy 4.1.2 was problematic with 5.1 as that version created varchar values in the repository which could not be managed (accepted) by MySQL5.1. That’s fixed in Servoy 4.1.3.
We are attempting to keep all Db activity within Servoy however - so we can be completely Db-agnostic for the future. Therefore we have not tried any row specific replication etc.
I was also using 4.1.3 with the latest Mysql 5.1 as of yesterday. Install went fine. Repository created fine. However when importing a solution, it completely bombed out. Then I deleted databases, rebuilt repository, and tried it 2 more times with the same result. After that I did the exact same thing with Mysql 5.0, and everything was fine.
Hi Scott,
You also used the lastest JDBC driver for MySQL ?
ROCLASI:
You also used the lastest JDBC driver for MySQL ?
… More specifically: did you use the connector-j (jdbc driver) for MySQL 5.1?
The 5.1 driver is different than the one for 5.0.
goldcougar:
I was also using 4.1.3 with the latest Mysql 5.1 as of yesterday. Install went fine. Repository created fine. However when importing a solution, it completely bombed out. Then I deleted databases, rebuilt repository, and tried it 2 more times with the same result. After that I did the exact same thing with Mysql 5.0, and everything was fine.
I’ve none of those problems Scott (fingers crossed now…)
jcarlos:
ROCLASI:
You also used the lastest JDBC driver for MySQL ?… More specifically: did you use the connector-j (jdbc driver) for MySQL 5.1?
The 5.1 driver is different than the one for 5.0.
Yes. of course mysql-connector-java-5.1.7-bin.jar
Also note my solution use i18n, if that made a difference.
Kahuna:
We’ve been running 5.1 for some time now without Db created issues so far! Servoy 4.1.2 was problematic with 5.1 as that version created varchar values in the repository which could not be managed (accepted) by MySQL5.1. That’s fixed in Servoy 4.1.3.
Thank you Ian, this is reassuring.
Kahuna:
We are attempting to keep all Db activity within Servoy however - so we can be completely Db-agnostic for the future. Therefore we have not tried any row specific replication etc.
You still can have your application (solution) completely Db-agnostic and still do replication. The replication feature in managed by the database server. The data can be replicated after transactions are committed (Asynchronous replication)
goldcougar:
Yes. of coursemysql-connector-java-5.1.7-bin.jar
Also note my solution use i18n, if that made a difference.
… It seems that you did all the right things, but still it didn’t work. It’s not good. As I said, I’ll wait little longer to install MySQL 5.1 in my production server. Thanks
We imported a large solution from 5.0x to 5.1x with no issues…except for a case where a query had:
... concat(id_task, ': ', task_name) as summary ...
which needed to be changed to:
... concat(cast(id_task as CHAR), ': ', task_name) as summary ...
Tracking that little bleep down wasn’t fun. At all.