Re: bogus error message for ALTER TABLE ALTER CONSTRAINT
От | Tom Lane |
---|---|
Тема | Re: bogus error message for ALTER TABLE ALTER CONSTRAINT |
Дата | |
Msg-id | 195582.1741125028@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | bogus error message for ALTER TABLE ALTER CONSTRAINT (Álvaro Herrera <alvherre@alvh.no-ip.org>) |
Ответы |
Re: bogus error message for ALTER TABLE ALTER CONSTRAINT
|
Список | pgsql-hackers |
=?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@alvh.no-ip.org> writes: > I just discovered that trying to set a foreign key as NO INHERIT in > ALTER TABLE ALTER CONSTRAINT returns an absurd error message: > create table pk (a int primary key); > create table fk (a int references pk); > alter table fk alter constraint fk_a_fkey deferrable, alter constraint fk_a_fkey no inherit; > ERROR: ALTER CONSTRAINT statement constraints cannot be marked NO INHERIT > The explanation is that somebody misunderstood what must be given to > processCASbits in 2013. The intended message is: > ERROR: FOREIGN KEY constraints cannot be marked NO INHERIT Hmm. I agree that "ALTER CONSTRAINT statement" is off the mark here, but I'm not convinced that "FOREIGN KEY" is entirely on-point either. The grammar has no way of knowing what kind of constraint is being targeted. I do see that ATExecAlterConstraint currently rejects every other kind of constraint, but do we need to think of a more generic phrase? regards, tom lane
В списке pgsql-hackers по дате отправления: