A Dimarts, 27 de setembre de 2011 21:31:06, Cédric Krier va escriure: > Here is a summary about what I think for the future of Property. > > The current ir.property implementation is good because it will allow in the > future to create properties by the user as it doesn't require to change the > DB schema.
IMHO the good thing about current implementation is that it allows to make it possible for a developer to make all existing properties to depend on something which is not the company at once. However, I'm not sure if this is a very important feature in front of data integrity. So you do not want user defined fields to extend the existing model adding new columns dynamically? Wouldn't it be too slow to make those fields as properties if the user adds lots of them? > But also Albert is right about data integrity which could be important from > some kind of data. > So the idea will be to have a option on Property field to define which > Model to use (by default ir.property). Those Models should expose the same > API (set/get/search methods). > This will also allow to use external database to store those field in the > same idea as the Openlabs MongoDB field. > > On your keyboard, get set, go ! -- 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
