Hi Olivier,
Yes I've considered forcing all fields on the unlink() side.
I was just considering keeping the same behaviour as v6.0 so we can still use
write(ids, {}) *hack* to force triggering stores update on a specific object -
this is really usefull when thing get wrong and we quick way to recompute
stores without touching DB values until bug is fixed.
But I agree with you, forcing all columns is more explicit - I will change my
code accordingly. Perhaps we can introduce a better way to force store compute
on trunk ?
Cheers,
Xavier
--
https://code.launchpad.net/~openerp-dev/openobject-server/6.1-opw-577292-xal/+merge/121195
Your team OpenERP R&D Team is subscribed to branch
lp:~openerp-dev/openobject-server/6.1-opw-577292-xal.
_______________________________________________
Mailing list: https://launchpad.net/~openerp-dev-gtk
Post to : [email protected]
Unsubscribe : https://launchpad.net/~openerp-dev-gtk
More help : https://help.launchpad.net/ListHelp
