[JBoss JIRA] (TEIIDDES-2649) Cannot modify values in several dialogs - with JBDS 9
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2649?page=com.atlassian.jira.plu... ]
Andrej Šmigala updated TEIIDDES-2649:
-------------------------------------
Summary: Cannot modify values in several dialogs - with JBDS 9 (was: Cannot modify values in several dialogs)
> Cannot modify values in several dialogs - with JBDS 9
> -----------------------------------------------------
>
> Key: TEIIDDES-2649
> URL: https://issues.jboss.org/browse/…
[View More]TEIIDDES-2649
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dialogs, Modeling
> Affects Versions: 9.0.3
> Environment: Teiid Designer 9.0.3 Final
> JBDS 9.0.0 CR1
> Reporter: Andrej Šmigala
>
> Cells in table widgets in several dialogs are not editable:
> * Create Relational View Table -> Columns
> * Create Relational Table -> Colums
> * Create Relational Procedure -> Parameters, Result Set
> * Create Relational Source Function -> Parameters
> * Create Relational Native Query Procedure -> Parameters, Result Set
> * Create Relational View -> Columns
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
9 years, 6 months
[JBoss JIRA] (TEIIDDES-2671) Dynamic VDB Editor is set as default for all XML files
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2671?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2671:
----------------------------------------
The Dynamic VDB editor has no real functionality. I think the solution is to remove the UI contribution and users will use their own/other XML editors if they wish.
Note that the VDB export is designed to be a snapshot representation of a Archive VDB.. so users will have to determine if/what they want to change in the dyn. vdb …
[View More]once generated.
> Dynamic VDB Editor is set as default for all XML files
> ------------------------------------------------------
>
> Key: TEIIDDES-2671
> URL: https://issues.jboss.org/browse/TEIIDDES-2671
> Project: Teiid Designer
> Issue Type: Bug
> Components: Editors
> Affects Versions: 9.0.4
> Environment: JBDS 8.1.0.GA + JBDS-IS 8.0.4.CR1 (Teiid Designer 9.0.4.CR1-v20150917-2111-B1187 )
> Reporter: Andrej Podhradsky
> Priority: Blocker
> Fix For: 9.0.4, 9.2
>
>
> Dynamic VDB Editor is set as default for all XML files. As a consequence opening an XML file fails due to
> org.eclipse.ui.PartInitException: File blueprint.xml is not a dynamic VDB
> In the example above the blueprint.xml should be opened by Camel Editor.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
9 years, 6 months
[JBoss JIRA] (TEIIDDES-2672) Wrong Foreign Key reference when exporting Dynamic VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2672?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-2672:
--------------------------------------
Assignee: Barry LaFond
> Wrong Foreign Key reference when exporting Dynamic VDB
> ------------------------------------------------------
>
> Key: TEIIDDES-2672
> URL: https://issues.jboss.org/browse/TEIIDDES-2672
> Project: Teiid Designer
> Issue Type: Bug
…
[View More]> Components: Import/Export, Modeling, VDB & Execution
> Affects Versions: 9.0.4
> Reporter: Andrej Šmigala
> Assignee: Barry LaFond
> Fix For: 9.0.4, 9.2
>
> Attachments: DynamicVdbFk.zip
>
>
> When creating a dynamic VDB from an existing VDB, Foreign Key definitions use the wrong table in the REFERENCES clause. The reference table is the same as the one that contains this FK.
> For example, in the table SUPPLIER_PARTS, the following constraint is generated:
> {code:sql}CONSTRAINT FK_SPLIER_PRTS_SPLY FOREIGN KEY(SUPPLIER_ID) REFERENCES SUPPLIER_PARTS(SUPPLIER_ID){code}
> which is obviously wrong. The correct constrant definition should be:
> {code:sql}CONSTRAINT FK_SPLIER_PRTS_SPLY FOREIGN KEY(SUPPLIER_ID) REFERENCES SUPPLIER(SUPPLIER_ID){code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
9 years, 6 months
[JBoss JIRA] (TEIIDDES-2672) Wrong Foreign Key reference when exporting Dynamic VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2672?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2672:
-----------------------------------
Fix Version/s: 9.0.4
9.2
> Wrong Foreign Key reference when exporting Dynamic VDB
> ------------------------------------------------------
>
> Key: TEIIDDES-2672
> URL: https://issues.jboss.org/browse/TEIIDDES-2672
> Project: Teiid Designer
> …
[View More]Issue Type: Bug
> Components: Import/Export, Modeling, VDB & Execution
> Affects Versions: 9.0.4
> Reporter: Andrej Šmigala
> Assignee: Barry LaFond
> Fix For: 9.0.4, 9.2
>
> Attachments: DynamicVdbFk.zip
>
>
> When creating a dynamic VDB from an existing VDB, Foreign Key definitions use the wrong table in the REFERENCES clause. The reference table is the same as the one that contains this FK.
> For example, in the table SUPPLIER_PARTS, the following constraint is generated:
> {code:sql}CONSTRAINT FK_SPLIER_PRTS_SPLY FOREIGN KEY(SUPPLIER_ID) REFERENCES SUPPLIER_PARTS(SUPPLIER_ID){code}
> which is obviously wrong. The correct constrant definition should be:
> {code:sql}CONSTRAINT FK_SPLIER_PRTS_SPLY FOREIGN KEY(SUPPLIER_ID) REFERENCES SUPPLIER(SUPPLIER_ID){code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[View Less]
9 years, 6 months