Re: pgsql: Add PL/pgSQL SQLSTATE and SQLERRM support which sets these values

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Pavel Stehule <stehule(at)kix(dot)fsv(dot)cvut(dot)cz>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Add PL/pgSQL SQLSTATE and SQLERRM support which sets these values
Date: 2005-05-26 06:38:55
Message-ID: 200505260838.55585.peter_e@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-patches

Tom Lane wrote:
> I suggest that what we should do is define SQLSTATE and SQLERRM
> similarly to FOUND: they are procedure-local variables that are
> assigned to by an occurrence of an error. I'd be inclined to make
> them start out NULL, too, not 00000/"Successful completion".

Does Oracle support GET DIAGNOSTICS? If so, couldn't we just use that?
I can't see what good will become of making any slightly useful
information become available as magic variables of some kind.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Pavel Stehule 2005-05-26 07:19:51 Re: pgsql: Add PL/pgSQL SQLSTATE and SQLERRM support
Previous Message Bruce Momjian 2005-05-26 04:11:17 Re: [COMMITTERS] pgsql: Add PL/pgSQL SQLSTATE and SQLERRM support

Browse pgsql-patches by date

  From Date Subject
Next Message Pavel Stehule 2005-05-26 07:16:55 Re: Implementation of SQLSTATE and SQLERRM variables
Previous Message answer-return-1-pgsql-patches=postgresql.org 2005-05-26 05:56:34