[
https://issues.apache.org/jira/browse/OFBIZ-7890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381317#comment-15381317
]
Rishi Solanki commented on OFBIZ-7890:
--------------------------------------
Community, we decided to not provide delete operation for this entity, could
you please help us here, what should we do in such cases. Here no from
date/thru date or status field exists. But it contains the historical data IMO,
and as per the entity def it can not (and should not) expire.
We have two option;
1) Do not provide delete service for such cases. (In ticket description I
proposed to follow this.)
2) Provide delete service and let the business user decide weather to remove
any record or not. We can add description in the service something like;
"Entity contains historical data, and ideally not used."
> Improvements in BudgetRevision entity definition and services
> -------------------------------------------------------------
>
> Key: OFBIZ-7890
> URL: https://issues.apache.org/jira/browse/OFBIZ-7890
> Project: OFBiz
> Issue Type: Sub-task
> Components: accounting
> Affects Versions: Trunk
> Reporter: Rishi Solanki
> Priority: Minor
>
> Required improvements;
> - All is good with entity definition .
> - Add crud services using entity-auto. Make sure PK is not optional while
> create service.
> - Do related changes if any occurrence found for direct create/update/delete
> of this entity, and replace them with crud services implemented.
> - As no status/from date/thru date exists in entity, but it looks like it
> will contain the revisions of same data so history needs to be maintain. We
> should not provide service for delete its record.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
