Timeline for proper items db design mysql
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 22, 2022 at 19:24 | answer | added | Zibelas | timeline score: 1 | |
| Feb 22, 2022 at 16:12 | comment | added | sharpness | @Zibelas Thanks alot, could you perhaps give a visualization of what you mean? That would help me understand it better | |
| Feb 22, 2022 at 15:40 | comment | added | Zibelas | I would not even have a weapon table. One table for items and one column would be item type that defines the item. So you would still have a weapon table, but the user would refer to the item table of it. Your user weapon table would be changed to something like user item table and the weapon id to just the item id. Regardless if it is armor, weapon or tool, they would all fit. A mystery box is just an item, you would have a different table for just mystery box that specifies what kind of items it could contain | |
| Feb 22, 2022 at 15:29 | comment | added | sharpness | @Zibelas Yes however I would have to then make 3 tables (because I would also need to make a marketplace for exp ups and mystery boxes) because I have 3 different entities correct? I'm not sure if this is scalable friendly because everytime I introduce a new entity I'd have to create 3 tables (the entity itself, the user_.. table to store who has what and the marketplace for that entity) isn't there a simpler way? | |
| Feb 22, 2022 at 15:28 | comment | added | Zibelas | For a market place, you could make a new table that contains its own id, the player id and the weapon id, time listed, initial price, current price, etc | |
| S Feb 22, 2022 at 15:19 | review | First questions | |||
| Feb 23, 2022 at 11:09 | |||||
| S Feb 22, 2022 at 15:19 | history | asked | sharpness | CC BY-SA 4.0 |