Hi,
At first it wasn't clear what you wanted. A second look provided a better insight.
I have a couple comments about your general design. It's going to get you in trouble.
I have two ideas for you:
ONE IDEA:
I might suggest making a separate item table. Make it's key or primary key item_id. Then make a separate table called item_size. It should have the columns.
item_id
size_seq
size_value
Now let's pretend some item, that has item_id of 55 comes in three sizes, 'Small', 'Medium', 'Large'. It will have one row in the item table and three rows in the item size table.
To select an item and it's available sizes, you select from the item_size table where item_id is the item you're displaying. So if you're displaying item_id 55, then
SELECT from ITEM_SIZE where item_id = '55'
That will get you three rows you can display in your <select> control.
IDEA TWO
As you can see, idea one doesn't allow for reuse or normalization of size data. No big deal neither does your design. You can make the sizes as a comma delimited string and store them in the item table itself. So the item table will have a column called
item_size: varchar255
One example of it's data might be " Small, Medium, Large " .Then after you get this data from the item table use can use php's split function to parce it into an array of sizes.
Varchars have a lot of overhead in mySQL so that's a con of idea two.
I'm actually a database designer... A table called size? Size what? Size of a shirt, size of coat, size of a shoe, size of a body? size of pickup truck?
Look at your columns, size_1, size_2, size_3,...size_5 NOW what are you going to do when you need size 6 or size 7??????
OK.. I'm not trying to be mean or anything. I did provide two design ideas for you.
Hope that helps!!!!
Gooood Luuuuccck
