[
https://issues.jboss.org/browse/TEIID-4319?page=com.atlassian.jira.plugin...
]
Van Halbert commented on TEIID-4319:
------------------------------------
As for deprecating, I think a translator-override should be added that would trigger the
inclusion of Object column when the metadata is reverse engineered. This would enable
backwards compatibility. But most likely, no one is using this column since the logic
was changed to not need the OBJECTTABLE in order to transform the object to a row.
Deprecate automatically adding of the class object to the source
table
----------------------------------------------------------------------
Key: TEIID-4319
URL:
https://issues.jboss.org/browse/TEIID-4319
Project: Teiid
Issue Type: Enhancement
Components: Misc. Connectors
Affects Versions: 9.x
Reporter: Van Halbert
Assignee: Van Halbert
If the source model is not defined with the metadata, but allowing the infinispan
(object) translator to reverse engineer the metadata from the cache object class, the
process will add a column that represents the cache object. This is a holdover from the
original implementation that used the OBJECTTABLE function for transforming the object
into a row in the result set. This column is not required and can be excluded (or
removed) if modeling the object source table.
This column also causes WARNING to show up in the server log because it is assumed by the
engine to be part of materialization. However, this column is not updatable and can be
excluded in materialization by not specifying it in the INSERT INTO statement.
So to clean up all this, it would be good to stop adding the class object as a column in
the source table. And the user can always add it back if they wish to use it.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)