-
Feature Request
-
Resolution: Won't Do
-
Major
-
None
-
None
-
None
-
None
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.