Re^2: Static Data, SQL::Parser

A little more background; the project I'm working on is classifying specific chunks of data (database, table, columns, etc.) from queries used in our ColdFusion environment. I chose ANSI just because it should cover all of our different JDBC connections (Oracle 9i, DB2, SyBase, TeraData, etc.). The DUAL actually works in the query; changing 1 to a fake column name parses correctly. Since it's possible (although somewhat pointless) to include a static value in a column definition I was hoping that there might be some way to get the parser to recognize that the column name comes after the AS.

SELECT [static_value1] [AS] c1, [static_value2] [AS] c2, ... cn
[download]

The DUAL was just used as an example as we have many queries which include staticly defined values.

I guess the fastest solution will be to strip out anything which may be a static define.

Comment on Re^2: Static Data, SQL::Parser Download Code

Replies are listed 'Best First'.
Re^3: Static Data, SQL::Parser by renodino (Curate) on May 08, 2007 at 02:36 UTC
The DUAL actually works in the query; changing 1 to a fake column name parses correctly. Sorry, I should've been more specific. Yes, any table name will parse OK, as will omitting the FROM clause entirely. I meant to indicate that you shouldn't rely on DUAL being supported by any underlying specialization. (Teradata ? As I live and breathe, I never expected to encounter someone on PM who actually knows what a Teradata is...) Perl Contrarian & SQL fanboy	[reply]
Re^4: Static Data, SQL::Parser by CLovegren (Novice) on May 08, 2007 at 08:21 UTC
The good thing is, I don't need them to run; I already know they do since they are in a production level environment. I may end up just grepping the data out of the queries since I don't really need the joins to work or anything of that nature; just the statement structures were exactly what I was looking for. And as for Teradata... not my choice; seriously. We're just a reporting environment. :)	[reply]