Re: plpgsql raise - parameters can be expressions

From: Neil Conway <neilc(at)samurai(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Pavel Stehule <stehule(at)kix(dot)fsv(dot)cvut(dot)cz>, pgsql-patches(at)postgresql(dot)org
Subject: Re: plpgsql raise - parameters can be expressions
Date: 2005-06-14 00:45:46
Message-ID: 42AE28BA.3010005@samurai.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Tom Lane wrote:
> That doesn't bother me either, seeing that an undefined variable isn't
> detected at compile time anywhere else. However, fixing the SQLSTATE
> tests by removing them doesn't seem like a great solution ...

Yeah, true, I can just invoke the function to trigger the undefined
variable error.

> Actually, the reason I didn't do something about RAISE in 8.0 was that
> I thought we should reconsider the whole design of the statement

The ensuing discussion on this sounds good to me; should I apply Pavel's
RAISE patch now, or wait for the subsequent work on specifying a
particular SQLSTATE?

-Neil

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2005-06-14 01:01:00 Re: plpgsql raise - parameters can be expressions
Previous Message Neil Conway 2005-06-14 00:13:25 Re: pl/pgsql dump tree cleanup