From: | marcelo <marcelo(dot)nicolet(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Schemas and foreign keys |
Date: | 2017-07-21 14:20:24 |
Message-ID: | c8d5f75a-7c65-5f22-63f6-2771ec68b47a@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thank you, Andreas.
Your answer closes this thread.
On 21/07/17 11:07, Andreas Kretschmer wrote:
>
>
> Am 21.07.2017 um 14:58 schrieb marcelo:
>> Recently I asked regarding schemas, and received very useful answers.
>> I conclude that I can put some tables in one schema and left others
>> in the public one.
>> If my app selects some schema, the backend will found automatically
>> the absent tables in "public".
>> So far, so good.
>> But what about foreign keys? At least, I will have foreign keys from
>> the tables in the specified schema to the tables in "public", because
>> I'm thinking that the tables in "public" would be references, while
>> the tables residing in the specified schema will be the transactional
>> ones.
>> TIA
>> Marcelo
>>
>>
>
> that's no problem:
>
> test=# create schema demo1;
> CREATE SCHEMA
> test=*# create schema demo2;
> CREATE SCHEMA
> test=*# create table master_table(id int primary key);
> CREATE TABLE
> test=*# create table demo1.demo_table(id int primary key, master_id
> int references public.master_table);
> CREATE TABLE
> test=*# create table demo2.demo_table(id int primary key, master_id
> int references public.master_table);
> CREATE TABLE
>
>
> Regards, Andreas
>
From | Date | Subject | |
---|---|---|---|
Next Message | Jordan Gigov | 2017-07-21 14:25:00 | Re: pg_restore misuse or bug? |
Previous Message | Albe Laurenz | 2017-07-21 14:16:56 | Re: Schemas and foreign keys |