Re: cataloguing NOT NULL constraints

From: Vik Fearing <vik(at)postgresfriends(dot)org>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: cataloguing NOT NULL constraints
Date: 2023-07-24 17:19:48
Message-ID: ca44cc48-786d-d64e-d202-69106c6de85b@postgresfriends.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 7/24/23 18:42, Alvaro Herrera wrote:
> 55490 17devel 3166154=# create table foo (a int constraint nn not null);
> CREATE TABLE
> 55490 17devel 3166154=# alter table foo add constraint nn not null a;
> ERROR: column "a" of table "foo" is already NOT NULL

Surely this should be a WARNING or INFO? I see no reason to ERROR here.
--
Vik Fearing

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pierre Ducroquet 2023-07-24 17:27:36 Re: Inefficiency in parallel pg_restore with many tables
Previous Message Alvaro Herrera 2023-07-24 17:18:54 Re: cataloguing NOT NULL constraints