> 2009/1/10 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>> Bruce Momjian <bruce(at)momjian(dot)us> writes:
>>> Uh, is this ready to be applied?
>> I don't think any consensus has been reached on changing this behavior.
> I thing, so this is bug - RETURN QUERY has to supply FOR SELECT LOOP
> RETURN NEXT pattern.
> My first patch expected so RETURN QUERY is final statement, so I don't
> solve FOUND variable, but Heikki changed this behave.
> Without correct FOUND behave we can't to use RETURN QUERY for following pattern
> RETURN QUERY some;
> IF FOUND THEN RETURN; END IF;
> RETURN QUERY some_other;
+1. I can't imagine it's good for this to be randomly inconsistent.
In response to
pgsql-hackers by date
|Next:||From: Simon Riggs||Date: 2009-01-10 13:36:13|
|Subject: Re: Synch Rep v5|
|Previous:||From: Bernd Helmle||Date: 2009-01-10 12:39:51|
|Subject: Re: WIP: Automatic view update rules|
pgsql-bugs by date
|Next:||From: Heikki Linnakangas||Date: 2009-01-10 18:30:12|
|Subject: Re: [HACKERS] BUG #4516: FOUND variable does not work after
|Previous:||From: Pavel Stehule||Date: 2009-01-10 08:51:12|
|Subject: Re: [HACKERS] BUG #4516: FOUND variable does not work after RETURN QUERY|