The SitePoint Forums have moved.

You can now find them here.
This forum is now closed to new posts, but you can browse existing content.
You can find out more information about the move and how to open a new account (if necessary) here.
If you get stuck you can get support by emailing forums@sitepoint.com

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Not understanding an awful lot about what I'm doing, I went back to look at the "show.rhtml" file. I notice a difference in what is presented in the book and what is located in the code archives I downloaded. The book file looks like this:

The totality of your current error is that your Vote model needs a "created_at column ... perhaps of type datetime or timedate or whatever. Remember to migrate it after you make it.

That instruction appears to have been overlooked in the book (I assume it would be on pages 217-18, or somewhere thereabouts). Being a total newbie, would you care to share with me how I might accomplish that?

I'm pretty darned sure I didn't miss anything. Without the book, I think you may not be the one to be providing assistance. Please, don't get me wrong, I appreciate all that you've done.

The saga continues. In my wisdom (LOL) I went in and took a look at the database structure. There was a column, under votes, labeled "create_at" but not "created_at." Not knowing as much about MySQL as I do Ruby, I deleted the column and attempted to re-insert it. Well, that apparently ain't gonna happen. So, I've made my problem worse, instead of better.

I guess, from this point on, the book becomes a nice little paperweight.

There was a column, under votes, labeled "create_at" but not "created_at."

If the code archive or something in the book tells you to make a migration or generate a model with a column called "create_at", that probably needs to be changed or added to the errata. "created_at" is the field that automatically gets set when you create a model.

Assuming the book has been using migrations to make tables, "create_at" can be found and changed in a file like db/migrate/003_some_migration

From there you can:
rake db:migrate VERSION=2 (one version less than the number on the file you changed)
rake db:migrate

Using your unpaid time to add free content to SitePoint Pty Ltd's portfolio?

If the code archive or something in the book tells you to make a migration or generate a model with a column called "create_at", that probably needs to be changed or added to the errata. "created_at" is the field that automatically gets set when you create a model.

Assuming the book has been using migrations to make tables, "create_at" can be found and changed in a file like db/migrate/003_some_migration

From there you can:
rake db:migrate VERSION=2 (one version less than the number on the file you changed)
rake db:migrate

I really appreciate your "hand-holding" with all of this.

Your suggestion fixed that problem. However, in the process of raking and migrating I appear to have upset another applecart. I am now getting this error message:

ActionController::RoutingError in Story#index
Showing app/views/story/index.rhtml where line #3 raised:

The sad thing is all of this worked properly up to the point of my initial post in this thread. I think I must've had a typo (create, instead of created) and everything has snowballed downhill from there.

I've looked at the errata - heck, I even added to the errata. I'm just about to scrap the whole thing and start fresh. (Man, I can't even believe I said that.)