Fully-qualified names should not be required when referencing procedures that have unique
unqualified names
-----------------------------------------------------------------------------------------------------------
Key: TEIID-1462
URL:
https://issues.jboss.org/browse/TEIID-1462
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.0
Reporter: Michael Walker
Assignee: Steven Hawkins
Priority: Minor
Fix For: 7.0
This problem occurs in our transformation editor, and also occurs with real-time queries
(e.g. from QueryBuilder/SQLExplorer, or any client).
If you reference a non-qualified table name, e.g. "myTable", in a query,
we'll attempt to resolve it if it is a unique name.
Strangely, we don't do the same thing for virtual procedures, even if they are unique.
Instead, you must use the fully-qualified name. There should be no disparity. This is a
usability defect.
This also happens to greatly extend the size of virtual procedure code, making it harder
to read and debug.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira