Database Design & Relational tables
Posted: Sat Nov 03, 2007 9:03 pm
hey everyone..
here is my question... when you are designing a relational database you have many different relations, is it better to assign a table to each 'type' of relation or to create a master relational table where all relations are defined.
For example:
rtbl_bananas_oranges
rtbl_bananas_pears
in contrast to:
rtbl_relations.. containing the columns
id(primarykey) .. object1_id.. object2_id
then go into object_id table and see what type it is..
....
the reason I ask is it gets tedious to keep track of an object ID's as well as its type ..
hopefully this makes sense, Im going crazy trying to figure out how to implement this..
Andrew
here is my question... when you are designing a relational database you have many different relations, is it better to assign a table to each 'type' of relation or to create a master relational table where all relations are defined.
For example:
rtbl_bananas_oranges
rtbl_bananas_pears
in contrast to:
rtbl_relations.. containing the columns
id(primarykey) .. object1_id.. object2_id
then go into object_id table and see what type it is..
....
the reason I ask is it gets tedious to keep track of an object ID's as well as its type ..
hopefully this makes sense, Im going crazy trying to figure out how to implement this..
Andrew