I found mysql2 gem. It works fine with ruby 1.9 and utf8 encoding (as opposed to mysql gem).
But I have doubts. Does somebody use this gem in production? What about the performance test? Is it faster than mysql gem? Is it stable?
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
mysql2is meant as a more modern replacement for the existingmysqlgem, which has been stale for a while now. I also heard that the author isn’t supporting it anymore and instead recommends everyone use his pure-ruby version since it’s compatible with more Ruby implementations (but is much slower).The first issue with the
mysqlgem is it doesn’t do any type casting in C, it gives you back ruby strings which you then have to convert into proper ruby types. Doing that in pure-ruby is extremely slow, and creates objects on the heap that never needed to existing in the first place. And as we all know, Ruby’s GC is it’s primary reason for it’s slowness. So it’s best to avoid it and do as much in pure C as you can.Second is that it blocks the entire ruby VM while connecting, sending queries and waiting for responses, and even closing the connection.
mysqlplusdefinitely helps with this issue, but only for sending queries as far as I know.mysql2aims to solve these problems while keeping the API extremely simple.Eric Wong(author of Unicorn) has contributed some awesome patches that make nearly everything non-blocking and/or release the GVL in Ruby. TheMysql2::Resultclass implements Enumerable so if you know how to use an Array, you know how to use it.I’m only aware of a few people using it in production right now but it is being evaluated at Twitter, WorkingPoint and UserVoice too.
I’m also in talks with
Yehudaabout it being the recommended/default for Rails 3 when it ships. Some of its techniques and optimizations are also going to be brought into DataObjects’do_mysqldriver soon as well.The ActiveRecord driver should be pretty solid at the moment. All you should need to do is have the gem installed, and change your adapter name in database.yml to
mysql2.If you’re interested in using it, give it a try. I’m quick to push fixes if you find any issues 😉