[
https://jira.jboss.org/jira/browse/TEIID-750?page=com.atlassian.jira.plug...
]
Steven Hawkins commented on TEIID-750:
--------------------------------------
Made minor cleanups related to visibility and added another test. It would still be best
to refactor and remove the need for the ModelVisiblityValidationVisitor. It also seems
that a problem could arise with prepared plans, if the visibility flag is toggled to
private after a plan is created, we do not revalidate on plan execution.
Add more filtering in the internal processing of queries so that
hidden items do not requires fully qualified names to be used
------------------------------------------------------------------------------------------------------------------------------
Key: TEIID-750
URL:
https://jira.jboss.org/jira/browse/TEIID-750
Project: Teiid
Issue Type: Feature Request
Components: Query Engine, Server
Affects Versions: 6.1.0
Reporter: Rob Hutton
Priority: Minor
Fix For: 6.3
If you have a table in a source model and a table in a view model with the same name, you
must use the fully qualified name of the view model table when querying the VDB even if
the source model is not visible. It would be nice if the visibility flag was taken in to
account when trying to resolve object names while querying the VDB
--
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