Heroku rake db：migrate aborts;實習空串...爲什麼？

Question

好吧我試過尋找這個網站的其他類似的問題，但那些接近沒有答案，所以希望鐵路/ heroku古魯可以幫助我。

我創建了一個基本的導軌應用程序（我正在學習），並設法讓它完美地運行在我的家用機器上。但是，當我把它推到的Heroku和類型：

heroku rake db:migrate我碰到下面的錯誤/秒：

c:\iltapp>heroku rake db:migrate --trace 
rake aborted! 
interning empty string 
/app/.bundle/gems/ruby/1.8/gems/actionpack-3.0.5/lib/action_dispatch/routing/mapper.rb:1309:in `to_sym' 
/app/.bundle/gems/ruby/1.8/gems/actionpack-3.0.5/lib/action_dispatch/routing/mapper.rb:1309:in `action_path' 
/app/.bundle/gems/ruby/1.8/gems/actionpack-3.0.5/lib/action_dispatch/routing/mapper.rb:1304:in `path_for_action' 
/app/.bundle/gems/ruby/1.8/gems/actionpack-3.0.5/lib/action_dispatch/routing/mapper.rb:1159:in `match' 
/app/.bundle/gems/ruby/1.8/gems/actionpack-3.0.5/lib/action_dispatch/routing/mapper.rb:1360:in `match' 
/app/config/routes.rb:11 
/app/.bundle/gems/ruby/1.8/gems/actionpack-3.0.5/lib/action_dispatch/routing/route_set.rb:233:in `instance_exec' 
/app/.bundle/gems/ruby/1.8/gems/actionpack-3.0.5/lib/action_dispatch/routing/route_set.rb:233:in `draw' 
/app/config/routes.rb:1 
/app/.bundle/gems/ruby/1.8/gems/activesupport-3.0.5/lib/active_support/dependencies.rb:235:in `load' 
/app/.bundle/gems/ruby/1.8/gems/activesupport-3.0.5/lib/active_support/dependencies.rb:235:in `load' 
/app/.bundle/gems/ruby/1.8/gems/activesupport-3.0.5/lib/active_support/dependencies.rb:227:in `load_dependency' 
/app/.bundle/gems/ruby/1.8/gems/activesupport-3.0.5/lib/active_support/dependencies.rb:235:in `load' 
/app/.bundle/gems/ruby/1.8/gems/railties-3.0.5/lib/rails/application.rb:127:in `reload_routes!' 
/app/.bundle/gems/ruby/1.8/gems/railties-3.0.5/lib/rails/application.rb:127:in `each' 
/app/.bundle/gems/ruby/1.8/gems/railties-3.0.5/lib/rails/application.rb:127:in `reload_routes!' 
/app/.bundle/gems/ruby/1.8/gems/railties-3.0.5/lib/rails/application.rb:120:in `routes_reloader' 
/app/.bundle/gems/ruby/1.8/gems/activesupport-3.0.5/lib/active_support/file_update_checker.rb:32:in `call' 
/app/.bundle/gems/ruby/1.8/gems/activesupport-3.0.5/lib/active_support/file_update_checker.rb:32:in `execute_if_updated' 
/app/.bundle/gems/ruby/1.8/gems/railties-3.0.5/lib/rails/application/finisher.rb:51 
/app/.bundle/gems/ruby/1.8/gems/railties-3.0.5/lib/rails/application/finisher.rb:52:in `call' 
/app/.bundle/gems/ruby/1.8/gems/railties-3.0.5/lib/rails/application/finisher.rb:52 
/app/.bundle/gems/ruby/1.8/gems/railties-3.0.5/lib/rails/initializable.rb:25:in `instance_exec' 
/app/.bundle/gems/ruby/1.8/gems/railties-3.0.5/lib/rails/initializable.rb:25:in `run' 
/app/.bundle/gems/ruby/1.8/gems/railties-3.0.5/lib/rails/initializable.rb:50:in `run_initializers' 
/app/.bundle/gems/ruby/1.8/gems/railties-3.0.5/lib/rails/initializable.rb:49:in `each' 
/app/.bundle/gems/ruby/1.8/gems/railties-3.0.5/lib/rails/initializable.rb:49:in `run_initializers' 
/app/.bundle/gems/ruby/1.8/gems/railties-3.0.5/lib/rails/application.rb:134:in `initialize!' 
/app/.bundle/gems/ruby/1.8/gems/railties-3.0.5/lib/rails/application.rb:77:in `send' 
/app/.bundle/gems/ruby/1.8/gems/railties-3.0.5/lib/rails/application.rb:77:in `method_missing' 
/app/config/environment.rb:5 
/app/.bundle/gems/ruby/1.8/gems/railties-3.0.5/lib/rails/application.rb:103:in `require' 
/app/.bundle/gems/ruby/1.8/gems/railties-3.0.5/lib/rails/application.rb:103:in `require_environment!' 
/app/.bundle/gems/ruby/1.8/gems/railties-3.0.5/lib/rails/application.rb:216:in `initialize_tasks' 
/app/.bundle/gems/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `call' 
/app/.bundle/gems/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `execute' 
/app/.bundle/gems/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `each' 
/app/.bundle/gems/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `execute' 
/app/.bundle/gems/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:597:in `invoke_with_call_chain' 
/usr/ruby1.8.7/lib/ruby/1.8/monitor.rb:242:in `synchronize' 
/app/.bundle/gems/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain' 
/app/.bundle/gems/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:607:in `invoke_prerequisites' 
/app/.bundle/gems/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:604:in `each' 
/app/.bundle/gems/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:604:in `invoke_prerequisites' 
/app/.bundle/gems/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:596:in `invoke_with_call_chain' 
/usr/ruby1.8.7/lib/ruby/1.8/monitor.rb:242:in `synchronize' 
/app/.bundle/gems/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain' 
/app/.bundle/gems/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:583:in `invoke' 
/app/.bundle/gems/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:2051:in `invoke_task' 
/app/.bundle/gems/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' 
/app/.bundle/gems/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `each' 
/app/.bundle/gems/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' 
/app/.bundle/gems/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' 
/app/.bundle/gems/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level' 
/app/.bundle/gems/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:2001:in `run' 
/app/.bundle/gems/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' 
/app/.bundle/gems/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in `run' 
/app/.bundle/gems/ruby/1.8/gems/rake-0.8.7/bin/rake:31 
/usr/ruby1.8.7/bin/rake:19:in `load' 
/usr/ruby1.8.7/bin/rake:19 
(in /app) 
** Invoke db:migrate (first_time) 
** Invoke environment (first_time) 
** Execute environment 

很抱歉的長貼，但說實話，我不知道，可能的哪個部分我翔實。我注意到，我希望這不是這種情況是我已經安裝Ruby 1.9.2 & Rails 3，我看到上面提到的heroku提到1.8。如果我繼續使用我的版本，或者如果這是問題，我的代碼是否與heroku完全不兼容？是否有解決方法？

更新＃1：我試圖@正在重置與herolu rake db:reset DB的Svilen的建議，並得到同樣的錯誤和一些新的，這可能會或可能不相關。並澄清我runnign它放在一個竹堆棧（竹REE-1.8.7）繼承人我得到什麼：

更新＃2

Couldn't drop hvjiqvwyxn : #<ActiveRecord::StatementInvalid: PGError: ERROR: must be owner of database hvjiqvwyxn 
: DROP DATABASE IF EXISTS "hvjiqvwyxn"> 
hvjiqvwyxn already exists 
rake aborted! 
interning empty string 

：按@ Svilen的我有棧的提遷移到bamboo-mri-1.9.2其中紅寶石1.9.2（並糾正我，如果我錯了）支持「實習空串」

任何答案將不勝感激。

Answer 1

Heroku僅在Bamboo堆棧上支持Ruby 1.9.2。您可以通過輸入heroku堆棧來檢查您正在使用的堆棧。如果你在舊的 - 阿斯彭 - 你可以輕鬆移動到竹子。檢查這篇文章中Heroku的開發中心：http://devcenter.heroku.com/articles/stack

如果不是這種情況，請嘗試重新設置數據庫，並迫使所有遷移（注：你將失去現有的所有數據！）與Heroku的耙分貝：重置。您也可以嘗試使用heroku重啓重新啓動Heroku。

如果您在git推送到heroku時發現任何異常，它可能與問題有關並值得使用其他數據更新您的問題。