Re: ENABLE/DISABLE CONSTRAINT NAME

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: ENABLE/DISABLE CONSTRAINT NAME
Дата
Msg-id 1380076858.1440.23.camel@vanquo.pezone.net
обсуждение исходный текст
Ответ на Re: ENABLE/DISABLE CONSTRAINT NAME  (Bernd Helmle <mailings@oopsware.de>)
Ответы Re: ENABLE/DISABLE CONSTRAINT NAME  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
On Tue, 2013-09-24 at 11:58 +0200, Bernd Helmle wrote:
> Hmm not sure i understand this argument either: this patch doesn't
> allow disabling a primary key. It only supports FKs and CHECK
> constraints explicitly. 

Well, as soon as the patch for cataloging not-null constraints as check
constraints is available, it will be possible to create views that
depend functionally on check constraints.  Then you'll have the same
problem there.

It's also not clear why this patch only supports foreign keys and check
constraints.  Maybe that's what was convenient to implement, but it's
not a principled solution to the general issue that constraints can be
involved in dependencies.




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

Предыдущее
От: Peter Geoghegan
Дата:
Сообщение: Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE
Следующее
От: Peter Eisentraut
Дата:
Сообщение: Re: UTF8 national character data type support WIP patch and list of open issues.