Re: [RFC] nodeToString format and exporting the SQL parser

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Tharp <gxti(at)partiallystapled(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [RFC] nodeToString format and exporting the SQL parser
Date: 2010-04-02 20:16:28
Message-ID: 3669.1270239388@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Michael Tharp <gxti(at)partiallystapled(dot)com> writes:
> Due to popular demand on #postgresql (by which I mean David Fetter), I
> have been spending a little time making the internal SQL parser
> available to clients via a C-language SQL function. The function itself
> is extremely simple: just a wrapper around a call to raw_parser followed
> by nodeToString.

What exactly is the use-case for this? Generally speaking I'm against
exposing that data structure to clients, because there will inevitably
be griping when we change it (as we most certainly will). Your
complaints boil down to "this is hard to parse from the client side",
and that already tells me you're doing something that we will refuse
to support.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2010-04-02 21:50:38 Re: Compile fail, alpha5 & gcc 4.3.3 in elog.c
Previous Message Michael Tharp 2010-04-02 19:53:35 [RFC] nodeToString format and exporting the SQL parser