-
1. Re: Turning off fully qualified names in VDB
rareddy Aug 5, 2009 3:00 PM (in response to huttonr)When you are importing the schema from sources using the Designer, on the wizard there is a option to turn off fully qualified names.
On virtual tables, querying with unqualified names work as long as there is no other table with same name in other models. If there is conflict it fails with "ambiguous" group error -
2. Re: Turning off fully qualified names in VDB
huttonr Aug 5, 2009 3:12 PM (in response to huttonr)What I am seeing is:
1) I have imported the mysql db into designer with fully qualified names. It contains three tables, all with unique names.
2) I have created a model called resource_manager_master and created the virtual tables in it
3) I have created a VDB called resource_manager_vdb and added the resource_manager_master model to it
4) When I run the VDB and drill down on the structure, I see the virtual tables with the name resource_manager_master.[tablename]. If I execute "Select * from [tablename];" I get an error about it being an unknown resource or something like that (I am not in front of the machine right now, so I cant get the specific error message). If I execute "Select * from resource_manager_master.[tablename];", it works fine. -
3. Re: Turning off fully qualified names in VDB
jpav Aug 5, 2009 3:36 PM (in response to huttonr)Without seeing the error message, I'd guess that you're simply experiencing a name conflict. If you created the virtual model using the same tables names as in the physical model(s), then you must qualify references to those tables to include which model you're trying to query, physical or virtual. Without that qualification, the table name by itself would be ambiguous.
-
4. Re: Turning off fully qualified names in VDB
huttonr Aug 5, 2009 3:46 PM (in response to huttonr)Gotcha -
So even though the physicals are not visible, it still has to be qualified. -
5. Re: Turning off fully qualified names in VDB
jpav Aug 5, 2009 3:54 PM (in response to huttonr)Yes, but didn't realize you made the physical models not visible. We actually should be able to address that. It shouldn't be too much trouble for the Teiid project to add more filtering in the internal processing of queries to avoid a conflict in this scenario. Could you add a defect to the Teiid project (not Designer) describing the problem and your setup?
-
6. Re: Turning off fully qualified names in VDB
huttonr Aug 5, 2009 3:55 PM (in response to huttonr)Absolutely