RE: Swapping DBs based on subdomains

Williams, Chris
2005-02-28T17:14:40Z

> -----Original Message-----
> From: rails-bounces-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
[mailto:rails-
> bounces-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org] On Behalf Of
Steven Critchfield
> Sent: Monday, February 28, 2005 12:32 PM
> To: rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> Subject: Re: [Rails] Swapping DBs based on subdomains
>
> On Mon, 2005-02-28 at 11:24 -0500, Williams, Chris wrote:
> > Hi,
> >
> >         I''m in a situation where I''d like to share
the exact same DB
> > structure, controllers, helpers, models and views between two
"teams".
> > Each "team" needs a separate DB that has identical structure
but
> > different data.
> >
> > So here''s the question: How do I go about setting this up?
I''d like
to
> > do it by subdomain (but I''ve never even tried to set one up,
so I''m
> > lost), but would settle for a field on a User class that I can check
> > when they login to know what team''s DB to use.
> >
> > Basically the idea is I need multiple production DBs, but would like
> > to share common code and structure across them.
>
> While splitting the teams up by database would probably use the least
> amount of code change, it might throw up future barriers using tools
> like memcached as you will have to know what database the records
where
> pulled from.
>
> You could alternately go in and add an ID to link specific records to
> the team that is working with it.

Well it''s even an issue of security. The teams don''t want the
others to
see they''re data.

It seemed best to just clone the DB structure and let each have their
own to store data - and swapping the DB based on subdomain looked like
the easiest way to keep the code looking like I just needed to deal with
a single team''s data.

Thanks,
Chris