Brian wrote: > I'm starting to think about how my application can scale if it needs > to. This is all very premature - I don't even have clear performance > goals yet, much lest perf testing in place, so it may be unnecessary.
Yeah...it may be premature to act on this, although thinking never hurts. :) > However, one quality my data has is that it's isolated into groups of > records that never reference anything outside of that group. This > leads me to think I can have a small group of tables in a main DB to > store user info, [...] > Is there any built-in way to handle this in rails (or a popular plugin > that can do this)? I think you will want to do this on the DB side rather than in the app. The various DB servers out there have ways of breaking up tables for performance reasons and still having them look the same to the application (I think MERGE tables in mySQL fit this description). So investigate what your DB server can do for you before you start trying to get clever with table-based subclasses. Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- 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 -~----------~----~----~----~------~----~------~--~---
