[JBoss JIRA] (TEIIDDES-2756) After importing older models transformation SQL is missing "AS columnName" part
by Matus Makovy (JIRA)
Matus Makovy created TEIIDDES-2756:
--------------------------------------
Summary: After importing older models transformation SQL is missing "AS columnName" part
Key: TEIIDDES-2756
URL: https://issues.jboss.org/browse/TEIIDDES-2756
Project: Teiid Designer
Issue Type: Enhancement
Affects Versions: 9.0.4
Reporter: Matus Makovy
Attachments: Screen Shot 2016-01-12 at 10.30.21 (2).png, Screen Shot 2016-01-12 at 10.30.37 (2).png
After I imported some older VDB and exported models from this VDB, there seem to be some validation errors.
It is necessary to add "AS ColumnName" to transformation sql.
See screenshots
Is there a possibility that TD would do this automatically? Or could we have at least some Quick fix for this?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (TEIIDDES-2755) No Quick fix offered after importing VDB with same models
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2755?page=com.atlassian.jira.plu... ]
Matus Makovy updated TEIIDDES-2755:
-----------------------------------
Attachment: Screen Shot 2016-01-12 at 9.58.00 (2).png
Screen Shot 2016-01-12 at 9.57.48 (2).png
Screen Shot 2016-01-12 at 9.57.25 (2).png
> No Quick fix offered after importing VDB with same models
> ---------------------------------------------------------
>
> Key: TEIIDDES-2755
> URL: https://issues.jboss.org/browse/TEIIDDES-2755
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 9.0.4
> Reporter: Matus Makovy
> Attachments: QT_Greenplum_Push.vdb, QT_MySql50_Push.vdb, Screen Shot 2016-01-12 at 9.57.25 (2).png, Screen Shot 2016-01-12 at 9.57.48 (2).png, Screen Shot 2016-01-12 at 9.58.00 (2).png
>
>
> I have 2 VDBs with models that have same names. After importing the first one and extracting the models, TD doesn't offer this option for the second VDB in second project.
> I can see that the warning says that models are not in +workspace+, but I think TD should check if models are in the +project folder+ not in workspace.
> In the screenshots, you can see that there is no warning for NewProject2.
> VDBs attached.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (TEIIDDES-2755) No Quick fix offered after importing VDB with same models
by Matus Makovy (JIRA)
Matus Makovy created TEIIDDES-2755:
--------------------------------------
Summary: No Quick fix offered after importing VDB with same models
Key: TEIIDDES-2755
URL: https://issues.jboss.org/browse/TEIIDDES-2755
Project: Teiid Designer
Issue Type: Bug
Affects Versions: 9.0.4
Reporter: Matus Makovy
Attachments: QT_Greenplum_Push.vdb, QT_MySql50_Push.vdb
I have 2 VDBs with models that have same names. After importing the first one and extracting the models, TD doesn't offer this option for the second VDB in second project.
I can see that the warning says that models are not in +workspace+, but I think TD should check if models are in the +project folder+ not in workspace.
In the screenshots, you can see that there is no warning for NewProject2.
VDBs attached.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (TEIIDDES-2754) Extracting models from VDB without Quick Fix?
by Matus Makovy (JIRA)
Matus Makovy created TEIIDDES-2754:
--------------------------------------
Summary: Extracting models from VDB without Quick Fix?
Key: TEIIDDES-2754
URL: https://issues.jboss.org/browse/TEIIDDES-2754
Project: Teiid Designer
Issue Type: Enhancement
Affects Versions: 9.0.4
Reporter: Matus Makovy
Attachments: Screen Shot 2016-01-12 at 9.44.44 (2).png
I am testing backwards compatibility with VDBs generated from older versions of TD. I imported finished VDB and I am trying to deploy it to my server.
First thing I came across:
Is there a way to extract models from VDB except the Quick fix? I haven't found any other option.
If there is not, I'd suggest to include such option in context menu after right-clicking the VDB.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (TEIIDDES-2732) Issues with Dynamic VDB to Models - FOREIGN KEY REFERENCING MULTIPLE COLUMNS
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2732?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2732:
-----------------------------------
Attachment: TestcaseforImport-vdb.xml
Tweaked the DDL to make sure column names match including case sensitivity.
Run the import with this xml
> Issues with Dynamic VDB to Models - FOREIGN KEY REFERENCING MULTIPLE COLUMNS
> -----------------------------------------------------------------------------
>
> Key: TEIIDDES-2732
> URL: https://issues.jboss.org/browse/TEIIDDES-2732
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs, Import/Export, Patch Release
> Affects Versions: 9.2
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Fix For: 9.0.5, 9.2.1
>
> Attachments: TestcaseforImport-vdb.xml, TestcaseforImport.zip
>
>
> AFTER IMPORTING FROM XML INTO TEIID: FOREIGN KEY REFERENCING MULTIPLE COLUMNS POINTS TO WRONG COLUMNS IN SOURCE MODEL
> Test case : Foreign key relation on Unique constraints, spanning two columns: CatalogItem(CatalogSecondID, CatalogThirdID) Catalog(SecondID, ThirdID)
> XML INPUT fragment for Source model, table CatalogItem:
> CONSTRAINT FKI_CATALOG_ID FOREIGN KEY(CatalogID) REFERENCES Catalog(ID),
> CONSTRAINT FKI_SECOND_THIRD_ID FOREIGN KEY(CatalogSecondID, CatalogThirdID) REFERENCES Catalog(SecondID, ThirdID)
> Expected in Teiid:
> CatalogItem(CatalogSecondID, CatalogThirdID) Catalog(SecondID, ThirdID)
> Actual:
> CatalogItem(CatalogSecondID, CatalogThirdID) Catalog(ID)
> 3. AFTER IMPORTING FROM XML INTO TEIID: FOREIGN KEY REFERENCING MULTIPLE COLUMNS IS MISSING IN VIEW MODEL.
> Test case : Foreign key relation on Unique constraints, spanning two columns: CatalogItem(CatalogSecondID, CatalogThirdID) Catalog(SecondID, ThirdID)
> XML INPUT fragment for View model, table CatalogItem:
> CONSTRAINT FKI_CATALOG_ID FOREIGN KEY(CatalogID) REFERENCES Catalog(ID),
> CONSTRAINT FKI_SECOND_THIRD_ID FOREIGN KEY(CatalogSecondID, CatalogThirdID) REFERENCES Catalog(SecondID, ThirdID)
> Expected in Teiid:
> CatalogItem(CatalogSecondID, CatalogThirdID) Catalog(SecondID, ThirdID)
> Actual:
> Not Foreign key reference at all.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (TEIIDDES-2732) Issues with Dynamic VDB to Models - FOREIGN KEY REFERENCING MULTIPLE COLUMNS
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2732?page=com.atlassian.jira.plu... ]
Barry LaFond edited comment on TEIIDDES-2732 at 1/11/16 4:32 PM:
-----------------------------------------------------------------
master: https://github.com/Teiid-Designer/teiid-designer/commit/fe8f8c8281c49cb87...
9.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/578629b39333e2002...
was (Author: blafond):
master: https://github.com/Teiid-Designer/teiid-designer/commit/fe8f8c8281c49cb87...
> Issues with Dynamic VDB to Models - FOREIGN KEY REFERENCING MULTIPLE COLUMNS
> -----------------------------------------------------------------------------
>
> Key: TEIIDDES-2732
> URL: https://issues.jboss.org/browse/TEIIDDES-2732
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs, Import/Export, Patch Release
> Affects Versions: 9.2
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Fix For: 9.0.5, 9.2.1
>
> Attachments: TestcaseforImport.zip
>
>
> AFTER IMPORTING FROM XML INTO TEIID: FOREIGN KEY REFERENCING MULTIPLE COLUMNS POINTS TO WRONG COLUMNS IN SOURCE MODEL
> Test case : Foreign key relation on Unique constraints, spanning two columns: CatalogItem(CatalogSecondID, CatalogThirdID) Catalog(SecondID, ThirdID)
> XML INPUT fragment for Source model, table CatalogItem:
> CONSTRAINT FKI_CATALOG_ID FOREIGN KEY(CatalogID) REFERENCES Catalog(ID),
> CONSTRAINT FKI_SECOND_THIRD_ID FOREIGN KEY(CatalogSecondID, CatalogThirdID) REFERENCES Catalog(SecondID, ThirdID)
> Expected in Teiid:
> CatalogItem(CatalogSecondID, CatalogThirdID) Catalog(SecondID, ThirdID)
> Actual:
> CatalogItem(CatalogSecondID, CatalogThirdID) Catalog(ID)
> 3. AFTER IMPORTING FROM XML INTO TEIID: FOREIGN KEY REFERENCING MULTIPLE COLUMNS IS MISSING IN VIEW MODEL.
> Test case : Foreign key relation on Unique constraints, spanning two columns: CatalogItem(CatalogSecondID, CatalogThirdID) Catalog(SecondID, ThirdID)
> XML INPUT fragment for View model, table CatalogItem:
> CONSTRAINT FKI_CATALOG_ID FOREIGN KEY(CatalogID) REFERENCES Catalog(ID),
> CONSTRAINT FKI_SECOND_THIRD_ID FOREIGN KEY(CatalogSecondID, CatalogThirdID) REFERENCES Catalog(SecondID, ThirdID)
> Expected in Teiid:
> CatalogItem(CatalogSecondID, CatalogThirdID) Catalog(SecondID, ThirdID)
> Actual:
> Not Foreign key reference at all.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months