Guest Posted January 22, 2016 Posted January 22, 2016 Hi, After 10 Years of OSCommerce, I had to restart from scratch and ran again into an old OSC problem: The product ID is still 12 Chars only. Why so narrow? We don't have to spare every byte any more, do we? The international ISBN standard for books is 13 chars and will not fit into OSCommerce ProductID, EAN is 13 chars as well, many product codes in the industry are wider. OK the fix is easy, but wouldn't it be as easy to extend it to 16 or better 24 Chars in the standard and to avoid future trouble? Regards RIN
multimixer Posted January 22, 2016 Posted January 22, 2016 How is the products_id related to EAN code or ISBN or anything else? It is used only internally My community profile | Template system for osCommerce - New: Responsive | Feedback channel
burt Posted January 22, 2016 Posted January 22, 2016 I think @@rin67630 refers to products_model... And, ummmmm, taken direct from the install SQL products_model varchar(64)
multimixer Posted January 22, 2016 Posted January 22, 2016 Yes, products model make a sense I just downloaded osCommerce from here and in the install sql it is products_model varchar(12), So I guess that OP is right My community profile | Template system for osCommerce - New: Responsive | Feedback channel
burt Posted January 22, 2016 Posted January 22, 2016 Hmm. That's the normal osCommerce, if you're using that, a model of 12 is the least of your worries. Anyone starting from scratch would be best advised to use the Responsive osCommerce.
burt Posted January 22, 2016 Posted January 22, 2016 Split => chit-chat about Responsive vs Normal @ http://www.oscommerce.com/forums/topic/408917-responsive-vs-normal/
♥bruyndoncx Posted January 22, 2016 Posted January 22, 2016 if database size/space is no concern, and you want to search efficiently on products model, I think you should be using a char field that has fixed length for each entry and your index will be much more performant KEEP CALM AND CARRY ON I do not use the responsive bootstrap version since i coded my responsive version earlier, but i have bought every 28d of code package to support burts effort and keep this forum alive (albeit more like on life support). So if you are still here ? What are you waiting for ?! Find the most frequent unique errors to fix: grep "PHP" php_error_log.txt | sed "s/^.* PHP/PHP/g" |grep "line" |sort | uniq -c | sort -r > counterrors.txt
Guest Posted January 26, 2016 Posted January 26, 2016 if database size/space is no concern, and you want to search efficiently on products model, I think you should be using a char field that has fixed length for each entry and your index will be much more performant Performance should only be a concern for really huge shops. With some thousand products I don't have to worry about the product indexing.
Guest Posted January 26, 2016 Posted January 26, 2016 I think @@rin67630 refers to products_model... And, ummmmm, taken direct from the install SQL Yes thanks for the precision.
♥bruyndoncx Posted January 26, 2016 Posted January 26, 2016 Performance should only be a concern for really huge shops. With some thousand products I don't have to worry about the product indexing.lucky you :D KEEP CALM AND CARRY ON I do not use the responsive bootstrap version since i coded my responsive version earlier, but i have bought every 28d of code package to support burts effort and keep this forum alive (albeit more like on life support). So if you are still here ? What are you waiting for ?! Find the most frequent unique errors to fix: grep "PHP" php_error_log.txt | sed "s/^.* PHP/PHP/g" |grep "line" |sort | uniq -c | sort -r > counterrors.txt
Recommended Posts
Archived
This topic is now archived and is closed to further replies.