This came to -general, it seems like a serious problem...

Chris


> -----Original Message-----
> From: pgsql-general-owner@postgresql.org 
> [mailto:pgsql-general-owner@postgresql.org]On Behalf Of Damjan Pipan
> Sent: Tuesday, 28 January 2003 9:36 PM
> To: pgsql-general@postgresql.org
> Subject: [GENERAL] problems with dropped columns 
> 
> 
> Hi!
> 
> I have following problem:
> I have created a table with some fields, then I dropped last 
> field (integer)
> and added
> one extra field (integer). Then I have created a function which returns
> record of table
> type. I have selected a record from table and returned it, but 
> the values in
> last
> field are wrong (missing). It looks like that it takes the dropped field
> instead of the last field.
> 
> Damjan
> 
> CREATE OR REPLACE FUNCTION damjan_test111(integer) RETURNS 
> public.fk_test AS
> '
> DECLARE
> rec fk_test%ROWTYPE;
> siteid ALIAS FOR $1;
> BEGIN
> FOR rec IN SELECT * FROM public.fk_test WHERE
> i = siteid LOOP
> RETURN rec;
> END LOOP;
> END;
> ' LANGUAGE 'plpgsql';
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
> 
> http://archives.postgresql.org
> 


Wed, 29 Jan 2003 15:52:27 +0800
"Christopher Kings-Lynne" <chriskl@familyhealth.com.au>
FW: [GENERAL] problems with dropped columns 
"Christopher Kings-Lynne" <chriskl@familyhealth.com.au> writes:
> This came to -general, it seems like a serious problem...

By and large, there's no support for dropped columns in function result
types.  Feel free to fix it ...

			regards, tom lane

Wed, 29 Jan 2003 11:01:58 -0500
Tom Lane <tgl@sss.pgh.pa.us>
Re: FW: [GENERAL] problems with dropped columns 