2010/9/16 Louis-David Mitterrand :
> On Thu, Sep 16, 2010 at 10:12:57AM -0400, Tom Lane wrote:
>> Louis-David Mitterrand 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
On Thu, Sep 16, 2010 at 10:12:57AM -0400, Tom Lane wrote:
> Louis-David Mitterrand 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-st
Louis-David Mitterrand 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 li
Hello
2010/9/16 Louis-David Mitterrand :
> Hi,
>
> I noticed that in a pl/pgsql function FOUND is not set after an
>
> EXECUTE ... into var;
>
> Bug or feature?
>
feature :(
use a GET DIAGNOSTICS statement instead
Regards
Pavel Stehule
> --
> Sent via pgsql-general mailing list (pgsql-
Hi,
I noticed that in a pl/pgsql function FOUND is not set after an
EXECUTE ... into var;
Bug or feature?
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
