Did you read the original post? It's not just one SQL, it is one SQL and then hit every user object returned to see if it is time to send the email. Anyone can see that eventually this is going to cause a problem, and I don't know about you, but I would rather find that sort of thing now, before my customers notice a problem than wait until it actually causes one.
Oh, and you don't actually need a qualification to be able to pick a premature jerky response, just some experience on the internet. On Tue, 21 Oct 2008 13:28:22 +0800, Hassan Schroeder <[EMAIL PROTECTED]> wrote: > > On Mon, Oct 20, 2008 at 10:08 PM, Bsytlz <[EMAIL PROTECTED]> wrote: > >> There is no so such thing as premature optimization, maybe mis- >> prioritized optimization (may be more impactful things to address >> first), but if you wait until you "have to" optimize to do it...it is >> too late. > > And the OP presented zero evidence of an actual problem, or hint > of any potential problem. Running one SQL query every 15 minutes > seems, uh, not too much to worry about. IMO. > >> There is however a such thing as a premature jerky, smart ass response >> like the one above.. > > Thanks for the evaluation. And your qualifications on constructing > and running high-traffic web sites? Just curious. > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
