Re: RAISE concatination/variables in plpgsql - Mailing list pgsql-bugs

From Bruce Momjian
Subject Re: RAISE concatination/variables in plpgsql
Date
Msg-id 200105072352.f47Nqvd11948@candle.pha.pa.us
Whole thread Raw
In response to Re: RAISE concatination/variables in plpgsql  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
> "Henshall, Stuart - WCP" <SHenshall@westcountrypublications.co.uk> writes:
> > In the plpgsql docs it has the following example:
> > RAISE NOTICE ''Id number '' || key || '' not found!'';
> > When I put a function round this statement it gives a compile error at the
> > |.
> > Also when fiddling if I put a variable first it complains about that
> > variable (eg key || '' val.....'')
>
> 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'?

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

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

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: RAISE concatination/variables in plpgsql
Next
From: Bruce Momjian
Date:
Subject: Re: RAISE concatination/variables in plpgsql