From: | Andreas Kretschmer <andreas(at)a-kretschmer(dot)de> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Schemas and foreign keys |
Date: | 2017-07-21 14:07:29 |
Message-ID: | 2265ebc5-cb8f-01d6-d129-68bb5e40879f@a-kretschmer.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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
--
2ndQuadrant - The PostgreSQL Support Company.
www.2ndQuadrant.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-07-21 14:09:38 | Re: pg_dump and insert json with copy |
Previous Message | Tom Lane | 2017-07-21 14:03:23 | Re: pg_restore misuse or bug? |