cubicweb #961831 migration failure when defining form fields [resolved]

In the cube conference, I use the cube shoppingcart, but define a custom field to override the behavior of the default form for ShoppingItem. This custom field references ShoppingItem in an attribute of the class. When Python reads the class definition, it looks for ShoppingItem in the schema, but since the migration and its add_cube('shoppingcart') has not been run yet, it can not find it. This means that one can not access the shell nor migrate the instance. Embracing the form field definition in a try/except fixes the problem, but is kind of ugly. Could not we find a better way to prevent this to happen ?

prioritynormal
typebug
appeared in<not specified>
done in3.9.9
load1.000
load left0.000
closed by#6392:faee4c380e50

Workflow history

from state (3)to statecommentdateUser
validation pendingresolved2011/05/27 15:51sthenault
donevalidation pending

version publiée

2010/10/22 18:11sthenault
opendone2010/10/04 19:07sthenault

Comments

  • 2010/10/01 17:36, written by sthenault

    would you have a snippet of the offending code?

    • 2010/10/01 21:55, written by nchauvat

      I think it is the migration of conference-0.5.0, but that ticket is not very important to me now.

      • 2010/10/04 07:41, written by adimascio

        I think the problem was (is) with code using the etype_relation_field factory, as in:

        class ShoppingItemInlineForm(forms.EntityFieldsForm):
    __regid__ = 'inline-shoppingitem-form'
    form_renderer_id = 'inline-shoppingitem-renderer'
    quantity = autoform.etype_relation_field('ShoppingItem', 'quantity')
    item_type = autoform.etype_relation_field('ShoppingItem', 'item_type')

        If either item_type or quantity is only defined in the new version of the schema, this code will break until the migration is done.

Ticket #961831 - latest update on 2011/05/27, created on 2010/05/12 by Nicolas Chauvat