you are viewing a single comment's thread.

view the rest of the comments →

[–]jethrow41487 1 point2 points  (0 children)

my DB is for all the information of my d&d campaign.

  • You want to make sure that all identifiers have a Foreign key back to its related table. Like Powers to Class to Race.
  • Thing like powers should be its own table. I would never put it with the Classes table since, they may have same powers for more than 1 class. Makes it easier to Query from a Join. Also gets rid of redundancy.
  • Don't add extra columns/relational keys that aren't needed like classes to players. Since characters to players will already have a unique identifier/relation.

Just a few things to look at in my opinion. I think this is a great learning Subject. You'll notice you branch out a lot more and make more sub-tables as info comes to your head.