Re: [PATCH] Generalized JSON output functions - Mailing list pgsql-hackers

From Shulgin, Oleksandr
Subject Re: [PATCH] Generalized JSON output functions
Date
Msg-id CACACo5TwSi+X7Nxo7_qhkJO3MuBMgt8rYFWKaENtYYdZkiLuOw@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Generalized JSON output functions  (Merlin Moncure <mmoncure@gmail.com>)
Responses Re: [PATCH] Generalized JSON output functions  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
<p dir="ltr">> > we talking about output - I can imagine, so there is only two possibilities<br /> > > -
plainjoin, and pretty formatted join (but with only one style).<br /> ><br /> > This makes sense.  Postgres core
reallyonly needs to support the<br /> > minimum styles necessary for core requirements.  This means raw<br /> >
unformattedjson for data productions to client and an appropriate<br /> > formatting for explain.  Fancier stuff
likea generic formatted is<br /> > fine but those features *belong in an extension*.<p dir="ltr">The thing is - it's
notonly about whitespace, otherwise I would probably not bother with the generic interface. For my original problem,
thereis simply no way to do this correctly in an extension w/o copying over all of the logic from json.c, which I have
todo right now, would rather not.<p dir="ltr">Alex<br /> 

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: TABLESAMPLE doesn't actually satisfy the SQL spec, does it?
Next
From: Pavel Stehule
Date:
Subject: Re: [PATCH] Generalized JSON output functions