The new table really "fits" in one of the existing files, so I'll try what you suggested. I had heard that rolling in and out of versions hurt performance, but probably won't be the case if this is the first time I haven't purged the database ;-)
On Mar 24, 5:18 pm, "Edward Grant" <[EMAIL PROTECTED]> wrote: > > Perhaps I'm doing this wrong, but I created a new model/table and > > needed to then create a join table. So I added the join table to the > > migrations file that already existed for my model. I run rake > > db:migrate and I'm not seeing the new table. If the table exists and > > there are no new files, does the migration ignore it? > > > I'd like to add the new table based on what I defined in the migration > > file without having to wipe all my current data. Any pointers? I > > read some of the RoR wiki pages and didn't get anywhere. > > If you have already run a migration and you latter descide you need to > change the schema of the database you can do one of two things. > > I think this would be called the best practices way. Create a new > migration. In this new migration you would add you definition for the > linking table. > > Another way would be to migrate to a level before the migration you > wan to edit and edit it and re run the migrations. > > check out the rake db options > > -- > Edward Grant > [EMAIL PROTECTED] > > RPGA #342155 > CAMARILLA #US2002022579 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Heroku" 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/heroku?hl=en -~----------~----~----~----~------~----~------~--~---
