SQL::Parser currently only accepts column names and functions in the select list. Yes, numbers, string literals and numberic expressions in the select list are valid SQL but SQL::Parser does not pretend to parse all valid SQL (see the docs). Patches and/or collaborators are welcome.
jZed, first off, let me say a fantastic tool it is; fast and flexible, an absolute god-send.
The post of this thread really was to see if there was a quick (and possibly dirty) way to get it to ignore this particular error and move on with parsing. In the future I'd love to rip in to the code and see what I can do with it. Since I'm unfamiliar with all of its in's and out's I was really hoping it was something I had overlooked (along the lines of tweaking a setting or loading a different file to get it to work).
For now I'll look at another solution to get what I need done, but going forward I'd love to see what I can do with this; it'd make a fantastic data farming tool for our environment!