[
https://issues.jboss.org/browse/TEIID-1589?page=com.atlassian.jira.plugin...
]
Mark Addleman commented on TEIID-1589:
--------------------------------------
I think it only makes sense to apply this at the column level since multiple translators
are potential involved in a single result set. Further complicating this problem is that
multiple translators could be involved on a row basis if we're talking about a UNION
statement. I'm not sure how to address attaching metadata on a row-wise basis but an
extension to the ResultSetMetadata interface to handle column-wise metadata would look
something like:
public Serializable getExecutionFactoryMetadata(String columnName);
metadata per translator per request
-----------------------------------
Key: TEIID-1589
URL:
https://issues.jboss.org/browse/TEIID-1589
Project: Teiid
Issue Type: Feature Request
Reporter: Mark Addleman
Assignee: Steven Hawkins
Priority: Minor
I'd like to the translator to attach metadata to the results it passes back to the
Teiid JDBC client. For example, I'd like the translator to examine the connection
object and decorate the returned data with which datasource provided the data.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira