BUG #2839: after record with NULL field, query result is wrong

From: "Vladimir" <dvs(at)fon(dot)kamchatka(dot)ru>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #2839: after record with NULL field, query result is wrong
Date: 2006-12-19 04:56:56
Message-ID: 200612190456.kBJ4uuf4010495@wwwmaster.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


The following bug has been logged online:

Bug reference: 2839
Logged by: Vladimir
Email address: dvs(at)fon(dot)kamchatka(dot)ru
PostgreSQL version: 8.1.3
Operating system: FreeBSD
Description: after record with NULL field, query result is wrong
Details:

create table tst (a int[]);
insert into tst values ('{1}'); -- (1)
insert into tst values (null);
insert into tst values ('{2}'); -- (3)
select z.a from tst z where exists (select 1 from
(
select generate_series(1,1) as s,* from (select z.a as arr0) qq
) q
where (q.arr0[q.s] is null) );
a
-----

{2}
(2 rows)

-- What difference between (1) and (3) records?
-- really, my query more complex (auto generated) and table has many
columns, wrong rows return after row where tested field is null

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Thomas H. 2006-12-19 05:01:46 Re: No error when FROM is missing in subquery
Previous Message Jaime Casanova 2006-12-19 04:09:44 Re: No error when FROM is missing in subquery