[ https://issues.jboss.org/browse/TEIID-5561?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5561: --------------------------------------- That only works by separating out the schema. It does not work if the table name actually contains '.'. So I can: 1. Add validations and logs when a table / column name is not valid - we could also add an annotation to the metadata, but I didn't do that just yet. 2. Update all of the schema and sql construction logic to allow for some escaping mechanism, such that any name could be supported - which is a fairly involved change. Alternatively there would need to be some kind of intermediate virtual metadata layer that does the appropriate cleanup. For now I'll just do 1 and call it a day. Throwing an error is possible, but it may inadvertently break some cases so I won't do that for now. Similarly excluding the table / column leads to all kinds of other issues with the logic given our base expectations that anything with a unique / pk is available. -- This message was sent by Atlassian Jira (v7.12.1#712002)