> I'm struggling a bit with the best way to override the private create > and update methods. I have an adapter for a non sql backend and I > need to either override create and update, or alternatively maybe > override create_or_update and have it call replacements for create and > update. I would prefer the approach that modifies as little as > possible of activerecord. > > Suggestions?
Given all the other things we do with SQL like .find(:all, :include=>...) you're going to be changing a lot more than that. My advice would be to aim to be duck-type compatible rather than reuse the implementation. Take a look at how we've implemented ActiveResource. -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core?hl=en -~----------~----~----~----~------~----~------~--~---
