Great Idea guys. It would be a great Enhancement. Am 19.08.10 10:30, schrieb Sharoon Thomas: > Hi, > > Thats a very interesting idea. > > To make it general would be easy but gives amazing functionality. > > We will refactor the code for the same and resubmit for the review. > > Thanks, > > Sharoon Thomas > > On 18 Aug 2010, at 17:25, 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 >> >> ProductEAV -> ProductAttribute >> ProductProduct -> Product >> >> Some more comments on codereview. >> >> Regards, >> Mathias >> >> -- >> >> Mathias Behrle >> MBSolutions >> Gilgenmatten 10 A >> D-79114 Freiburg >> >> Tel: +49(761)471023 >> Fax: +49(761)4770816 >> http://mbsolutions.selfip.biz >> UStIdNr: DE 142009020 >> PGP/GnuPG key availabable from any keyserver, ID: 0x8405BBF6
-- [email protected] mailing list
