Search Postgresql Archives

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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Sep 16, 2010 at 10:12:57AM -0400, Tom Lane wrote:
> Louis-David Mitterrand <vindex+lists-pgsql-general@xxxxxxxxxxx> 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.

but is really surprising and non-intuitive, given that 'return query
execute' does.

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux