Hello!
I'm just switching a 2.02 app to 2.1 and it mostly works, but I discovered these things:
(1)
Installing rails 2.1 broke the existing 2.0.2 app !
gem install rails gem list rails
*** LOCAL GEMS ***
rails (2.1.0, 2.0.2)
$ rake db:version (on an app that has RAILS_GEM_VERSION = '2.02')
"Your config/boot.rb is outdated: Run "rake rails:update" with rake tasks"
after running "rake rails:update" everything is ok, but now I have 2.02 app with new boot.rb script... if I take that app somewhere where 2.1 is not installed, it won't work.. and the point is that "rake install rails" broke the existing 2.0.2 app.... I had this confirmed by one other guy on IRC.
It was also very subtle, since I use Background Job for sending signup emails.. and this stopped working, because it uses script/runner ... (which also failed in the same way as db:version for example)
(2)
$ script/dbconsole production ERROR 1045 (28000): Access denied for user 'rails'@'localhost' (using password: NO)
//// even though the password is set in database.yml
Not sure if I'm doing something wrong here, but it surely doesn't 'just work'.
(3)
$ RAILS_ENV=production script/about /Library/Ruby/Gems/1.8/gems/activesupport-2.1.0/lib/active_support/ dependencies.rb:275:in `load_missing_constant': uninitialized constant Rails::Info (NameError) from /Library/Ruby/Gems/1.8/gems/activesupport-2.1.0/lib/ active_support/dependencies.rb:467:in `const_missing' from /Library/Ruby/Gems/1.8/gems/rails-2.1.0/lib/commands/about.rb:2 from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:27:in `gem_original_require' from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:27:in `require' from script/about:3
Another question:
script/runner -e production RAILS_ENV=production script/about script/dbconsole production
hmm. Do we have some consistency issues here?
Please let me know what you think!
I'm willing to tackle some source code as well... but I'm just
starting here.. and I think it's the right time GitHub for the
president ! (or smth)
David