[
https://issues.jboss.org/browse/TEIID-2711?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2711:
---------------------------------------
Also another workaround (similar to the patch) is to alter the source xml column type to
instead by clob and use a native-query on the table to convert that column to a clob:
select col1, col2, to_clob(xml_col) ... from tbl
Based upon this workaround and the documented (but not locally verified) approach from the
first comment, I'm inclined to not commit this just yet.
Better support for Oracle SQLXML values
---------------------------------------
Key: TEIID-2711
URL:
https://issues.jboss.org/browse/TEIID-2711
Project: Teiid
Issue Type: Quality Risk
Components: JDBC Connector
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Attachments: oracle.patch
When using a typical driver configuration to read oracle xml values, the driver will
return an OPAQUE instance rather than a SQLXML value.
--
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