Ensure all implicit constraints are named

Поиск
Список
Период
Сортировка
От Rod Taylor
Тема Ensure all implicit constraints are named
Дата
Msg-id 1054774083.26169.6.camel@jester
обсуждение исходный текст
Ответы Re: Ensure all implicit constraints are named  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Ensure all implicit constraints are named  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: Ensure all implicit constraints are named  (Bruce Momjian <pgman@candle.pha.pa.us>)
Список pgsql-patches
If they're not, the below causes problems, as the foreign key is added
after the CHECK.  Cluster depends on the index name, so I thought it
wise to ensure all names are available, rather than leaving off the
CONSTRAINT "$n" portion for internally named constraints.

CREATE TABLE jkey (col integer primary key);
CREATE TABLE j (col integer REFERENCES jkey);
ALTER TABLE j ADD CHECK(col > 5);


This is a problem in 7.3 series as well as -Tip.

--
Rod Taylor <rbt@rbt.ca>

PGP Key: http://www.rbt.ca/rbtpub.asc

Вложения

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

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: pgstattuple for schemas
Следующее
От: Rod Taylor
Дата:
Сообщение: Re: pgstattuple for schemas