[
https://issues.apache.org/jira/browse/OFBIZ-10008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16425310#comment-16425310 ]
Jacopo Cappellato commented on OFBIZ-10008:
-------------------------------------------
I agree we should disable this feature by default.
As regards the mechanism, ideally the code should be refactored so that this features is not coded into the entity engine component; this behavior should be instead injected from an higher level, more specialized module (e.g. entityext).
However this refactoring is not trivial so for now I would opt for a general property (that we could remove when the code will be refactored).
> Add mechanism to prevent the usage of EntitySyncRemove
> ------------------------------------------------------
>
> Key: OFBIZ-10008
> URL:
https://issues.apache.org/jira/browse/OFBIZ-10008> Project: OFBiz
> Issue Type: Improvement
> Components: framework
> Affects Versions: Trunk
> Reporter: Chandan Khandelwal
> Assignee: Jacques Le Roux
> Priority: Major
>
> No configurations available to disable usage of EntitySyncRemove. And It is creating problems when having a large database and frequent delete operations.
> saveEntitySyncRemoveInfo is used to create EntitySyncRemove records in GenericDelegator.removeValue() and removeByPrimaryKey().
> Idea is to add mechanism to prevent the usage of EntitySyncRemove by adding configuration in entityengine.xml.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Locked
