[
https://issues.jboss.org/browse/TEIIDDES-1864?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-1864:
----------------------------------------
The simplistic use-case described above does make sense and the current capability of the
VDB Editor is allow creating, editing and managing data roles for a given VDB containing
specific versions of models.
Renaming a model outside the VDB and synching the VDB poses all sorts of issues and
scenarios.
In the case above, user renames one column. But what if user renamed BOTH columns. Unless
the refactoring (rename actions) operated directly on the VDB (models AND data roles),
there no way to handle anything but the "singular change" use-case.
Changes to a table's columns can result in role being reset for
the entire model
--------------------------------------------------------------------------------
Key: TEIIDDES-1864
URL:
https://issues.jboss.org/browse/TEIIDDES-1864
Project: Teiid Designer
Issue Type: Bug
Affects Versions: 7.7, 8.2
Reporter: Marc Shirley
Assignee: Barry LaFond
Fix For: 8.3
I have a model like below with a role defined to remove read privileges on
'column1a2' only.
model1
-> table1a
---> column1a1
---> column1a2
-> table1b
---> column1b1
---> column1b2
I adjust the model to rename 'column1b2' to 'uselessColumn':
model1
-> table1a
---> column1a1
---> column1a2
-> table1b
---> column1b1
---> uselessColumn
The role is reset and now has default read privileges defined across the entire model. I
have to manually edit the role to reset it to the prior defined permissions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira