Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • To clarify, wouldn't keys be unique per item? I am not asking about SKUs or UniqueIDs. I'm talking about what Cloudsuite calls Product Codes, which are generic categorization codes applied to all items in certain categories. One product code might have 300 items that it's assigned to. Commented Jul 22, 2020 at 12:20
  • 1
    I'm assuming that the product codes are stored in a data structure separate from the item data structure. Then one field in the item data structure would reference (either by natural or surrogate key) the product codes data structure. So there are unique keys for items and unique keys for product codes. Alternatively, if one item can be assigned to more than one product code, you have a n:m relation, which is usually done with another table that only holds a reference to item and product code. Not sure if this clears it up for you, open a chat room if you want to discuss this further. Commented Jul 22, 2020 at 15:34