[
https://issues.jboss.org/browse/TEIIDDES-1885?page=com.atlassian.jira.plu...
]
Lucie Fabrikova edited comment on TEIIDDES-1885 at 11/14/13 8:19 AM:
---------------------------------------------------------------------
I observed this error again, on MacOS; the "No difference report was found, See the
import messages for more info" occured for these combinations:
- Auto-select unchecked + any of dialects
- Auto-select checked
The option "TEIID" dialect generated a preview of DDL contents, but the error
message is same.
Observed on both java 1.6 apple, 1.7 oracle + MacOS 10.8.
was (Author: lfabriko):
I observed this error again, on MacOS; the "No difference report was found, See
the import messages for more info" occured for these combinations:
- Auto-select unchecked + any of dialects
- Auto-select checked
The option "TEIID" dialect generated a preview of DDL contents, but the error
message is same.
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