Comment 1 for bug 1289781

Hi Martin,

Is it OpenERP v8? I suspect a "bug" in this version as "fields.string" does not exist, and it appears to be used as a type in some fields.function instead of the type "char":

openerp@oerp:~/instances/openerp-8.0/openerp/addons$ grep -Hn "type=.string." $(find . -name "*.py")
./crm/crm.py:175: type="string", readonly=True, multi='_get_opportunities_data',
./crm/crm.py:178: type="string", readonly=True, multi='_get_opportunities_data',
./sale_crm/sale_crm.py:105: type='string', readonly=True, multi='_get_sale_orders_data',
./sale_crm/sale_crm.py:108: type='string', readonly=True, multi='_get_sale_orders_data',
./sale_crm/sale_crm.py:111: type='string', readonly=True,

These fields seem to have been introduced from the v8.0.

Anyway, in OERPLib, maybe the best choice would be to set the "char" type by default for unknown type, raising an exception can be a blocking point...