Renaming fields in Openerp

Bug #488211 reported by www.mgazelle.com
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Odoo Server (MOVED TO GITHUB)
Invalid
Undecided
Unassigned
Nominated for Trunk by Numérigraphe

Bug Description

Fields are not handeled correctly when renamed.

1. Create an object "x_product_category" with a field x_name and a field x_code
2. Create an object "x_product" with a field x_name and a field x_category as many2one with a rel object "x_product_category" and should be required
3. Create an a product category
4. Create a product
5. Rename the field x_category in step 2 to x_category_id
4. Create a new product.

You will get a warning that the field x_category can not be empty.

This behaviour is due to the fact that Openerp did create a second column in the x_product table with the name x_category_id instead of renaming the first one.

Revision history for this message
Numérigraphe (numerigraphe) wrote :

I may be wrong but I think this can only be improved if you somehow tell the server that the field was renamed, and is not a new field.
May I humbly suggest you have a look at this bleueprint? https://blueprints.launchpad.net/openobject-server/+spec/refactor-fields
Please comment on the blueprint's whiteboard if you think it fits your needs.
Lionel.

Revision history for this message
Jay Vora (Serpent Consulting Services) (jayvora) wrote :

Closing the bug, as the blueprint is created.

By the way, its not a simple code that will rename the column.

Thank you.

Changed in openobject-server:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.