example) building site there hierarchal structure so: territory -> gang -> wizard.
each 1 of these objects have close same columns (uid, wins, losses, hp etc..). users can create territories (different types of territories), gangs, , wizards. wizards can direct child of territory.
would make sense store 3 objects in single table different tables based on territory type?
no, (in opinion) wouldn't make sense that. different kinds of things, should stored in different tables.
if have aspect in common, make single table stores aspect appropriate foreign key relationships or correct entities. different kinds of things, should separated.
for example, territories cannot contain other territories, though can contain gangs. therefore, entities dissimilar in important ways, , should stored separately.
Comments
Post a Comment