Re: PLPGSQL and FOUND stange behaviour after EXECUTE - Mailing list pgsql-bugs

From Tom Lane
Subject Re: PLPGSQL and FOUND stange behaviour after EXECUTE
Date
Msg-id 20422.1096898066@sss.pgh.pa.us
Whole thread Raw
In response to Re: PLPGSQL and FOUND stange behaviour after EXECUTE  (Neil Conway <neilc@samurai.com>)
List pgsql-bugs
Neil Conway <neilc@samurai.com> writes:
> Tom Lane wrote:
>> Yeah, this has been on my to-do list for awhile...

> Ah, ok. Is this something you want to handle, or should I take a look?

Well, it's not *high* on my to-do list; feel free to take a look.

>> One question here is whether Oracle's PL/SQL has a
>> precedent, and if so which way does it point?

> I did some limited testing of this, and it appears that PL/SQL's EXECUTE
> IMMEDIATE modifies SQL%FOUND.

Hm, okay, then we should probably think about doing so too.

If the EXECUTE executes something that's not
SELECT/INSERT/UPDATE/DELETE, should it clear FOUND?  Or leave it alone?

            regards, tom lane

pgsql-bugs by date:

Previous
From: "PostgreSQL Bugs List"
Date:
Subject: BUG #1278: PL/pgSQL: ROWTYPE does not care for droped columns
Next
From: Tom Lane
Date:
Subject: Re: BUG #1278: PL/pgSQL: ROWTYPE does not care for droped columns