Message-ID: <091fee86-6878-8791-574d-8497e79beb82@postgresfriends.org>
Date: Wed, 6 Sep 2023 01:35:24 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.15.0
Subject: Re: information_schema and not-null constraints
Content-Language: en-US
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>,
 Pg Hackers <pgsql-hackers@lists.postgresql.org>, Tom Lane
 <tgl@sss.pgh.pa.us>, Peter Eisentraut <peter@eisentraut.org>,
 Peter Eisentraut <peter.eisentraut@enterprisedb.com>
References: <202309051715.7ghhtqh76hyw@alvherre.pgsql>
 <d5a08654-33ea-0a12-8f95-e0029f65c75e@postgresfriends.org>
 <CAKFQuwZJmP3bTkc2dRYySy2XXDdxx-xzVQu3sGd8bRtg+GcYwA@mail.gmail.com>
From: Vik Fearing <vik@postgresfriends.org>
In-Reply-To: <CAKFQuwZJmP3bTkc2dRYySy2XXDdxx-xzVQu3sGd8bRtg+GcYwA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/091fee86-6878-8791-574d-8497e79beb82%40postgresfriends.org>
Precedence: bulk

On 9/6/23 00:14, David G. Johnston wrote:
> 
> I'm not all that for either A or B since the status quo seems workable.

Pray tell, how is it workable?  The view does not identify a specific 
constraint because we don't obey the rules on one side and we do obey 
the rules on the other side.  It is completely useless and unworkable.

> Though ideally if the system has unique names per schema then everything
> should just work - having the views produce duplicated information (as
> opposed to nothing) if they are used when the DBA doesn't enforce the
> standard's requirements seems plausible.
Let us not engage in victim blaming.  Postgres is the problem here.
-- 
Vik Fearing