Re: Bug with FOR ... LOOP and composite types - Mailing list pgsql-bugs

From Oleg Serov
Subject Re: Bug with FOR ... LOOP and composite types
Date
Msg-id cec7c6df0809030733i16ce630euda20292f10f50a4d@mail.gmail.com
Whole thread Raw
In response to Re: Bug with FOR ... LOOP and composite types  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Yes, you are right, with record type working correct;
Thanks

2008/9/2 Tom Lane <tgl@sss.pgh.pa.us>

> "Oleg Serov" <serovov@gmail.com> writes:
> > But if there are some records in t_table and we romove WHERE 1=0, we will
> > have
> > ERROR: wrong record type supplied in RETURN NEXT CONTEXT: PL/pgSQL
> function
> > "t_func" line 9 at RETURN NEXT
>
> I couldn't reproduce that here, at least not with versions newer than
> 8.0.  Maybe you were testing a case that also involved dropped columns?
>
>                        regards, tom lane
>

pgsql-bugs by date:

Previous
From: "Daniel"
Date:
Subject: BUG #4395: internal account lookup faulure
Next
From: "Stephen Cuppett"
Date:
Subject: BUG #4396: Trigger event fired "UPDATE" when "DELETE" happening via foreign key