| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| Cc: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Documentation tweak for row-valued expressions and null |
| Date: | 2015-11-12 13:23:57 |
| Message-ID: | CA+TgmoZdKqc2cuq6N2TUERVtOr+hiNWVEu_5WJ3dd9NofjBADQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Nov 10, 2015 at 11:10 AM, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> wrote:
> On 7/26/15 8:40 PM, Thomas Munro wrote:
>>
>> I wonder if it might be worth adding a tiny note to the manual to
>> point out that the special logic for "<row-valued-expression> IS [ NOT
>> ] NULL" doesn't apply anywhere else that we handle nulls or talk about
>> [non]-null values in the manual. See attached.
>
> Yes. This is a common point of confusion.
Agreed. But I actually don't know whether Thomas's proposed language
matches the actual behavior in every case.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kouhei Kaigai | 2015-11-12 13:35:01 | Re: CustomScan support on readfuncs.c |
| Previous Message | Brendan Jurd | 2015-11-12 13:21:01 | Re: psql: add \pset true/false |