c2c-oerpscenario team mailing list archive

["Ferdinand @ Camptocamp" <688914@xxxxxxxxxxxxxxxxxx>]

you are right  - it's "only" for database consistency. 
other programs be able to rely that there is a value. 
the function also could return a null value if not explicitly excluded.
hence the way it is now the function must check for not null and raise an error.
I just wanted to use a build in feature which apparently will only "work" after init. 
Hence I I suggest to change the sequence   
* compute field
* set not null

-- 
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/688914

Title:
  [6.0] add function field - required true - wrong sequence

Status in OpenObject Server:
  Incomplete

Bug description:
  adding a required function field in a module 
IMHO it must compute the value first and then issue 
ALTER TABLE set <field> not null;

if not a warning is issued like

 WARNING:orm:WARNING: unable to set column period_id of table stock_move not null !
Try to re-run: openerp-server.py --update=module
If it doesn't work, update records and execute manually:
ALTER TABLE stock_move ALTER COLUMN period_id SET NOT NULL