[
https://issues.jboss.org/browse/TEIIDDES-303?page=com.atlassian.jira.plug...
]
Steven Hawkins commented on TEIIDDES-303:
-----------------------------------------
Sort of. If you develop a mat view model for external materialization that has a string
length restriction that is inaccurate, and if you use the default generated create schema
script, and you are using a database that doesn't automatically truncate, then this is
still possible.
However there is no issue with internal materialization and external materialization is
not really considered a built-in process so this isn't necessarily an up-to-date
issue.
Materialization can fail when MMX passes back data that exceeds the
maximum length, as defined in the materialized model.
-------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-303
URL:
https://issues.jboss.org/browse/TEIIDDES-303
Project: Teiid Designer
Issue Type: Bug
Affects Versions: 7.1
Environment: Windows 2003 Server, 5.5 + patch 62
Reporter: Michael Walker
Labels: materialization
When querying data from a source model, MMX allows data to exceed the model's length
restrictions. For example, a SalesForce model might have a column called
"biography:string(200)". Querying data from this column can sometimes result in
a string that exceeds 200 characters, and MMX does not truncate the data.
This causes problems when you attempt to materialize the model. Since the create table
scripts are based on the model definition, the mat view table will not accommodate data
that exceeds the length restrictions. Following the previous example, this means that the
biography data will raise a "inserted length too large for column" error,
causing the rest of the materialization to fail.
The new materialization process will need to account for this issue, or perhaps MMX
should truncate data that exceeds the defined length found within the model.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira