[teiid-issues] [JBoss JIRA] (TEIID-5656) DDL based import statement incorrectly parses the foreign schema name

[Steven Hawkins (Jira)]

    [ https://issues.jboss.org/browse/TEIID-5656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13699563#comment-13699563 ] 

Steven Hawkins commented on TEIID-5656:
---------------------------------------

> What do you recommend here? Can we not use exact name as a pattern to match?

No, you cannot interchange the two without risking weird scenarios involving the meta / escaping characters.

So if we want to match a name exactly, we need to add support for that in the translator.  Either as a post operation, or as the pattern - but with the appropriate escaping which needs to consult https://docs.oracle.com/javase/7/docs/api/java/sql/DatabaseMetaData.html#getSearchStringEscape()



> DDL based import statement incorrectly parses the foreign schema name
> ---------------------------------------------------------------------
>
>                 Key: TEIID-5656
>                 URL: https://issues.jboss.org/browse/TEIID-5656
>             Project: Teiid
>          Issue Type: Bug
>          Components: VDB
>            Reporter: Ramesh Reddy
>            Assignee: Ramesh Reddy
>            Priority: Major
>             Fix For: 12.1
>
>
> The DDL import statement like
> {code}
> IMPORT FOREIGN SCHEMA public FROM SERVER sampledb INTO accounts OPTIONS("importer.useFullSchemaName" 'false');
> {code}
> does not set the "importer.schemaPattern" to "public" instead it sets to "importer.schemaName" property to "public" in runtime thus invalidating its use. 



--
This message was sent by Atlassian Jira
(v7.12.1#712002)