| From: | Rich Doughty <rich(at)opusvl(dot)com> |
|---|---|
| To: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Adding ON UPDATE CASCADE to an existing foreign key |
| Date: | 2006-05-05 08:53:49 |
| Message-ID: | 445B129D.8090405@opusvl.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Stephan Szabo wrote:
> On Thu, 4 May 2006, Rich Doughty wrote:
>
>
>>I have a foreign key constraint that I'd like to alter. I'd rather not
>>drop and re-create it due to the size of the table involved. All I need
>>to do is add an ON UPDATE CASCADE.
>>
>>Is it ok to set confupdtype to 'c' in pg_constraint (and will this be
>>all that's needed) or is it safer to drop and recreate the constraint?
>
>
> I don't think that's going to work, you'd probably need to change the
> function associated with the trigger involved too. It's probably safer to
> do the drop and create.
ok, thanks.
--
- Rich Doughty
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Houssais Hugues | 2006-05-05 09:21:07 | Unify distant Postgres databases |
| Previous Message | Tuukka Norri | 2006-05-05 08:50:05 | Field names and NEW |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Saito | 2006-05-05 09:26:49 | Re: [pgsql-hackers-win32] Build with Visual Studio & MSVC |
| Previous Message | Christopher Kings-Lynne | 2006-05-05 08:23:18 | Re: [pgsql-hackers-win32] Build with Visual Studio & MSVC |