Re: Bug in functions returning setof where table has dropped column?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stephen Quinney <stephen(dot)quinney(at)computing-services(dot)oxford(dot)ac(dot)uk>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Bug in functions returning setof where table has dropped column?
Date: 2004-01-10 19:05:57
Message-ID: 11627.1073761557@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Stephen Quinney <stephen(dot)quinney(at)computing-services(dot)oxford(dot)ac(dot)uk> writes:
> I have written a function which shows fairly simply my problem.

> CREATE FUNCTION foobar() RETURNS SETOF wibble AS
> 'SELECT * FROM wibble' LANGUAGE SQL;

> Doing 'select * from foobar();' gives me the error:

> ERROR: query-specified return row and actual function return row do not
> match

Yeah, there are various bits of the system that are still not fully
comfortable with dropped columns, and that's one of them. Not sure
how hard it would be to fix this particular problem.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2004-01-10 19:10:31 Re: postgresql dies without saying why
Previous Message Greg Stark 2004-01-10 18:28:08 Re: psql \d option list overloaded