[JBoss JIRA] (TEIIDDES-1864) Changes to a table's columns can result in role being reset for the entire model
by Marc Shirley (JIRA)
Marc Shirley created TEIIDDES-1864:
--------------------------------------
Summary: 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: 8.2, 7.7
Reporter: Marc Shirley
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
12 years, 7 months
[JBoss JIRA] (TEIIDDES-1863) Add native type to procedure parameters
by Steven Hawkins (JIRA)
Steven Hawkins created TEIIDDES-1863:
----------------------------------------
Summary: Add native type to procedure parameters
Key: TEIIDDES-1863
URL: https://issues.jboss.org/browse/TEIIDDES-1863
Project: Teiid Designer
Issue Type: Enhancement
Components: Modeling, Teiid Integration
Reporter: Steven Hawkins
TEIID-2644 adds out parameter cursor handling for oracle, and adds a native type property to procedure parameters (just like regular columns). That is not currently in the index metadata. This value would need to be captured on import and either a new index version used, or an extension property (with additional Teiid handling), or the vdb.xml can use alter statements to add an option.
--
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
12 years, 7 months
[JBoss JIRA] (TEIIDDES-1861) Designer deletes data role "condition" information
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1861?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1861:
----------------------------------------
Tried reproducing using steps above. Tried many different types of ".. keep working and saving/synching..." and can't get the condition to be NULL'd out.
> 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.2.x-prod-eds6.0
>
>
> 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
12 years, 7 months