erp5_base: Do not explicitly set accounts on movement.
The resource-to-account relationship is intended to be declared by predicates (which are used here), but should only be explicitely set on movements when they *differ* from these rules, as special overrides. So, setting default accounts on movement is unnecessary work: - predicate lookup is expensive, and business-model-specific shortcuts may be available which such generic implementation cannot implement - multiplying unneeded relationships increases category table size, which is generally detrimental to performances
Showing
Please register or sign in to comment