From: Tom Lane <tgl@sss.pgh.pa.us>
To: basuraspam - <basuraspam0@gmail.com>
cc: pgsql-sql@postgresql.org
Subject: Re: Database views metadata always nullable columns
In-reply-to: 
 <CAAMZiXCo2PdDXBB0b+uCfdNMk+meGa_7J1y_qm5eumFc9zV-5Q@mail.gmail.com>
References: 
 <CAAMZiXCo2PdDXBB0b+uCfdNMk+meGa_7J1y_qm5eumFc9zV-5Q@mail.gmail.com>
Comments: In-reply-to basuraspam - <basuraspam0@gmail.com>
	message dated "Fri, 02 Jun 2017 16:11:25 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <12455.1496413290.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 02 Jun 2017 10:21:30 -0400
Message-ID: <12456.1496413290@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-sql-owner@postgresql.org

basuraspam - <basuraspam0@gmail.com> writes:
>    Doing some automatic metadata parsing job against postgresql schema I
> just find that database views always shown all its column as nullable, it
> doesn't matter what are the constraints in the original table columns used
> as source to create the view.
> I just checked it against infomation_schema and pg_attribute with the same
> result.

regression=3D# create table foo (f1 int, f2 int not null);
CREATE TABLE
regression=3D# select column_name, is_nullable from information_schema.colu=
mns where table_name =3D 'foo';
 column_name | is_nullable=20
-------------+-------------
 f1          | YES
 f2          | NO
(2 rows)

regression=3D# select attname,attnotnull from pg_attribute where attrelid =
=3D 'foo'::regclass and attnum > 0;
 attname | attnotnull=20
---------+------------
 f1      | f
 f2      | t
(2 rows)

So I don't see anything particularly broken here.  Maybe you should
provide some concrete examples rather than making sweeping claims.

			regards, tom lane


--=20
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql