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

Re: enhanced error fields

From: "anarazel(at)anarazel(dot)de" <andres(at)anarazel(dot)de>
To: Robert Haas <robertmhaas(at)gmail(dot)com>,Peter Geoghegan <peter(at)2ndquadrant(dot)com>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>,Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>,PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>,Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Subject: Re: enhanced error fields
Date: 2013-01-04 17:19:09
Message-ID: 1d25dc31-e98e-47a0-a91a-e884619f7fbc@email.android.com (view raw or flat)
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> schrieb:

>On Sat, Dec 29, 2012 at 4:30 PM, Peter Geoghegan
><peter(at)2ndquadrant(dot)com> wrote:
>> Ascertaining the identity of the object in question perfectly
>> unambiguously, so that you can safely do something like lookup a
>> comment on the object, seems like something way beyond what I'd
>> envisioned for this feature. Why should the comment be useful in an
>> error handler anyway? At best, that seems like a nice-to-have extra
>to
>> me. The vast majority are not even going to think about the ambiguity
>> that may exist. They'll just write:
>>
>> if (constraint_name == "upc")
>>     MessageBox("That is not a valid barcode.");
>
>The people who are content to do that don't need this patch at all.
>They can just apply a regexp to the message that comes back from the
>server and then set constraint_name based on what pops out of the
>regex.  And then do just what you did there.

Easier said than done if you're dealing with pg installations with different lc_messages...

Andres

--- 
Please excuse the brevity and formatting - I am writing this on my mobile phone.


In response to

Responses

pgsql-hackers by date

Next:From: Boszormenyi ZoltanDate: 2013-01-04 17:27:35
Subject: Re: Proposal for Allow postgresql.conf values to be changed via SQL [review]
Previous:From: Robert HaasDate: 2013-01-04 17:12:20
Subject: Re: enhanced error fields

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