[
https://issues.jboss.org/browse/TEIIDDES-1861?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-1861:
----------------------------------------
The issue arises because of the use of the fully-qualified table name referenced in the
permission. This name contains the delimiter character '.' The permission's
"resource-name" string value, (path-based name of the table) assumes the
'.' is a path delimiter. Designer also assumes this when it tries to resolve that
resource-name, and in this instance removes the permission because it couldn't find
the table.
The fix will require forcing double-quotes around all object names containing the
'.' character, creating a validation rule (ERROR) to warn the user if they name it
by hand, changing the JDBC Importer to wrap these names in d-quotes (if '.'
present) and tweaking the DataRoleResolver.getTargetName() method to check for d-quotes
when converting the resource-name to a IPath string (i.e. replacing '.' with a
'/' character)
Designer deletes data role "condition" information
--------------------------------------------------
Key: TEIIDDES-1861
URL:
https://issues.jboss.org/browse/TEIIDDES-1861
Project: Teiid Designer
Issue Type: Bug
Components: Teiid Integration, VDB & Execution
Affects Versions: 8.2
Environment: Windows 7, Eclipse kepler.
Reporter: Pablo Navascues
Assignee: Barry LaFond
Fix For: 8.3.x
Attachments: Teiiddes-1861-screencapture.m4v
Create a VDB
Create a source model by importing from JDBC
Add model to VDB
Define data role with a table wide condition like "USERNAME=substring(user(), 1,
locate('@', user()) - 1)"
Synchronize, save VBD.
Condition is applied to queries, can be seen in the designer, can be seen in the VBD
internal xml.
Keep working and after another save (not necessarily de second one) condition field value
is empty in designer and gone from teh XML as well.
This has happened more than once and to more than one developer in the team.
--
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