agora inbox for pgsql-sql@postgresql.org
help / color / mirror / Atom feedFrom: 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
Date: Fri, 02 Jun 2017 12:07:17 -0400
Message-ID: <23126.1496419637@sss.pgh.pa.us> (raw)
In-Reply-To: <CAAMZiXBE1TzMRc+XgjXkjrSi65LbT9VAmjYPk_oGqp=znoQRCg@mail.gmail.com>
References: <CAAMZiXCo2PdDXBB0b+uCfdNMk+meGa_7J1y_qm5eumFc9zV-5Q@mail.gmail.com>
<12456.1496413290@sss.pgh.pa.us>
<CAAMZiXBE1TzMRc+XgjXkjrSi65LbT9VAmjYPk_oGqp=znoQRCg@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-sql>
basuraspam - <basuraspam0@gmail.com> writes:
> I agree, it would be better including an example. The "issue" I reported
> is with database views not with tables. Taking your example as base:
> create table foo (f1 int, f2 int not null);
> create view foo_view as select * from foo;
Ah, gotcha. No, sorry, we do not track nullability of view columns as
such.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
view thread (6+ messages) latest in thread
Message-ID: <23126.1496419637@sss.pgh.pa.us>
Permalink: ../23126.1496419637@sss.pgh.pa.us/
Also on: postgresql.org/message-id/23126.1496419637@sss.pgh.pa.us
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, basuraspam0@gmail.com
Subject: Re: Database views metadata always nullable columns
In-Reply-To: <23126.1496419637@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox