[
https://issues.jboss.org/browse/TEIID-3870?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3870:
---------------------------------------
Can you explain how to use the JDBC api database metadata to get
objects in packages?
The DatabaseMetaData doesn't have this concern. As long as the package is in the
schema(s) you are importing against the procedures will be reported in the getProcedures
method - just with a catalog name as the package name.
Add ability to properly qualify package objects
-----------------------------------------------
Key: TEIID-3870
URL:
https://issues.jboss.org/browse/TEIID-3870
Project: Teiid
Issue Type: Feature Request
Components: JDBC Connector
Affects Versions: 8.7.1.6_2
Environment: Red Hat JBoss Data Virtualization 6.2 on EAP6.4.0 patched to version
6.4.3,
JBoss Developer Studio 8.1.0GA with Teiid Designer plugin
9.0.3.Final.v20150810-1438-B1157
64-bit Windows 7 environment
Reporter: Steve Tran
Assignee: Steven Hawkins
Fix For: 8.13, 8.12.4
Even if the catalog name pattern matches package names, there is no option or recognition
that contained procedures should be qualified as <package / catalog>.<name>.
We need this because at least in Oracle, procedures may be encapsulated in Oracle
Packages that are used as catalog names in the DatabaseMetaData. When trying to import
these into Teiid, the "Name in Source" field does not allow me to specify the
Package name, so I can't call those procedures.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)