Return to Question

Can anyone tell why magento saves product attribute multiselect as varchar and hence its options in catalog_product_entity_varchar as array?

With options saved as array i can't do the correct between catalog_product_entity_varchar and eav_attribute_option_value on value=option_id

Is not it better to consider multiselect as "multidropdown" and save its options like int and insert multiple records in catalog_product_entity_int?

So is possible join correctly  catalog_product_entity_int with eav_attribute_option_value on value=option_id

Do you know why magento saves multiselect attribute type as varchar and relative product assocations in catalog_product_entity_varchar as array?

With array is not possible join between catalog_product_entity_varchar and eav_attribute_option_value on value=option_id

when value is varchar like 1,2,3, because option_id is int.

Isn't better considerer multiselect as multiple int and insert multiple record in catalog_product_entity_int?

So is possible join correctly  catalog_product_entity_int and eav_attribute_option_value on value=option_id

Can anyone tell why magento saves product attribute multiselect as varchar and hence its options in catalog_product_entity_varchar as array?

Is not it better to consider multiselect as "multidropdown" and save it like an int and insert multiple records in catalog_product_entity_int?

If it were so I could join catalog_product_entity_int with eav_attribute_option_value on value=option_id

What I can't do with catalog_product_entity_varchar if value is an array.

Can anyone tell why magento saves product attribute multiselect as varchar and hence its options in catalog_product_entity_varchar as array?

With options saved as array i can't do the correct between catalog_product_entity_varchar and eav_attribute_option_value on value=option_id

Is not it better to consider multiselect as "multidropdown" and save its options like int and insert multiple records in catalog_product_entity_int?

So is possible join correctly catalog_product_entity_int with eav_attribute_option_value on value=option_id

Can anyone tell why magento saves product attribute multiselect as varchar and hence its options in catalog_product_entity_varchar as array?

Is not it better to consider multiselect as "multidropdown" and save it like an int and insert multiple records in catalog_product_entity_int?

If it were so i could join catalog_product_entity_int with eav_attribute_option_value on value=option_id

what i can't do with catalog_product_entity_varchar if value is an array.

Can anyone tell why magento saves product attribute multiselect as varchar and hence its options in catalog_product_entity_varchar as array?

Is not it better to consider multiselect as "multidropdown" and save it like an int and insert multiple records in catalog_product_entity_int?

If it were so I could join catalog_product_entity_int with eav_attribute_option_value on value=option_id

What I can't do with catalog_product_entity_varchar if value is an array.