]
Van Halbert moved JBEDSP-1172 to TEIIDDES-331:
----------------------------------------------
Project: Teiid Designer (was: JBoss Enterprise Data Services Platform)
Key: TEIIDDES-331 (was: JBEDSP-1172)
Component/s: Import/Export
(was: Designer)
Affects Version/s: (was: 5.5.2)
SalesForce importer's Native Type value for columns causes
problems when tables are materialized.
-------------------------------------------------------------------------------------------------
Key: TEIIDDES-331
URL:
https://jira.jboss.org/jira/browse/TEIIDDES-331
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Environment: Windows 2003 Server, 5.5.2 MMX with SFDC Technical Preview Release
installed
Reporter: Michael Walker
Priority: Minor
The SFDC importer uses the Native Type field of each column to represent the native type
in SFDC. These types can include "picklist", "currency", and other
SFDC-specific types. The importer correctly maps these native types to the appropriate
Java type, e.g. "string", "double", etc.
Views built off imported SFDC objects will also contain this native type information.
If these views are materialized, our materialized views script generation will use
whatever Native Type setting is found in the view. This ends up generating table creation
scripts that uses types that have no meaning in the source system (see attached example).
If we continue to use materialized views script generation, we should take care not to
use invalid native type values, but instead, convert the Java type back to the appropriate
SQL type for the source system.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: