Depending on the complexity of the select statments, and the flavor of SQL you are using I would think that you could write a parser fairly quickly using
Parse::Yapp, or simular.
The grammer of a simple select statment is:
select_statement: 'SELECT' opt_distinct fields_list 'FROM' tables_list
+ opt_where opt_orderby opt_groupby
;
opt_distinct: 'DISTINCT' | ;
opt_where: 'WHERE' where_list | ;
fields_list: field
| field ',' fields_list
;
opt_groupby: 'GROUP BY' fields_list | ;
opt_orderby: 'ORDER BY' order_fields_list | ;
order_fields_list: order_field
| order_field ',' order_fields_list
;
At this point I would say you are done. Writing out the SQL with XML does not get you anything. If the SQL is badly formed then the XML will also be badly formed.
You might also look at Parse::RecDescent::Genezzo::Parse::SQL.
-- gam3
A picture is worth a thousand words, but takes 200K.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.