rwdaigle / miyagi

Miyagi - a Heroku-inspired journal of application development.

Home Page:http://miyagijournal.com

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

relation "users" does not exist

zeke opened this issue · comments

~/Projects/forks/miyagi master+* >be rake db:create:all
~/Projects/forks/miyagi master+* >be rake data:refresh
Removing all users
rake aborted!
PG::Error: ERROR:  relation "users" does not exist
LINE 1: DELETE FROM "users"
                    ^
: DELETE FROM "users"
/Users/zeke/.rvm/gems/ruby-1.9.3-p194@adj/gems/activerecord-3.2.9/lib/active_record/connection_adapters/postgresql_adapter.rb:1153:in `async_exec'
/Users/zeke/.rvm/gems/ruby-1.9.3-p194@adj/gems/activerecord-3.2.9/lib/active_record/connection_adapters/postgresql_adapter.rb:1153:in `exec_no_cache'
/Users/zeke/.rvm/gems/ruby-1.9.3-p194@adj/gems/activerecord-3.2.9/lib/active_record/connection_adapters/postgresql_adapter.rb:673:in `block in exec_delete'
/Users/zeke/.rvm/gems/ruby-1.9.3-p194@adj/gems/activerecord-3.2.9/lib/active_record/connection_adapters/abstract_adapter.rb:280:in `block in log'
/Users/zeke/.rvm/gems/ruby-1.9.3-p194@adj/gems/activesupport-3.2.9/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/Users/zeke/.rvm/gems/ruby-1.9.3-p194@adj/gems/activerecord-3.2.9/lib/active_record/connection_adapters/abstract_adapter.rb:275:in `log'
/Users/zeke/.rvm/gems/ruby-1.9.3-p194@adj/gems/newrelic_rpm-3.5.1.14/lib/new_relic/agent/instrumentation/active_record.rb:32:in `block in log_with_newrelic_instrumentation'
/Users/zeke/.rvm/gems/ruby-1.9.3-p194@adj/gems/newrelic_rpm-3.5.1.14/lib/new_relic/agent/method_tracer.rb:242:in `trace_execution_scoped'
/Users/zeke/.rvm/gems/ruby-1.9.3-p194@adj/gems/newrelic_rpm-3.5.1.14/lib/new_relic/agent/instrumentation/active_record.rb:29:in `log_with_newrelic_instrumentation'
/Users/zeke/.rvm/gems/ruby-1.9.3-p194@adj/gems/activerecord-3.2.9/lib/active_record/connection_adapters/postgresql_adapter.rb:672:in `exec_delete'
/Users/zeke/.rvm/gems/ruby-1.9.3-p194@adj/gems/activerecord-3.2.9/lib/active_record/connection_adapters/abstract/database_statements.rb:101:in `delete'
/Users/zeke/.rvm/gems/ruby-1.9.3-p194@adj/gems/activerecord-3.2.9/lib/active_record/connection_adapters/abstract/query_cache.rb:14:in `delete'
/Users/zeke/.rvm/gems/ruby-1.9.3-p194@adj/gems/activerecord-3.2.9/lib/active_record/relation.rb:413:in `delete_all'
/Users/zeke/.rvm/gems/ruby-1.9.3-p194@adj/gems/activerecord-3.2.9/lib/active_record/querying.rb:7:in `delete_all'
/Users/zeke/Projects/forks/miyagi/lib/tasks/data.rake:10:in `block (3 levels) in <top (required)>'
/Users/zeke/Projects/forks/miyagi/lib/tasks/data.rake:8:in `each'
/Users/zeke/Projects/forks/miyagi/lib/tasks/data.rake:8:in `block (2 levels) in <top (required)>'
Tasks: TOP => data:refresh => data:clear
(See full trace by running task with --trace)

Arg. Doing a refresh before any migrations will cause this. You can just do:

$ rake db:migrate
$ rake db:seed

on a fresh db for now.

Yeah, rake data:refresh isn't supported on a new db. As the readme says, use rake db:setup instead.

rake data:refresh should only be used once in dev to re-populate the db data.