public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: Tuomas Leikola <[email protected]>
Cc: [email protected]
Subject: Re: uniqueness and null could benefit from a hint for dba
Date: Fri, 27 Dec 2019 14:49:27 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<CALhc4GAq4H9DSeC7tU6Nkr34zykiA4g8WQ+suWmXSXTDApgHEA@mail.gmail.com>
<[email protected]>
<CALhc4GA=Bxs-w5Fo9x301-sWbBOcC7eQW=wTEEYUQhA1vA_Chg@mail.gmail.com>
<[email protected]>
On Tue, Nov 5, 2019 at 12:13:06PM -0500, Bruce Momjian wrote:
> On Tue, Oct 29, 2019 at 02:00:38PM +0200, Tuomas Leikola wrote:
> > On Thu, Oct 24, 2019 at 5:31 PM Bruce Momjian <[email protected]> wrote:
> >
> > Uh, I am wondering if it is just too details for our docs. Can you
> > think of some text and its location?
> >
> >
> >
> > "Unique indexes on functions can be used to create special types of
> > constraints, like considering unique values equal (coalesce) or only allowing a
> > single unique integer value of a float column (floor). A filtered unique index
> > only enforces uniqueness on the subset of rows that match the filter."
> >
> > I guess this would append to the paragraph "When an index is declared unique,
> > multiple table rows with equal indexed values are not allowed. Null values are
> > not considered equal. A multicolumn unique index will only reject cases where
> > all indexed columns are equal in multiple rows.". Links to the mentioned
> > keywords and concepts would of course be helpful, but not strictly necessary.
> >
> > I also thought of mentioning the caveat of (un)scannability of function or
> > filtered indexes but maybe that is a bit much.
>
> I have reviewed our documentation and found approrpiate places to
> mention your floor() example, and my IS NULL example. Patch attached.
Patch applied back through 9.4. Thanks.
--
Bruce Momjian <[email protected]> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
view thread (7+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: uniqueness and null could benefit from a hint for dba
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox