Cédric Krier
c2059bddf0
By using a class with slots instead of standard dict, we can reduce a lot the memory usage to store the record data in the caches and values. Also we can rely on the data in the cache to exist only for real field which can be used to create a fast path in ModelStorage.__getattr__. As now storing data in the cache has no extra cost, we can store data from the transactional cache in the local. This allow also to have a shorter path in ModelStorage.__getattr__. For more memory efficiency, we remove the record from the cache instead of clearing them. It was better to clear a dict but a record is less expensive to re-instantiate than clearing. issue9369 issue9225 review297861002
Party Relationship Module ######################### The party relationship module allows to define different types of relations between parties. Each relation is defined by a relation type. A reverse relation type can be defined, so when creating a relation of a type, the reverse relation will be automatically created. It is possible to order parties by how closely related they are to a defined party. The distance is calculated based on the number of steps it takes to get from the defined party to another. By default all the different types of relationship are considered, but this can be limited by adding ``relation_usages`` to the context. Configuration ************* The party_relationship module use the section `party_relationship` to retrieve some parameters: - `depth`: The maximum number of steps to consider when calculating the distance between parties. The default value is `7`.