Re: making the backend's json parser work in frontend code

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: David Steele <david(at)pgmasters(dot)net>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: making the backend's json parser work in frontend code
Date: 2020-01-22 00:23:56
Message-ID: CA+TgmoaiJZWt0mfi8MmOyrMoQf_MhNGiE6GjxFh-PSPXbFf+ng@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jan 21, 2020 at 5:34 PM David Steele <david(at)pgmasters(dot)net> wrote:
> Though, throw_a_json_error() is not my favorite name. Perhaps
> json_ereport()?

That name was deliberately chosen to be dumb, with the thought that
readers would understand it was to be replaced at some point before
this was final. It sounds like it wasn't quite dumb enough to make
that totally clear.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2020-01-22 00:41:04 Re: Increase psql's password buffer size
Previous Message David Fetter 2020-01-22 00:06:21 Re: Minor issues in .pgpass