I hacked our vendor tree to explode on startup if the mysql gem could
not be found. IMHO this should be the default behavior, the built in
mysql adapter is crap and its silent use is a ticking time bomb
Cheers
Dave
On 27/02/2008, at 6:42 PM, [EMAIL PROTECTED] wrote:
Thank you for the replies.
Here's what I found - mysql gem was not installed and that maybe a
core source of problems as suggested by Zed. We've had too many
problems when we tried to install this, and found that none of the
solutions that are mentioned really work. We will try to install
this gem again.
_______________________________________________
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
