As it seems no one has managed to compile the latest version of mysql-ruby to work on windows (at least no one is sharing libraries that I could find), and I couldn’t stand it not working (Mostly the latter). I decided to give it a try.
I finally got the bitch working on WinXP (I think..). I compiled against both mysql server version 4.1.15 and 5.0.15. (I currently only use (and briefly tested) the former, as the latter gives problems with older aps)
Anyway, the result is at http://jeroen.concept-q.biz/files/
I’d appreciate feedback if it works for you too, as I’m sure others would like to know whether or not these libraries are useful to them (I haven’t done extensive testing so I cannot claim it works). If it doesn’t work I’m sorry to say my C knowledge has already been stretched to its limits and I’m rather clueless on how to solve any problems.
Apparently a real programmer (at-least more real than me) took over the job of providing ruby with a decent mysql-ruby win32 dll. As I’m not planning to update my stuff I’ve updated this first post and will now link to (hopefully) actively maintained solutions: http://www.vandomburg.net/pages/mysql-ruby-windows. You could also take a look at http://rubyforge.org/projects/mysql-win
This is the answer to the Hellish lost connection with mysql and ruby problem. As far as I can tell it’s a problem with Instant Rails using ruby-mysql-2.6 instead of 2.7.
Jeroen’s mysql.so file works but his version of msvcr70.dll is dodgey. But you can download that off t’internet for nothing, just google for it.
At last a stable Rails development environment on Windows XP and 2000.
The 5.0.15 driver seems to be working perfectly.
You can Turn this behaviour off.
This distribution doesn’t require an external msvcr.dll and will be actively maintained.
This is another solution
I found a completely different solution at HowTosWorkerThreads
Yet another solution
http://rubyforge.org/projects/mysql-win
Despairing on 2000 I have RoR working with MySQL absolutely fine on my XP laptop at home, but I’ve spent half a day today trying to get a stable configuration on the 2000 desktop I have at work with no success. I’ve tried all the mysql.so variants (I’ve even tried deleting the file altogether) above as well as the libmysql.dll from 4.1 and 5.0 installs of MySQL. Each one allows one or two data-driven pages to be viewed before the http server segfaults. That goes for WEBrick and Mongrel.
Having to restart the server after every other page view is not agile.
I was getting the segfaults. To fix, I had to reinstall DBI and MySql gem. Details: I removed all mysql gems. This included looking into the gem directory where I found an old version of mysql lerking. Then I removed DBI and DBD from ruby’s lib\ruby\site_ruby\1.8. After that, I got the latest DBI from http://ruby-dbi.rubyforge.org/ and followed the instructions to install it. I only included setting up the dbd_odbc and dbd_msyl. (I use odbc for sql server connections). After that I installed the latest mysql gem. Now it runs without segfaults. I think there was something wrong with the version of DBI that shipped with the windows one-click installer.