Re: enhanced error fields

Peter Geoghegan <peter@2ndquadrant.com>

From: Peter Geoghegan <peter@2ndquadrant.com>

To: Stephen Frost <sfrost@snowman.net>

Cc: Tom Lane <tgl@sss.pgh.pa.us>, Pavel Stehule <pavel.stehule@gmail.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Alvaro Herrera <alvherre@commandprompt.com>

Date: 2012-12-30T04:21:31Z

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 →

Create a "sort support" interface API for faster sorting.
- c6e3ac11b60a 9.2.0 cited

On 30 December 2012 03:32, Stephen Frost <sfrost@snowman.net> wrote:
> Err.  I intended to say "I really don't think what I sketched out, or
> something similar, would be that unlikely to happen", or something along
> those lines.  Apologies for the confusion.

Almost anything can be misused.

If you're going to insist that I hack a bunch of mechanism into this
patch so that the user can unambiguously identify each constraint
object, I'll do that. However, that's more code, and more complexity,
that will have to be documented, for just next to no practical benefit
that I can see.

-- 
Peter Geoghegan       http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services