[
https://issues.jboss.org/browse/TEIIDDES-1176?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-1176:
----------------------------------------
Looks like importing attached DDL results in a ParsingException because OracleDdlParser
has "CREATE UNIQUE INDEX" as a registered statement start however the
parseCreateIndex() method has the logic to handle the "UNIQUE" use-case is
commented out. So the resulting logic is expecing INDEX as the next token and it's
not.
AND
When importing the copy of the DDL saved on LINUX whatever the save does, changes the file
enough so that only the CREATE TABLE statements are fully processed.
The Parsing Scores for Testfile.ddl : Oracle = 684, Standard = 597 Derby&Postgres =
555 (Oracle would win but it throws a parsing exception and it's parser result is NOT
returned
Parsing score for Re-saved DDL is : Oracle = 1064, Standard = 885, Derby/Postgres = 843
(Since the Oracle Parser doesn't get to processing CREATE UNIQUE INDEX statement, it
won't throw exception and ORACLE parser wins)
So this is a Modeshape issue as far as I can tell. Probably the CREATE UNIQUE INDEX
should NOT be registered, and the statements would be parsed as "UNKNOWN"
statement
Usability Issue: On DDL importer, need better feed back when a file
cannot be imported
--------------------------------------------------------------------------------------
Key: TEIIDDES-1176
URL:
https://issues.jboss.org/browse/TEIIDDES-1176
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 7.4.2
Reporter: Van Halbert
Attachments: Testfile.ddl
When importing a DDL file, the importer fails. Its hard to determine where the problem
is in the file. It was suggested it would be nice if it could parse what it can and then
indicate after which statement it failed.
Also, it would be nice to be able to select which objects (like the jdbc importer of
selecting tables, indexes, etc.) to import. Maybe the ddl importer could utilize part the
jdbc importer wizard to provide the same options.
--
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