The whole idea behind using a Relational Database like MySQL is to not have redundant data.
there is no need to create a recordset and insert the redundant data into the items table when you can just use a Join Query when displaying the item info that pulls the data from the decor table.
the way this would work is to creat the decour table and the items table:
items:
itemID - primary key
itemName
itemPrice
itemDecorID - relates to the decors.decorID
etc....
decors
decorID - primary key
decorName
etc....
when you insert a new item, store the decorID value for the decor record that relates to the decors table.
then return the related information on the items display page using a join query:
SELCT *
FROM items
INNER JOIN decor ON items.itemDecorID = decors.decorID
this way the decor values are only defined once and can be used by as many different products as is needed.
it's certainly possible to do it the way you describe, but it is a terrible use of a relational database, and not a good practice.
read up on Data Normalization.
