Re: function with a composite type calling another function - Mission Impossible? - Mailing list pgsql-sql

From Tom Lane
Subject Re: function with a composite type calling another function - Mission Impossible?
Date
Msg-id 24964.1086191039@sss.pgh.pa.us
Whole thread Raw
In response to function with a composite type calling another function - Mission Impossible?  ("Riccardo G. Facchini" <abief_ag_-postgresql@yahoo.com>)
Responses Re: function with a composite type calling another function - Mission Impossible?  ("Riccardo G. Facchini" <abief_ag_-postgresql@yahoo.com>)
List pgsql-sql
"Riccardo G. Facchini" <abief_ag_-postgresql@yahoo.com> writes:
> declare my_new_complex complex_number;

> select * from complex_to_complex(my_new_complex) into my_result;

> ERROR:  column "my_new_complex" does not exist

plpgsql doesn't presently cope with passing whole-row variables into SQL
expressions, which is essentially what you've got here.  There's some
chance it will work in time for 7.5.
        regards, tom lane


pgsql-sql by date:

Previous
From: "Riccardo G. Facchini"
Date:
Subject: function with a composite type calling another function - Mission Impossible?
Next
From: "Riccardo G. Facchini"
Date:
Subject: Re: function with a composite type calling another function - Mission Impossible?