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

Re: [HACKERS] Implementation of SQLCODE and SQLERRM variables for

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Pavel Stehule <stehule(at)kix(dot)fsv(dot)cvut(dot)cz>, neilc(at)samurai(dot)com,pgsql-patches(at)postgresql(dot)org
Subject: Re: [HACKERS] Implementation of SQLCODE and SQLERRM variables for
Date: 2005-04-19 04:46:06
Message-ID: 16521.1113885966@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Guys, is this patch ready for application?  I think so, but am not 100%
> sure.

I haven't read the code yet, but in any case I still object to choosing
Oracle-like names for Oracle-incompatible functionality.  We need to
settle on better names.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Oleg BartunovDate: 2005-04-19 04:55:33
Subject: Re: Problem with PITR recovery
Previous:From: John HansenDate: 2005-04-19 04:12:23
Subject: Re: Call to build-in operator from new operator

pgsql-patches by date

Next:From: Pavel StehuleDate: 2005-04-19 05:00:20
Subject: Re: [HACKERS] Implementation of SQLCODE and SQLERRM
Previous:From: Michael FuhrDate: 2005-04-19 04:44:02
Subject: Re: How to include "EXCEPTION" handling block in PL/TCL function.

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