From: | Andreas Kretschmer <akretschmer(at)spamfence(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Alter table to "on update cascade" |
Date: | 2010-11-17 17:49:32 |
Message-ID: | 20101117174932.GA4779@tux |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Richard Broersma <richard(dot)broersma(at)gmail(dot)com> wrote:
> On Wed, Nov 17, 2010 at 8:43 AM, David Fetter <david(at)fetter(dot)org> wrote:
>
> > You can do it like this:
> >
> > BEGIN;
> > ALTER TABLE foo DROP CONSTRAINT your_constraint;
> > ALTER TABLE foo ADD FOREIGN KEY ...;
> > COMMIT;
>
> The nice thing about the ALTER TABLE statement is that you can do it
> in one command:
>
>
> ALTER TABLE foo
> DROP CONSTRAINT your_constraint,
> ADD CONSTRAINT your_constraint FOREIGN KEY ...
> ON UPDATE CASCADE ON DELETE RESTRICT;
yeah, cool ;-)
Andreas
--
Really, I'm not out to destroy Microsoft. That will just be a completely
unintentional side effect. (Linus Torvalds)
"If I was god, I would recompile penguin with --enable-fly." (unknown)
Kaufbach, Saxony, Germany, Europe. N 51.05082°, E 13.56889°
From | Date | Subject | |
---|---|---|---|
Next Message | Allan Kamau | 2010-11-17 19:11:33 | Re: Trying to obtain the intersect of two tsvector values |
Previous Message | Josh Berkus | 2010-11-17 17:49:07 | Re: Survey on backing up unlogged tables: help us with PostgreSQL development! |