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

Re: [HACKERS] Implementation of SQLCODE and SQLERRM

From: Pavel Stehule <stehule(at)kix(dot)fsv(dot)cvut(dot)cz>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
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
Date: 2005-04-19 05:00:20
Message-ID: Pine.LNX.4.44.0504190656200.32148-100000@kix.fsv.cvut.cz (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Hello,

I am not sure, I corrected memory problems, I think, but there are some 
changes in plpgsql code. I'l update patch today.

Regards
Pavel Stehule

On Mon, 18 Apr 2005, Bruce Momjian wrote:

> 
> 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
> 
> 


In response to

Responses

pgsql-hackers by date

Next:From: Oleg BartunovDate: 2005-04-19 05:07:35
Subject: Re: Problem with PITR recovery
Previous:From: Oleg BartunovDate: 2005-04-19 04:55:33
Subject: Re: Problem with PITR recovery

pgsql-patches by date

Next:From: Pavel StehuleDate: 2005-04-19 06:09:24
Subject: Re: [HACKERS] Implementation of SQLCODE and SQLERRM
Previous:From: Tom LaneDate: 2005-04-19 04:46:06
Subject: Re: [HACKERS] Implementation of SQLCODE and SQLERRM variables for

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