Re: RAISE concatination/variables in plpgsql

Bruce Momjian <pgman@candle.pha.pa.us>

From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: "Henshall, Stuart - WCP" <SHenshall@westcountrypublications.co.uk>, "'pgsql-bugs@postgresql.org'" <pgsql-bugs@postgresql.org>
Date: 2001-05-08T00:08:26Z
Lists: pgsql-bugs

Attachments

> Bruce Momjian <pgman@candle.pha.pa.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@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