Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f6IGU4a38573 for ; Wed, 18 Jul 2001 12:30:04 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id f6IGToC05410; Wed, 18 Jul 2001 12:29:51 -0400 (EDT) To: Gary Stainburn cc: "pgsql-sql" Subject: Re: pl/pgsql - code review + question In-reply-to: <0107181624100B.11978@gary.ringways.co.uk> References: <01071815102309.11978@gary.ringways.co.uk> <0107181624100B.11978@gary.ringways.co.uk> Comments: In-reply-to Gary Stainburn message dated "Wed, 18 Jul 2001 16:24:10 +0100" Date: Wed, 18 Jul 2001 12:29:50 -0400 Message-ID: <5407.995473790@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200107/251 X-Sequence-Number: 4048 Gary Stainburn writes: > 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 based of the function below. IIRC, there's an erroneous example in the 7.1 plpgsql documentation: RAISE doesn't actually accept an expression for its string parameter, only a literal (and only simple variables for the additional parameters). So you need to write something like raise exception ''Member % not found'', unitno; regards, tom lane