Comment 7 for bug 799378

I have found something very similar in v6.1RC1, using certified modules.
If you install base_contact (that changes the behaviour of res.partner.address very deeply, adding some fields like 'location_id' and changing the definition of several ones), and you install the crm module (which inherits in crm.lead from res.partner.address), you will not be allowed to create crm.leads.

After the installing of both modules, at any attempt to call create an crm.lead (from UI or loading an xml or csv data file), it will raise an SQL error on the SQL insert statement due to the field 'location_id' not found on crm_lead table ('location_id' is a field inherited by a modified res.partner.address). This makes impossible to use crm and base_contact together (both, official and certified modules!)

In my opinion, this is a high importance fault. It is difficult to image a case where a crm user will not request the base_contact features. Additionally, it seems to be a conceptual fault in the osv framework, so most probably it will cause problems on other parts of real systems, where official and private modules for sure are combined.