[
https://issues.jboss.org/browse/TEIID-994?page=com.atlassian.jira.plugin....
]
Steven Hawkins commented on TEIID-994:
--------------------------------------
I should add that the native-query property using the TABLE keyword is only appropriate
for a function returning a table type. If a ref cursor is being returned, then the
native-query needs to be "SELECT func(params...) FROM DUAL" and the procedure
needs to be modeled with a return parameter with a native type of REF CURSOR.
Unable to execute Oracle pipelined table function as procedure
--------------------------------------------------------------
Key: TEIID-994
URL:
https://issues.jboss.org/browse/TEIID-994
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors, Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.7, Open To Community
Oracle pipelined table functions (can be used in Oracle queries as TABLE(...)) that can
be put in the FROM clause and used as if they were tables although they are really
procedures. We found that we imported this table function, although didn't get it
quite right - the result set was wrong, which may just be a deficiency of the JDBC import
metadata. We were able to map the proc to a table and execute but when we did we got a
PL/SQL error from the db.
Because this is a proc, we are executing it as a CallableStatement down in the JDBC
connector which apparently does not work with DataDirect. I'm not sure how we can
detect and do something different but seems like we need to have some metadata (procedure
name in source?) that can tell us that this proc needs to be run differently and have the
Oracle JDBC Connector deal with this properly.
--
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