Re: How to implement a "subordinate database"?
От | chris smith |
---|---|
Тема | Re: How to implement a "subordinate database"? |
Дата | |
Msg-id | 3c1395330604190431i4fb7cbbfu72df1fb78063dd46@mail.gmail.com обсуждение исходный текст |
Ответ на | How to implement a "subordinate database"? ("Kynn Jones" <kynnjo@gmail.com>) |
Ответы |
Re: How to implement a "subordinate database"?
|
Список | pgsql-general |
On 4/19/06, Kynn Jones <kynnjo@gmail.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/
В списке pgsql-general по дате отправления: