| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David E(dot) Wheeler" <david(at)kineticode(dot)com>, Brendan Jurd <direvus(at)gmail(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: When is a record NULL? |
| Date: | 2009-07-24 20:29:34 |
| Message-ID: | 407d949e0907241329x3d495e65yecb57e82af4e86fd@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jul 24, 2009 at 7:49 PM, Merlin Moncure<mmoncure(at)gmail(dot)com> wrote:
> Still, why:
>
> *) is select null::foo is distinct from (null, null)::foo; true?
> (null should not be distinct from null)
>
> *) does (null, null) allow STRICT functions to execute?
>
> *) is (null, null)::text not null?
These are all good questions. Are you interested in checking what the
spec says should happen in these cases?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2009-07-24 20:53:42 | Re: SE-PostgreSQL Specifications |
| Previous Message | Peter Eisentraut | 2009-07-24 20:24:28 | Re: Proposal: More portable way to support 64bit platforms |