Seems like unnecessary duplication if you have to specify the field in a migration as well as in the model itself.
What's the point of having to specify the field on the model if it's already in the table? Unless there is some other benefit that I am not seeing right away. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-core/-/H3ZxWdejlX8J. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
