Re: cannot assign non-composite value to a row variable

Updating did solve the problem. Thanks.

On Fri, Jun 4, 2010 at 11:23 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl> writes:
> > I'm pretty sure you have a naming conflict.
>
> Yeah. Specifically, the given example looks like it would try to assign
> a null to the target variable, since it'd be taking the null value of a
> different variable instead of a value from the intended source.
>
> I believe the bizarre error message is coming from a plpgsql bug that we
> fixed in 8.4.3, which basically was that assigning a null to a composite
> variable would fail in some cases. If you weren't shooting yourself in
> the foot with naming conflicts, you might not trip over that case ...
> but an update to 8.4.recent wouldn't be a bad idea anyway.
>
> regards, tom lane
>

--
Eliot Gable

"We do not inherit the Earth from our ancestors: we borrow it from our
children." ~David Brower

"I decided the words were too conservative for me. We're not borrowing from
our children, we're stealing from them--and it's not even considered to be a
crime." ~David Brower

"Esse oportet ut vivas, non vivere ut edas." (Thou shouldst eat to live; not
live to eat.) ~Marcus Tullius Cicero