Comment 4 for bug 493657

Revision history for this message
Raphaƫl Valyi - http://www.akretion.com (rvalyi) wrote : Re: Custom fields obstructing updates

Hello,

a few more tests if that can helps:

If you change the custom field state to "base" instead of "manual" (using SQL), then just after you created the field, it's usable in your object. After that change, you can also restart you server with --update=module_with_model_where_custom_field_is_defined
It won't break into the error mentioned by Xavier in that case.

However, doing this change, once you updated the server, the field won't be found anymore in the object, views will break into errors because of that for instance. So this is not a possible workaround and may be knowing how it behaves for 'base' state custom fields helps you to find a fix.