[JBoss JIRA] Moved: (TEIIDDES-340) Update Incorrect When Changing Model Name On Last Page Of JDBC Wizard
by Van Halbert (JIRA)
[ https://jira.jboss.org/jira/browse/TEIIDDES-340?page=com.atlassian.jira.p... ]
Van Halbert moved JBEDSP-103 to TEIIDDES-340:
---------------------------------------------
Project: Teiid Designer (was: JBoss Enterprise Data Services Platform)
Key: TEIIDDES-340 (was: JBEDSP-103)
Component/s: Modeling
(was: Designer)
Fix Version/s: (was: Future Versions)
Affects Version/s: (was: 5.5.2)
> Update Incorrect When Changing Model Name On Last Page Of JDBC Wizard
> ---------------------------------------------------------------------
>
> Key: TEIIDDES-340
> URL: https://jira.jboss.org/jira/browse/TEIIDDES-340
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Environment: Fedora 8
> Reporter: Dan Florian
> Assignee: Dan Florian
>
> If you change step 3.3.2.1 of the E2E XML Book Set Mixed Test Script to select the project in the tree not the model, the model deltas are not calculated. Proceed as the test script says until the last page. Change the model name to match the update model and check "update." Now hit "Next >" to go to the last page and notice there are no differences when there should be since the foreign keys are being added. If you click "Finish" nothing is updated. This is because if go back in the wizard after changing the model name, the "Foreign Keys" and "Indexes" checkboxes are now unselected. I did not have this problem when running the same kit under MS Windows.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Moved: (TEIIDDES-337) Cut and paste from SQL Explorer enters VDBName as Model name in the xmi file, but valids in transformation
by Van Halbert (JIRA)
[ https://jira.jboss.org/jira/browse/TEIIDDES-337?page=com.atlassian.jira.p... ]
Van Halbert moved JBEDSP-1130 to TEIIDDES-337:
----------------------------------------------
Project: Teiid Designer (was: JBoss Enterprise Data Services Platform)
Key: TEIIDDES-337 (was: JBEDSP-1130)
Fix Version/s: Future
(was: Future Versions)
> Cut and paste from SQL Explorer enters VDBName as Model name in the xmi file, but valids in transformation
> ----------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-337
> URL: https://jira.jboss.org/jira/browse/TEIIDDES-337
> Project: Teiid Designer
> Issue Type: Bug
> Reporter: Debbie Steigner
> Fix For: Future
>
> Attachments: 365698.zip
>
>
> Using my attached Model Project Set (365698.zip)(Issue tracker ticket) Execute the NewVDB.VDB in the Designer, right click on DateTZ_Oracle.DATETZ.TABLE2 table and "Generate Select in SQL Editor":
> select ROW_ID, TZ_USED, TS_STRING, DATEVAL, TS_VAL, TS_W_TZ_VAL, TS_W_LTZ_VAL from "NewVDB"."DateTZ_Oracle.DATETZ.TABLE2"
> Return to the Designer Perspective and create a new Base Table under the VModel, paste the the clipboard contents from the SQL Editor into the Transformation Editor, click "Save/Validate SQL". You'll notice the validator removes the "NewVDB" name and the quotes and validates and saves the transformation:
> SELECT ROW_ID, TZ_USED, TS_STRING, DATEVAL, TS_VAL, TS_W_TZ_VAL, TS_W_LTZ_VAL
> FROM DateTZ_Oracle.DATETZ.TABLE2
> Now Save, Build and Synchronize the NewVDB.VDB. Execute again and query the new View table. You'll receive a "Group does not exist: NewVDB.TABLE2" error. The xmi file contains the VDB name as the model name in the transformation.
> But apparently, if you go back into the transformation and make any changes and save/validate again it corrects the issue. (Turned SQL Optimization off, saved, Turned it back on, saved)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months