]
Barry LaFond closed TEIIDDES-337.
---------------------------------
Assignee: Barry LaFond
Resolution: Won't Fix
VDB Editor, VDB content have totally changed. SQL Explorer replaced with standard DTP
querying.
Obsolete defect.
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/browse/TEIIDDES-337
Project: Teiid Designer
Issue Type: Bug
Reporter: Debbie Steigner
Assignee: Barry LaFond
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: