[
https://jira.jboss.org/browse/TEIIDDES-577?page=com.atlassian.jira.plugin...
]
Barry LaFond commented on TEIIDDES-577:
---------------------------------------
That was my first thought, but I think data access is a top-down thing which takes into
account:
1) Virtual Table SQL and values of SupportsUpdate (supports CREATE/UPDATE/DELETE/SELECT)
2) Supports Update values of the Physical Tables
3) Visibility of the Physical models
4) CRUD values based on data role permissions
Not sure you can cover the whole gamut if you don't have access to Physical models
that are tagged as NOT VISIBLE.
Maybe Steve/Ramesh or someone else can chime in?
Models which are NOT visible should not be shown in the data roles
editor
-------------------------------------------------------------------------
Key: TEIIDDES-577
URL:
https://jira.jboss.org/browse/TEIIDDES-577
Project: Teiid Designer
Issue Type: Bug
Components: VDB & Execution
Affects Versions: 7.1
Environment: All
Reporter: Paul Nittel
Attachments: visible.png
At the risk of opening huge cans of worms, a model which has been marked NOT VISIBLE
should not be shown in the data roles editor. Presently, they are shown in that editor.
They should not be.
Screenshot is attached.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira