diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2006-09-28 20:51:43 +0000 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2006-09-28 20:51:43 +0000 |
| commit | f213131f2024bcb85aea7d2a7dfadef6a0ee1b31 (patch) | |
| tree | 090a85694dfd64f735732bc49b8489835186d83b /src/backend/utils/adt/arrayfuncs.c | |
| parent | d3aa4a8e33bee5e5274615cfd461aac810d7bbc1 (diff) | |
| download | postgresql-f213131f2024bcb85aea7d2a7dfadef6a0ee1b31.tar.gz postgresql-f213131f2024bcb85aea7d2a7dfadef6a0ee1b31.zip | |
Fix IS NULL and IS NOT NULL tests on row-valued expressions to conform to
the SQL spec, viz IS NULL is true if all the row's fields are null, IS NOT
NULL is true if all the row's fields are not null. The former coding got
this right for a limited number of cases with IS NULL (ie, those where it
could disassemble a ROW constructor at parse time), but was entirely wrong
for IS NOT NULL. Per report from Teodor.
I desisted from changing the behavior for arrays, since on closer inspection
it's not clear that there's any support for that in the SQL spec. This
probably needs more consideration.
Diffstat (limited to 'src/backend/utils/adt/arrayfuncs.c')
0 files changed, 0 insertions, 0 deletions