Ruby on Rails: Creating Relationships problem

I noticed that for some reasons it was like rake db:migrate not working properly... After some research I did the following:

1. Downloaded project files from treehouse to check if I have some typos in my code. And there was big diff in db/schema.rb file.

2. Copied all the data from treehouse's project and paste it in my db/schema.rb file.

3. Since you can not modify this file (file is auto-generated from the current state of the database.) I ran next command in terminal

           rake db:schema:load
   

And it did the trick :) Hope it helps

I fixed it! I was following the videos step by step, so when Jim's new status page worked and mine didn't, I tripped out! After going back and checking my code for errors, I decided to watch the video again and see if I could pick something up. After watching the next step in the video, I decided I was going to try the next step since it had :user_id, and it worked! Just wondering, did this happen because I have a newer version of bootstrap?

I added ( :user_id ) to,

status.rb

class Status < ActiveRecord::Base attr_accessible :content, :user_id end

I'm having the same problem.

I've tried to run rake db:migrate again but still not working. Any suggestions?

Also, this is what my db migration add_user_id_to_statuses file looks like if that helps:

class AddUserIdToStatuses < ActiveRecord::Migration

    def change
        add_column :statuses, :user_id, :integer
        add_index :statuses, :user_id
        remove_column :statuses, :name
    end
end

Hi Adam,

This error kinda ruined my sunday afternoon. Here's what I figured out for my similar error. Hope this helps.

Re: my entry According to a response from the instructor Jim, on another user's entry:
"NoMethodError in the case of models is usually a symptom of the database not having the right columns. Since you didn't have the method :user_id, and it was a column we were adding at that point in time, I would guess that you may have forgot to migrate the database, or the migration may have failed the first time around."

I also ran rake db:migrate again and it did not solve the error. I have already gone through the Michael Hartl RoR tutorial and we had used SQLite Database Browser. sqlitebrowser.sourceforge.net/ I'm using 2.0 but some have to use 1.1 if you run into trouble. In taking a look at the database information I wanted to see if all of my columns were there. [I apologize but apparently you can't paste images into this forum.]

After opening Treebook's development.sqlite3 file with the browser software I saw the right columns but in clicking into the ["Browse Data" tab : statuses table drop down] I could see that the user_id cell was 0. I figured this was the nil that was causing the error so I manually changed it in SQLite Database Browser to 4 to match the id cell count.

Then I saved and went right to check the site and I could get back to all the pages that were crashing before making the change. There's probably a way to fix this through the Rails Console but if you're receiving nil errors this could be why. Also SQLite Database Browser is a tool for visual checks of what's sitting in the dev database.

NoMethodError in the case of models is usually a symptom of the database not having the right columns. Since you didn't have the method :user_id, and it was a column we were adding at that point in time, I would guess that you may have forgot to migrate the database, or the migration may have failed the first time around.