Marnen Laibow-Koser wrote: > Poppycock. You might not be willing to alter your production DB this > season, but you *can* (and probably should) set up a testing environment > to see what you can do. >
I mentioned in paragraph two that I will be setting up a test environment for it. But, again, I'm not going to alter my production DB at this time. The season is just a couple weeks away and it wouldn't allow for enough time to implement, test, and then complete. I won't risk any issues. > Why? I talked about table corruption previously. Matt simply said well you can restore from backup. If I had 50,000 subscribers all expecting a service and a table this large that would basically represent all of the data provided in the service failed, there will be a critical outage. Table corruption has a larger chance of occurring on larger tables. I like to ensure whatever I provide works 100%. My current situation is a lot more improved (query times are really good right now) and with caching, will only get better. What I'm doing right now is not wrong, it can just be more efficient later on (as Matt pointed out). At this point in time, we can agree to disagree on this topic. Thanks. -- 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 -~----------~----~----~----~------~----~------~--~---
