I have 2 options for making a database. Which one could be more future proof and why?
Use-case: We have a shop with different products like 50. They are categorized into 6 different types of packaging (tubes, buckets, glass,...). Now we want to keep the relations between them so we know which product has which packaging so we could calculate the cost. (The cost fields are left behind in the designs). So we are looking to find which way could be the best to keep those relations clear and maintainable.
I think the first option is more maintainable than the second one whereas the second one is shorter in table design but you have to foresee each product seperately for their whole package.
So which one is better when the database gets bigger and could be more futureproof?