| From: | rikard(dot)pavelic(at)zg(dot)htnet(dot)hr |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | BUG #6701: IS NOT NULL doesn't work on complex composites |
| Date: | 2012-06-20 15:53:37 |
| Message-ID: | E1ShNDt-00005k-8t@wrigleys.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 6701
Logged by: Rikard Pavelic
Email address: rikard(dot)pavelic(at)zg(dot)htnet(dot)hr
PostgreSQL version: 9.1.3
Operating system: Windows 7
Description:
create type t AS (i int);
create type complex as (t t, i int);
create table bad(i int, c complex);
insert into bad values(1, null);
insert into bad values(1, ROW(null, 2));
insert into bad values(1, ROW(ROW(1), 2));
select * from bad;
select * from bad where c is null;
--This doesn't work as expected
select * from bad where c is not null;
--Fortunately a workaround
select * from bad where NOT c is null;
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Meskes | 2012-06-20 16:02:42 | Re: BUG #6700: Potential Bug in numeric.c |
| Previous Message | Amit Kapila | 2012-06-20 06:33:47 | Re: BUG #6698: sub-query with join producing out of memory in where clause |