Hello All,
Where can I find patch for SQLERRM/SQLSTATE variable implementation?.
I am using Postgres 8.0.1.
Its very urgent.... because I have an assignment of Porting Oracle's PL?SQL
into PL/pgSQL.
Thanks
Dinesh Pandey
-----Original Message-----
From: pgsql-patches-owner@postgresql.org
[mailto:pgsql-patches-owner@postgresql.org] On Behalf Of Bruce Momjian
Sent: Tuesday, April 19, 2005 9:29 AM
To: Pavel Stehule
Cc: Tom Lane; neilc@samurai.com; pgsql-patches@postgresql.org
Subject: Re: [PATCHES] [HACKERS] Implementation of SQLCODE and SQLERRM
variables
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@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org