[
https://issues.apache.org/jira/browse/OFBIZ-5487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13871185#comment-13871185
]
Christian Carlow commented on OFBIZ-5487:
-----------------------------------------
The FLOAT logic in ModelUtil.induceFieldType() includes this rule:
if (length > 18 || precision > 6) return "invalid-" + sqlTypeName + ":" +
length + ":" + precision;
The MSSQL database has FLOAT fields with length=50 and MONEY fields with
length=19. I don't think any of the fields have values that cannot be
converted to length 18 with precision 6.
Does anyone know if increasing the max length and precision is likely cause any
issues?
> Improve induceFieldType() of ModelUtil.java to handle MSSQL FLOAT types
> -----------------------------------------------------------------------
>
> Key: OFBIZ-5487
> URL: https://issues.apache.org/jira/browse/OFBIZ-5487
> Project: OFBiz
> Issue Type: Improvement
> Affects Versions: SVN trunk
> Reporter: Christian Carlow
>
> When using the ModelInduceFromDb.jsp to import MSSQL data many of the fields
> were assigned to types like "invalid-float:0:50". This is because the
> induceFieldType() of ModelUtil.java does not handle "FLOAT The function
> should be changed to allow FLOAT type.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
