[
https://issues.apache.org/jira/browse/OFBIZ-5766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14164977#comment-14164977 ]
Julien NICOLAS commented on OFBIZ-5766:
---------------------------------------
Hi,
I don't know why using BigDecimal on a field that store millisecond ?
Maybe I'm wrong but do we need nanosecond ? Are systems able to provide nanosecond for time elapsed ? Do we need it in ERP ?
The problem is that BigDecimal use more memory and processor time to be managed unlike long variable.
I know that change again estimatedMilliSecond and estimatedSetupMillis from BigDecimal to long could be painful.
Maybe we could use the automatic conversion to do the job and solve this problem like that ?
Any suggestions ?
> Error when adding/modifying a task to a Production Run - field type error
> -------------------------------------------------------------------------
>
> Key: OFBIZ-5766
> URL:
https://issues.apache.org/jira/browse/OFBIZ-5766> Project: OFBiz
> Issue Type: Bug
> Components: manufacturing
> Affects Versions: Release Branch 13.07, Trunk
> Reporter: Guillaume Sigoigne
> Assignee: Nicolas Malin
> Priority: Trivial
> Attachments: Add-Task-To-Production-Run-13.07.patch, Add-Task-To-Production-Run-trunk.patch
>
>
> You select a production run, then you click on "Task" tab to list tasks included in the production run.
> You are not able to add a new task or modify any of already included tasks because of field type error.
> Following events and services are waiting estimatedMilliseconds and estimatedSetupMillis as BigDecimal instead of Double.
> Events :
> ProductionRunSimpleEvents.editProductionRunRoutingTask
> ProductionRunSimpleEvents.addProductionRunRoutinsTask
> Services :
> services_production_run.addProductionRunRoutingTask
> services_production_run.checkUpdatePrunRoutingTask
> Add-Task-To-Production-Run (13.07 and trunk releases) change fields type from BigDecimal to Double.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Locked
