On 8 June 2012 07:57, Bataille Gregory <[email protected]> wrote: > Indeed, the right way would have been to use the generator to add a field to > your model. This would have update your model AND created a DB migration. > In your case, you changed the DB, but not the Ruby object that corresponds > to it. So indeed the new field does not exist in your object, thus the > error.
What generator command would have added attr_accessible for the new field in the model.rb? Colin > > > On Friday, June 8, 2012 12:08:22 AM UTC+2, Ruby-Forum.com User wrote: >> >> Hi, >> >> i added a column to my DB using >> rails g migration AddAttrToTablename attr:string >> rake db:migrate >> >> I didnt change the model file. Should i? >> >> Now when i create a new record to the table assigning values to existing >> attrs and newly added attribute i get this error "Can't mass-assign >> protected attributes: attr" >> >> Any1 understand whats happening here? >> >> -- >> Posted via http://www.ruby-forum.com/. > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/rubyonrails-talk/-/DNxEeD1WP3EJ. > > 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-talk?hl=en. -- 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 [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-talk?hl=en.
