[
https://issues.jboss.org/browse/TEIIDDES-2782?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-2782:
----------------------------------------
[~phantomjinx] Paul. I debugged this in Windows and the SQL contains "\r\n"
chars. The Teiid runtime's parser has no issue with these chars because the parser
treats as special tokens and ignores them.
The feature you added that supports embedded comments and multi-line comments breaks this
basic parsing (without any comments). At some point the token ends up being
"null" which results in NPE's. I can add simple checks for "null"
token in the Teiid8Parser.jjt but it partially breaks the comment feature and any embedded
comment get's tacked on to the END of the SQL.
Also, with my partial fix, the parsing of our System Functions via SQL.sql files on
Windows, results in the same NPE even without any comments in the SQL.
Bottom line is I'd like your help Monday understanding your comments feature code
changes and how we can adapt to get past this Windows line feed char issue. Thx
Copy paste sql to the transformation editor is not parsable
-----------------------------------------------------------
Key: TEIIDDES-2782
URL:
https://issues.jboss.org/browse/TEIIDDES-2782
Project: Teiid Designer
Issue Type: Bug
Components: Editors, Transformations
Affects Versions: 10.0.1
Environment: Windows 10 Pro N
Windows 7 Enterprise
Reporter: Matej Kralik
Assignee: Ted Jones
Priority: Critical
Fix For: 11.1.3
Attachments: XmlStagingProject.zip, endOfFile.mkv
When I copy a sql query from any source (notepad, web browser ...) and paste it to the
transformation editor show me that "The query is not parsable.Error in parsing of sql
- null ."
When I deleted all newlines from sql query or I wrote it myself to the editor, sql query
was validated.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)