Redundant attributes

[Valery Sorokin]

Hello all,

As I can see product attributes are bound to product classes having relation of one-to-many. This means that common attributes such as 'weight', 'dimensions' or 'color' are redundant. Each product class has its own instances of attribute of the same name and same meaning. Or am I wrong?

Wouldn't it be better to have many-to-many relation between product attributes and classes? That should make it possible to avoid redundant data and to improve attribute management ie attribute translation.

Valery Sorokin

[David Winterbottom]

On 16 September 2014 11:46, Valery Sorokin <val...@valsor.com> wrote:

Hello all,

As I can see product attributes are bound to product classes having relation of one-to-many. This means that common attributes such as 'weight', 'dimensions' or 'color' are redundant. Each product class has its own instances of attribute of the same name and same meaning. Or am I wrong?

​Product attributes can belong either to a product class or to an individual product. But you're right that you can't have an attribute that is linked to multiple product classes.​

 

Wouldn't it be better to have many-to-many relation between product attributes and classes? That should make it possible to avoid redundant data and to improve attribute management ie attribute translation.

​I'm not sure - but it sounds plausible. I'm surprised with causes a translation problem - if two attributes have the same name (eg "weight"), doesn't this just show up as one string to translate?​

 

Valery Sorokin

--
https://github.com/tangentlabs/django-oscar
http://django-oscar.readthedocs.org/en/latest/
https://twitter.com/django_oscar
---
You received this message because you are subscribed to the Google Groups "django-oscar" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-oscar...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-oscar.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-oscar/208752b3-c51f-41b0-b54e-3dccde726c15%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

David Winterbottom
Technical Director

Tangent Snowball
84-86 Great Portland Street
London W1W 7NR
England, UK

[Valery Sorokin]

Sorry about translation example. I didn't check it before. Maybe it's
because of my background and some resistance I feel having to deal
with redundant attributes. Many-to-many relationships between
attributes and product class seems to me more logical. As a matter of
fact I cannot see the benefits of having here one-to-many
relationship. Am I missing something? Please don't take it as a
critic. I just try to understand the reasons for such decision.

> https://groups.google.com/d/msgid/django-oscar/CAA0jhkpqvST7%2Bw-i3MXNs4B68ZajmJmbrf%3DSKZ6rey%3Dv%2B-Lk1g%40mail.gmail.com.