[
https://issues.jboss.org/browse/TEIIDDES-2725?page=com.atlassian.jira.plu...
]
Matus Makovy updated TEIIDDES-2725:
-----------------------------------
Description:
When you use connection parameters in REST connection profile definition, the resulting
transformation SQL generated during import from this CP is malformed.
ViewModel.getCases.query AS query, *+|| '/' || ViewModel.getCases.query+*
ViewModel.getCases.newSearch AS newSearch *+|| '/' ||
ViewModel.getCases.newSearch+*
SQL without the bold/underlined parts works. (I mean underlined/bold parts in this bug
Description, not in screenshot)
See attached screenshots
was:
When you use connection parameters in REST connection profile definition, the resulting
transformation SQL generated during import from this CP is malformed.
ViewModel.getCases.query AS query, *+|| '/' || ViewModel.getCases.query+*
ViewModel.getCases.newSearch AS newSearch *+|| '/' ||
ViewModel.getCases.newSearch+*
SQL without the bold/underlined parts works.
See attached screenshots
Transformation sql is not correct when using REST import with URL
attributes
----------------------------------------------------------------------------
Key: TEIIDDES-2725
URL:
https://issues.jboss.org/browse/TEIIDDES-2725
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 9.0.4
Reporter: Matus Makovy
Attachments: Screen Shot 2015-11-12 at 14.55.52.png, Screen Shot 2015-11-12 at
15.22.59.png
When you use connection parameters in REST connection profile definition, the resulting
transformation SQL generated during import from this CP is malformed.
ViewModel.getCases.query AS query, *+|| '/' || ViewModel.getCases.query+*
ViewModel.getCases.newSearch AS newSearch *+|| '/' ||
ViewModel.getCases.newSearch+*
SQL without the bold/underlined parts works. (I mean underlined/bold parts in this bug
Description, not in screenshot)
See attached screenshots
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)