© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
4d1350f
(Get the code!)
Hi,
For the record, this can be considered as a bug but a very small one :)
Actually, the 'translate' column in ir_model_fields doesn't exist right at the start of the ORM; i.e. it is not created by base.sql. This means that the proposed fix is not enough, the column should be added in base.sql.
Now, the bug materializes itself only when doing a 'read' on ir_model_fields for a python field: we will always read that a python field is not translatable. For a custom field, the value will be correct.
But in the GUI, the flag next to a field to show if it is translatable is always correct: it is still possible for a non-custom field to see if it is translatable by inspecting the _columns attribute of the model.
We will probably add the translatate field in base.sql so the information is correct even for python fields though.