Re: [HACKERS] Implementation of SQLCODE and SQLERRM variables for - Mailing list pgsql-patches

From Pavel Stehule
Subject Re: [HACKERS] Implementation of SQLCODE and SQLERRM variables for
Date
Msg-id Pine.LNX.4.44.0503081003370.13222-400000@kix.fsv.cvut.cz
Whole thread Raw
In response to Re: [HACKERS] Implementation of SQLCODE and SQLERRM variables for  (Pavel Stehule <stehule@kix.fsv.cvut.cz>)
Responses Re: [HACKERS] Implementation of SQLCODE and SQLERRM variables  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: [HACKERS] Implementation of SQLCODE and SQLERRM variables  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-patches
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


Attachment

pgsql-patches by date:

Previous
From: David Fetter
Date:
Subject: Re: [HACKERS] Best practices: MERGE
Next
From: Tom Lane
Date:
Subject: Re: Display Pg buffer cache (WIP)