| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Juan Rodrigo Alejandro Burgos Mella <rodrigoburgosmella(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: ECPG Semantic Analysis |
| Date: | 2023-06-23 11:06:32 |
| Message-ID: | 13884.1687518392@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Michael Paquier <michael(at)paquier(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2023-06-23 11:28:52 | Re: Migration database from mysql to postgress |
| Previous Message | Postgres all-rounder | 2023-06-23 10:53:49 | Re: synchronous_commit= remote_apply | "The transaction has already committed locally..." |