c2c-oerpscenario team mailing list archive
-
c2c-oerpscenario team
-
Mailing list archive
-
Message #32197
[Bug 789576] Re: fields.related override: store function persists
I change the status of this bug report. You can see the reason on the
merge proposal, copy/pasted here:
The idea seems good.
Instead of removing the function when the field is not a function field
or not stored, we can in fact always remove it. This means the loop (a
few lines below the changed code) to test if the current function will
be appended or not can be removed.
The for-loop with calls to list.remove() is not safe (as it changes the
iterated list). You can use instead a list comprehension ar a call to
filter().
** Changed in: openobject-server
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to OpenERP Project Group.
https://bugs.launchpad.net/bugs/789576
Title:
fields.related override: store function persists
Status in OpenERP Server:
In Progress
Bug description:
Hi,
when a fields.related is overridden by a regular field, the store
function is not removed. Values assigned to the field by the users of
the system get overwritten immediately by the store function of the
original field definition.
Here is an example from the HR module:
'parent_id': fields.related('department_id', 'manager_id',
relation='hr.employee', string='Manager', type='many2one', store=True,
select=True, readonly=True, help="It is linked with manager of
Department"),
We want to override this definition with
"fields.many2one('hr.employee', 'Manager')", but any write on this
field triggers a recalculation based on the related field.
The problem is in orm.__init__() where the list of a model's store
functions is populated but never purged.
Reproducable with openerp-server/6.0 rev. 3435.
Cheers,
Stefan.
To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-server/+bug/789576/+subscriptions
References