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.