> I'm assuming all 10 tables are actually the same for each client, > right? Just have an 11th table - "clients". Relate your other tables > to the clients table, and use the power of ActiveRecord to query for > all the data you need for a specific client. > > You can use a before_filter in your application controller to look at > the subdomain to discover which client you're supposed to be using.
That sounds super convenient, but wouldn't it lead to really bloated tables and slow searches in the long run? I think I would vote for option #2, individual databases for each client. Also, obviously they would be backed up, but this would also prevent one database getting hosed from knocking out all your clients. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
