I’m happy to announce the release of MySQL Ruby bindings version 2.8.1
This release is based on my GitHub fork from original Kevin Williams work.
For those who are not aware, Kevin’s gem is a Gem package of tmtm mysql-ruby bindings at RubyForge
Changes
This started to improve GCC support, but it ended with a take over and better packing to improve both Windows support and Ruby 1.9 compatibility.
You can read more details of this release here
This release is a fat-binary release, meaning it will work with both Ruby 1.8 and 1.9.
Importance of MySQL version
As I stated over a previous tutorial the version of MySQL is important.
The binary version has been built against MySQL 5.0.83, which means will be compatible with 5.0 series, but not 5.1
Moving forward
This gem is a repackage of tmtm’s work, and improved testing functionality, packaging and build process. On this project, contrary to SQLite3/Ruby bindings, we are tied to tmtm’s version (link provided above).
Please report issues when installing from source, but most of the usage ones (related to new features and bug fixes) should be addressed to tmtm project at RubyForge.
Once tmtm releases new versions, I’m going to package those into an updated gem version for us to rejoice.
Installation
Since on previous tutorial I provided a mysql gem version 2.8.1.1
gem uninstall mysql --version 2.8.1.1
gem install mysql --source http://gems.rubyforge.org
To be able to install the RubyForge version, please uninstall the older first.
Apologizes for this, going to remove the RubyInstaller version soon.
That’s it, enjoy!, now I need to take a plane!
No Trackbacks
You can leave a trackback using this URL: http://blog.mmediasys.com/2009/08/21/mysqlruby-2-8-1-released/trackback/
4 Comments
Hi thanks for this.
is this encoding -aware with ruby 1.9.1 and will it support UTF8 ?
@adam:
You will need to check tmtm release notes for more details.
Hi Luis,
I installed mysql-2.8.1.1 few weeks ago following your tutorial (gem install mysql –source http://gems.rubyinstaller.org)
with mysql 5.1.37 server and I have no problem with it till now
@erwann: depends if you’re connecting to a local server or a remote.
Is so random that just to avoid weird reports, I prefer to state that incompatibility.
Thank you for your comment.