mismatch beetween 3.2.7 and new version 3.3.2

13.01.2012 12:41
#1
notfall
Joomshopping forum user no avatar
Name: Patient
04.03.2011
Posts: 59
Quote
mismatch beetween 3.2.7 and new version 3.3.2

I am surpised ... what is that?

it seems to me knitting with hot needle...

Now my product table as over 60 columns.

An relation table will be more effective, datatypes should be better matched.

PS: column DETAILS is my own - i need an multiple attribute-options set. this field stored an json object.
mismatch beetween 3.2.7 and new version 3.3.2

 
13.01.2012 16:24
#2
webdesigner
(Support Team)
User webdesigner
Name: Admin
05.08.2010
Posts: 16479
Quote
Aw: mismatch beetween 3.2.7 and new version 3.3.2

You can always change (optimize store for you)

 
14.01.2012 10:37
#3
notfall
Joomshopping forum user no avatar
Name: Patient
04.03.2011
Posts: 59
Quote
Aw: mismatch beetween 3.2.7 and new version 3.3.2

This decision (js 3.2.7) using INT for mysql column and (js 3.3.2) using TEXT for mysql column makes not sense and is not an advantage in my opinion. Product characteristics are available now as TEXT in (js 3.3.2) - without translations usefull in most cases for numeric entries like car doors "5". Using an LIST for car doors like (js 3.2.7) is wasting, because car doors "5" not need an translation. (exception de FÜNF- en FIVE) or computer screen width (de VIERUNDZWANZIG en twenty four) (but people with brain would be write "24" for both).

What is the advantage for using column type TEXT for extra_field_XX in product table?

 
Copyrights MAXXmarketing GmbH. All Rights Reserved