[
https://issues.jboss.org/browse/TEIIDDES-1531?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-1531:
----------------------------------------
The following type check is currently in place. I imported from BQT2 (SQL SERVER) and a
column with VARCHAR2 was imported as string() datatype.
So I think this is already implemented.
{code:title=OracleModelProcessor.java|borderStyle=solid}
protected EObject findType( final String jdbcTypeName,
final List problems ) {
String standardName = jdbcTypeName;
if (VARCHAR2_TYPE_NAME.equalsIgnoreCase(jdbcTypeName) ||
NVARCHAR2_TYPE_NAME.equalsIgnoreCase(jdbcTypeName)) {
standardName = RelationalTypeMapping.SQL_TYPE_NAMES.VARCHAR;
}
return super.findType(standardName, problems);
}
{code}
Exception when updating Oracle NVARCHAR2 columns
------------------------------------------------
Key: TEIIDDES-1531
URL:
https://issues.jboss.org/browse/TEIIDDES-1531
Project: Teiid Designer
Issue Type: Bug
Components: Teiid Integration
Environment: Windows 7 64 bit, Eclipse Indigo, Oracle jdbc thin 11.2.0.2.0
Reporter: I Leitch
Assignee: Mark Drilling
Fix For: 8.1
If it doesn't already do so, the Oracle importer should import NVARCHAR2 (type 1111)
and VARCHAR2 (type 12) as string.
--
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