[
https://issues.jboss.org/browse/TEIID-2798?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2798:
---------------------------------------
But out of this, need to fix the metadata so that it doesn't
include the Object source in the source table. It could be useful if the object was being
returned to the client, but I don't think it should be added by default. What do you
think?
I think the current behavior is fine as the default. Generally speaking unless the object
is a simple bean, then the members are going to be more complicated than just built-in
type scalar values, which may require further use of an objecttable to denormalize/pull
fields.
Add creation of view when exposing metadata via Object translator
-----------------------------------------------------------------
Key: TEIID-2798
URL:
https://issues.jboss.org/browse/TEIID-2798
Project: Teiid
Issue Type: Enhancement
Components: Misc. Connectors
Affects Versions: 8.4.1
Reporter: Van Halbert
Assignee: Van Halbert
When the metadata is exposed for the java object via the Object translator, a view should
also be created using a template similar to:
SELECT
t.{pkKeyField}, o.{colname}, o.{colname}
FROM Order
{ObjectSourceTable} as T,
OBJECTTABLE('x' PASSING T.{ObjectTypeName}Object as x COLUMNS
{colname} {type} 'teiid_row.{colname}', ….) as o
where
{pkKeyField} is the primary key column to the cache
{ObjectSourceTable} is the source table imported above
{ObjectTypeName} is the column added in {ObjectSourceTable} to reference the cache
object
{colname} is the name of the columns that have “get” methods, see the {ObjectSourceTable}
for columns to use
{type} is the data type for this column
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira