Marc Shirley created TEIIDDES-3082: -------------------------------------- Summary: Revisit JDBC procedure import to ensure we are using all available information available in the driver Key: TEIIDDES-3082 URL: https://issues.jboss.org/browse/TEIIDDES-3082 Project: Teiid Designer Issue Type: Feature Request Environment: Oracle JDBC import including procedures Reporter: Marc Shirley JDBC procedure import (for Oracle at least) generally results in a skeleton procedure object being created, usually with input parameters and an undefined result set. Can we determine if there is any additional modeling we can do during import utilizing the available information from the driver or by executing a sample call to the procedure? TEIID-2644 [1] looks to potentially have something we can leverage at least in the case of a REF CURSOR output parameter that could be used to flesh out the imported procedure in some cases. [1] https://issues.jboss.org/browse/TEIID-2644 -- This message was sent by Atlassian JIRA (v7.2.3#72005)