Re: SQL Parsing

Would you care to expand on *why* you want to do this? Your question is short on detail.

To a certain extent, you're running pretty close to the old "only perl can parse Perl" example. The only thing that's likely to reliably and perfectly parse the more advanced and obscure bits of your particular dialect of SQL would be the SQL engine from your DB of choice.

I just have a feeling that if you explain more, some monk might come up with a creative way to help you that you might not expect...

Comment on Re: SQL Parsing

Replies are listed 'Best First'.
Re^2: SQL Parsing by Anonymous Monk on Feb 24, 2006 at 16:44 UTC
The situation here is like this... The SQL generated by a set of reports need to be parsed in order to obtain the metadata. The reports are hitting a database of type 'A'.The metadata obtained after parsing the SQL will be used to identify the table structures that need to be created in a database of type 'B' so that the reports can be migrated to 'B'. The only good thing is that both 'A' and 'B' support SQL. The reports are my only source of information about 'A'	[reply]

Replies are listed 'Best First'.

Re^2: SQL Parsing
by Anonymous Monk on Feb 24, 2006 at 16:44 UTC

The situation here is like this... The SQL generated by a set of reports need to be parsed in order to obtain the metadata. The reports are hitting a database of type 'A'.The metadata obtained after parsing the SQL will be used to identify the table structures that need to be created in a database of type 'B' so that the reports can be migrated to 'B'. The only good thing is that both 'A' and 'B' support SQL. The reports are my only source of information about 'A'

[reply]