[
https://issues.jboss.org/browse/TEIIDDES-3034?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-3034:
----------------------------------------
Note that exporting a virtual procedure with no result set, but an RETURN parameter ends
up with the following, which is equivalent to the DDL in the description
{code}
CREATE VIRTUAL PROCEDURE ProcedureWithRS (
IN stringIN string(4000) OPTIONS(ANNOTATION 'parameter 1 description'),
OUT resultSet string(255) RESULT
) OPTIONS(ANNOTATION 'Example', UPDATECOUNT '1')
AS
BEGIN
SELECT test_vp.ProcedureWithRS.stringIN AS result;
END;
{code}
Importing Virtual Procedure DDL containing a simple RETURNS type add
a Result Set to procedure
----------------------------------------------------------------------------------------------
Key: TEIIDDES-3034
URL:
https://issues.jboss.org/browse/TEIIDDES-3034
Project: Teiid Designer
Issue Type: Enhancement
Reporter: Barry LaFond
testing and debugging for TEIIDDES-2783 exposed an issue when importing a procedure
containing a RETURNS data type and no result set.
The transformation resolving framework contains logic that will auto-create a result set
containing a generated column.
We need to catch this use-case and prevent the result set from being created using this
simple DDL input
{code}
CREATE VIRTUAL PROCEDURE ProcedureWithRS (
stringIN string(4000) OPTIONS(ANNOTATION 'parameter 1 description')
) RETURNS string(255) OPTIONS(ANNOTATION 'Example') AS
BEGIN
SELECT stringIN AS result;
END
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)