-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[IMP]backend link to attribute.attribute. #47
base: 7.0
Are you sure you want to change the base?
Conversation
@Rona111 I didn't ask you to create a new field and keep the old one (and make it invisible...), you need to change the current field to link with another model ( |
@seb-elico Usually,we can not modified the field directly, because the old fields foreigh key still exists,and if you update the old data directly,the database will raise an error that there is no that id, and when you save the new data,the database will raise a error that the foreign key is wrong.modified the id is not enouth.the relationship between is still exist.so it's not a good way to update the old one directly.add the new field and migrate the data based one the old one ,and recreate the relationship between the two models is more simple and stable. |
@Rona111 clear, thanks. In that case, please:
|
@Rona111 Would it be possible to rename the old field to |
@seb no,rename the old field will lost all the data. |
@Rona111 Ok, so please rename the field |
cc @seb-elico |
…e-development Conflicts: mmx_magento_attributes/__openerp__.py mmx_magento_attributes/product_driver.py mmx_magento_attributes/product_model.py mmx_magento_attributes/product_scale.py
creation shouldn't be linked to Magento attribute (magento.attribute) of a specific backend but should be linked to attribute.attribute.