[
https://issues.jboss.org/browse/TEIIDDES-776?page=com.atlassian.jira.plug...
]
Barry LaFond commented on TEIIDDES-776:
---------------------------------------
So a potential use-case is:
1) User has Relational Model with 100 tables in it and 20 columns per table
2) For default data role, there will be 4 permission entries in the vdb.xml
- This will include Read = TRUE, Create, Update and Delete = FALSE (All objects under
the model's READ permission will inherit READ = TRUE)
3) User selects on column in one Table to have Update capability
4) Resulting vdb.xml will have 99 permission entries where Update = FALSE
Not sure if we can get around this.
Data Roles: After unchecking a model, cannot check subordinate
metadata, like columns
-------------------------------------------------------------------------------------
Key: TEIIDDES-776
URL:
https://issues.jboss.org/browse/TEIIDDES-776
Project: Teiid Designer
Issue Type: Bug
Components: VDB & Execution
Affects Versions: 7.1.1
Reporter: Paul Nittel
Fix For: 7.4
In the case where an administrator wishes to prevent access to all columns but a
relatively few, they should be able to:
Uncheck the model (which causes all subordinate objects to be unchecked)
Check the small number to which access is desired.
What happens is once the model is unchecked, the subordinate objects cannot be checked.
(Also, if all subordinate objects are manually unchecked, the model has a grayed-out check
as if there is a checked subordinate object. If all objects under a model are unchecked,
the model itself should also be unchecked.)
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira