Field definition translate=Yes is not stored in ir.model.fields
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Odoo Server (MOVED TO GITHUB) |
Fix Released
|
Low
|
OpenERP Publisher's Warranty Team |
Bug Description
The field translate exists in the database, but it's not used, NULL in all databases on all fields here.
Reading ir.model.fields over OpenObject doesn't work either, compare http://
I compared two dumps: dumped database (with pg_dump), changed one field to translate=True, -u modulename, dumped again:
diff shows no indication of translate= being stored anywhere in the database. Same effect on removal of translate=True.
In ir_model.py, create and write are customized, handling model_props like translate somehow, but I can't figure out where translate is stopped from going into the database properly.
As read is not customized, though, I think this might be the problem.
So there is no way to detect from a function (action triggered) if a field is translatable at all.
Related branches
- OpenERP Core Team: Pending requested
-
Diff: 43 lines (+6/-5)1 file modifiedbin/osv/orm.py (+6/-5)
- OpenERP Core Team: Pending requested
-
Diff: 55 lines (+7/-5)2 files modifiedopenerp/addons/base/base.sql (+1/-0)
openerp/osv/orm.py (+6/-5)
- OpenERP Core Team: Pending requested
-
Diff: 58 lines (+8/-5)2 files modifiedbin/addons/base/base.sql (+1/-0)
bin/osv/orm.py (+7/-5)
(tested on 6.0.2 and up-to-date lp/6.0)