Re: function with a composite type calling another function - Mission Impossible?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Riccardo G(dot) Facchini" <abief_ag_-postgresql(at)yahoo(dot)com>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: function with a composite type calling another function - Mission Impossible?
Date: 2004-06-02 15:43:59
Message-ID: 24964.1086191039@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

"Riccardo G. Facchini" <abief_ag_-postgresql(at)yahoo(dot)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

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Riccardo G. Facchini 2004-06-02 15:55:15 Re: function with a composite type calling another function - Mission Impossible?
Previous Message Riccardo G. Facchini 2004-06-02 14:52:54 function with a composite type calling another function - Mission Impossible?