That doesn't seem to do what the OP wants
Come now young man, where's your sense of adventure? With a bit of lookahead and a state machine you can easily massage the token stream into something useful:
use SQL::Tokenizer;
my $query = q{f1,f2, SUM(f3),CONCAT(f4,f5, f6), sum((f1+f2)*f3)};
my @token = SQL::Tokenizer->tokenize($query);
my $paren_depth = 0;
my $cache = '';
while(my $val = shift @token) {
if ($token[0] eq '(') {
$paren_depth++;
}
if ($val eq ')') {
$paren_depth--;
if ($paren_depth == 0) {
print $cache;
$cache = '';
}
}
if ($paren_depth) {
$cache .= $val;
}
else {
print "$val\n";
}
}
__PRODUCES__
f1
,
f2
,
SUM(f3)
,
CONCAT(f4,f5, f6)
,
sum((f1+f2)*f3)
That's not too shabby. The tokenizer does the heavy lifting, you just have to put the pieces back together again.
• another intruder with the mooring in the heart of the Perl
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.