| From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
|---|---|
| To: | Dann Corbit <DCorbit(at)connx(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Stark <gsstark(at)mit(dot)edu>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Unique Index |
| Date: | 2005-01-20 19:14:05 |
| Message-ID: | 20050120110908.H50057@megazone.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 20 Jan 2005, Dann Corbit wrote:
> It is clear to me that only allowing a single null value will not
> violate the explanation below.
Given two rows in T with one column each
(NULL), (NULL)
Find two rows such that the value of each column in one row is non-null
and equal to the value of the corresponding column in the other row
according to 8.2. If there are no such rows the unique predicate returns
true (ie the constraint is satisfied).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Frank D. Engel, Jr. | 2005-01-20 19:26:43 | Re: Unique Index |
| Previous Message | Marek Lewczuk | 2005-01-20 19:09:27 | Re: Client's variables |