Re: ecpg rejects input parameters - Mailing list pgsql-general

From Adrian Klaver
Subject Re: ecpg rejects input parameters
Date
Msg-id 5526911F.20201@aklaver.com
Whole thread Raw
In response to Re: ecpg rejects input parameters  (Andrew Pennebaker <andrew.pennebaker@gmail.com>)
List pgsql-general
On 04/09/2015 07:12 AM, Andrew Pennebaker wrote:
> Makes sense.
>
> Yes, it would be great if psql offered a flag for validating syntax.
> Other programming languages do this, for example, bash -n, ruby -c, and
> php -l.

Or pgsanity could take this:

CREATE DATABASE :db;

and convert it into:

CREATE DATABASE db;

before submitting it for syntax checking.

The basic issue is whose syntax are you interested in checking, SQL or
the program that is  creating the SQL. If it is just the SQL end result,
then it needs to rendered down to an actual valid SQL statement. If it
is the program, then it gets complicated in a hurry. Already you have
mentioned psql and ecpg. Then in Postgres there are various procedural
languages that have their own way of creating SQL. Then there are
external languages, for example the one I use a lot  Python. It has its
own method(s) of passing in variable information via DB-API.


>
> On Wed, Apr 8, 2015 at 3:53 PM, Tom Lane <tgl@sss.pgh.pa.us
> <mailto:tgl@sss.pgh.pa.us>> wrote:
>
>     Andrew Pennebaker <andrew.pennebaker@gmail.com
>     <mailto:andrew.pennebaker@gmail.com>> writes:
>     > I can't find a relevant section to address my specific problem: ecpg
>     > complaining when I try to check the syntax of my .sql files that use input
>     > parameters.
>
>     I'm not sure why you think that should work.  psql and ecpg have quite
>     distinct input languages.  Both are extensions of SQL, but the key word
>     there is "extension".  ecpg certainly isn't going to accept psql's
>     backslash commands for instance, any more than psql would accept ecpg's
>     C code portions.  And I doubt it would be useful for ecpg to simply
>     ignore
>     the variable-interpolation symbols; but it has no way to know what's
>     going
>     to be substituted for those symbols.
>
>     It would be more interesting to consider giving psql a syntax-check-only
>     mode; though I'm afraid use of variable interpolation would still be
>     pretty
>     problematic, since the variables are commonly filled from execution of
>     previous commands.
>
>                              regards, tom lane
>
>
>
>
> --
> Cheers,
>
> Andrew Pennebaker
> www.yellosoft.us <http://www.yellosoft.us>


--
Adrian Klaver
adrian.klaver@aklaver.com


pgsql-general by date:

Previous
From: Andrew Pennebaker
Date:
Subject: Re: ecpg rejects input parameters
Next
From: Dennis
Date:
Subject: Can a bdr enabled server belong to more than one bdr group?