Skip site navigation (1) Skip section navigation (2)

Re: Implementation of SQLSTATE and SQLERRM variables

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Neil Conway <neilc(at)samurai(dot)com>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>,Pavel Stehule <stehule(at)kix(dot)fsv(dot)cvut(dot)cz>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Implementation of SQLSTATE and SQLERRM variables
Date: 2005-05-26 03:30:00
Message-ID: 22967.1117078200@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-patches
Neil Conway <neilc(at)samurai(dot)com> writes:
> The second RAISE will report "successful completion". Is this the 
> behavior we want?

No, certainly not --- I was just griping about the same thing.

> Is SQLERRM the best name for that variable? It seems a little obscure to me.

Oracle uses that name.  We had an argument previously about whether we
should use an exactly Oracle-compatible name to deliver a definitely
not Oracle-compatible text string ...

			regards, tom lane

In response to

pgsql-patches by date

Next:From: Neil ConwayDate: 2005-05-26 03:37:55
Subject: Re: pgsql: Add PL/pgSQL SQLSTATE and SQLERRM support
Previous:From: Tom LaneDate: 2005-05-26 03:26:00
Subject: Re: pgsql: Add PL/pgSQL SQLSTATE and SQLERRM support which sets these values

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group