From: | Fabrice Scemama <fabrices(at)ximmo(dot)ftd(dot)fr> |
---|---|
To: | maxsbox <maxsbox(at)scds(dot)co(dot)za> |
Cc: | pgsql-sql(at)hub(dot)org |
Subject: | Re: [SQL] Re: pgsql-sql-digest V1 #422 |
Date: | 1999-11-25 22:03:30 |
Message-ID: | 383DB232.302E0F52@ximmo.ftd.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
The wheel does not have to be reinvented.
Try perl's SQL::Statement .
Fabrice Scemama
maxsbox wrote:
>
> >
> >
> > Date: Wed, 24 Nov 1999 09:09:51 +0530
> > From: CHAITANYANC <CHAITANYANC(at)inf(dot)com>
> > Subject: Info on SQL Parsing required
> >
> > Hi
> > Can anybody tell me where I can find the ways of parsing an sql statement
> > and making a query plan ?
> > Thanks in advance
> > Chaitu
> >
> > ------------------------------
>
> Not that this really answers your question, but:-
>
> Have a look at Paradox, I'm using version 8. It allows you to query either an
> SQL data base or the .db and .dbf files using either an SQL or a QBE query. I
> was rather surprised to find that a QBE query would work from it accessing
> postgreSQL using ODBC.
>
> Found, for a script, the SQL query had more flexibility, however, as it allows
> greater use of variables in the query, particularly where you want to substitute
> a variable for a file name.
>
> Hope this helps you
>
> Regards
>
> Max Wood
>
> ************
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 1999-11-25 23:43:37 | Re: [SQL] Info on SQL Parsing required |
Previous Message | Jan Wieck | 1999-11-25 12:37:11 | Re: [SQL] pqReadData() error |