From: | John R Pierce <pierce(at)hogranch(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Managing two sets of data in one database |
Date: | 2012-03-29 21:22:45 |
Message-ID: | 4F74D2A5.9070203@hogranch.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 03/29/12 2:16 PM, Thomas Kellerer wrote:
> Jonathan Bartlett wrote on 29.03.2012 22:39:
>> 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.
>
> If you create different Postgres users, you can set the search_path
> per user, so you don't have to remember doing that while connecting.
heck, the default search_path is $USER,"public"
--
john r pierce N 37, W 122
santa cruz ca mid-left coast
From | Date | Subject | |
---|---|---|---|
Next Message | David Salisbury | 2012-03-29 22:16:23 | default value returned from sql stmt |
Previous Message | Thomas Kellerer | 2012-03-29 21:16:25 | Re: Managing two sets of data in one database |