What is the best version of MySQL to use with Rails 3 as of today (28/4/11)?
At the moment I got Mysql 5.5.11 community server and I have had lots of problems with it. I want to install an older version of MySQL. Which one would you recommend?
Thanks in advance.
PS: The issues were with the mysql2 gem.
I would say 5.1 only because of problems I had trying to compile the driver with MySQL 5.5 on mac (which is of course a show stopper).
And I had no issues at all with MySQL 5.1.
Even with the very public outage it recently suffered, we would recommend Amazon's RDS service. We find it has been very reliable and easy to administer.
Our RDS instance is currently running MySQL version 5.1.45.
Related
I need to upgrade/move a 5.7 version of mysql on ubuntu 18.04 so that it's still 5.7 but does not use the MariaDB engine. Everything I can find online talks about moving from Mysql to MariaDB, not the other way around. I'm not even sure there is a way to do this.
I'm stuck with having to install a webapp that uses MySQL but cannot use MariaDB. The creators of the app have assured the user community that it's "an easy upgrade" but then provide no details.
Any help is appreciated.
I am bit novice in some aspects here and no related information found...
I have an AWS instance with mysql client installed at 5.5 version. And also an RDS db instance with mysql 5.6 (in order to use t2.micro). I don't think so but, could this in your opinion/experience produce some kind of trouble when requesting queries (via PHP, specifically Symfony2) between them?
I hope it is no; but if yes, is strictly necessary then to upgrade my mysql client in the instance or there is any other way to use t2.micro with mysql server at 5.5?
Any guidance or related experience would be much appreciated.
See Upgrading from MySQL 5.5 to 5.6:
Note particularly any changes that are marked Known issue or
Incompatible change.
That said, your client app should be able to use 5.6 safely, and you got it right, that is required to use db.t2.micro instances.
I've scoured the MySql website to see if they have compatibility listings for MySQL Workbench, but have not found anything. Does anyone know if 6.0.x can connect to 5.5.x databases? I'd rather not install and then have to roll back.
MySQL Workbench can connect to most MySQL server versions, but that is probably not the primary question. You should rather ask what minimum version it can work with. MySQL Workbench requires at least MySQL 5.0 and can work with any MySQL server after that (including the new 5.7). Some features like authentication plugin or performance schema support require higher server versions, though.
the company i work for is considering for multiple reasons (some of them libked to the politics of open source and oracle) a switch from MySQL to Mariadb. Our development team has been using Zend Server (now it's 6th version) which always install mysql. Is it possible to switch from mySQl to Mariadb smoothly? are there any hurdles that we should be aware of ahead of time? The OS for every development computer is Ubuntu 13.04 at this point.
No, there should be no more issues than when upgrading to a new MySQL version.
See How can I upgrade from MySQL to MariaDB?
I'm running Ruby on Rails on a Solaris 10 server. I just reinstalled Ruby today to get things to work correctly with my MySQL system so I could add a new application I've been working on. I also updated my gems and the system. MySQL is the only thing in this system that hasn't been updated lately, that's at version 5.1.25.
When I run the Mongrel server the system will work okay for a couple loads, sometimes more. After reloading the index of one of my scaffolds a couple times, or adding a new item and loading its show page, the server reports a segmentation fault and exits. There is no debug output other than: "Segmentation Fault (core dumped)". All other output appears normal.
I've made a couple new applications on my server, and those show the same errors. Creating an application with the database disabled does not present this problem.
Any help or advice is greatly appreciated!
UPDATE: Unfortunately downgrading to MySQL 5.0.45 and reinstalling the mysql gem did not resolve the problem. If you have another suggestion, please let me know! You can see a complete list of the software installed and its versions here.
This is almost certainly a problem with the native C extensions of the mysql gem. There are a couple things I would try
Update your mysql-devel packages in your package manager and rebuild the mysql gem
Install a 5.0 version of mysql, and rebuild the mysql gem
Use the pure ruby mysql gem (http://www.tmtm.org/en/ruby/mysql/)
You might try installing the latest 5.0.x series version of MySQL, currently 5.0.83. I've never been able to get ActiveRecord to work with MySQL 5.1.x. I haven't gotten segfaults -- in my case it was different errors -- but I am using CentOS.
I think 5.0.x is the way to go.
if you check database.yml it's on the first line
MySQL. Versions 4.1 and 5.0 are recommended.
I ran into similar problems in XP with mysql 5.1
If all the other anwsers are not working, roll back to rails 2.1 that still has the mysql connector instead of the gem. I saw on some machines that the mysql gems was causing the software to crash or not work properly...