Message-ID: <ca44cc48-786d-d64e-d202-69106c6de85b@postgresfriends.org>
Date: Mon, 24 Jul 2023 19:19:48 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.13.0
Subject: Re: cataloguing NOT NULL constraints
To: Alvaro Herrera <alvherre@alvh.no-ip.org>,
 Dean Rasheed <dean.a.rasheed@gmail.com>
Cc: Peter Eisentraut <peter@eisentraut.org>,
 pgsql-hackers@lists.postgresql.org
References: <20230724164228.r57cshpl7v2cxqnj@alvherre.pgsql>
From: Vik Fearing <vik@postgresfriends.org>
Content-Language: en-US
In-Reply-To: <20230724164228.r57cshpl7v2cxqnj@alvherre.pgsql>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/ca44cc48-786d-d64e-d202-69106c6de85b%40postgresfriends.org>
Precedence: bulk

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