Re: UNIQUE null treatment option - Mailing list pgsql-hackers

From Marko Tiikkaja
Subject Re: UNIQUE null treatment option
Date
Msg-id CAL9smLAP5D3mJ6ijSO-M=459_pSS2d2Eo1vLxAMQi0rD1U1jUg@mail.gmail.com
Whole thread Raw
In response to UNIQUE null treatment option  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Responses Re: UNIQUE null treatment option  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
List pgsql-hackers
On Fri, Aug 27, 2021 at 3:38 PM Peter Eisentraut <peter.eisentraut@enterprisedb.com> wrote:
In the SQL:202x draft, this
has been formalized by making this implementation-defined and adding
an option on unique constraint definitions UNIQUE [ NULLS [NOT]
DISTINCT ] to choose a behavior explicitly.

The CREATE UNIQUE INDEX syntax extension is not from the standard,
it's my own invention.

For the unique index syntax, should this be selectable per column/expression, rather than for the entire index as a whole?


.m

pgsql-hackers by date:

Previous
From: vignesh C
Date:
Subject: Re: Added schema level support for publication.
Next
From: Alexey Kondratov
Date:
Subject: Re: Supply restore_command to pg_rewind via CLI argument