Re: [GENERAL] Adding ON UPDATE CASCADE to an existing foreign key

Поиск
Список
Период
Сортировка
От Jim C. Nasby
Тема Re: [GENERAL] Adding ON UPDATE CASCADE to an existing foreign key
Дата
Msg-id 20060504203825.GE97354@pervasive.com
обсуждение исходный текст
Список pgsql-hackers
Moving to -hackers...

On Thu, May 04, 2006 at 09:17:31AM -0700, 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.

It would be nice if there was a way to do this that didn't involve
re-validating all the data. Can this be added as a TODO?
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: patch review, please: Autovacuum/Vacuum times via stats.
Следующее
От: "Jim C. Nasby"
Дата:
Сообщение: [bruno@wolff.to: Re: [GENERAL] 8.1.4 anytime soon?]