Re: Error handling in stored functions/procedures - Mailing list pgsql-general

From Jurgen Defurne
Subject Re: Error handling in stored functions/procedures
Date
Msg-id 20040531072819.2ffa9670.jurgen.defurne@pandora.be
Whole thread Raw
In response to Re: Error handling in stored functions/procedures  (Karsten Hilbert <Karsten.Hilbert@gmx.net>)
Responses Re: Error handling in stored functions/procedures  (Karsten Hilbert <Karsten.Hilbert@gmx.net>)
List pgsql-general
On Sun, 30 May 2004 22:08:10 +0200
Karsten Hilbert <Karsten.Hilbert@gmx.net> wrote:

> > This then, removes the first part of my explanation, and dumps me
> > completely in the second part, which is where the biggest problems
> > reside.
> AFAICT 7.4 does much better error handling (no, you can't
> easily control error handling inside a transaction, though). It
> reports errors in a way that can be parsed a lot better thus
> allowing for fairly easy translation into meaningful user
> messages.

You mean that the default generated error messages contain some more
information I presume, like the table name and the constraint name ?

I think I noticed that already, and since I had time since yesterday
evening, I thought things over and came to the conclusion that this
mechanism at least gives an escape hatch, since it is possible to give a
name to each constraint, and then use this name as an index to get a
proper error message.

Regards,

Jurgen

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Large table search question
Next
From: "Cyril VELTER"
Date:
Subject: Re: Dump 7.1.3->7.4.2