Re: RAISE concatination/variables in plpgsql

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Henshall, Stuart - WCP" <SHenshall(at)westcountrypublications(dot)co(dot)uk>, "'pgsql-bugs(at)postgresql(dot)org'" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: RAISE concatination/variables in plpgsql
Date: 2001-05-08 00:08:26
Message-ID: 200105080008.f4808Q813238@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> >> Looking at the plpgsql code, it's clear that what's actually implemented
> >> is
> >> RAISE level string-literal [ , variable [ , variable [ ... ] ]
>
> > I see the current docs showing:
>
> > RAISE level 'format' [, identifier [...]];
>
> > Is this acceptable? Should 'identifier' be 'variable'?
>
> Probably. And 'format' is even more misleading, since it implies that
> you write a printf-like format string, which you do not. The output is
> just the concatenation of the literal and the variable values.

Updated with patch attached.

>
> >> which is pretty bletcherous; seems like it should accept a list of
> >> expressions instead. But for 7.1, I guess this is a documentation bug
> >> rather than something to change in the code.
>
> > Do I need a TODO item here?
>
> It seems in need of fixing to me ...

TODO updated with:

* Allow Pl/PgSQL's RAISE function to take expressions

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

Attachment Content-Type Size
unknown_filename text/plain 1.1 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2001-05-08 00:15:22 Re: RAISE concatination/variables in plpgsql
Previous Message Tom Lane 2001-05-08 00:05:17 Re: backend dies on 7.1.1 loading large datamodel.