[teiid-issues] [JBoss JIRA] Moved: (TEIID-994) Unable to execute Oracle pipelined table function as procedure [Tripos POC]

[Van Halbert (JIRA)]

     [ https://jira.jboss.org/jira/browse/TEIID-994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Van Halbert moved JBEDSP-894 to TEIID-994:
------------------------------------------

              Project: Teiid  (was: JBoss Enterprise Data Services Platform)
                  Key: TEIID-994  (was: JBEDSP-894)
          Component/s: Misc. Connectors
                       Query Engine
                           (was: Connectors)
                           (was: Query)
        Fix Version/s:     (was: Future Versions)
    Affects Version/s:     (was: 5.5.1)


> Unable to execute Oracle pipelined table function as procedure [Tripos POC]
> ---------------------------------------------------------------------------
>
>                 Key: TEIID-994
>                 URL: https://jira.jboss.org/jira/browse/TEIID-994
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: Misc. Connectors, Query Engine
>            Reporter: Steven Hawkins
>
> Defect Tracker #20072: At Tripos, they have some 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 contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira