A Diumenge, 2 de desembre de 2012 17:16:49, Teagarden va escriure: > On Dec 2, 2012, at 7:35 PM, Cédric Krier <[email protected]> wrote: > > It could be possible to cache the default_get method but I'm not sure it > > is a correct solution. I think it is better to say, you have to create > > the singleton. Also I think it is the Property field that are slow and > > they should be replace by explicit Function field using a new table with > > real foreign key. > > Property fields are probably one of the slowest components and the > bottleneck appears to be the entity attribute value model on ir.property > > +1 for replacing configuration singletons with function fields and an > intersection table with fk to company and the related model.
Yes, that was already agreed and I think it even was on the roadmap. Also the advantage is that although it is an API change we can leave fields.Property as deprecated for one or two releases, if some people want to avoid the change. -- Albert Cervera i Areny http://www.NaN-tic.com Tel: +34 93 553 18 03 http://twitter.com/albertnan http://www.nan-tic.com/blog -- -- [email protected] mailing list
