Re: Make PG's "NOT NULL"s and attnotnull ("is_nullable") conform to SQL-2011
David G. Johnston <david.g.johnston@gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
To: Vitaly Burovoy <vitaly.burovoy@gmail.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2016-05-04T06:11:34Z
Lists: pgsql-hackers
On Monday, February 8, 2016, Vitaly Burovoy <vitaly.burovoy@gmail.com> wrote: > > 12. At the same time in (subcl. 4.13) mentioned there can be "at least > one NNC" (may be via inheritance?). > > This is a bit hard to reason about given that our implementation of inheritance is non-standard. Are we close to the standard semantics with regard to this particular dynamic? David J.
Commits
-
Catalog NOT NULL constraints
- e056c557aef4 16.0 landed
-
Improve documentation about PRIMARY KEY constraints.
- c477e84fe247 9.6.0 cited