On 18/08/10 18:25 +0200, Mathias Behrle wrote: > * Betr.: " [tryton-dev] Product Attributes EAV model" (Wed, 18 Aug 2010 > 13:46:55 +0100): > > > Hello All, > > > > We have built a POC for the EAV [1] model of storing product attibutes. > > Quite > > often we have to add extra fields to product depending on specific customer > > installations. Like color, manufacturer etc. > > > > This is a general approach to the problem by having a relationship between > > products and attributes just like contact mechanisms of party. > > > > I request your comments and code review on the same. > > > > [1] http://en.wikipedia.org/wiki/Entity-attribute-value_model > > Very interesting concept, thanks a lot! > > For an even more generic generic way, I would even favor to put models > > ProductAttributes -> Attribute > ProductAttributeOptions -> AttributeOption > > in a separate module attribute (thus they could be (re)used on a number of > different objects where the same concept could be required (like party in > [1])) > > and to do only the product specific implementation in module product_attribute > containing models
But what will be the advantage to have all atributes in one table? Because you will have the same attribute available for any Model, I find it strange. -- Cédric Krier B2CK SPRL Rue de Rotterdam, 4 4000 Liège Belgium Tel: +32 472 54 46 59 Email/Jabber: [email protected] Website: http://www.b2ck.com/
pgpp7uTuzKEIA.pgp
Description: PGP signature
