In order to make the DB change work I would have to perform the following:
I would have to change how my parser pulls data and uploads data I would have to change the querying for all MVCs in my project .. that's just for starters .. That is a lot of work. I look at things from a priority perspective. Right now, all of the priority mechanisms in my app work 100% and have very good query times. Nothing is broken. Everything tests out 100% from within internal tests. Everything tests out 100% from external tests. I finished up all my mailers, observers and fully implemented my payment gateway. However, I'm working on another segment for the payment gateway and perhaps another type of payment gateway plan (paymo or boku for mobile payments) to cover those that don't have credit cards or paypal accounts. I still have a lot of extra things that need to get done before I'm happy with my app (clubhouse pages, reporting cycles for upcoming bowl games, etc.). Because the DB situation is fine now (again, realizing that it can be more optimized down the road), there's no reason for me to reinvent and add more potential problems to my app when I still have other things to work on. So, when I say we can agree to disagree - I'm referring to the "timing" of the optimizations. I believe they should occur "after this season", with proper testing, and implementation. I'm very systematic about how I work on things. -- 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 -~----------~----~----~----~------~----~------~--~---
