Hi Sphericus,
First of all I should tell you that we have introduced a specific SKU field for the next release. It will appear in the products_quantity table as follows:
CREATE TABLE products_quantity(
products_id int NOT NULL,
products_options varchar(128) NOT NULL,
products_quantity int NOT NULL,
products_sku varchar(255),
PRIMARY KEY (products_id, products_options)
);
You'll note that it's a varchar(255).
It will be accessible from the Admin App for modification and searching.
It might be best if you could map your existing product's SKU to this field if you can wait for the next release (it should be out in about 2 or 3 weeks).
But back to your question. With the exception of some validation failing in some places (I'm thinking of the Admin App) I do not know of any problems that you would encounter if you simply extended database field lengths. Changing types is more likely to cause problems.
Which field(s) are you thinking of extending? Perhaps it is a column we might want to extend as a default for KonaKart in future? It depends which column and whether it's still required given that we are introducing a specific products_sku column in the next release. Another potential problem is that we do try to remain compatible at the database level with osCommerce; so we would have to take that into account as well.
Regards,
John
