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

Alvaro Herrera <alvherre@2ndquadrant.com>

From: Alvaro Herrera <alvherre@2ndquadrant.com>

To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>

Cc: Robert Haas <robertmhaas@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, David Steele <david@pgmasters.net>, Bruce Momjian <bruce@momjian.us>, Mark Dilger <mark.dilger@enterprisedb.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>

Date: 2020-01-24T19:08:24Z

Lists: pgsql-hackers

On 2020-Jan-24, Peter Eisentraut wrote:

> I'm not fond of the base64 idea btw., because it seems to sort of penalize
> using non-ASCII characters by making the result completely not human
> readable.  Something along the lines of MIME would be better in that way.
> There are existing solutions to storing data with metadata around it.

You mean quoted-printable?  That works for me.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

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