Description of problem:

In certain cases the statement parser can incorrectly match the 
<SINGLE_STRING> token as a <SQL_TOKEN>


How reproducible:

Every time.


Steps to Reproduce:

If you have a string token in a sql file that has non white space 
characters preceeding it then it will be matched as a sql token.  If 
that string has a space in in then you could end up with a parse 
error.

Ex.

v_foo +'string'

produces two <SQL_TOKEN>'s "v_foo" and "+'string'"

And if the string has spaces in it...

Ex.

v_foo +'string spaces '

produces 3 <SQL_TOKEN>'s "v_foo", "+'string", "spaces" and the
start of a <SINGLE_STRING> which is supposed to be the end of the
<SINGLE_STRING>!