Re: pl/pgsql - code review + question

From: "Richard Huxton" <dev(at)archonet(dot)com>
To: "Gary Stainburn" <gary(dot)stainburn(at)ringways(dot)co(dot)uk>, "pgsql-sql" <pgsql-sql(at)postgresql(dot)org>
Subject: Re: pl/pgsql - code review + question
Date: 2001-07-18 16:24:27
Message-ID: 002301c10fa6$1f176820$1001a8c0@archonet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

From: "Gary Stainburn" <gary(dot)stainburn(at)ringways(dot)co(dot)uk>

> My problem now is that when I include the code to handle the record not
being
> there, from the pgsql chapter (section 23.2.3.3) I get the following
errors

Hey - stop that! If everyone starts reading the docs and quoting chapter
refs all we'll be left with are *difficult* questions ;-)

> based of the function below. Can anyone explain why the concat of the
string
> is failing. If I simply "raise exception ''member not found''" all works
fine.

Yep - this one keeps getting me too.

> raise exception ''Member '' || unitno || '' not found'';

RAISE EXCEPTION ''Member % not found'', unitno;

Don't know why the parser for RAISE doesn't like string concat. Possibly
because it maps to the elog() error-reporting function underneath.

- Richard Huxton

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Tom Lane 2001-07-18 16:29:50 Re: pl/pgsql - code review + question
Previous Message Gary Stainburn 2001-07-18 15:56:19 Re: pl/pgsql - code review + question