> rake db:migrate That did it!!!! I've been racking my brains over this for two, just because I want to adopt what I feel are "best practices". You've rescued me from an embarrassing ordeal.
Thank you very much for your insight Steve. - Richard On Feb 23, 9:23 pm, Steve Rowley <[email protected]> wrote: > > All I get from rake db;create:all is, consistent with database.yml: > > empty tables if they do not already exist > > announcements/warnings if the tables already exist (without recreating > > them so that populated tables maintain whatever definitions/data that > > they had) > > Hi Richard - it's possible I misunderstand the question, but judging > from the title of your post, could the problem be that you are > creating the database but aren't running the migrations to create the > tables? > > rake db:create:all > > creates the development, test and production databases on the server, > akin to the executing SQL DDL like "CREATE DATABASE xxx." This > wouldn't create any tables. > > To actually create the tables defined in your migrations (or create > indexes, or alter the tables, or any of the other stuff you define in > migrations), you would run: > > rake db:migrate > > which executes any migrations that haven't already been run already in > the current default environment database (say, development if you are > working in development), akin to executing SQL like "CREATE TABLE xxx" > or "ALTER TABLE", etc. This of course assumes you have generated some > migrations (it sounds like you have). > > -Steve -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
