Ruby on Rails

On 23 November 2010 16:56, Blake Miller <lists@ruby-forum.com> wrote:

Please remember to quote the previous message so one can follow the thread

> I think you're right...it's probably somewhere in the save code.

Who?

> Problem is, the save method is buried in the Devise (gem) code, so have
> to figure out what's going on there :/.  I've verified before and after
> the save method, the value is 1; however, the value in the raw sql
> insert query into the database is 0.

Are you sure the attribute name exactly matches the column name -
check for typo.
Check that mass write is not prevented (as Marnen suggested) by
creating, setting and saving a record in the console.

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.