Re: EXCLUDE constraint with not equals - Mailing list pgsql-general

From Kai Groner
Subject Re: EXCLUDE constraint with not equals
Date
Msg-id CALiRuxm22LXHo2YjQ7HEWsEmWeSSc=xg1Kr8ZYo83=LzuKy3Rg@mail.gmail.com
Whole thread Raw
In response to Re: EXCLUDE constraint with not equals  (Emre Hasegeli <emre@hasegeli.com>)
Responses Re: EXCLUDE constraint with not equals  (Kai Groner <kai@gronr.com>)
List pgsql-general
On Tue, Mar 3, 2015 at 3:27 AM, Emre Hasegeli <emre@hasegeli.com> wrote:
>
> > Given the following table, I would like to ensure that all the rows for an
> > email that have a user defined map to the same user.
> >
> > CREATE TABLE person (
> >   id INTEGER PRIMARY KEY,
> >   user TEXT,
> >   email TEXT NOT NULL);
>
> You can use the btree_gist extension from contrib:
>
> CREATE EXTENSION btree_gist;
>
> CREATE TABLE person (
>   id INTEGER PRIMARY KEY,
>   "user" TEXT,
>   email TEXT NOT NULL,
>   EXCLUDE USING gist (email WITH =, "user" WITH <>)
>     WHERE ("user" IS NOT NULL));

Thanks, Emre.  The btree_gist extension seems to be just what I was looking for.

I found it necessary to add the gist_text_ops opclass for the inequality:

CREATE TABLE person (
  id INTEGER PRIMARY KEY,
  "user" TEXT,
  email TEXT NOT NULL,
  EXCLUDE USING gist (email WITH =, "user" gist_text_ops WITH <>)
    WHERE ("user" IS NOT NULL));

Is that expected?



Kai

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Copy Data between different databases
Next
From: gmb
Date:
Subject: Re: Performance on DISABLE TRIGGER