| From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
|---|---|
| To: | Aasmund Midttun Godal <postgresql(at)envisity(dot)com> |
| Cc: | <pgsql-general(at)postgresql(dot)org>, <wsheldah(at)lexmark(dot)com> |
| Subject: | Re: alter table workaround |
| Date: | 2001-10-31 18:05:50 |
| Message-ID: | 20011031100044.M18798-100000@megazone23.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, 31 Oct 2001, Aasmund Midttun Godal wrote:
> Well, the foreign keys are dumped out as separate statements, so I
> think it will work. It's definitely worth a try...
It'll only write out part of the constraint in those cases I believe
(and it seems to be borne out by my 7.2 pg_dump output). It looks like it
writes out the triggers for the table that's specified, but not for the
other side of the constraint, but when you do the drop table, all of the
constraints are removed. The restore after a drop table would probably
be a partially functioning constraint.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Piornik | 2001-10-31 19:41:11 | Record blocking in Postgresql |
| Previous Message | Aasmund Midttun Godal | 2001-10-31 17:10:31 | Re: alter table workaround |