[teiid-issues] [JBoss JIRA] (TEIID-3033) Importing metadata thru Designer versus using dynamic VDB is different

[Steven Hawkins (JIRA)]

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

Steven Hawkins commented on TEIID-3033:
---------------------------------------

> So I can't recommend enabling it, because of this issue. 

I don't think there is a need to prevent Designer from exposing functionality that is essentially correct.

> As for the change, just duplicate the JDBCMetadataProcessor for the ModeShapeMetadataProcessor

No need to duplicate, there is already a subclass.

>  and make the change only for mode shape

If you do so, then you need to make it an option.  Otherwise what I'm getting at is that you are making the modeshape metadata idiosyncratic compared to the rest of the teiid importers.  Just because Designer did it that way does not make it correct and I don't want the precedent to be that we have to mimic the Designer import logic moving forward in all cases as we convert more over to the Teiid connection importer.

And again my qualm is the feature here is to "not quote identifiers", which is a general issue and not inherently specific to modeshape.

> Importing metadata thru Designer versus using dynamic VDB is different
> ----------------------------------------------------------------------
>
>                 Key: TEIID-3033
>                 URL: https://issues.jboss.org/browse/TEIID-3033
>             Project: Teiid
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Misc. Connectors
>    Affects Versions: 8.7.1, 8.9
>            Reporter: Van Halbert
>            Assignee: Van Halbert
>
> The columns names and NIS, imported via Designer, show that the column name is set as the NIS, and then converted (replace colon with underscore) to be used as the column name.   However, in the mode shape translator, this logic isn't being applied



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)