ansaurus

Question

Answer 1

+1 A:

You can take a look at this one at rails guide. But I suggest, if it is possible, you should delete the models and all references to the models. This will probably save time later as you don't need to maintain the dead code in the codebase.

Sohan 2009-12-30 18:56:41

Answer 2

+1 A:

What about doing ruby script/destroy model? That should take care of the model and the migration.

bobbywilson0 2009-12-30 22:23:55

what about later migrations that add data to this model? does script/destroy search the migrations or does it just delete the initial one that created the table?

brad 2010-01-02 21:04:11

Later migrations will need their own `script/destory migration migration_name`. A good way to think about it, it is the undo of the genarate command. So, no it also won't search for other migrations that alter the same model.

bobbywilson0 2010-01-03 03:41:56

right, so then the final answer to all of this is that I can use script/destroy, but I also need to manually edit any migrations that might contain refs to these deleted models. Thanks so much

brad 2010-01-03 17:48:19

Answer 3

+1 A:

Depending on how far into development or production you are, you may want to migrate the models out safely using a migration to remove/backup data or what not. Then as bobbywilson0 suggested, using

script/destroy model

or if you rspec anything

script/destroy rspec_model

This will remove any spec tests as well.

Or you can always just drag them to the trash folder.

nowk 2009-12-30 22:38:05

ansaurus

tags:

views:

answers:

rails remove old models with migrations

related questions