Re: automatically generating node support functions

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: automatically generating node support functions
Date: 2022-04-19 14:53:45
Message-ID: 31d17e34-afc7-b9fc-c14a-725547ce24ed@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 19.04.22 16:39, Tom Lane wrote:
> Maybe we should fix JsonPathSpec to be less creative while we
> still can? It's not real clear to me why that typedef even exists,
> rather than using a String node, or just a plain char * field.

Yeah, let's get rid of it and use char *.

I see in JsonCommon a pathspec is converted to a String node, so it's
not like JsonPathSpec is some kind of universal representation of the
thing anyway.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2022-04-19 14:54:30 Re: error handling in pqRowProcessor broken
Previous Message Israa Odeh 2022-04-19 14:47:10 GSoC Proposal Submission.