[
https://issues.jboss.org/browse/TEIID-3033?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3033:
---------------------------------------
I'm still not sure what change/fix is appropriate. The metadata that the modeshape
translator is providing in a dynamic case has not changed in a number of releases. The
only possibility for this to be viewed as a regression is from Designer's
perspective.
The next point is that name "simplifying" for Teiid table names is a general
feature and not specific to modeshape. All of the teiid translators will report their
metadata in the most straight-forward way possible. The only provision we have along
these lines is that the MetadataFactory can automatically correct column names that
contain a period. Otherwise there is no general routine - which would need to do quite a
bit more than just replace semi-colon in the general case.
So I'm interpreting this issue as desiring a name simplifier somewhere - either Teiid
or Designer. Because you loose some of the ease of association with the source table
name, introduce a greater chance for introducing name conflicts, etc., I haven't seen
a need for that on the Teiid side.
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)