I've run in to an issue using SQL::Parser that I'm not sure how to work around. The following code throws an error despite this being valid SQL.
$parser = SQL::Parser->new( 'ANSI', {RaiseError=>0,PrintError=>1} )
$stmt = SQL::Statement->new( 'SELECT 1 AS A FROM DUAL', $parser )

[download]
The result is:
SQL ERROR: Bad table or column name '1' starts with non-alphabetic character!

I'm currently using the most up-to-date versions of SQL::Parser (1.13) and SQL::Statement (1.15).

Any thoughts as to how I can get around this error? Is it possible to identify these types of statements as valid to the parser? Do I need to filter out all static columns from my query?

Thanks in advance!

In reply to Static Data, SQL::Parser by CLovegren

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.