From: | <ries(at)jongert(dot)nl> |
---|---|
To: | <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: partial unique constraint |
Date: | 2004-04-06 15:05:37 |
Message-ID: | 001601c41be8$9ece4f60$fd01000a@IT001 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
You should create a functional index here.
Ries
> -----Oorspronkelijk bericht-----
> Van: pgsql-sql-owner(at)postgresql(dot)org
> [mailto:pgsql-sql-owner(at)postgresql(dot)org]Namens Robert Treat
> Verzonden: dinsdag 6 april 2004 16:30
> Aan: pgsql-sql(at)postgresql(dot)org
> Onderwerp: [SQL] partial unique constraint
>
>
> Trying to come up with the proper syntax to meet the
> following criteria:
>
> create table foo (bar integer, baz boolean UNIQUE (bar, baz = true));
>
> note the above syntax is not correct, but should demonstrate what i'm
> trying to do; I want to add a unique constraint such that we
> only allow
> one case of bar and baz = true... i can have unlimited bar and baz =
> false, and there can be multiple bar and baz = true if the bars are
> different... did some doc reading and mail list searching but a valid
> syntax for this seems to be escaping me...
>
> btw I'm pretty sure I could do this with an external trigger, but am
> wondering about a constraint oriented approach
>
> Robert Treat
> --
> Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-04-06 15:17:03 | Re: partial unique constraint |
Previous Message | Stephan Szabo | 2004-04-06 15:05:15 | Re: partial unique constraint |