Postgres Pro
Downloads
Home   >   mailing lists

Re: making the backend's json parser work in frontend code - Mailing list pgsql-hackers

From Robert Haas
Subject Re: making the backend's json parser work in frontend code
Date
Msg-id CA+TgmoaiJZWt0mfi8MmOyrMoQf_MhNGiE6GjxFh-PSPXbFf+ng@mail.gmail.com
Whole thread Raw
In response to Re: making the backend's json parser work in frontend code  (David Steele <david@pgmasters.net>)
Responses Re: making the backend's json parser work in frontend code  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Tree view 
On Tue, Jan 21, 2020 at 5:34 PM David Steele <david@pgmasters.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

pgsql-hackers by date:

Previous
From: David Fetter
Date:
Subject: Re: Minor issues in .pgpass
Next
From: David Fetter
Date:
Subject: Re: Increase psql's password buffer size