The quickest thing to do is edit your VDB1 using the Designer, and on "Element" table properties find the "Name in Source" property and enter the name as "Element" in there with double quotation marks. I believe that should resolve it.
I am not entirely sure that Teiid does not do this already based on some configuration. If in case it does not support it, this can be added as an issue to be fixed. I will investigate.
On side note, can I persuade you in writing a small blog about your use case in showing how Teiid is helping to solve your data integration needs?
Designer 7.2 should resolve this issue automatically - if you reimport. All imported JDBC metadata should be quoted using the quoting character from the source. Dynamic VDBs already import metadata in this way.
There is however no automatic mechanism to correct this on the Teiid side, so the workaround that Ramesh suggests is the best approach until you use Designer 7.2.
Hi, Ramesh & Steve
Thanks for your help.
I have tried the approach. But it is same with before. I will try it on Designer 7.2.
However, I think that even though the approach can work. It has another question.
Because in my case, there are two data source, one is Teiid VDB, another is oracle database. They have same schema.
Below SQL (table name is wrapped by double quotation marks) is ok for Teiid VDB, but it is not ok for Oracle.
select ELE_ID from "ELEMENT";
Ramesh: I am pleasure to write a blog to share my usage of Teiid.
Thank Teiid Community for the great efforts!
If you changed the name in source value for the ELEMENT table in VDB1 that is querying Teiid to be "ELEMENT", then the generated query against VDB2 should work against Teiid. This is essentially what Designer 7.2 will do for you automatically.
What do mean by the quoted query will not work against Oracle? Oracle supports the SQL standard double quoting of identifiers.
select ELE_ID from "ELEMEN
1 of 1 people found this helpful
Here's the oracle naming rules http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/sql_elements008.htm
The most likely issue is that the quoted name is being treated as case sensitive.
You are right.