| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [SPAM]Re: Questions about 9.0 release note |
| Date: | 2010-04-05 02:10:48 |
| Message-ID: | 201004050210.o352AmQ05766@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > + Exclusion constraints ensure that if any two rows are compared on
> > + the specified columns or expressions using the specified operators,
> > + at least one of these operator comparisons will be false. The syntax is:
>
> Isn't that phrasing outright incorrect? Consider nulls.
Well, doesn't a comparison returning null really behave as false?
Should I reword it as "not true" or "false or null"?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2010-04-05 02:12:51 | Re: pgsql: Add contraint exclusion section to contraint docs. |
| Previous Message | Bruce Momjian | 2010-04-05 02:06:50 | Re: pgindent cleanup |