From: Neil Conway <neilc@samurai.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Pavel Stehule <stehule@kix.fsv.cvut.cz>
Cc: pgsql-patches@postgresql.org
Subject: Re: User's exception plpgsql
Date: Fri, 08 Jul 2005 14:32:16 +1000
Message-ID: <42CE01D0.8060700@samurai.com> (raw)
In-Reply-To: <42CC7EB4.5090201@samurai.com>
References: <Pine.LNX.4.44.0506260904040.21791-200000@kix.fsv.cvut.cz>
<42CBF6AD.9080600@samurai.com>
<26946.1120665361@sss.pgh.pa.us>
<42CC0260.4090407@samurai.com>
<28184.1120669779@sss.pgh.pa.us>
<42CC7EB4.5090201@samurai.com>
Neil Conway wrote:
> Ah, I see. I would be content to allow opt_sqlstate to be either a
> string literal, a T_WORD (predefined error condition), or a TEXT
> variable. If users need to throw a sqlstate that is derived from a SQL
> expression, they can always assign to a TEXT variable and then specify
> that variable to RAISE.
>>> RAISE [ opt_sqlstate ] LEVEL 'fmt' [ , expr ... ]
BTW, do have we reached a consensus on this?
-Neil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: neilc@samurai.com, tgl@sss.pgh.pa.us, stehule@kix.fsv.cvut.cz, pgsql-patches@postgresql.org
Subject: Re: User's exception plpgsql
In-Reply-To: <42CE01D0.8060700@samurai.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox