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: | 3E67099F.2000407@mascari.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
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
mascarm(at)mascari(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Clift | 2003-03-06 13:23:08 | Postgresql.org site outage |
Previous Message | btober | 2003-03-06 08:23:14 | Re: My contract has been renewed |