Youyou Semsem wrote: > 1. Whenever I want to SELECT from the table, I need to include where > expiry_date > NOW. If the table Post grows like a monster, I will be in > trouble. Imagine after 3 years or more. Indexes will be huge too.
Obviously using indices is the easiest. I'm not sure how many posts you're expecting, but unless you *know* it'll run into the millions with a high percentage of cache misses this sounds like premature optimization. First let your RDBMS deal with the size of the indices (it'll do fine) and then let your DBA worry about it (he'll cache it into RAM and put it on a fast disk). -- Roderick van Domburg http://www.nedforce.com -- 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 -~----------~----~----~----~------~----~------~--~---
