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

Re: Error codes revisited

From: Mike Mascari <mascarm(at)mascari(dot)com>
To: Christoph Haller <ch(at)rodos(dot)fzk(dot)de>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Error codes revisited
Date: 2003-03-06 08:41:03
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Christoph Haller wrote:
>>Given the repeatedly-asked-for functionalities (like error codes)
>>for which the stopper has been the long-threatened protocol revision,
>>I'd think it might be boring, but would hardly be thankless. Heck, I'd
>>expect a few whoops of joy around the lists.
> Yes. Error codes would be great.

Particularly if they arrive in conjunction with Bruce's "Nested 
Transaction" implementation. I image many people would like to 
create a subtransaction, which, if it fails due to a unique key 
violation, could recover and perform an update.

I'd personally like some way of mapping RI-related messages into 
  application-specific, perhaps localized, messages. Error codes 
will provide a nice starting point. Will the action and object 
upon which the action is being attempted also be available?

Mike Mascari

In response to

pgsql-hackers by date

Next:From: Justin CliftDate: 2003-03-06 13:23:08
Subject: site outage
Previous:From: btoberDate: 2003-03-06 08:23:14
Subject: Re: My contract has been renewed

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