Comment 103 for bug 1160365
Revision history for this message
| Fabien (Open ERP) (fp-tinyerp) wrote Re: [Bug 1160365] Re: [7.0] incorrect handling of contact/companies for invoicing and related purposes | #103 |
On 10/04/13 21:30, Maxime Chambreuil (http://
wrote:
> @ Fabien
>
> On the performance perspective, I would be interested to know how you
> solution behave.
>
> I foresee that your solution will save time on the write but increase on
> reporting.
It's not an issue. You can do a fields.related() with store=True.
> Raphaël solution will take more time on the write (but won't be
> significant, it is just one field to compute), but will be faster when
> reporting (no need to look for the 1st commercial entity id).
As we said, we think adding a field (Raphaël's solution) was not the
real issue. We did not followed his proposition because we think it does
not fix all business cases, it does not handle the other problems, it
does not respect the direction foreseen in v7 which may break some
modules unless we do huge changes in several models.
> Other scenario for you: how do you handle the case where Joël is now
> working for C2C CH ? Will its claim follow to C2C CH or will it stay
> with C2C FR ? From a user standpoint, I expect the claim to stay with
> C2C FR.
>
If Joël start working for another company:
- you have to create another Joël in the new company or
- you install base_contact to handle this scenario
But changing the company of Joël may create inconsistencies in
the DB (same than in v6.1 and Raphaël's proposition)
Fabien