Consider a model M that defines `display_name` as a computed stored field, then an extension of M that introduces a mixin model A before that definition in the MRO of M's class. The model A is expected to have an automatic, non stored field `display_name`, while M must have its non-automatic, stored field `display_name`. closes odoo/odoo#36427 Signed-off-by: Raphael Collet (rco) <rco@openerp.com>