Re: RAISE concatination/variables in plpgsql

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Henshall, Stuart - WCP" <SHenshall(at)westcountrypublications(dot)co(dot)uk>
Cc: "'pgsql-bugs(at)postgresql(dot)org'" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: RAISE concatination/variables in plpgsql
Date: 2001-04-19 18:08:08
Message-ID: 21831.987703688@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-bugs

"Henshall, Stuart - WCP" <SHenshall(at)westcountrypublications(dot)co(dot)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 [ ... ] ]
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.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Eisentraut 2001-04-19 19:22:02 Re: BUG??, fault in POSTMASTER when using GMAKE
Previous Message Pimenov Yuri 2001-04-19 17:44:43 locale & glibc-2.2.2