Additionally, I think a significant amount of people like to design their dbs first, or in chunks instead of 1 model -> 1 migration. This is the case for myself.
That's great. We still allow for that. There's all the opportunity in the world to go chasing waterfalls with --skip-migration, but it's certainly not an approach that I want to encourage. The current approach embeds the opinion that developing your application model-by-model is preferable over chunk-by-chunk, but still allows you to do the latter at the cost of configuration.
Why not make the generator clever: if there's no existing table, and no existing migration named create_xxx, create the migration. Otherwise, don't create it.
|
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core
