Mapping to biginteger is possible. Currently only the oracle translator will make that mapping with the useIntegralTypes import setting. You could certainly request the biginteger mapping for precision >= 19 as default behavior.
Hello Stevens .. is there a similar setting for MSSQL DB ? I have same DB on oracle and on MSSQL. I want to use same virtual view for oracle and MSSQL but i get different column types (bigdecimal for oracle and long for MSSQL). casting solves the problem. I casted the columns to Long so that it would be the same type for MSSQL and oracle. but it made bad performance for oracle.
i want to make the columns biginteger for both DBs (ORACLE/MSSQL) but without casting.
is there a way ?
Currently you'd have to specify the source DDL, rather than rely upon the import.
Otherwise, you can log an enhancement for the automatic mapping to biginteger.
How to specify the source DDL ?
1 of 1 people found this helpful
DDL supported Schema Object DDL · Teiid Documentation
In sample above the DDL is defined on VIRTUAL view, you can do same on PHYSICAL view too. A example like that is