Re: PLPGSQL and FOUND stange behaviour after EXECUTE

From: Neil Conway <neilc(at)samurai(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Константин <beholder(at)mmska(dot)ru>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: PLPGSQL and FOUND stange behaviour after EXECUTE
Date: 2004-10-04 07:19:11
Message-ID: 4160F96F.3060809@samurai.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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?

> 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.

-Neil

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PostgreSQL Bugs List 2004-10-04 11:33:05 BUG #1278: PL/pgSQL: ROWTYPE does not care for droped columns
Previous Message Sean Chittenden 2004-10-04 07:18:28 Denial of service via VACUUM, all backends exit and restart...