"If save(false) isn't something that you're calling in your code it is likely in plugins or gems that you're loading." ---
Thank you for your time. This makes sense. However, there is not a single place in my application where I am calling save(false) and this warning is triggered all over the place WITHOUT a reference to the line of code (in the plugin/gem) that might be triggering it. I have simply commented it out in the rails 3.0 code since in my judgement, it is more trouble than worth it? What do you think? Bharat -- 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.
