"David G. Johnston" <david.g.johnston@gmail.com> writes: > I am thinking now that the failure to include NULLS [NOT] DISTINCT in the > CREATE TABLE syntax is an oversight that needs to be fixed. It just > doesn't make sense to have the two commands expose different features.
It looks to me like it was pretty intentional, because both CREATE and ALTER TABLE let you write UNIQUE NULLS NOT DISTINCT but not PRIMARY KEY NULLS NOT DISTINCT. That doesn't seem like an oversight.
OK, that was me tunnel-visioned on the "index_parameters" syntax section where INCLUDE, etc... are listed and not seeing it there.
So, don't document that PRIMARY KEY accepts the NULLS [NOT] DISTINCT but make it do so anyway?
