Re: schema proxying virtual database

From: Rajesh Kumar Mallah <mallah(dot)rajesh(at)gmail(dot)com>
To: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: schema proxying virtual database
Date: 2009-09-13 18:42:05
Message-ID: a97c77030909131142l4a348b46y5818726766ee0426@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

thanks that sounds like a really easy & neat solution.

On Sun, Sep 13, 2009 at 11:02 PM, Stefan Kaltenbrunner
<stefan(at)kaltenbrunner(dot)cc> wrote:

> Rajesh Kumar Mallah wrote:
>
>> Dear List,
>>
>> There are many opensource applications that support postgresql
>> (eg , gforge , bricolage , dspam ..) but does not use schemas(namespaces)
>> as a result of which you are forced to use/create a new database and loose
>> the
>> advantage of linking the application data with your existing database.
>> as no-cross database queries can be done in PG.
>>
>>
>> my question is , is it a feasible idea to have some special kind of
>> database
>> in the postgresql cluster that mimics a schema of an existsing database.
>>
>> say rt3 is a special database that links to existing maindb databases' rt3
>> namespace then any DDL / DML done to public schema of rt3 database
>> is redirected to rt3 namespace of the existing database maindb's rt3
>> schema.
>>
>
> well in most cases it is enought to give those apps their own user and
> setting the default search_path for that user to it's own schema. That way
> you usually don't have to modify the app at all and still get it (more or
> less) running in it's own schema.
>
>
> Stefan
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Peter Eisentraut 2009-09-13 19:40:41 Re: invalid byte sequence for encoding
Previous Message John R Pierce 2009-09-13 18:17:30 Re: postgresql.key secure storage