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-07 23:52:57 |
Message-ID: | 200105072352.f47Nqvd11948@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
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 [ ... ] ]
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(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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-05-08 00:03:53 | Re: RAISE concatination/variables in plpgsql |
Previous Message | Robert Hentosh | 2001-05-07 22:23:18 | Re: backend dies on 7.1.1 loading large datamodel. |