openerp-community team mailing list archive

["Jose Antonio Morales Ponce\(vauxoo\)" <jose@xxxxxxxxxx>]

Well it all depends on whether you want the record or field is not in the
db.

If you want the field will not save, store = False to be, it will make the
sensible and calculated field to display automatic, fnct_search there if
you need because there is being saved.

If you are using store = {model: method} the field is saved in the db and
calculated each time you have a change in the selected model, as this is
saved no need to use a fnct_search.

It's about what you need at that time, if you want to save the field or not
El 25/02/2013 10:26, "Michael Telahun Makonnen" <mmakonnen@xxxxxxxxx>
escribió:

> Ok. I hadn't thought of that.
> My main point was that it should be searchable. Otherwise, it's broken.
>
> Which way is the recommended way?
> 1. store=False and use fnct_search
>     or
> 2. store={...} (and have the value in the db updated when the related
> field changes).
>
> I'm just wondering for my own future reference.
>
> Regards,
> Mike.
>
> --
>
> https://code.launchpad.net/~openerp-community/openobject-addons/trunk-bug-1090224/+merge/149980
> Your team OpenERP Community is subscribed to branch
> lp:~openerp-community/openobject-addons/trunk-bug-1090224.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-community
> Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openerp-community
> More help   : https://help.launchpad.net/ListHelp
>

-- 
https://code.launchpad.net/~openerp-community/openobject-addons/trunk-bug-1090224/+merge/149980
Your team OpenERP Community is subscribed to branch lp:~openerp-community/openobject-addons/trunk-bug-1090224.