pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: Juan Rodrigo Alejandro Burgos Mella <rodrigoburgosmella@gmail.com>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: ECPG Semantic Analysis
Date: Fri, 23 Jun 2023 07:06:32 -0400
Message-ID: <13884.1687518392@sss.pgh.pa.us> (raw)
In-Reply-To: <ZJUnGUSpkLq5j9sL@paquier.xyz>
References: <CAHbZ42wiR1u4ws+cuUSQofW-E8i1UFaCKfo8yZjfMwBn_m_qJg@mail.gmail.com>
	<ZJUnGUSpkLq5j9sL@paquier.xyz>

Michael Paquier <michael@paquier.xyz> writes:
> On Fri, Jun 23, 2023 at 12:21:48AM -0400, Juan Rodrigo Alejandro Burgos Mella wrote:
>> I have a modified version of ECPG, to which I gave the ability to do
>> semantic analysis of SQL statements. Where can you share it or with whom
>> can I discuss it?

> I cannot say what kind of problem this solves and/or if this is useful
> as a feature of the ECPG driver in PostgreSQL core itself, but you
> could consider submitting a patch for integration into core.

TBH I'd have to discourage you from expecting that such a patch would
be accepted.  ECPG is pretty much of a development backwater nowadays.
We keep maintaining it because it's (mostly) not too much trouble
thanks to the work that was done years ago to auto-generate its
grammar from the main grammar.  However, adding any sort of semantic
analysis to it seems like it'd take an enormous amount of new C code
that would then have to be kept in sync (by hand) with the backend
parser.  Testing such a thing seems like a big time sink as well.
I seriously doubt that we'd be willing to take on such a maintenance
burden.

			regards, tom lane





view thread (3+ messages)

Message-ID: <13884.1687518392@sss.pgh.pa.us>
Permalink:  ../13884.1687518392@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/13884.1687518392@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: tgl@sss.pgh.pa.us, michael@paquier.xyz, rodrigoburgosmella@gmail.com
  Subject: Re: ECPG Semantic Analysis
  In-Reply-To: <13884.1687518392@sss.pgh.pa.us>
  References: <CAHbZ42wiR1u4ws+cuUSQofW-E8i1UFaCKfo8yZjfMwBn_m_qJg@mail.gmail.com> <ZJUnGUSpkLq5j9sL@paquier.xyz> <13884.1687518392@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox