Re: [HACKERS] Implementation of SQLCODE and SQLERRM variables

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Pavel Stehule <stehule(at)kix(dot)fsv(dot)cvut(dot)cz>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, neilc(at)samurai(dot)com, pgsql-patches(at)postgresql(dot)org
Subject: Re: [HACKERS] Implementation of SQLCODE and SQLERRM variables
Date: 2005-04-19 03:59:13
Message-ID: 200504190359.j3J3xDP02838@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches


Guys, is this patch ready for application? I think so, but am not 100%
sure.

---------------------------------------------------------------------------

Pavel Stehule wrote:
> Hello,
>
> I changed code by your and Neil's notes. The name SQLCODE isn't well,
> better is SQLSTATE. It's very similar DB2 variable. I am not sure, so my
> solutions is best. Propably not. It's only particular solution for
> plpgsql. The files plpgsql.sql and plpgsql.out are diffs for regression
> tests.
>
> This patch is implementation of variables SQLERRM and SQLSTATE for plpgsql
> language. Variable SQLSTATE contains five chars PostgreSQL Error Code,
> SQLERRM contains relevant message last catched exception. All variables
> are attached to plpgsql_block and have local scope. Default values are
> '00000' for SQLSTATE and 'Sucessful completion' for SQLERRM.
>
> Regards
>
> Pavel Stehule
>

Content-Description:

[ Attachment, skipping... ]

Content-Description:

[ Attachment, skipping... ]

Content-Description:

[ Attachment, skipping... ]

>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2005-04-19 04:00:40 Re: [WIP] shared locks
Previous Message Bruce Momjian 2005-04-19 03:55:44 Re: [HACKERS] Best practices: MERGE

Browse pgsql-patches by date

  From Date Subject
Next Message Alvaro Herrera 2005-04-19 04:00:40 Re: [WIP] shared locks
Previous Message Bruce Momjian 2005-04-19 03:55:44 Re: [HACKERS] Best practices: MERGE