> The auto-migration feature is really nice in a non-scaffolding > workflow, though. The way I use and work with a Rails application is > by creating one model at the time as they're needed to make the > application work.
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. I think the way that migrations were eased in as an option, and now set as default (overridable in environment.rb) is the way to go. 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. Does anyone else think that shoving in this default is a bad idea at the moment? _______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
