c2c-oerpscenario team mailing list archive

["Stephane Wirtel \(OpenERP\)" <780584@xxxxxxxxxxxxxxxxxx>]

Hi!

For a customization, we need to find out in python code if a field is 
set to be translatable.

https://bugs.launchpad.net/openobject-server/+bug/780584

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://www.openerp.com/forum/topic24970.html 
<http://www.openerp.com/forum/topic24970.html>.

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.
(Actually, I think write/create is the problem, was the field in the 
database can easily be set)


This effects occurs at least in 6.0.2+ (regularly updated from 
launchpad), I haven't tried it on trunk.

I asked about this in IRC on May 10th, and xrg prepared a short fix to 
this problem:
http://git.hellug.gr/?p=xrg/openobject-server;a=commit;h=d7a8fa5352e995d526c

see diff:
http://git.hellug.gr/?p=xrg/openobject-server;a=blobdiff;f=bin/osv/orm.py;h=7a750710b3d31599ce2838cf2bd91d40b9ac50f9;hp=0a2300d6bb99ffad7e91596923dcacb96e277c40;hb=d7a8fa5352e995d526c;hpb=9c5a74926ff9d46e231a07e31f657a151aeba873

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/780584

Title:
  Field definition translate=Yes is not stored in ir.model.fields

Status in OpenERP Server:
  New

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://www.openerp.com/forum/topic24970.html.

  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.