> I agree, this is a cool new feature, but I think it should be an > option rather than a default for 1.1. This completely breaks the > principle of least surprise (which rails in general follows). When I > go to generate a model, I expect the model to be created, not model > and migration.
Heh. You might want to look up matz's feelings about PoLS, I think they apply very well here. (In other words, it breaks _my_ principle of least surprise not to have migrations come along with models, so PoLS is inherently personal). > 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. -- David Heinemeier Hansson http://www.loudthinking.com -- Broadcasting Brain http://www.basecamphq.com -- Online project management http://www.backpackit.com -- Personal information manager http://www.rubyonrails.com -- Web-application framework _______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
