rubyonrailsin

On 22 March 2010 16:08, Mike Montagne <lists@ruby-forum.com> wrote:
> So let's not argue about this. I should be able to *start* with my
> intended design far faster than I can *eventually* modify a wrong design
> -- imposed in the name of "agility" -- to the right one (which in the
> least, is twice the work).

If you don't like the field definitions generated by the scaffold then
you can edit the migration before you run it, or run another migration
later. Is there anything in your sql table creation that cannot be
specified in migration code?

Colin

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.