rpsec fails after editing todo_item_spec.rb

Tim -

Thanks. Your suggestion still doesn't work but I have done some digging and found a different problem that may be contributing to the problem. What I did to try to fix the problem may have made things worse. I apologize for the details that follow. Let me know if I should start a new discussion thread to address this:

When Jason entered this command: bin/rails generate model todo_item todo_list:references content:string

I entered this: (a space between todo_list: -and- references) bin/rails generate model todo_item todo_list: references content:string

That seems to have affected the model that was created. So I git a git reset --hard (to the previous working version: Add spec for deleting to-dos).

After that I reinstalled the 'shoulda-matches' gem, and regenerated the todo_items model. I ran bin/rake db:migrate and got some error messages BUT the complete: bin/rspec spec/models/todo_item_spec.rb ran with no problem.

I realize now that the git reset --hard restores the previous version of my files but it doesn't reset the database.

My question: If I do another git reset --hard to get to the working files I want, how do a reset the database to the same point.

Here are the errors I got when I ran bin/rake db:migrate:

Robert-Otts-MacBook-Pro-4:odot robertott$ bin/rake db:migrate == 20150126230445 CreateTodoItems: migrating ================================== -- create_table(:todo_items) rake aborted! StandardError: An error has occurred, this and all later migrations canceled:

SQLite3::SQLException: table "todo_items" already exists: CREATE TABLE "todo_items" ("id" INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL, "todo_list_id" integer, "content" varchar, "created_at" datetime NOT NULL, "updated_at" datetime NOT NULL) /Users/robertott/teamth/project/odot/db/migrate/20150126230445_create_todo_items.rb:3:in change' -e:1:in<main>' ActiveRecord::StatementInvalid: SQLite3::SQLException: table "todo_items" already exists: CREATE TABLE "todo_items" ("id" INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL, "todo_list_id" integer, "content" varchar, "created_at" datetime NOT NULL, "updated_at" datetime NOT NULL) /Users/robertott/teamth/project/odot/db/migrate/20150126230445_create_todo_items.rb:3:in change' -e:1:in<main>' SQLite3::SQLException: table "todo_items" already exists /Users/robertott/teamth/project/odot/db/migrate/20150126230445_create_todo_items.rb:3:in change' -e:1:in<main>' Tasks: TOP => db:migrate (See full trace by running task with --trace)

I also ran bin/rake db:migrate RAILS_ENV=test. This seemed to have run with no problem:

Robert-Otts-MacBook-Pro-4:odot robertott$ bin/rake db:migrate RAILS_ENV=test == 20150126230445 CreateTodoItems: migrating ================================== -- create_table(:todo_items) -> 0.0039s -- add_foreign_key(:todo_items, :todo_lists) -> 0.0000s == 20150126230445 CreateTodoItems: migrated (0.0043s) =========================

Thanks for your thoughts on this.

Robert,

Have you tried rolling back the migration?

rake db:rollback

Thanks Tim.

I didn't know the command to rollback the db. I assume that I should perform the rollback right after I do the git reset --hard?

Robert

Robert,

What you'd probably want to do in the future is first rollback your migration and then you can also reverse the generator. So something like this:

rake db:rollback
rails destroy model todo_item

Rarely have I been in a position during development were I needed to roll things back in git. Since you have already and this is just a development/learning project it's probably going to be best that you just reset your database and reload the schema.

Now please note, this will delete any of the data in your database.

Use:

rake db:drop
rake db:setup

Then also run it on your test environment.

rake db:drop RAILS_ENV=test
rake db:setup RAILS_ENV=test

Tim,

Many kudos! I'm back on track now.

Thanks!