| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Jonathan Bartlett <jonathan(at)newmedio(dot)com> |
| Cc: | Tom Molesworth <tom(at)audioboundary(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Managing two sets of data in one database |
| Date: | 2012-03-29 21:09:10 |
| Message-ID: | CAOR=d=12-8axbDuLRwoyfRtJQr62TBUHv4RQmoC+=YY=HPir4g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Mar 29, 2012 at 2:39 PM, Jonathan Bartlett
<jonathan(at)newmedio(dot)com> wrote:
> Tom -
>
> Your suggestion gives me an idea, and I'd like your opinion since I haven't
> done much with schemas.
>
> (1) Separate the datasets into different schemas
> (2) Use different schema names for different static data releases
> (3) For the *company*, we can use a schema search path that includes the
> next schema
> (4) For the *users*, they can use a schema search path that includes the
> released schema
>
> Then, I wouldn't have to modify any code, except to set the schema search
> path based on who was connecting.
>
> Does this sound reasonable?
It's pretty much what I was going to suggest.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Kellerer | 2012-03-29 21:16:25 | Re: Managing two sets of data in one database |
| Previous Message | Jonathan Bartlett | 2012-03-29 20:39:38 | Re: Managing two sets of data in one database |