[JBoss JIRA] (TEIIDDES-2392) Don't allow override name to be the same name as existing translator name
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2392?page=com.atlassian.jira.plu... ]
Andrej Šmigala reopened TEIIDDES-2392:
--------------------------------------
Still not fully fixed:
It is no longer possible to _create_ a translator override that has the same name as an existing translator, but is still is possible to _edit_ the name of a TO and set it to the name of an existing translator.
Also, when there is no connection to the server, Designer does not check that the TO name already exists (this makes sense, since there is no way of knowing the names of translators on the server). However, it should ideally check the TO names once a connection to the server is made.
> Don't allow override name to be the same name as existing translator name
> -------------------------------------------------------------------------
>
> Key: TEIIDDES-2392
> URL: https://issues.jboss.org/browse/TEIIDDES-2392
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 8.6.1
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: 9.1, 8.6.2 Beta1, 9.0.2 Beta1, 9.0.2, 8.6.2
>
>
> When creating a translator override, the name of the override should not be able to be set to the name of an existing translator (or translator override).
> In this case, the translator override was set to "teradata".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2530) Generate REST Virtual Procedure should use fully qualified names in the generated procedures
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2530?page=com.atlassian.jira.plu... ]
Andrej Šmigala edited comment on TEIIDDES-2530 at 5/19/15 5:52 AM:
-------------------------------------------------------------------
It appears designer uses the fully qualified name in case the table name is _not_ ambiguous, and the simple name when it is.
was (Author: asmigala):
It appears designer uses the fully qualified name in case the tables name is _not_ ambiguous, and the simple name when it is.
> Generate REST Virtual Procedure should use fully qualified names in the generated procedures
> --------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2530
> URL: https://issues.jboss.org/browse/TEIIDDES-2530
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling, Transformations
> Affects Versions: 9.0.2 Beta1
> Reporter: Andrej Šmigala
>
> When generating REST procedure using the new Generate REST Virtual Procedures function, the generated procedure contains simple names of the referenced tables, which causes validation errors when there are tables with the same name in other models.
> Designer should use the fully qualified name in the generated procedure.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2530) Generate REST Virtual Procedure should use fully qualified names in the generated procedures
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2530?page=com.atlassian.jira.plu... ]
Andrej Šmigala commented on TEIIDDES-2530:
------------------------------------------
It appears designer uses the fully qualified name in case the tables name is _not_ ambiguous, and the simple name when it is.
> Generate REST Virtual Procedure should use fully qualified names in the generated procedures
> --------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2530
> URL: https://issues.jboss.org/browse/TEIIDDES-2530
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling, Transformations
> Affects Versions: 9.0.2 Beta1
> Reporter: Andrej Šmigala
>
> When generating REST procedure using the new Generate REST Virtual Procedures function, the generated procedure contains simple names of the referenced tables, which causes validation errors when there are tables with the same name in other models.
> Designer should use the fully qualified name in the generated procedure.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2531) Generate REST Virtual Procedure should allow setting the view XML tag names per table
by Andrej Šmigala (JIRA)
Andrej Šmigala created TEIIDDES-2531:
----------------------------------------
Summary: Generate REST Virtual Procedure should allow setting the view XML tag names per table
Key: TEIIDDES-2531
URL: https://issues.jboss.org/browse/TEIIDDES-2531
Project: Teiid Designer
Issue Type: Enhancement
Components: Modeling, Transformations
Affects Versions: 9.0.2 Beta1
Reporter: Andrej Šmigala
The Generate REST Virtual Procedures dialog now allows setting the View XML tag and Column XML tag, which are then used in the transformation for all the procedures. This rarely makes sense in the case two or more tables are selected, so the user will have to either manually edit the transformations, or run the wizard multiple times for each transformed table.
I suggest adding the ability to set both XML tag names per selected table.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2530) Generate REST Virtual Procedure should use fully qualified names in the generated procedures
by Andrej Šmigala (JIRA)
Andrej Šmigala created TEIIDDES-2530:
----------------------------------------
Summary: Generate REST Virtual Procedure should use fully qualified names in the generated procedures
Key: TEIIDDES-2530
URL: https://issues.jboss.org/browse/TEIIDDES-2530
Project: Teiid Designer
Issue Type: Bug
Components: Modeling
Affects Versions: 9.0.2 Beta1
Reporter: Andrej Šmigala
When generating REST procedure using the new Generate REST Virtual Procedures function, the generated procedure contains simple names of the referenced tables, which causes validation errors when there are tables with the same name in other models.
Designer should use the fully qualified name in the generated procedure.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2529) 1024 x 768 Issue with XML model editor - can not reach red "Staging table arrow" when scrolling
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2529?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2529:
----------------------------------------
The XML document diagram was stable a few years ago. I guess SWT/GEF and Eclipse have changed enough to make the diagram unstable.
The framework is pretty involved and would take some time and probably a re-write to some extend. Going to target 9.2 for now.
> 1024 x 768 Issue with XML model editor - can not reach red "Staging table arrow" when scrolling
> -----------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2529
> URL: https://issues.jboss.org/browse/TEIIDDES-2529
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 9.0.2 Beta1
> Reporter: Matus Makovy
> Fix For: 9.2
>
> Attachments: bug.mov, Screen Shot 2015-05-18 at 4.30.23 PM.png, Screen Shot 2015-05-18 at 4.30.30 PM.png, Screen Shot 2015-05-18 at 4.30.32 PM.png
>
>
> I am trying to add transformation source. I have to right-click "red arrow" in the model editor and I am not able to reach it.
> Screenshots + video attached
> Issue occured on OS X
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months