Well, I'm using separate timestamps for associated objects as an aid for cache-key generation, to avoid throwing out too many cache entries needlessly. I could look at the updated_at of the associated items themselves - but guess what, I want to save database queries :-) So adding another table is not quite the way. I consider writing my own (SQL-based!) method, especially after finding out through the lighthouse ticket mentioned previously that all the validations are called. I have quite a few triggers and procedures in the database already anyway doing stuff behind rails' back, I would just like to limit those to certain critical areas, and a (non-frequent) timestamp update wasn't on my list of things to do through trigger rather than through actvierecord.
Thanks, Michael On Oct 16, 3:06 pm, Patrick Doyle <[email protected]> wrote: ... > Create a separate table with a 1:1 relationship to your current table ... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
