Hi Maurício, thanks for your reply. In fact I can't just reuse another action because it's not just a matter of changing a field in the database (which in that case update could be ok), I also perform some background operations like sending emails and updating other protected fields of the model (like date of activation or removing activation code). To do that I need to call a model method like user.activate or user.block, and it would be a mess probably to integrate this behaviour inside the update method. -- 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 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 -~----------~----~----~----~------~----~------~--~---
