Bug 118147 - StatementParser.jj can incorrectly match <SINGLE_STRING>
StatementParser.jj can incorrectly match <SINGLE_STRING>
Status: NEW
Product: Red Hat Web Application Framework
Classification: Retired
Component: installation (Show other bugs)
nightly
All Linux
medium Severity low
: ---
: ---
Assigned To: ccm-bugs-list
Jon Orris
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-03-12 09:25 EST by Brett Prucha
Modified: 2008-05-01 11:39 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Brett Prucha 2004-03-12 09:25:24 EST
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>!

Note You need to log in before you can comment on or make changes to this bug.