September 2015 - teiid-designer-issues

[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 edited comment on TEIIDDES-2671 at 9/30/15 4:01 PM: ----------------------------------------------------------------- master: https://github.com/Teiid-Designer/teiid-designer/commit/3558f5f0b385fa034... https://github.com/Teiid-Designer/teiid-designer/commit/e5acaeef02da40ce7... 9.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/03b3f0a111ed510d3... https://github.com/Teiid-Designer/teiid-designer/commit/34853bc734357b3bb... was (Author: blafond): master: https://github.com/Teiid-Designer/teiid-designer/commit/3558f5f0b385fa034... 9.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/03b3f0a111ed510d3... > 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 > Assignee: Barry LaFond > 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)

8 years, 6 months

1
0
0 / 0

[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 edited comment on TEIIDDES-2672 at 9/30/15 4:01 PM: ----------------------------------------------------------------- master: https://github.com/Teiid-Designer/teiid-designer/commit/381a782b204bc2736... https://github.com/Teiid-Designer/teiid-designer/commit/989a9daea12a4723b... 9.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/1051d216e0ec5a504... https://github.com/Teiid-Designer/teiid-designer/commit/0dcb8a8b2e2d24746... was (Author: blafond): master: https://github.com/Teiid-Designer/teiid-designer/commit/381a782b204bc2736... 9.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/1051d216e0ec5a504... > 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 > 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)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2672) Wrong Foreign Key reference when exporting Dynamic VDB

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2672?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2672: --------------------------------------------------- Barry LaFond <blafond(a)redhat.com> changed the Status of [bug 1267538|https://bugzilla.redhat.com/show_bug.cgi?id=1267538] from NEW to MODIFIED > 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 > 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)

8 years, 6 months

1
0
0 / 0

[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: ---------------------------------------- master: https://github.com/Teiid-Designer/teiid-designer/commit/3558f5f0b385fa034... 9.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/03b3f0a111ed510d3... > 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 > Assignee: Barry LaFond > 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)

8 years, 6 months

1
0
0 / 0

[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 resolved TEIIDDES-2671. ------------------------------------ Resolution: Done > 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 > Assignee: Barry LaFond > 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)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2671) Dynamic VDB Editor is set as default for all XML files

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2671?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2671: --------------------------------------------------- Barry LaFond <blafond(a)redhat.com> changed the Status of [bug 1267613|https://bugzilla.redhat.com/show_bug.cgi?id=1267613] from NEW to MODIFIED > 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 > Assignee: Barry LaFond > 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)

8 years, 6 months

1
0
0 / 0

[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 commented on TEIIDDES-2672: ---------------------------------------- master: https://github.com/Teiid-Designer/teiid-designer/commit/381a782b204bc2736... 9.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/1051d216e0ec5a504... > 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 > 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)

8 years, 6 months

1
0
0 / 0

[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 resolved TEIIDDES-2672. ------------------------------------ Resolution: Done > 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 > 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)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2654) Renaming project with VDB in it causes VDB to disappear

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2654?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2654: ----------------------------------- Fix Version/s: 9.0.5 9.3 > Renaming project with VDB in it causes VDB to disappear > ------------------------------------------------------- > > Key: TEIIDDES-2654 > URL: https://issues.jboss.org/browse/TEIIDDES-2654 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 9.0.4 > Environment: MAC OS X > Reporter: Matus Makovy > Fix For: 9.0.5, 9.3 > > Attachments: bug.mov > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2649) Cannot modify values in several dialogs in JBDS 9 (Eclipse Mars)

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2649?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2649: ----------------------------------- Summary: Cannot modify values in several dialogs in JBDS 9 (Eclipse Mars) (was: Cannot modify values in several dialogs - with JBDS 9) > Cannot modify values in several dialogs in JBDS 9 (Eclipse Mars) > ---------------------------------------------------------------- > > Key: TEIIDDES-2649 > URL: https://issues.jboss.org/browse/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)

8 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues September 2015