Re: [COMMITTERS] pgsql: Mark JSON error detail messages for translation.

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

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

To: Robert Haas <robertmhaas@gmail.com>

Cc: Alvaro Herrera <alvherre@commandprompt.com>, Pg Hackers <pgsql-hackers@postgresql.org>

Date: 2012-06-13T14:35: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 →

Mark JSON error detail messages for translation.
- 36b7e3da17bc 9.2.0 cited

Robert Haas <robertmhaas@gmail.com> writes:
> On Tue, Jun 12, 2012 at 9:52 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> The code for this is as attached. Note that I'd rip out the normal-path
>> tracking of line boundaries; it seems better to have a second scan of
>> the data in the error case and save the cycles in non-error cases.

> Really?!

Um ... do you have a problem with that idea, and if so what?  It would
be considerably more complicated to do it without a second pass.

			regards, tom lane