If you are planning on using these attributes in filters in the ecommerce front-end to help customers refine their product interests then you will be in trouble, as attributes shown in the attribute filter are ALL the attributes from ALL the products - i.e. if you have product categories of computers and monitors then the attribute list will always show as :- processor speed (2,3,5 GHZ etc), RAM (16,32,64GB etc) screen size (17",21",27" etc) speakers (none,mono,stereo etc) regardless of what product category you are in. Thus the attribute filter currently is not useful for refining product interest once inside a category. If you are proposing to have many attributes for many different kinds of product category then the attributes filter will rapidly become unusably massive.
If you are defining your attributes using the module product_custom_attributes (v.6.1 or 7), then you are right that it does create a new column for every attribute you add, and you may incur in the postgres limit of maximum columns per table (the limit is actually on the row size), which is between 250 and 1600 depending on the type of fields.
If, instead, you are using the product variant attributes of Odoo 8 then no: they are stored in the tables product_attribute, product_attribute_line, product_attribute_value and each attribute/attribute value/attribute line is a line in these tables, so you won't have any limit.
Please try to give a substantial answer. If you wanted to comment on the question or answer, just use the commenting tool. Please remember that you can always revise your answers - no need to answer the same question twice. Also, please don't forget to vote - it really helps to select the best questions and answers!
About This Community
|Asked: 7/7/14, 10:35 AM|
|Seen: 969 times|
|Last updated: 3/16/15, 8:10 AM|