Re: CTAS not honoring NOT NULL, DEFAULT modifiers - Mailing list pgsql-hackers

From Tom Lane
Subject Re: CTAS not honoring NOT NULL, DEFAULT modifiers
Date
Msg-id 12700.1271684881@sss.pgh.pa.us
Whole thread Raw
In response to Re: CTAS not honoring NOT NULL, DEFAULT modifiers  (Nikhil Sontakke <nikhil.sontakke@enterprisedb.com>)
Responses Re: CTAS not honoring NOT NULL, DEFAULT modifiers  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Nikhil Sontakke <nikhil.sontakke@enterprisedb.com> writes:
> I think the semantics should be pretty ok as is. But I saw another DB
> honoring the NOT NULL modifiers and hence the wonder if there is
> something about this in the standards.

Actually, SQL:2008 does say that if an output column of the SELECT is
known not nullable, then the created table should have the NOT NULL
property for that column.  We don't implement anything about "known not
nullable", though, so I'd view this as a small part of an unimplemented
SQL feature.  The usefulness seems rather debatable anyway.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Nikhil Sontakke
Date:
Subject: Re: CTAS not honoring NOT NULL, DEFAULT modifiers
Next
From: Magnus Hagander
Date:
Subject: Re: walreceiver is uninterruptible on win32