[
https://issues.jboss.org/browse/TEIIDDES-1885?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-1885:
----------------------------------------
I wasn't able to repeat the scenario as above... what I found was
1) Import attached DDL file
2) The DDL Importer comes up defaulted to TEIID dialect and Auto-Select == FALSE
* This results in a parsing error on Differences page since the DDL file does not contain
Teiid Dialect and the importer was forced to try and parse the DDL using Modeshape DDL
Parser
3) Turning Auto-select == TRUE and clicking NEXT
* This results in no error on the Differences page since the importer should have
discovered/used the standard SQL92 dialect.
4) FINISH created the desired models
DDL importer problems for both source and view models
------------------------------------------------------
Key: TEIIDDES-1885
URL:
https://issues.jboss.org/browse/TEIIDDES-1885
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 8.2
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 8.3
Attachments: stdcust.ddl
When Importing from DDL to create a new view model (DDL File >> Source or View
model), the following problems appear:
a) when choosing auto-select for dialect, the wizard raises the difference panel after
hitting Next with generic "Error encountered importing DDL" message and a
"No difference report was found" message.
b) when leaving auto-select unchecked for dialect, clicking Next produces a DDL failed to
parse error (as well as a 'No difference report was found" error.
The DDL in question works in JBDS 6 and earlier.
Version-Release number of selected component (if applicable):
JBDS 7 with JBDSIS 7 beta 4
How reproducible:
Consistent.
Steps to Reproduce:
Import attached DDL via importer.
see:
https://bugzilla.redhat.com/show_bug.cgi?id=1016553
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira