Comment 158 for bug 1160365

That is "partner_id + commercial_id" we would need to face all the
issues described here except 1) may be
https://docs.google.com/presentation/d/1y0njSpm9kqJPGFUQQTiRMIpT1M5CfKppNhslvpl-aM4/pub?start=false&loop=false&delayms=3000#slide=id.p

and if you read that thread well, people actually want "partner_id +
contact_id", just for these reasons.

On Sun, Apr 14, 2013 at 6:03 PM, Raphael Valyi <email address hidden> wrote:

> On Sun, Apr 14, 2013 at 5:37 PM, Fabien (Open ERP) <email address hidden> wrote:
>
>> On 14/04/13 20:20, Michael Telahun Makonnen wrote:
>> > +1 for partner_id + contact_id
>>
>> Why not partner_id + commercial_id ? This would be the solution to
>> satisfy everyone's need
>
>
> Because of course it would forces us to change all the code everywhere
> where partner_id is used: that is what we call "swapping" the semantic.
> This is a lot of very risky work we cannot afford doing for v7.
> Instead of the added field is contact_id. Everywhere code that comes from
> v6.1 (the vast majority of the code that matters), we can still use
> partner_id normally.
> The question only becomes where exactly do we add these contact_id fields
> and how exactly do we add them (in the ORM automatically, in every class
> but then we need collaboration from OpenERP SA and less also ensure we
> avoid code duplication like when patching the views) and also where exactly
> are the few places with contact_id should be used instead of partner_id in
> reports or to send a mail.
>
> Regards.
>