| From: | Radoslaw Stachowiak <radek(at)alter(dot)pl> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: foreign keys |
| Date: | 2000-08-06 09:28:12 |
| Message-ID: | 20000806112812.B21078@blue.alter.pl |
| 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 ?
--
radoslaw.stachowiak.........................................http://alter.pl/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-08-06 17:19:36 | Re: Table Design: Timestamp vs time/date |
| Previous Message | Alex Pilosov | 2000-08-06 06:03:13 | Re: libperl.so |