| From: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michel Pelletier <pelletier(dot)michel(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Proposal to use JSON for Postgres Parser format |
| Date: | 2022-10-31 12:45:55 |
| Message-ID: | CAPpHfduCg-oRjYQr4jhwtXgvPiLOpqRG7bmXOTkGZb0e52LUEQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Oct 28, 2022 at 4:27 PM Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> On 2022-10-27 Th 19:38, Andres Freund wrote:
> > Hi,
> >
> > On 2022-09-19 22:29:15 -0400, Tom Lane wrote:
> >> Maybe a compromise could be found whereby we provide a conversion function
> >> that converts whatever the catalog storage format is to some JSON
> >> equivalent. That would address the needs of external code that doesn't want
> >> to write a custom parser, while not tying us directly to JSON.
> > +1
> >
>
>
> Agreed.
+1
Michel, it seems that you now have a green light to implement node to
json function.
------
Regards,
Alexander Korotkov
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Alekseev | 2022-10-31 12:49:37 | Re: ResourceOwner refactoring |
| Previous Message | Simon Riggs | 2022-10-31 12:43:13 | Re: Code checks for App Devs, using new options for transaction behavior |