-1

I have a game, and when an action is completed, I need to give the user an item. Items will each have a unique id. Each action is also stored and described in their own table. Each action will have its own reward, but I want an action to be able to give a varying amount of items, possibly none.

So far I have three approaches:

  1. Set three columns in each action row for item ids. The downsides is that it leaves redundant empty cells when the act doesn't give three items, but the upside is that it's simple.
  2. Set only one column that holds multiple values separated by spaces. It's a little less redundant than the above, but it requires a little more processing for separating the values.
  3. Make a new table for rewards and set each row with an item and an action that the item is for. Then, when the action is completed, it calls all rows with the action id from the rewards table. This has nearly zero redundancy but requires an extra query.

Which approach do you think would be the best to use?

Brian Tompsett - 汤莱恩
  • 5,753
  • 72
  • 57
  • 129
user1415803
  • 1
  • 1

1 Answers1

0

Have each item have an item id. Then each instance of an item will have a unique instance id. Then you can store multiple instances of the same item, the only difference between each instance is the instance id. e.g. a ball has an item ID of 5, a key has an item id of 6.

instance_id | item_id
1000          5
1001          5
1002          5
1023          6
1024          6
...
kevin628
  • 3,458
  • 3
  • 30
  • 44