[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:
----------------------------------------
With the attached model project set, I was able to reproduce your issue. on the first attempt.
> 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
>
> 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
10 years, 9 months
[JBoss JIRA] (TEIIDDES-1861) Designer deletes data role "condition" information
by Patrick Deenen (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1861?page=com.atlassian.jira.plu... ]
Patrick Deenen commented on TEIIDDES-1861:
------------------------------------------
An image does not show the use case as in the description, the video does. It plays with no problems on Windows with Quicktime.
> 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
>
> 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
10 years, 9 months
[JBoss JIRA] (TEIIDDES-1861) Designer deletes data role "condition" information
by Debbie Steigner (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1861?page=com.atlassian.jira.plu... ]
Debbie Steigner commented on TEIIDDES-1861:
-------------------------------------------
Already had them test on 8.3, problem persists.
> 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
>
> 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
10 years, 9 months
[JBoss JIRA] (TEIIDDES-1985) Better formating of SQL in transformation editor
by Patrick Deenen (JIRA)
Patrick Deenen created TEIIDDES-1985:
----------------------------------------
Summary: Better formating of SQL in transformation editor
Key: TEIIDDES-1985
URL: https://issues.jboss.org/browse/TEIIDDES-1985
Project: Teiid Designer
Issue Type: Enhancement
Components: Eclipse Integration, Editors, Usability
Affects Versions: 8.3, 8.2
Environment: Windows 7 sp1 64 bit, Eclipse Kepler build: 20130614-0229, JDK 1.6.0_45
Reporter: Patrick Deenen
Priority: Minor
Feature Improvement Request: Beautify SQL format in SQL transformation box. Currently all new lines are removed from the text behind SQL reserved words like SELECT, JOIN, FROM and WHERE. This doesn't improve readability, hence give the user the choice to have the SQL auto formatted or to maintain the original text or improve the auto format.
--
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
10 years, 9 months
[JBoss JIRA] (TEIIDDES-1984) Enhance security for data roles UI
by Patrick Deenen (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1984?page=com.atlassian.jira.plu... ]
Patrick Deenen updated TEIIDDES-1984:
-------------------------------------
Priority: Minor (was: Major)
> Enhance security for data roles UI
> ----------------------------------
>
> Key: TEIIDDES-1984
> URL: https://issues.jboss.org/browse/TEIIDDES-1984
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Eclipse Integration
> Affects Versions: 8.2, 8.3
> Environment: Windows 7 sp1 64 bit, Eclipse Kepler build: 20130614-0229, JDK 1.6.0_45
> Reporter: Patrick Deenen
> Priority: Minor
>
> Feature Improvement Request: The "security" checkbox in the data roles editor is not really a checkbox. You need to double-click it in order to get a window to open where you can configure conditions on tables. So therefore, why use a checkbox component? Also, the fact that table level conditions are configured from there and not from the "conditions" tab is confusing.
--
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
10 years, 9 months
[JBoss JIRA] (TEIIDDES-1984) Enhance security for data roles UI
by Patrick Deenen (JIRA)
Patrick Deenen created TEIIDDES-1984:
----------------------------------------
Summary: Enhance security for data roles UI
Key: TEIIDDES-1984
URL: https://issues.jboss.org/browse/TEIIDDES-1984
Project: Teiid Designer
Issue Type: Enhancement
Components: Eclipse Integration
Affects Versions: 8.3, 8.2
Environment: Windows 7 sp1 64 bit, Eclipse Kepler build: 20130614-0229, JDK 1.6.0_45
Reporter: Patrick Deenen
Feature Improvement Request: The "security" checkbox in the data roles editor is not really a checkbox. You need to double-click it in order to get a window to open where you can configure conditions on tables. So therefore, why use a checkbox component? Also, the fact that table level conditions are configured from there and not from the "conditions" tab is confusing.
--
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
10 years, 9 months
[JBoss JIRA] (TEIIDDES-1983) Support direct clickable checkboxes in table components
by Patrick Deenen (JIRA)
Patrick Deenen created TEIIDDES-1983:
----------------------------------------
Summary: Support direct clickable checkboxes in table components
Key: TEIIDDES-1983
URL: https://issues.jboss.org/browse/TEIIDDES-1983
Project: Teiid Designer
Issue Type: Enhancement
Components: Usability
Affects Versions: 8.3, 8.2
Environment: Windows 7 sp1 64 bit, Eclipse Kepler build: 20130614-0229, JDK 1.6.0_45
Reporter: Patrick Deenen
Priority: Minor
Bug: a quirk that happens in Teiid Designer exclusively under windows. Checkboxes rendered within a table component (VDB's models table, a data role's security details, etc) can't be clicked unless the first column of the row in which it is selected first.
--
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
10 years, 9 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:
----------------------------------------
Can't seem to view the attachment. Could you use jpg or png image instead?
I'd also recommend installing 8.3 Final and retesting. https://www.jboss.org/teiiddesigner/downloads
> 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
>
> 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
10 years, 9 months
[JBoss JIRA] (TEIIDDES-1861) Designer deletes data role "condition" information
by Patrick Deenen (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1861?page=com.atlassian.jira.plu... ]
Patrick Deenen edited comment on TEIIDDES-1861 at 12/9/13 8:47 AM:
-------------------------------------------------------------------
As you can in the attached screen capture this problem is easy to reproduce and very annoying as we expect to have many security conditions in the final design. So please reopen this issue.
was (Author: pdeenen):
As you can in the attached screen capture this problem is easy to reproduce and very annoying as we expect to have many security conditions in the final design.
> 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
>
> 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
10 years, 9 months