Re: [PATCH] Generalized JSON output functions
От | Pavel Stehule |
---|---|
Тема | Re: [PATCH] Generalized JSON output functions |
Дата | |
Msg-id | CAFj8pRB=gXh75oQ6xORC1BATQa=F5eRCyDh3QghE_09MgDE_4g@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [PATCH] Generalized JSON output functions ("Shulgin, Oleksandr" <oleksandr.shulgin@zalando.de>) |
Ответы |
Re: [PATCH] Generalized JSON output functions
|
Список | pgsql-hackers |
> > we talking about output - I can imagine, so there is only two possibilities
> > - plain join, and pretty formatted join (but with only one style).
>
> This makes sense. Postgres core really only needs to support the
> minimum styles necessary for core requirements. This means raw
> unformatted json for data productions to client and an appropriate
> formatting for explain. Fancier stuff like a generic formatted is
> fine but those features *belong in an extension*.The thing is - it's not only about whitespace, otherwise I would probably not bother with the generic interface. For my original problem, there is simply no way to do this correctly in an extension w/o copying over all of the logic from json.c, which I have to do right now, would rather not.
Alex
В списке pgsql-hackers по дате отправления: