From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
To: | "Hackers (PostgreSQL)" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | SRF/dropped column bug |
Date: | 2004-08-08 06:10:44 |
Message-ID: | 4115C3E4.2070607@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I see this behavior with CVS tip:
CREATE TABLE wibble (a integer, b integer);
INSERT INTO wibble VALUES (1,1);
ALTER TABLE wibble ADD COLUMN c BIGINT;
UPDATE wibble SET c = b;
ALTER TABLE wibble DROP COLUMN b;
ALTER TABLE wibble RENAME c TO b;
CREATE FUNCTION foobar() RETURNS SETOF wibble AS
'SELECT * FROM wibble' LANGUAGE SQL;
regression=# SELECT * FROM wibble;
a | b
---+---
1 | 1
(1 row)
regression=# select * from foobar();
a | b
---+---
1 |
(1 row)
The example comes from a complaint in January 2004, at which time it
would instead throw an ERROR:
ERROR: query-specified return row and actual function return row do not
match
I'll start digging into this, but any hints on where to look would be
greatly appreciated.
Thanks,
Joe
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-08-08 06:22:15 | Re: SRF/dropped column bug |
Previous Message | Joe Conway | 2004-08-08 06:04:58 | Re: beta time |