Bug 118147

Summary: StatementParser.jj can incorrectly match <SINGLE_STRING>
Product: [Retired] Red Hat Web Application Framework Reporter: Brett Prucha <pruchaba_bah>
Component: installationAssignee: ccm-bugs-list
Status: CLOSED EOL QA Contact: Jon Orris <jorris>
Severity: low Docs Contact:
Priority: medium    
Version: nightly   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 16:51:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Brett Prucha 2004-03-12 14:25:24 UTC
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>!