Ok - I found out what it was ... damn Merb!!
do_sqlite3-0.9.7
After I removed this gem (which is a dependency installed by Merb)
everything went back to working right. I reinstalled the gem, and I
get the same error again. So there's something going on between Rails
and this particular gem - although I'm not smart enough to figure out
what, nor have time to.
So if you're running into the same issue I would just take out that
gem - but it probably means you can't use SQLite with your Merb
applications. I have to wonder if this was done on purpose as a sort
of sabotage, since there is this religious war going on with Merb and
Rails.
On Nov 22, 7:48 am, ncancelliere <[EMAIL PROTECTED]> wrote:
> I've updated to the Rails 2.2 gem and now I can't run Rails because I
> get an error it cannot find SQLite3. I was running just fine under
> 2.1.2 with SQlite3. I'm on a Mac OS X 10.5 (Leopard) system.
>
> > gem list rails
>
> rails (2.2.2, 2.1.2, 2.0.2)
> rails-app-installer (0.2.0)
>
> > gem list sqlite
>
> sqlite3-ruby (1.2.4)
>
> > which sqlite3
>
> /usr/bin/sqlite3
>
> I know SQLite is installed and working because I can go into it from
> the command line. For some reason though Rails is not able to find
> it. Any ideas on how to fix this? (I've already tried reinstalling
> sqlite3-ruby - sudo gem install sqlite3-ruby, but that doesn't help).
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
