Re: [SPAM]Re: Questions about 9.0 release note

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-06 02:16:26
Message-ID: 201004060216.o362GQ714383@momjian.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > 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"?
>
> Either one.

I used "false or null".

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

Attachment Content-Type Size
/rtmp/diff text/x-diff 969 bytes

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Joseph Adams 2010-04-06 03:50:14 Re: Proposal: Add JSON support
Previous Message Giles Lean 2010-04-06 01:10:18 Re: make check hangs in alpha5