[
https://issues.jboss.org/browse/TEIIDDES-1259?page=com.atlassian.jira.plu...
]
Steven Hawkins commented on TEIIDDES-1259:
------------------------------------------
Starting with Designer 7.5 the error message will no longer be massive (TEIID-1655). The
detection of this situation tightly coupled with javacc. The QueryParserException would
need caught, getParseException would need to be called to get the actual javacc exception,
then ParseException.currentToken.kind would need to be checked to see if the token is not
a SQLParserConstants.ID, LPAREN, or any other non-reseved word token. Then you would have
to check the ParseException.expectedTokenSequences (which also reference
SQLParserConstants) to see if any valid expansions start with SQLParserConstants.ID. Even
then, that does not guarantee the situation will actually be the simple case of just
expecting a double quoted identifier.
USABILITY: When reconciling transformation and reserved word is
encountered, can the error message indicate its a reserved word
-------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1259
URL:
https://issues.jboss.org/browse/TEIIDDES-1259
Project: Teiid Designer
Issue Type: Enhancement
Components: Transformations
Affects Versions: 7.4.2
Reporter: Van Halbert
Priority: Minor
When the reconciler is validating the sql and a use of a reserved word is the cause of
the invalidation, could the error message indicate as such? This may have already been
done, but I didn't see a jira indicating it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira