Re: Make PG's "NOT NULL"s and attnotnull ("is_nullable") conform to SQL-2011
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: Vitaly Burovoy <vitaly.burovoy@gmail.com>,
PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2016-05-04T14:58:30Z
Lists: pgsql-hackers
"David G. Johnston" <david.g.johnston@gmail.com> writes: > This is a bit hard to reason about given that our implementation of > inheritance is non-standard. Yeah, that's a fairly key point. We've solved those problems with respect to inherited CHECK constraints, and it seems like what we ought to do with NOT NULL is make it work the same as CHECK, rather than invent some new concepts. regards, tom lane
Commits
-
Catalog NOT NULL constraints
- e056c557aef4 16.0 landed
-
Improve documentation about PRIMARY KEY constraints.
- c477e84fe247 9.6.0 cited