[
https://issues.apache.org/jira/browse/OFBIZ-10008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16425219#comment-16425219 ]
Jacques Le Roux commented on OFBIZ-10008:
-----------------------------------------
This started with this discussion [
https://markmail.org/message/g23cyoenv7qttdew]
I then suggested
{quote}A new mechanism should be introduced to prevent
this.saveEntitySyncRemoveInfo(value.getPrimaryKey());
in GenericDelegator.removeValue()
It seems to me that this should be set in entityengine.xml by delegator. Or maybe even simpler with a general property.
{quote}
Has anybody worked on it since?
The question is: should it be disabled by default?
It's only needed when you use EntitySync jobs. OOTB the "Clear EntitySyncRemove Info" job which uses the cleanSyncRemoveInfo service is run daily. But if you "inadvertently" remove this job then EntitySyncRemove records stack unnoticed.
So it's a balance between not having EntitySyncRemove records stack and forgetting to record records to remove when using EntitySync jobs. Because EntitySync is a kind of sorcery I'm undecided on this and I guess that's also why we have this OOTB.
> 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
