| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "anarazel(at)anarazel(dot)de" <andres(at)anarazel(dot)de> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Geoghegan <peter(at)2ndquadrant(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, 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 18:07:34 |
| Message-ID: | 22212.1357322854@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"anarazel(at)anarazel(dot)de" <andres(at)anarazel(dot)de> writes:
> Robert Haas <robertmhaas(at)gmail(dot)com> schrieb:
>> 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...
Exactly. To my mind, the *entire* point of this patch is to remove the
need for people to try to dig information out of potentially-localized
message strings. It's not clear to me that we have to strain to provide
information that isn't in the currently-reported messages --- we are
only trying to make it easier for client-side code to extract the
information it's likely to need.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2013-01-04 18:07:37 | Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database" |
| Previous Message | Boszormenyi Zoltan | 2013-01-04 17:36:43 | Re: Proposal for Allow postgresql.conf values to be changed via SQL [review] |