Pepe, i know what you're saying - ultimately this is my fault for not reading the documentation. But, it seems like a lot of people have missed this too. It's a very important aspect of callbacks, and i think it should be made more obvious in the documentation, especially since one is given no feedback whatsoever as to why the process failed.
In this case i noticed it because a record wasn't saved, but if it wasn't a before_create callback that went wrong, and was instead an after_destroy for example, i wouldn't have noticed. Maybe the documentation could be changed so that this is immediately drawn to the attention of someone reading the section on callbacks, rather than being two pages down. Anyway, i'd be interested to know how many other people didn't know about this. I think i'll do a couple of polls :) thanks! max -- 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 -~----------~----~----~----~------~----~------~--~---
