Re: URGENT: How to change ON CASCADE RESTRICT to DELETE?

From: Robert <robert(at)robert(dot)cz>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: URGENT: How to change ON CASCADE RESTRICT to DELETE?
Date: 2003-07-02 10:14:34
Message-ID: 3F02B08A.9050303@robert.cz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Stephan Szabo wrote:

>> how can I change ON CASCADE RESTRICT to ON CASCADE DELETE? I need to
>>do it on my production database now (client is really complaining...)
>>and I dont see any DROP CONSTRAINT in the docs - whats the right and/or
>>simplest way? Thanks a lot
>>
>>
>
>If you're using 7.3, you should IIRC be able to use alter table to drop
>the constraint and then re-add it.
>
>If you're using an older version, I think you may need to find the
>triggers involved and drop those and then re-add the constraint. I think
>techdocs has some info on finding the triggers.
>
>
Tried ALTER TABLE (yes, this is 7.3) but \d says

nbcz=# \d seasons
Table "public.seasons"
Column | Type |
Modifiers
----------+---------+---------------------------------------------------------
id | integer | not null default
nextval('public.seasons_id_seq'::text)
hotel_id | integer |
name | text |
Indexes: seasons_pkey primary key btree (id)
Foreign Key constraints: $1 FOREIGN KEY (hotel_id) REFERENCES hotels(id)
ON UPDATE NO ACTION ON DELETE NO ACTION

and

ALTER TABLE seasons DROP CONSTRAINT $1;

didn't work. Apparently I'm more then a bit confused, but what's the
name of the constraint here? I finally took a deep breath, dropped the
database and edited dump directly. Now it seems to work, but I'd still
like to now the correct way (ALTER TABLE but how?) Thanks for your help

- Robert

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ian Barwick 2003-07-02 10:35:45 Re: URGENT: How to change ON CASCADE RESTRICT to DELETE?
Previous Message Együd Csaba 2003-07-02 09:53:36 Stored Proc error after modifying field type