Neil Conway <neilc@samurai.com> writes:
> ... One way to fix this would be to reimplement EXECUTE to
> be essentially `eval': it would take an arbitrary string and execute it
> as a PL/pgSQL statement. That would fix the FOUND problem, and also give
> us EXECUTE INTO in one fell swoop.
Yeah, this has been on my to-do list for awhile...
> (Rather than reimplementing EXECUTE, we might want to add this
> functionality as a new command -- "EVAL" might be a good name for it.)
That would give cover for the inevitable backward-compatibility
arguments anyway. One question here is whether Oracle's PL/SQL has a
precedent, and if so which way does it point?
regards, tom lane
