Re: options for RAISE statement

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>
Cc: pgsql-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: options for RAISE statement
Date: 2008-05-13 22:14:57
Message-ID: 6999.1210716897@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

"Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> writes:
> I am sending enhanced version of original patch.

Applied with syntax revisions as per pghackers discussion.

I made a couple of other changes too: I took out the restriction against
throwing codes that are category codes, and instead just documented that
that might be a bad idea. I don't see a reason to prohibit that if
people really want to do it. Also, for the few condition names that are
duplicated in plerrcodes.h, I just made it throw the first sqlstate it
finds, rather than complaining. This will work, in the sense that you
can trap the error using the same condition name, and I don't think it's
really important to make the user think about this.

regards, tom lane

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Pavel Stehule 2008-05-13 22:22:24 Re: options for RAISE statement
Previous Message David Fetter 2008-05-13 21:06:39 Re: Making sure \timing is on