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

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>

To: Daniel Verite <daniel@manitou-mail.org>

Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, Mark Dilger <mark.dilger@enterprisedb.com>, David Steele <david@pgmasters.net>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>

Date: 2020-01-23T19:34:11Z

Lists: pgsql-hackers

On Thu, Jan 23, 2020 at 2:08 PM Daniel Verite <daniel@manitou-mail.org> wrote:
> It could be CSV, which has this problem already solved,
> is easier to parse than JSON, certainly no less popular,
> and is not bound to a specific encoding.

Sure. I don't think that would look quite as nice visually as what I
proposed when inspected by humans, and our default COPY output format
is tab-separated rather than comma-separated. However, if CSV would be
more acceptable, great.

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

Commits

Add jsonapi.c to Mkvcbuild.pm's @pgcommonallfiles.
- 006b9dcad419 13.0 landed
Move jsonapi.c and jsonapi.h to src/common.
- beb4699091e9 13.0 landed
Move some code from jsonapi.c to jsonfuncs.c.
- 73ce2a03f30b 13.0 landed
Adjust pg_parse_json() so that it does not directly ereport().
- 1f3a021730be 13.0 landed
Remove jsonapi.c's lex_accept().
- 530609aa4263 13.0 landed
Split JSON lexer/parser from 'json' data type support.
- 11b5e3e35d39 13.0 landed
Rationalize code placement between wchar.c, encnames.c, and mbutils.c.
- 5afaa2e42655 13.0 landed
Move wchar.c and encnames.c to src/common/.
- e6afa8918c46 13.0 landed
Update header comments for wchar.c and encnames.c.
- 3d4cb5d6c180 13.0 landed
Make StringInfo available to frontend code.
- 26aaf97b683d 13.0 cited
Use SASLprep to normalize passwords for SCRAM authentication.
- 60f11b87a234 10.0 cited