Horton

Re: enhanced error fields

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "anarazel@anarazel.de" <andres@anarazel.de>
Cc: Robert Haas <robertmhaas@gmail.com>, Peter Geoghegan <peter@2ndquadrant.com>, Stephen Frost <sfrost@snowman.net>, Pavel Stehule <pavel.stehule@gmail.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Alvaro Herrera <alvherre@commandprompt.com>
Date: 2013-01-04T18:07:34Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Create a "sort support" interface API for faster sorting.

"anarazel@anarazel.de" <andres@anarazel.de> writes:
> Robert Haas <robertmhaas@gmail.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