From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | radek(dot)stachowiak(at)alter(dot)pl |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: foreign keys |
Date: | 2000-08-06 17:51:28 |
Message-ID: | 200008061751.NAA19738@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> *** Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> [Saturday, 05.August.2000, 19:39 -0400]:
> > > Not to mentions fact that in a few places in docs it's shown as a method
> > > for copying table "SELECT... INTO" which does not "take" keys with it
> > > leading to database knwoledge loss.
> >
> > That is a good point. SELECT INTO doesn't support constraints.
> > Unfortunately, I don't really know a way around that. The only solution
> > is CREATE TABLE and then INSERT INTO ... SELECT.
> [.rs.]
>
> what about my other statement about third constraint not being transferred
> withh pg_dump -t table because it was "connected" to second database? Am I right?
>
> What is correct (mean: most simple) way of dupicating table with all FK ?
>
Sorry, I don't know.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | vectro | 2000-08-06 18:46:10 | Re: foreign keys |
Previous Message | Tom Lane | 2000-08-06 17:19:36 | Re: Table Design: Timestamp vs time/date |