| From: | "chris smith" <dmagick(at)gmail(dot)com> | 
|---|---|
| To: | "Kynn Jones" <kynnjo(at)gmail(dot)com> | 
| Cc: | pgsql-general(at)postgresql(dot)org | 
| Subject: | Re: How to implement a "subordinate database"? | 
| Date: | 2006-04-19 11:31:12 | 
| Message-ID: | 3c1395330604190431i4fb7cbbfu72df1fb78063dd46@mail.gmail.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-general | 
On 4/19/06, Kynn Jones <kynnjo(at)gmail(dot)com> wrote:
>
> I keep bumping against this situation: I have a main database A, and I want
> to implement a database B, that is distinct from A, but subordinate to it,
> meaning that it refers to data in A, but not vice versa.
>
> I don't simply want to add new tables to A to implement B, because this
> unnecessarily clutters A's schema with tables that entirely extraneous to
> it.
Hmm. Postgres supports table inheritance, but I don't think it
supports schema or database inheritance in the way you want it to.
http://www.postgresql.org/docs/8.1/interactive/tutorial-inheritance.html
http://www.postgresql.org/docs/8.1/interactive/ddl-inherit.html
--
Postgresql & php tutorials
http://www.designmagick.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2006-04-19 11:35:45 | Re: strange query filter problems | 
| Previous Message | Jonas Henriksen | 2006-04-19 11:27:45 | strange query filter problems |