Jacques Le Roux commented on OFBIZ-10008:

Here is a patch, I did not commit because, though I don't think it's needed, I 
wondered if we should handle it at the tenant level. Of course it would then 
need a bigger effort. Also I wondered if the test/filter should be part of 
saveEntitySyncRemoveInfo() (comment "don't store remove info on entities where 
it is disabled") but it would be diluted and is more appropriate at a higher 

I'm currently (slowly) working on 2 related aspects: "Separate System and 
Business properties" (new thread to come on dev ML) and refactoring (actually 
rewriting) the EntitySync documentation. And this slows things. For instance if 
we want to have this per tenant EntityUtilProperties should be used instead of 
UtilProperties, but there is no getPropertyAsBoolean() in EntityUtilProperties.

> 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
>         Attachments: OFBIZ-10008.patch
> 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

Reply via email to