> >
> > Luke
>
> Sorry for just getting back, super busy. :)
>
> So i created a new project and still Im running into the same issue.
>
> This is in my echo $PATH:
> /Library/Frameworks/Python.framework/Versions/2.7/bin:/Users/musdev/.rvm/ge ms/ruby-1.9.2-p136/bin:/Users/musdev/.rvm/gems/ruby-1.9.2-p136@global/bin:/ Users/musdev/.rvm/rubies/ruby-1.9.2-p136/bin:/Users/musdev/.rvm/bin:/Users/ musdev/.vim/bin:/Users/musdev/.gem/ruby/1.8/bin:/Users/musdev/.gem/ruby/1.9 /bin:/usr/local/bin/:/usr/local/sbin:/usr/local/mysql/bin:/usr/lib:/opt/loc al/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X1 1/bin:/usr/local/git/bin
>
Why is /usr/lib on your path? From previous messages there's an
sqlite3 file in there with it's execute permission set to true. Since
it's ahead of usr/bin, the shell is finding /usr/lib/sqlite3 and
trying to execute that, which presumably doesn't work because it's not
an executable.
Fred
> My database.yml file contains:
> # SQLite version 3.x
> # gem install sqlite3-ruby (not necessary on OS X Leopard)
> development:
> adapter: sqlite3
> database: db/development.sqlite3
> pool: 5
> timeout: 5000
>
> # Warning: The database defined as "test" will be erased and
> # re-generated from your development database when you run "rake".
> # Do not set this db to the same as development or production.
> test:
> adapter: sqlite3
> database: db/test.sqlite3
> pool: 5
> timeout: 5000
>
> production:
> adapter: sqlite3
> database: db/production.sqlite3
> pool: 5
> timeout: 5000
>
> whereis sqlite3 is in /usr/bin/sqlite3
>
> Running sqlite3 in usr/bin/sqlite3 worked just fine.
>
> Kindest regards
>
> --
> Posted viahttp://www.ruby-forum.com/.
--
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 rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
No comments:
Post a Comment