Re: "EXECUTE ... into var" doesn't set FOUND: bug or feature?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Louis-David Mitterrand <vindex+lists-pgsql-general(at)apartia(dot)org>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: "EXECUTE ... into var" doesn't set FOUND: bug or feature?
Date: 2010-09-16 14:12:57
Message-ID: 11620.1284646377@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Louis-David Mitterrand <vindex+lists-pgsql-general(at)apartia(dot)org> writes:
> I noticed that in a pl/pgsql function FOUND is not set after an
> EXECUTE ... into var;
> Bug or feature?

It's behaving as documented:
http://www.postgresql.org/docs/9.0/static/plpgsql-statements.html#PLPGSQL-STATEMENTS-DIAGNOSTICS

Adding EXECUTE to the list of statements that change FOUND would have a
rather large risk of breaking existing plpgsql functions, IMO.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Louis-David Mitterrand 2010-09-16 14:15:24 Re: "EXECUTE ... into var" doesn't set FOUND: bug or feature?
Previous Message Dean Rasheed 2010-09-16 14:08:10 Re: value