Re: UNIQUE null treatment option

From: Marko Tiikkaja <marko(at)joh(dot)to>
To: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: UNIQUE null treatment option
Date: 2021-08-27 12:44:37
Message-ID: CAL9smLAP5D3mJ6ijSO-M=459_pSS2d2Eo1vLxAMQi0rD1U1jUg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Aug 27, 2021 at 3:38 PM Peter Eisentraut <
peter(dot)eisentraut(at)enterprisedb(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexey Kondratov 2021-08-27 13:32:02 Re: Supply restore_command to pg_rewind via CLI argument
Previous Message vignesh C 2021-08-27 12:39:16 Re: Added schema level support for publication.