[teiid-designer-issues] [JBoss JIRA] (TEIIDDES-1614) Procedure result set not being generated when creating simple CREATE VIRTUAL PROCEDURE from SQL
[
https://issues.jboss.org/browse/TEIIDDES-1614?page=com.atlassian.jira.plu...
]
Paul Richardson commented on TEIIDDES-1614:
-------------------------------------------
With 34 references to getProjectedSymbols() in designer's codebase and the possibility
that many of those relate to other types of Command, that seems a worrying workaround to
the problem. Would you mind explaining:
* What is the difference between the resultSetColumns and projectSymbols collections?
* If the 2 collections are interchangeable why there are 2 collections?
* Why in 7.7 did the projectedSymbols get populated with the contents of resultSetColumns
and yet in 8.2+ this is no longer the case?
* The inclusion of the 'inferProcedureResultSetColumns' is a workaround for
designer to get back the columns so is any of this not required by teiid anymore?
Many thanks.
Procedure result set not being generated when creating simple CREATE
VIRTUAL PROCEDURE from SQL
-----------------------------------------------------------------------------------------------
Key: TEIIDDES-1614
URL: https://issues.jboss.org/browse/TEIIDDES-1614
Project: Teiid Designer
Issue Type: Bug
Components: Modeling, Validation
Affects Versions: 8.1
Reporter: Barry LaFond
Assignee: Paul Richardson
Fix For: 8.1
Attachments: DynamicSQLMPS.zip
Designer 7.7.x will auto-generated the virtual procedure result set and columns after
pasting in the following:
CREATE VIRTUAL PROCEDURE
BEGIN
SELECT * FROM PARTS;
END
Current Designer 8.1 codebase results in valid SQL (no errors) but the result set and
columns are not generated.
When creating a Web Service Model/Operation from same PARTS source table the resulting
Operation will have a resulting OUTPUT (result set) but no output column with XML type
--
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