| From: | Michael Glaesemann <grzm(at)seespotcode(dot)net> |
|---|---|
| To: | Michael Glaesemann <grzm(at)seespotcode(dot)net> |
| Cc: | Germán Hüttemann Arza <ghuttemann(at)cnc(dot)una(dot)py>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Throwing exceptions |
| Date: | 2007-06-26 19:31:54 |
| Message-ID: | 87262DA7-B388-47FA-A5FB-4116D7EE2BC4@seespotcode.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Jun 25, 2007, at 19:01 , Michael Glaesemann wrote:
> The message is just a string. Assign the message to a variable and
> use the variable in place of the message. For example, in PL/pgSQL:
>
> k_error_message := 'Boom! %';
> RAISE EXCEPTION k_error_message, v_foo.id;
I was wrong. The message is not just a string, but you can
interpolate the message text (and other variables) like so:
RAISE EXCEPTION '%, %', k_error_message, v_foo_id;
Michael Glaesemann
grzm seespotcode net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | kdealba@uaaan.mx | 2007-06-26 19:41:49 | Ordering in SELECT statement |
| Previous Message | Bill Moran | 2007-06-26 19:31:14 | Re: growing disk usage problem: alternative solution? |