Postgres Pro
Downloads
Home   >   mailing lists

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

From Daniel Verite
Subject Re: making the backend's json parser work in frontend code
Date
Msg-id 6513e2eb-cd9b-4b49-bdee-fe0c99f65b9f@manitou-mail.org
Whole thread Raw
In response to Re: making the backend's json parser work in frontend code  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: making the backend's json parser work in frontend code  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Tree view 
    Robert Haas wrote:

> With the format I proposed, you only have to worry that the
> file name might contain a tab character, because in that format, tab
> is the delimiter

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.


Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: making the backend's json parser work in frontend code
Next
From: Robert Haas
Date:
Subject: Re: making the backend's json parser work in frontend code