Steps to reproduce (warning! destroy the database!):
1) In a custom module, adds the following lines (these lines are in the base_partner_merge backport):
class res_partner(osv.Model):
_inherit = 'res.partner'
_columns = {
'id': fields.integer('Id', readonly=True),
'create_date': fields.datetime('Create Date', readonly=True),
}
2) Install the module
3) Uninstall the module
Result:
The columns 'id' and 'create_date' are dropped from the database.
Expected:
The columns 'id' and 'create_date' are still there.
Cause: the uninstall looks in ir_model_data and removes the columns no longer referenced by any record (a record in ir_model_data indicating that the column is still owned by another module). When we redeclare a special column, like "id", an ir_model_data entry is created for the custom module, example: base_partner_merge.field_res_partner_id, but the ORM does not create entries for theses columns normally -> when we uninstall the custom module, it removes the new xmlid and since there is no other xmlid, it drops the column.
Happens with https://code.launchpad.net/~camptocamp/partner-contact-management/add-base_partner_merge/+merge/189616 for instance.
Did you understood that uninstalling a module may trash the database as it will remove res_partner.id?
Is this bug really a *wishlist* ?