Re: [Rails-core] Confused about the new generator behavior with migrations

[Dave Thomas]

On Mar 4, 2006, at 18:43, David Heinemeier Hansson wrote: 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. So with a shop, I'd start by creating the product model, making it work, and then moving on to the cart or the order, and every step of the way making it all work. This is in contrast to, say, creating the entire schema first, then starting to work on the model or the controller. And that's why the current scaffolding approach is broken. It assumes that I create my database first while the new model of migrations encourage a concurrent approach. That's the way I create them too. I create an empty database, then create my first migration. From there, I may generate a migration, or create a scaffold (static or dynamic). Then maybe create a migration to modify the original table, or create a new table, etc etc. I think that there's nothing intrinsically wrong with scaffolding. It's just that in general, decoupled workflows are more flexible than ones that do too much at a time. Dave

smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core